Multi-Site CCPulse Files

[ChrisRW]

I work in an environment where we support two sites. Currently we have 2 shared drives (1 for each site. Neither sites employees can access the shared drive for the other site, very few people have access to both drives, I am one of the lucky few) on which we store CCPulse Workspace files (actions/thresholds etc...) We've recently installed SharePoint and I want to try to leverage this new tool so that we can migrate both of the, often different versions, from the separate shared drives on the network to a SharePoint site and have CCPulse pull the workspace files from the SharePoint site. It seems that I'm not able to do this because I've made what I think are the appropriate changes to our CME but I get error messages when I try to load CCPulse. Any thoughts?

I'd really like to only have to maintain a single file rather than 2, and more importantly I'd really like to make sure that both sites are looking at the same reporting/data.

[fnunezsa]

[quote]I get error messages when I try to load CCPulse[/quote]

Would you please post the error messages you're getting?

[Adam G]

Assuming you can access one Network Server from the other (even if your Users can't) and if you're not 24 hours, you could run a Batch File overnight (via WINTEL/AT or SOLARIS/CRON) to make sure all of your .stg's are copied/overwritten from the "main" to the "secondary" location Network Folder.

You'd still need a separate instance of CCP for each location but at least you won't waste time manually copying/overwriting files constantly...

HTH?

[Kevin S]

Concur with fnunezsa  and Tony:
1 - What are the error messages you are getting?
2 - We utilize the "master/copy" scenario that Tony described - we have a Master copy in one location, and use a batch file/script to update the remote copy. We had to do this because of speed across our WAN - it was taking 5+ minutes for CC Pulse in the remote site to load the workspace from the Master location. We kick the script off every 12 hours. The workfiles at the remote location are read-only except for the account that runs the script.

[ChrisRW]

Thank you all. This does help.

[Adam G]

Some notes to go with this:

CCPulse+ can slow down for a lot of reasons - here are some of the main ones:

CCP registering with Config Server across a WAN.  Try to use LAN Config Proxies where possible.
CCP registering with a StatServer across a WAN.  Try to install a LAN/local StatServer for your local CCP, where possible.
CCP opens a Workspace or View on "opening".  Try to avoid this since the combination of CCP pulling in all of the .stg file data *and* trying to pull in Stats across a LAN/WAN StatServer [i]at the same time [/i]can really slow things down.  If you can, have Users Open CCP first (which authenticates and then pulls in the .stg Data), then manually select the Workspace they want to use (which registers and pulls in the StatServer data) - that way you split up the initial load.

HTH?

TT