Creating CIs in BMC Atrium Explorer
In BMC Atrium Configuration Management Database (BMC Atrium CMDB), most configuration items (CIs) are created by discovery applications, such as BMC Atrium Discovery and Dependency Mapping. However, you can use BMC Atrium Explorer to create CIs manually.
For example, you might have installed a new computer system, and you do not want to wait until the next scheduled discovery process to include that CI in BMC Atrium CMDB.
You cannot directly create CIs in the BMC Asset dataset, which is reserved for production use. To add new CIs in the BMC Asset dataset, you must create the CIs in your Sandbox dataset and promote them. Remember that Promote Sandbox Changes works only with the Sandbox dataset.
If you manually create CIs in the CMDB, remember to populate key attributes with appropriate values so that the CI can be identified against discovery data. Define conventions for manually creating CIs, including the classes to populate, the attributes to populate, and the format of attribute values.
For example, your company's conventions for manually creating CIs might include the following:
- Calbro only manually creates Computer System CIs. Calbro never manually creates CIs for components such as Operating System or Diskdrive.
- Manually-created Computer System CIs must populate the HostName and Domain, or they must populate the Serial Number as configured on the Computer System.
Before you begin
Before you create an instance, you must know both the name of the class that you are instantiating and the namespace in which it resides. The classes provided with BMC Atrium CMDB in the Common Data Model (such as
BMC_ComputerSystem ) reside in the BMC.CORE namespace. Classes provided with other integrating BMC products reside in other namespaces, as should the classes that you create.
If you do not know the namespace for the class that you are instantiating, contact a BMC Atrium CMDB administrator. For more information about classes, see the BMC Atrium CMDB Data Model Help.
You must be a member of a group with either the CMDB Data Change role or the CMDB Data Change All role to create instances in BMC Atrium CMDB. For more information about roles, see BMC Atrium Core permission roles within applications.
To create a CI
- In BMC Atrium Explorer, open a new or existing view for an editable dataset (for example, the Sandbox).
You cannot directly create a CI in the BMC ASSET view. When you drag a CI class to a BMC Asset view, you are prompted to convert the view to a Sandbox view. Follow the instructions in the dialog box to create the CI in an open Sandbox view.
- From the Classes section of the navigation pane, drag a CI class to the display pane.
A new CI of the selected type is created in the Sandbox dataset (indicated by the star icon).
When you drag a CI class to a new view, the CI is created and its name is a combination of the class name and the number one. The number is incremented by one for each additional CI that is created from the same class. However, if you close BMC Atrium Explorer, reopen it, open the same view, and create another CI of the same class, the third CI of this class is created and its name is a combination of the class name and the number one. The numbering is reset when you close and reopen the BMC Atrium Explorer. For example, if you drag the
BMC_ComputerSystemclass to a new view, the first CI is created with
BMC_ComputerSystem_1as its name. When you create a second CI of the
BMC_ComputerSystemclass, the second CI is created with
BMC_ComputerSystem_2as its name. Now, if you close BMC Atrium Explorer, reopen it, open the same view, and create another CI of the
BMC_ComputerSystemclass, the third CI is created with
BMC_ComputerSystem_1as its name.
- Click the icon representing the CI, and select Edit.
- If the BMC Remedy ITSM applications are installed (7.6.03 or later), BMC Atrium Explorer opens the Asset view of the instance. For example, if you edit a computer system CI, the Computer System form (AST:ComputerSystem) is displayed.
- Otherwise, BMC Atrium Explorer opens the instance in its class form. For example, if you edit a computer system CI, the
BMC.CORE:BMC_ComputerSystemclass form is displayed.
BMC Asset Management does not have forms for all the classes in the CDM. If no Asset view of the instance exists, BMC Atrium Explorer opens the instance in its class form.
- Specify the following required attributes:
The name of the instance.
A description of the instance.
Do not edit values for the
ReconciliationIdentityattributes. BMC Atrium CMDB creates values for these attributes automatically when you save the instance, and workflow requires that these values remain unchanged.
- (optional) Specify access control for this instance by using the following attributes:
The groups and roles that have permission to view this instance.
The groups and roles that have permission to modify or delete this instance.
For more information about permissions in BMC Atrium CMDB, see Managing permissions in BMC Atrium Core.
- (optional) Specify additional attribute values for the instance in the General, Specifications, or Custom tabs.
For more information about the class attributes, see the BMC Atrium CMDB Data Model Help.
If you assign the Yes value to the
isVirtualattribute in the Custom tab of a CI created from a BMC class, BMC Atrium Explorer displays the CI's icon enclosed in a brown rectangle. The brown rectangle enables you to quickly identify CIs running as virtual machines. If you add the
isVirtualattribute to a CI of a custom class, you can add the
isVirtualattribute to the list of tooltip attributes for that class. For more information about defining tooltips for a class, see Defining BMC Atrium Explorer tooltips for a class.
- Click Save.
- Click Close.
Because no corresponding CI exists in the BMC Asset dataset until after you promote the new CI, the star icon next to the CI does not change to a pencil icon in the Sandbox view.
- If you are finished working in the Sandbox dataset and are ready to promote changes to the BMC Asset dataset, click Promote Sandbox Changes in the toolbar.
For more information, see Promoting instances.