PureEngage On-Premises

I have GAX with Pulse Plug In and Pulse Collectors on one server and also same on another server  as folows:
Server 01: GAX/PULSE/Collector
Server 02: GAX/PULSE/Collector
They both access and write to the same common Pulse Database.
If I save a Dashboard of Widgets on say Server 01 GAX Pulse, how can I open that saved Dashboard on Server 02 GAX Pulse. 

Both GAX Pulse on Server 01 and GAX Pulse on Server 02 can save their Dashboards to the same common Pulse Database so how can I then open any of these saved Dashboards from which ever GAX Instance I am on.

Cheers,
Geoff B.

Use latest version of Pulse component, where is no need to run Collector locally.

HTH!

Regards,
--Jakub--

Hi Jakub,
Thanks for the response but I am not sure how that helps with my question. Which is essentially how do I use any GAX Pulse instance to open Dashboards saved in the Pulse DB by different GAX Pulse instances.  At the moment a GAX Pulse instance can only see and open the Dashboards it saved in the Pulse DB. 
I curently have the latest version of Pulse installed (8.5.105.01).

Cheers,
GeoffB...

 

Hi Geoff,

    I'm facing the same issue. Have you solve this?

Cheers,
Wasakorn

Genesys support can confirm, but from our experience you should have a connection from each Gax application to each primary collector, and also a connection from each GAX instance to the other.

Hi Damien,
Thanks for the response.  We solved this a couple of months ago now.  We did have all the connections in place that you refer to. But with our multisite GAX / Pulse solution we could not save a Dashboard on one site and see and open it on another. Dashboards only saved and opened to the local site for each site.  Which means it was all working OK except for a centralised dashboard/widget save option. Genesys Tech suppprt advised that the only solution was to deploy WebDAV server at each site on all hosts with Pulse Collectors. But this is such a trek to set up and seems like such an overkill just to provide Pulse Dashboard/Widget centralised storage. Some after some trial and error we found that a simple Shared (DFS) directory set up works fine.  And you simply point at it in the "output-folder" option for each Collector. 
Example: transport-file / output-folder= "d:\Pulse\storage".

Hope this helps others.

Cheers,
Geoff B.

Thanks Geoff, we are facing the same issue, will give it a try.