Define Content Packs

Administration > Setup and Maintenance > Content Packs

Alternatively, click Content Packs.

A content pack definition contains a list of the data and the relationships between them to be included in a content pack which you can export to another OMi installation.

Creating a content pack is a two-step process. First you create the content pack definition in the Content Manager, and then you use the definition to export selected content to a content pack file.

1. Open Users, Groups, and Roles:

   Administration > Users > Users, Groups, and Roles

   Alternatively, click Users, Groups, and Roles.

2. Create or edit an existing role. For task information, see How to Create Roles.

3. In Permissions, select the Setup category.

4. Select Content Packs and assign the permissions as needed. For more information, see Users, Groups, and Roles.

1. Open the Content Packs page:

   Administration > Setup and Maintenance > Content Packs

   • To create a new content pack definition, click  New Item. The Create New Content Pack Definition wizard opens.

   • To edit an existing content pack definition, select it and click  Edit Item. The Edit Content Pack Definition dialog box opens.

2. In the General page of the wizard, or the General tab of the dialog box, enter information in the Display Name, Name, and Version fields.

   • The Name and Version combination must be unique.

   • The Name field is limited to a maximum length of 255 characters. The first character must be a letter (A-Z, a-z) or an underscore (_). All other characters may be letters, numbers, or underscores. No leading or trailing spaces are allowed. When you export the content pack, the contents of the Name field is the default file name for the file, with OMi Content Pack - as a prefix.

   • The Display Name is the name displayed in the Content Pack Definitions list, and need not be unique. It is limited to a maximum length of 255 characters.

   • The Version is a free text field. Use Version in combination with Display Name to manage version control of your content packs.

3. Continue to follow the wizard pages or edit the tabs of the dialog box to select content, set dependencies, and view a summary of your content pack definition's contents and any problems found.

It is not recommended to have referenced content within your own Content Pack, because this is an indication that the ownership of such content is not clear. If you are the owner, include the referenced content into your Content Pack Definition. A Content Pack cannot be exported as Predefined (vs. normal export) if it contains content that is not explicitly included. This restriction is there to ensure that such content always has a dedicated owner.

1. Make sure that the Enable Content Pack development settings is enabled:

   Caution It is not recommended to create new versions of predefined Content Packs that you are not responsible for as this may result in upgrade errors in the future.

   1. Open the Infrastructure Settings:

      Administration > Setup and Maintenance > Infrastructure Settings

      Alternatively, click Infrastructure Settings.

   2. Select Applications and from the Applications drop-down list, select Operations Management.

   3. From the Operations Management - Content Manager Settings pane, set Enable Content Pack development to true.

2. Open the Content Packs page:

   Administration > Setup and Maintenance > Content Packs

   Select the predefined content pack definition for which you want to create a new version.

3. Click  Duplicate Item to open the Create New Content Pack Definition Version dialog box.

4. Change the version number of the content pack and click OK.

   The new version of this content pack is saved as a custom content pack.

5. Open the new version of the content pack definition, make the changes that you need, and save the changes.

1. Open your Content Pack Definition for editing in the Content Manager and select the Dependencies tab.
2. Inspect all content artifacts printed in normal font. Select the Content Pack that is the owner of the referenced artifact and click the  Set Dependency toolbar button or shortcut menu to set a dependency to it. The goal is to have no content artifacts displayed in normal font in the Dependencies tab.

Before you publish a newly developed content pack, you should make the following checks on a system where all available Content Packs (at least all OOTB Content Packs) plus your Content Pack is imported.

These checks help you to have clear ownerships of the content artifacts, which helps in upgrade scenarios and in developing new Content Packs.

• Problems Found by Content Manager

  Select your Content Pack Definition in the Content Manager and check if there is a Problems Found panel reported at the bottom of the Details pane.

  This section typically reports inconsistencies between your Content Pack Definition and the available content. You must solve the reported problems before exporting the Content Pack. For example, your Content Pack Definition references content or dependent content that does not exist in the system. You must either remove the referenced content or dependency from your Content Pack Definition or make sure that the referenced content dependency is "installed".

