Outside of a Proof of Concept, any environment where an application like Cognos is installed, it is wise to have at least two instances

, one for development and one for production. In these cases you will have to deploy reports and other content from development to production and vice-versa. There are multiple ways this can be done depending on your needs. Business Case: et!s say you want to refresh development environment with the current version of production. Database Level Deployment: "ou can use this method when deploying the entire content store.

• #top cognos services in both development and production environments.
• $ave your %&' make a copy of the production cognos content store schema. • (estore the copy in your development environment. • Open cognos configuration in development environment • )nder *%ata 'ccess* section, add new content store database, and enter the details of the schema copy that you +ust created. • #tart cognos services in both environments. • ,ow your development environment will have all the content of your production environment including access rights and user information. Deployment through the Cognos Portal: This is the recommended and preferred method and works for all re-uirements. "ou will be using the deployment wi.ard to do this/ • ogin to your production environment and launch *I&0 Cognos 'dministration* from Cognos Portal.

• Click on *Configuration* tab and *Content 'dministration* in the left pane. • 1rom the toolbar item, click *,ew 23port*

• 2nter a name of the e3port and a description 4optional5 and click ,e3t

2nter a password/ . select the desired deployment method/ "ou can choose to e3port the entire content store or only selected folders or packages. • If you pick the entire content store. • If you are e3porting the entire content store.e3t.• . This will be the file name when the e3port completes. entire a name for the archive. cognos re-uires you to encrypt the archive using a password. you can optionally include user account information to have the same security settings as in the production environment • In the ne3t step.

• 1ind the .ow your content from production environment will be imported. • Copy this file to the development environment.• 'fter this step. save and run the e3port. • Check the activities in I&0 Cognos 'dministration to make sure e3port runs and completes successfully.ip file with the name you entered in the 23port wi. • . . • Create a *. • ogin to the production cognos server and navigate to/ 6cognos install directory78deployment folder. • 9o to *Current 'ctivities* in the *#tatus* tab of *I&0 Cognos 'dministration* and make sure the import completes successfully.ew Import* from the toolbar icon • #elect the archive that you +ust copied over and click ne3t. • #elect the desired settings and click 1inish. review the settings. • .ow login to the %evelopment environment and navigate to Content 'dministration.ard.