Resources for IT Professionals >
Office PerformancePoint Server Forums
>
Monitoring and Analytics
>
Moving Monitoring server data through environments
Moving Monitoring server data through environments
- Hi - my question is about moving dashboards and associated items through different environments.
I have read the article: "Migrating Monitoring Server data from a test environment". My issues is with data sources. The production server for data sources is different than the test server for data sources. Changing the server name in a data source doesn't seem to work - I need to create a new data source after which everything relying on the data source is now broken.
What's the recommendation for server names with data sources to protect from moving through environments?
Thanks!
Craig
All Replies
- Hi Craig,
BI Report automation publsiher tool http://www.codeplex.com/bipublisher may assist your needs.
Thank you,
Sundar - MSFT
This posting is provided "AS IS" with no warranties, and confers no rights.- Proposed As Answer byDan English Saturday, October 10, 2009 10:33 AM
- I would agree with Sundar on this one, the BI Report Automation Publisher (BIRAP) tool on CodePlex, http://bipublisher.codeplex.com/, allows you to easily promote items between environments. With the last release they allow you to point to a workspace file (bswx) and specify the target server to publish items and you can modify SSRS, ProClarity, Excel, data sources on the fly when they get deployed to the other environments. You will have to make sure that the SSRS, ProClarity, Excel items already exist in the other environments, you will just be redirecting the pointers to these items, not actually promoting them like the PPS items. You can even add properties and values to the PPS items to limit the scope of the items that get published. It is a very useful tool and I would download and review the document that is included. There is a sample config file that you can look at for all of the different options also to help you out. You can configure multiple deployment types within a single config file, so you could have one to promote to UAT and then PROD also, or depending on how many dashboards you have you could break this out even further.
So for the data sources you can leave the names more generic and don't have to name them based on the server name. You can specify the target full qualified server name when you publish and promote to another environment within the dataSources tags.
_____________________________________________________
Please mark posts as answer or helpful when they are.
