Import Content Packs

Administration > Setup and Maintenance > Content Packs

Alternatively, click Content Packs.

Then click Import Content Pack Definitions and Content.

The content of a content pack is either predefined or custom depending on how the content pack was exported. When importing a content pack, you generally overwrite existing data and add new data. However, if you are importing a predefined content pack, only predefined content is overwritten with new data. Customized content is left untouched. Importing a custom content pack always overwrites existing data.

Content packs are usually in ZIP format. However, XML format content packs can also be imported. Content Packs imported through the Content Manager UI must be accessible by the system on which the OMi browser is running.

You can preview the import operation without actually importing any of the listed data. The Preview feature displays all artifacts in the selected content pack definition, including fulfilled and missing dependencies to other Content Packs in an expandable tree.

The preview also shows whether the Content Pack to be imported is predefined or custom.

When it is predefined, there is a check mark next to the term Predefined. When it is custom, no check mark is displayed.

When you import a content pack, existing items with the same ID are generally overwritten. If you are importing a predefined content pack, only predefined content is overwritten with new data. Customized content is left untouched. Importing a custom content pack always overwrites existing data.

Unresolved references in the imported definition (for example, to unknown CI types) are not allowed.

1. In the Import Content Pack dialog box, click Browse and locate the content pack you want to import.

   The default location for content packs is:

   <OMi_HOME>/conf/opr/content/<locale>

   In a distributed deployment, this directory is located on the data processing server.

   Note By default, OMi looks for content packs in the file system on the system where you start the browser session. If the browser is running on a remote system, you must navigate to the file system of the OMi host.

2. Optional. You can click Preview to list the artifacts that are included in the selected Content Pack and any required dependencies and missing dependencies.

   • Contained artifacts (grouped by type)

   • Fulfilled dependencies to other Content Packs

   • Missing dependencies to other Content Packs

   This does not run an import, no changes are committed to OMi.

   The preview also shows whether the Content Pack to be imported is predefined or custom.

   When it is predefined, there is a check mark next to the term Predefined. When it is custom, no check mark is displayed.

3. Select Import to start the import or test operation.

   Note It is not possible to start an import if an import is already running.