Exporting tenant content to a deployment archive

You can export the tenant content from the source environment to a deployment archive. Later, you can import the archive into the target environment.

Before you begin

Only public content and objects belonging to the selected tenants are exported. Before you start an export, you must complete the assignment of tenancy to objects in the content store.

About this task

You can export the content in the following way:

  • Content that belongs to the selected tenants and public content
  • Content that belongs to the selected tenants only.
  • Public content only

User account information, including public user accounts, can be included or excluded from the export. When exporting tenants with public content included, the public user account information is also included by default. If you want to exclude the public account information from this type of export, use the CM.TENANTS_DEPLOYMENT_EXCLUDE_PUBLIC_USER_ACCOUNTS advanced setting. For more information, see Excluding public user account information when deploying public content.

When public content is excluded from the tenant export, and a tenant object has public ancestors, the public ancestors are included in the export so that the content references can be preserved in the target system. For example, in a situation where a data source connection belongs to a tenant, but the data source itself is public, the data source is exported.


  1. In IBM Cognos Administration, click the Multitenancy tab.
  2. Click the New export icon New export icon in the toolbar. The New Export wizard opens.
  3. Type a unique name and an optional description and screen tip for the deployment specification. Select the folder where you want to save it and click Next.
  4. In the Choose a deployment method page, select Select tenants. If applicable, select the Include user account information check box as well, and click Next.
  5. In the Select the tenants page, perform the following steps:
    1. Using the arrow icons, move the applicable tenants from the Available box to the Selected box. Ensure that correct tenant names are in the Selected box.
      Important: When you export public content only, the Selected box must be empty.
    2. If you want to include public content in the export, select the Include public content check box.
    3. Choose one of the Conflict resolution options. These options are used when the deployment archive is imported into the target environment. The Replace existing entries option replaces objects in the target environment with objects in the deployment archive. The Keep existing entries option merges objects from the deployment archive with associated objects in the target environment.
    4. Click Next.
  6. In the Specify a deployment archive page, under Deployment archive, select an existing deployment archive from the list, or type a new name to create one.

    If you are typing a new name for the deployment archive, do not use spaces in the name. If the name of the new deployment specification matches the name of an existing deployment archive, the characters _# are added to the end of the name, where # is a number such as 1.

  7. Under Encryption, click Set the encryption password, type the password, and click OK.
  8. Review the summary information and click Next. If you want to change the information, click Back and follow the instructions.
  9. Decide what to do with the deployment specification:
    1. To run it now or later, click Save and run once and click Finish. Specify the time and date for the run. Then, click Run. Review the run time and click OK.
    2. To schedule it at a recurring time, click Save and schedule and click Finish. Then, select frequency and start and end dates. Then click OK.
      Tip: To temporarily disable the schedule, select the Disable the schedule check box.
    3. To save it without scheduling or running, click Save only, and then click Finish.


The export deployment specification is saved in IBM Cognos Administration, on the Configuration tab, in Content Administration. From this location, you can update and run the deployment specification, and move the deployment archive to a different content store.