PS2010: Default ODC-Connection files not created in BI Center

Toutes les réponses

• dimanche 18 mars 2012 23:32

   

   
  

  0

  Well, you may have answered your own question, let's start there.

  Can you describe in some detail the "site backup and restore" method you used to move the config from Test to Prod?  I presume you mean backup the ProjectBICenter web site only and restore that web site (over the top?) of your existing BI center site?

  Hmm, yes, I do not think this would be a proper way to accomplish this.  But must confess have not tried it myself.  As you are experiencing, I would think this is fraught with issues.  Part of the BI Center web site creation sets up many linkages inside PWA and SharePoint configuration.  I would not be certain that all those linkages would be properly set for the new environment by using the standard SharePoint Backup / Restore tools.  These tools are not aware of PS 2010 requirements.

  I prefer to use the 5 database attach method to move entire PWA environments from Prod to Test or Test to Prod.  Even though this says "Upgrade" the method is sound for just promoting PS 2010 environments.  

  Database-attach full upgrade to Project Server 2010

   

  that will indeed capture all the customizations you have made to your BI center, and will also perform the linkage fix up needed when you move PWA from one environment to another.

  You will also have your "test" entries sure, but they are easily deleted.  The new production entries will be created on OLAP cube builds as you desire.

  Please try this method and let us know if this solves your issue.

   

  ---

  Thanks, Eric S. http://www.pcubed.com

  • Réponse
  • Citation

   
• lundi 19 mars 2012 09:07

   

   
  

  0

  Hi Eric,

  thanks for your reply. I guess you are right concerning the loss of the connections. We did the usual site backup and restore via PowerShell commands which then showed the strange behaviour. Since my post we rebuild the BI Center on productive system like described by Brian and manually recreated our development from the test environment in the productive environment (by saving the lists and libraries as templates and recreating the pages and web part connections) - a lot of work and not really comfortable, but at least now everythings works.

  Perhaps the 5 database attach upgrade method would do the trick, but that's no solution for us.

  As we are developing on our test environment we always have some items which are still in development whereas others have been approved for release. Doing a database copy would move the non-approved content too. Also we would overwrite our productive environment with its project sites and productive data. Doing first a copy from productive to test environment doesn't help as we would overwrite our developments (and we would need to freeze the systems for quite some time)... a vicious circle. Addionally, due to data security policies in the company, we are not allowed to keep productive user and project data in the test environment, so we created test users (about 300 users) and data - we don't want to rebuild this for every development.

  So for now, we will stick with documenting our releases and manually transferring the changes from test to prod.

  • Marqué comme réponse Gáski lundi 19 mars 2012 09:08
  •  
  • Réponse
  • Citation

   
• jeudi 26 avril 2012 20:10

   

   
  

  0

  One item you can try is another posting from Brian Smith - if you can afford to remove the Project BI Center, you can then re-create it anew...which will update all the folders and ODC files and such ...

  see this:  Project Server 2010: Business Intelligence Center – Behind the Scenes

  ---

  Thanks, Eric S. http://www.pcubed.com

  • Réponse
  • Citation

   
• vendredi 27 avril 2012 06:18

   

   
  

  0
  Yes, that's exactly what we did. We then repeated all our changes from the test system again on the productive environment. Not comfortable but working.
  • Réponse
  • Citation