Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Update Document on Subscriber Node

So I have a two node UCCX 7.0 HA cluster. Now it looks like when you upload things via the Web UI such as prompts and documents. This gets put into the SQL DB and then replicated over to the subscriber node.

I have a couple scripts that go out and update XML files stored in the Document Repository and also a few prompts in the Prompt Repository. This works fine but I’m noticing this only effects whatever the active node is for that call as it’s making a change to the file system and not to SQL so this does not get replicated over to the subscriber node.

So my question is would it be better to write these to some sort of network share, or is there a way to make the UCCX cluster know a file is being updated in the Document / Prompt repository and to replicate it to the subscriber node?

Thanks in advance.

~~~ Rate helpful posts Blog - http://tripplehelix.net
Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Super Bronze

Re: Update Document on Subscriber Node

Hi

The problem is that you aren't actually updating the repository - you're updating the cached copies of respository stuff on the local disk.

This causes several problems:

1) A failover will lose settigns/prompts other stuff, as you've noticed

2) If you patch, upgrade or restore the system you will probably lose stuff

3) You've no guarantee changes will stick properly

Instead of writing to the disk, use the correct steps:

Upload Prompt

Upload Document

etc.

To get these to work, you have to use the get user/authenticate user steps with a User variable to authenticate to the repository as a suitable user, and then use the Upload step referenceing the authenticated user variable.

Regards

Aaron

Please rate helpful posts...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
1 REPLY
Super Bronze

Re: Update Document on Subscriber Node

Hi

The problem is that you aren't actually updating the repository - you're updating the cached copies of respository stuff on the local disk.

This causes several problems:

1) A failover will lose settigns/prompts other stuff, as you've noticed

2) If you patch, upgrade or restore the system you will probably lose stuff

3) You've no guarantee changes will stick properly

Instead of writing to the disk, use the correct steps:

Upload Prompt

Upload Document

etc.

To get these to work, you have to use the get user/authenticate user steps with a User variable to authenticate to the repository as a suitable user, and then use the Upload step referenceing the authenticated user variable.

Regards

Aaron

Please rate helpful posts...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
294
Views
0
Helpful
1
Replies