Data imported into BMC.SIM

This section describes factors that affect the data imported into the BMC.SIM dataset.

If the ContinueOnSkip parameter of the sim2cmbd.conf file is set to T (true), data will be imported in BMC.SIM, even if some of the data cannot be imported. If the parameter is set to F (false), then if some of the data cannot be imported, no data is imported. In both cases, the data that cannot be imported is sent to the output file with a message describing the reason for the failure to import.

When Diary (Notes in SIM) are imported from SIM to CMDB, the Notes slot is not imported as multiple entries. All entries are concatenated into a single string and imported as one entry.

 Weak relationships

If the relationship is a weak relationship, its destination member, called the weak member, cannot exist without its source member, called the strong member. A weak relationship creates a logical composite object consisting of both member CIs.

In BMC CMDB, the strong members are the CIs derived from BMC_System class and the weak members are the CIs derived from BMC_SystemComponent or BMC_SystemService. An example of BMC_System class is BMC_ComputerSystem, and an example of BMC_SystemComponent class is BMC_FileSystem. Normally, since a FileSystem cannot exist without a ComputerSystem, sim2cmdb creates a weak relationship between them. So, an instance of BMC_HostedSystemComponents is created, which is a logical composite object consisting of both member CIs.

For CIs whose class is derived from BMC_SystemComponent or BMC_SystemService, BMC recommends that you set a value in the SystemName slot so that a weak relationship can be created when sim2cmdb runs.

If a BMC_SystemComponent or BMC_SystemService object has a value in the SystemName slot, sim2cmdb attempts to create the following two weak relationships during the import process:

Source (Strong member)

Weak relationship

Destination (Weak member)

BMC_System

BMC_HostedSystemComponents

BMC_SystemComponent

BMC_System

BMC_ HostedService

BMC_SystemService

Possible Import Results

The following table lists possible import results for specific circumstances:

Possible import results

Condition

Result

A relationship has only one endpoint in BMC CMDB.

  • The relationship is not created in BMC CMDB.
  • The endpoint CI in BMC CMDB is not affected
  • If ContinueOnSkip is true, the relationship is not imported
  • If ContinueOnSkip is false, none of the data is imported

A CI belongs to an abstract class in the cell

  • The CI and any relationships to the CI are not imported into BMC CMDB
  • The CI and relationships are listed in the output file
  • If ContinueOnSkip is true, the CI and relationships are not imported
  • If ContinueOnSkip is false, none of the data is imported

A weak CI points to a strong CI that does not exist in BMC CMDB

  • The weak relationship is not created
  • The no-strong member message is listed in the output file
  • If ContinueOnSkip is true, the CI without a strong relationship is imported, but the weak relationship is not created
  • If ContinueOnSkip is false, none of the data is imported

A value for HomeCellAliases is not found for a CI

  • The CI is not imported into BMC CMDB
  • The not found message is written to the output file
  • If ContinueOnSkip is true, the CI is not imported
  • If ContinueOnSkip is false, none of the data is imported

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*