Skip to content

IBM Cognos - Process Steps

Export

Export content from the content store to an archive file in the deployment directory within your Cognos home.

NameTypeDescriptionRequired
Archive NameStringThe name of the export archive. Do not include the .zip file extension.Yes
Cognos Java Library DirectoryStringThe Cognos java library directory. The directory must contain the required JAR files, including cognosClient.jar and cognos-axis.jar. For example: C:\Program Files\IBM\cognos\c10_64\sdk\java\libYes
Deployment SpecStringSpecify the name of an export deployment specification. If this specification doesnt exist on the Cognos server, it will be created.Yes
Export ContentStringSpecify the search path of the content to export. For example: /content/folder/[@name=Samples]. The search path is displayed in the properties of any file or folder in the Cognos web application.Yes
Gateway URLStringThe URL of the Cognos gateway to use to communicate to the dispatcher. Alternately, specify the URL of the dispatcher itself. For example: http://localhost:9300/p2pd/servlet/dispatchYes
IBM Cognos ReportNet Home (CRN_HOME)StringThe location where Cognos is installed. Do not include a trailing forward slash.Yes
NamespaceStringThe user namespace. The user namespace is displayed on the user preferences page of the Cognos web application.Yes
Overwrite Deployment Spec.BooleanCheck this box to overwrite the deployment specification if it exists in the content store.No
Parent DirectoryStringProvide the search path of the directory that your new or existing deployment specification exists under. This will default to the root directory /adminFolder. For example the path /adminFolder/adminFolder[@name=Exports] will specify the Exports directory under the adminFolder root directory.No
PasswordPasswordThe password of the administrator user. (default: ${p:resource/crnPassword})Yes
UserIDStringAn administrator user ID that is capable of importing/exporting content.Yes

Import

Import content from an archive to the Cognos content store.

NameTypeDescriptionRequired
Archive NameStringThe name of the archive to import. Do not include the .zip file extension.Yes
Cognos Java Library DirectoryStringThe Cognos java library directory. The directory must contain the required JAR files, including cognosClient.jar and cognos-axis.jar. For example: C:\Program Files\IBM\cognos\c10_64\sdk\java\libYes
Deployment SpecStringSpecify the name of an import deployment specification. If this specification doesnt exist on the Cognos server, it will be created.Yes
Gateway URLStringThe URL of the Cognos gateway to use to communicate to the dispatcher. Alternately, specify the URL of the dispatcher itself. For example: http://localhost:9300/p2pd/servlet/dispatchYes
IBM Cognos ReportNet Home (CRN_HOME)StringThe location where Cognos is installed. Do not include a trailing forward slash.Yes
NamespaceStringThe user namespace. The user namespace is displayed on the user preferences page of the Cognos web application. on the user preferences page.Yes
Overwrite Deployment Spec.BooleanCheck this box to overwrite the deployment specification if it exists in the content store.No
Parent DirectoryStringProvide the search path of the directory that your new or existing deployment specification exists under. This will default to the root directory /adminFolder. For example the path /adminFolder/adminFolder[@name=Imports] will specify the Imports directory under the adminFolder root directory.No
PasswordPasswordThe password of the administrator user. (default: ${p:resource/crnPassword})Yes
Target DirectoryStringIf this is a new deployment specification, provide the search path of the directory in the Cognos content store where your artifact will be deployed.No
UserIDStringAn administrator user ID that is capable of importing/exporting content.Yes