Preloaded CI data model

Edit online

During product installation, a best practices–based Common Data Model and set of authorized CI classifications, promotion scopes, and naming rules are preloaded into the Maximo IT database. With the preloaded data model you can start importing and promoting actual CIs immediately, with no additional installations necessary. If you have any of these data model components installed already, in any version, the ones that you have will not be overwritten.

Before you can begin importing and managing your configuration items, you need a set of components related to the CI data model. In the past these components required that you install them using a number of different mechanisms:
  • The Integration Composer CI Types adapter or Deployer's Workbench to load the Common Data Model
  • The Deployer's Workbench to load the authorized CI classifications
  • The Deployer's Workbench to load promotion scopes
  • The Maximo® integration framework to load naming rules
The following table shows the advantage of having the CI data model preloaded. The first two columns show the previous, longer installation process; the third and fourth columns show the shorter, simplified process, where preloading the data model enables you to begin promoting your actual CIs almost immediately.
Installation process then Process steps then Installation process now Process steps now
Load the Common Data Model using Integration Composer
  1. Install Integration Composer and TADDM
  2. Create data sources and mapping from TADDM to Maximo IT
  3. Run the mapping
 Install the best practices–related CI data model, which includes Common Data Model and set of authorized CI classifications, promotion scopes, and naming rules CI data model components are loaded automatically when Maximo IT is installed for the first time
Activate the CI Types to import
  1. Log in to Maximo IT
  2. Activate the CI Types
 Activate the CI Types to import and you are ready to import your CIs
  1. Log in to Maximo IT
  2. Activate the CI Types (all actual CI classifications related to the authorized CI classifications that were preloaded from the best practices)
Load the authorized CI classifications and promotion scopes using Deployer's Workbench
  1. Install Deployer's Workbench
  2. Create and configure Deployer's Workbench project and copy best practices
  3. Export changes to server
    
Load the naming rules
  1. Log in to Maximo IT
  2. Configure the external system
  3. Configure the external service
  4. Import the naming rules XML file
    

For most users the preloaded components should suffice for getting started, and you can always make enhancements to them later, as detailed later in this topic. Typically you can start immediately managing actual CIs with the preloaded Common Data Model, as it has a robust set of classifications. Later you can import updates and make changes to the model with Deployer's Workbench, if your process requires it.

Common Data Model

The version of the Common Data Model that is preloaded is the version that is shipped with TADDM. If your Maximo IT environment is configured to use TADDM 7.2.1 or earlier, that version is compatible with the preloaded Common Data Model. However, if you want to customize the actual CI classes, you must make those modifications and extensions in TADDM and then import your changes into using Integration Composer an its CI Types adapter.

Maximo IT

In the event that you are using a later version of TADDM, or if you have customized your TADDM 7.2.1 version of the data model, it is recommended that you import that updated data model from TADDM using Integration Composer and the CI Types adapter, as shown in row 1 of the Installation process then columns in the preceding table. Doing so updates the existing, preloaded classes and adds the extra classes, thereby synchronizing the TADDM Common Data Model with the one preloaded into Maximo IT.

Likewise, if you install or upgrade to a post-7.2.1 version of TADDM, you should use the CI Types adapter to import the newer Common Data Model and synchronize it with your preloaded classes.

If you do already have a post-7.2.1 version of TADDM but choose to only import your discovered CI data using the Actual CI adapter, your discovered data will be imported but any authorized CI classes, promotion scopes, and relationship rules found in the post-7.2.1 TADDM Common Data Model will not appear in your existing authorized CI space.

Use the CI Types adapter per row 1 of the Installation process then columns in the preceding table if you have to import a Common Data Model from a post-7.2.1 version of TADDM. You can still copy any Common Data Model version from Maximo IT into Deployer's Workbench, where it saves it as a Deployer's Workbench project (which you can then convert into a library project). Creating such projects might be useful if, for example, you have development, preproduction, and production environments with different Common Data Model versions that you want to save.

The Common Data Model defines types of CIs as well as their attributes and relationships. After you have reviewed the CIs that have been discovered in your environment, and decided which types of CIs you want to manage and which attributes of each CI type you are interested in, you can create your authorized CI space based on this information.

Authorized CI classifications

The preloaded authorized CI classifications are identical to the Simple Best Practices defined in Deployer's Workbench. As soon as Maximo IT installation completes, you can begin importing your authorized CIs using these classifications, which are prefixed with CI. and can be found as children of the CIROOT class in the Classifications application.

These classifications define a default authorized CI space that is designed for someone who wants to start with a small set of managed CI Types and expand the list over time. The CI space includes Computer Systems, Application Servers, Business Applications, and Business Services, plus children of these classifications, such as IP address and Operating System for Computer Systems.

You can use these classifications to work with authorized CIs that you load with the Quick Configuration application.

If you are upgrading to Maximo IT, the CI classifications are not installed if a CIROOT classification or partial CI space already exists. Otherwise, the classifications are installed and the CI Root class is automatically set to CIROOT, if it has not already been set.

If you want to load your own set of authorized CI classifications, or make changes to the preloaded classifications, you must do so using Deployer's Workbench, as shown in row 3 of the Installation process then column in the preceding table.

Promotion scopes

Promotion scopes are templates that contain mappings of classifications between the actual and authorized CI classifications. Promotion scopes are the roadmaps used by Maximo IT to promote actual CIs to create authorized CIs.

When you promote one or more actual CIs of a particular type, you can choose one of these promotion scopes, or templates, to be used in the promotion process.

Promotion scopes are preloaded only if the following conditions are met:
  • There are no existing promotion scopes already defined
  • The Common Data Model classifications are already preloaded
  • The authorized CI classifications are already preloaded
In addition to using the preloaded promotion scopes, you can still use Deployer's Workbench to create and edit your own promotion scopes.

Naming Rules

Naming rules define a set of criteria to uniquely identify a CI. If you create an authorized CI and then later discover the same CI as an actual CI, you can use the naming rules to successfully find and link the authorized version of the CI to its matching actual CI. This link enables you to include the CI in audits and other comparisons.

Naming rules are preloaded only if the following conditions are met:
  • There are no existing naming rules already defined
  • The Common Data Model classifications are already preloaded
  • The authorized CI classifications are already preloaded

With the naming rules now preloaded, you do not have to set up the integration framework and use it to import the naming rules. You can begin linking authorized CIs to their matching actual CIs immediately, using the Link to Actual CIs action in the Configuration Items application.

You can also create your own naming rules and then use the integration framework to import them, as shown in row 4 of the Installation process then column in the preceding table. Or you can customize the preloaded naming rules by editing the naming rule XML file, at the following location, where the SCCD_HOME directory is typically c:\ibm\smp:

SCCD_HOME\maximo\tools\maximo\en\cci_content_pmp\NamingRuleSample.xml

The NamingRuleSample.xml file is unpacked to the administrative workstation during an advanced content payload installation.