• Check for Content in other Content Packs

  Open your Content Pack Definition for editing in the Content Manager and select the Content tab. Check if there is a section titled Content in other Content Packs (bottom of Included Content pane).

  In the Content in other Content Packs section, inspect each content artifact and decide if you are really the owner of this content artifact. If you are not the owner, exclude the content artifact from your Content Pack Definition and set a dependency to the owning Content Pack. Otherwise, contact the owner of the other Content Packs and request that they exclude the content artifact from their Content Pack Definition.

  To exclude a content artifact from a content pack, select the artifact and click the  Exclude toolbar button or shortcut menu.

• Check for Referenced Content included in This Content Pack

  Select your Content Pack Definition in the Content Manager and check if there is a Referenced Content included in This Content Pack panel reported in the Details pane.

  It is not recommended to have referenced content within your own Content Pack because this is an indication that the ownership of such content is not clear. If you are the owner, include the referenced content into your Content Pack Definition. Select the referenced content in the Included Content pane and click the  Include Referenced Content toolbar button or shortcut menu.

  If you are not the owner, set a dependency to the Content Pack Definition that owns the referenced content. For details, see How to Set a Dependency.

The Content Pack Definitions pane displays a list of all the content pack definitions that are available for your environment.

UI elements are listed in the following table.

UI Elements	Description
	Refresh. Refreshes the contents of the displayed list. Use if new content becomes available while you are working or you uploaded new contents (for example, from the command-line interface).
	New Item. Opens the Create New Content Pack Definition wizard. For details about the wizard, see How to Create and Edit Content Pack Definitions.
	Create a New Version of the Selected Content Pack Definition. Opens the Create New Content Pack Definition Version dialog box from which you can create a new version of the selected content pack definition. Alternatively, double-click a section in the Details pane to open the appropriate tab in the Create New Content Pack Definition Version dialog box or the Content Pack Definition in the Definitions pane (not valid for content packs that are not predefined). For details, see How to Create a New Version of a Predefined Content Pack Definition.
	Edit Item. Opens the Edit Content Pack Definition dialog box, which enables to you edit the name, version, and description, content to be included, and dependencies for the selected content pack. This dialog box presents the same screens as the Create New Content Pack Definition wizard, but in tab format. Alternatively, double-click a section in the Details pane to open the appropriate tab in the Edit Content Pack Definition dialog box or the Content Pack Definition in the Definitions pane (not valid for content packs that are not predefined). For details, see How to Create and Edit Content Pack Definitions.
	Delete Item. Deletes the selected content pack definition (but not referenced content such as indicators and KPIs) from the list of definitions displayed.
	Import Content Pack Definitions and Content. Opens the Import Content Pack dialog box, which enables you to specify or browse to a file that contains the definition details for import. For details, see Import Content Packs.
	Export Content Pack Definitions and Content. Opens the Select Location for Download dialog box, which enables you to specify or browse to a file location where you want to export the definition details. Export Content Pack Definitions and Content (Predefined). Opens the Select Location for Download dialog box, which enables you to specify or browse to a file location where you want to export the definition details as a predefined content pack.

The Details pane provides high-level information concerning the properties of the selected content pack definition and a short summary of the content pack definition's content and any problems found.

User interface elements are described below:

This wizard page enables you to define the display name, name, version and description of a new content package.

This wizard page enables you to select the content to be included in a new content pack definition.

UI Elements (A-Z)	Description
	Refresh: Refreshes the contents of the displayed list. Use if new content becomes available while you are working or you have uploaded new contents (for example, from the command-line interface).
	Add to Included Content: Adds the selected item(s) to the list of included content. If included content has already been included in another content pack, it is listed in the Content in Other Content Packs pane, and can safely be excluded from the content pack you are creating. It is not necessary to include content in multiple content packs. Tip: Selecting a CI type automatically selects all assigned content of the CI type and also all assigned content for child CI types. Selecting specific content, such as an individual indicator or KPI, automatically selects the reference to the CI type to which the content is related.
	Expand Selection: Expands the Available Content or Included Content list to display items belonging to the selected group.
	Collapse Others: Collapses all open branches except for the selected branch.
	Expand: Expands the Filter pane to display available filters.
	Collapse: Collapses the Filter pane.
	Expands the selected folder.
	Collapses the selected folder.
	Include Referenced Content: Adds the selected item(s) to the list of included content.
	Exclude: Removes the selected item(s) from the list of included content.
	Exclude All: Removes all items from the list of included content.
	Display All Selected Content Pack Items: Expands the Included Content list to display all items selected for inclusion in the content pack.
	Search Content: Use the Search field to find the content in the Available Content or Included Content pane. Enter a search string in the Search box and click  Search Content. The first content to match the specified string is highlighted. If that content is not initially visible, the tree expands to display it. To find the next occurrence of content matching the specified string, click again. The search string must be at least three characters long. Searching is automatically started as soon as the third character is entered and the first match is highlighted. This prerequisite avoids searches being started too often and resources being blocked. Names with less than three characters can be found by clicking .
