I'm installing UCCE 7.0 side B where I'm deploying a Secondary AW Distributor in the same AW Primary site.
In order to provide WebView db backup I'm going to install the Webview DB also on the Secondary AW.
This will be the scenario:
AW Primary + WVDB + WV Server
AW Secondary + WVDB + WV Server
The two WebView Server points to the primary WVDB. If it fails I'll let the AWDB servers point to the secondary WV DB.
I know that the secondary WV DB should be keept manually updated.
Is this configuration supported?
Ok, now I understand a bit better.
You're right for the agent real-time statistics - you do need to identify a Distributor site name in the Peripheral config to get that data.
If your AWs are on the same LAN, then it's just fine to set up a PRI/SEC as you describe so that you are only entering one Distributor Site name in the Peripheral config.
If the AWs are separated by a WAN, then I would just have them as two separate sites and put both of them in as Distributor sites in the Peripheral config.
(again, this config was a way to set a specific site name to receive agent real-time data to save on WAN bandwidth so that every AW didn't get real-time data for every agent at every site. Valuable for TDM ACDs that serve agents at a single site - less of a 'common sense' approach for UCCE since agents are no longer expressly tied to ACD copper circuits at a 'site'.)
As far as Webview goes, sure add a second webview server on the second AW âServer Bâ, just point the WVDB on that server to âServer Aâ in ICM setup. This will assure that any templates authored on either server will be available from either server. Just protect this single WVDB by a normal backup process as you would with any other valuable Db.
You said, âDid you never install AW prim + HDS + WV server & AW sec + HDS + WV Serverâ. Yes, but the far majority of the time, I have only a single WVDB and it's on âServer Aâ.
The obvious next question is, âbut what if Server A diesâ. Yea, well so you lose your custom templates until the WVDB can be restored but Webview itself will still be functioning on Server B. My earlier post does speak to setting up SQL replication across two WVDBs but that is a pain to manage and if it's done incorrectly can destroy the data in both. I hesitate to do this (and in fact have only been pressured to do it once). I am fixing a site this week that has two WVDBs on two AWs so there are some templates in A and some in B which creates all kinds of confusion for day to day reporting.
The real solution? Wait patiently for Cisco Intelligence Suite in v7.5. ;-)