Moving Frameworks from a test to prod environment

[terry_stjean]

I am looking for advice on moving Framework changes from a test to production environment.
We want to develop the Framework on our test server and publish the change to a test Content store.
How would we move the Framework changes to a production server and publish the package to the Production Content store.
How best can we automate this process. I don't want someone manually copying files and publishing packages if possible.

Terry

[rockytopmark]

Best Practice is to do it the way you are doing... publishing in Test, promoting to Prod.

What I have done in the past, is set the deployment folder in both environments to the same physical folder.  This way there is no file copying required.  Your exports are created in Test and delivered to the folder, which Prod is also using, so the Imports are available immediately in Prod.

Now, create a job on Prod, that runs the Import on the desired frequency.  Any updates to the Deployment(s) will be picked up with the next run of the scheduled import job.

[terry_stjean]

If I wanted to migrate a single report, would I move it to a "Transfer" folder, export it from test server, copy export file to Prod server, import to Prod into a "Transfer" folder and then move it to the appropriate folder?

What if I only want to update the package in Prod with changes from Test package without moving any of the reports in the Test package.

Terry

[rockytopmark]

Then I would struction Cognos Connection to have Package folders empty and the reports in manually created folder structure, created to your organizational preference.

Common misconception is that reports need to reside within their associated package folder in Cognos Connection... this simply is not true.

[terry_stjean]

Then you would hide the Package folders?

Terry

[rockytopmark]

If desired, yes.  Not necessary though.