Available Content	Hierarchical list representing the available content in your IT environment. Tip: To include content in a content pack definition, drag it from the Available Content pane to the Included Content pane or select it and click the Add to Included Content button. OMi warns you if content already exists in other content packs when you perform an include operation. Color coding: Folder with no content: gray Selected content: bold Referenced content: italic Dependent content pack definition with version number: blue
Filter: Show only CI types with assigned content	Filters the CI Types tree to display only CI types that have content assigned to them. Note Filters can be combined.
Filter: Hide Predefined Content	Filters the CI Types tree to display only the content that is not marked as Predefined. During Content Pack development, only custom content is usually included in a new Content Pack. This filter enables you to hide all predefined content. Note Filters can be combined.
Filter: Hide Content already included in other Content Packs	Filters the CI Types tree to display only content that is not included in another Content Pack. It is not usually necessary to have the same content in multiple Content Packs. This filter enables you to hide all content that is already included in another Content Pack. Note Filters can be combined.
Included Content	List of content selected for inclusion in a content pack, along with any dependent content. Tip: To exclude an item, select an item (or group of items) and select the Exclude button. Color coding: Folder with no content: gray Selected content: bold Referenced content: italic Dependent content pack definition with version number: blue
Content in Other Content Packs	If content selected for inclusion is included in other content packs, it is listed here to indicate that it can be removed from this content pack. It is not necessary to include the same content in multiple content packs, and the recommended practice is not to do so.

This wizard page enables you to set dependencies on dependent content that is included in more than one other content pack.

UI Elements	Description
	Refresh. Refreshes the contents of the displayed list of dependencies. Use if new content becomes available while you are working or you have uploaded new contents (for example, from the command-line interface).
	Set Dependency. If referenced content is also included in other content pack definitions, a message indicating this is displayed, and one of these was automatically set for you. To specify a different content pack definition for this content, use the Set Dependency action. To include the referenced content in your content pack definition, use the Add to Included Content action. The dependent content in the referenced content pack is displayed in bold, indicating that dependency has been set on it.
	Add to Included Content. Adds the selected dependent content to the list of content included in this content pack.
<Color coding>	Color coding: Internally referenced content: normal Content included in the currently selected content pack definition: bold Content included in another content pack definition: gray
<Version dropdown box>	If there is more than one version of a content pack that could be specified for referenced content, the version dropdown box becomes active and displays the selected content pack version. You can select an alternative version and set the dependency to it.

This wizard page enables you to see summary information regarding the content, dependencies, and any problems found in a new content pack definition.

User interface elements are described in the table below.

The Summary Page displays a summary of the selected content pack definition's contents, divided into the following subsections. Each subsection contains a list of content and for each item in the list, the following information is displayed:

• Total number of artifacts
• Number of predefined artifacts
• Number of Predefined (Customized) artifacts
• Number of custom artifacts

Expanding the content group displays the artifacts contained within that group, the CI Type of the artifact (where applicable), and the origin of the artifact (Predefined, Predefined (Customized), Custom).

For example, indicators, mapping rules, and indicators, also show CI type, that is, the type of configuration item to which the indicator is assigned (for example: Application, Host, or Oracle System).

Make sure you perform the Include action at the correct level in the configuration item type hierarchy so that all elements assigned to the selected configuration item type (and any children) are included at the same time.

Content pack contains references to configuration items that do not exist on the target system. Make sure that the Override and Create options are correctly specified before starting the import.