Class Configuration
By default all classes are preloaded in an inactive state. To sync data to the Service Now CMDB you must activate the classes you wish to send. Classes for multiple instances of Service Now can be configured independently. To start configuring classes for a specific instance navigate to Integrations → Service Now and select the instance you wish to configure. From the Actions menu select “Configure Syncronisation”.
From here you can see the list of the Syncronisation Definitions for each Schema. To configure the classes select a schema, navigate to the “Actions” menu and select “Configure Classes”
The following table shows the details for each column shown :
Column Name | Description | Notes |
---|---|---|
Name | ServiceNow Data Class Name |
|
Class | ServiceNow CI class name |
|
Default | Service Now parent table for the data. | Example of Hosts, cmdb_ci_server is the default (Parent table) highlighed green, cmdb_ci_linux_server is a child table of this highlighted red. |
Active | uControl setting for Class active / inactive | Initial default in inactive for all classes |
Attributes Mapped | Displays green when attributes are mapped. | Default attributes are mapped during setup. |
Class Rules Mapped | Are filters applied to the CI class configuration | Default is no filters applied for parent tables, child tables will have OOTB filters applied. |
BMC Kind | The associated node kind from BMC Discovery that will write data into the ServiceNow CI class |
|
Activate a ServiceNow Definition
To start sending data to the Service Now CMDB you will need to activate a class configuration.
To do this :
Navigate to Integration → ServiceNow
Select the instance from the list of Service Now Instances. Select “Actions” and “Configure Syncronisation”
Select a schema and from the actions dropdown select “Activate”.
Here you can see that the Host class configuration has been activated.
Configure the atttribute mappings
When the initial setup has run default attribute mappings were completed. You can however modify these to you requirements.
To remove a default attribute mapping
Navigate to Integration → ServiceNow, select the instaince from the list and select “Configure Syncronisation” from the actions menu.
Select a schema from the list and select “Configure Classes” from the “Actions” menu.
Select the class to configure the attributes for and select “Configure Fields” from the “Action” menu.
Select the attribute you would like to remove and select the “Delete Record” from the “Actions” menu.
To Add a new attribute mapping
Navigate to Integration → ServiceNow, select the instaince from the list and select “Configure Syncronisation” from the actions menu.
Select a schema from the list and select “Configure Classes” from the “Actions” menu.
Select the class to configure the attributes for and select “Configure Fields” from the “Action” menu.
Seelct the “Plus” add button from the top right of the table
Select the Service Now Field and the Asset Field and click “Create”
Class Rules
You will notice that class rules have been automatically setup for child classes as part of the initial setup.
Class rules allow you to filter the device types from BMC Discovery that you wish to send to Service Now. These filters can be positive or negative depending on the requirement. Eg.
Send Only “Oracle Database Server” CI to the cmdb_ci_appl class:
type → Equals → “Oracle Database Server”
Send Only servers with “Prod” in the name to the cmdb_ci_server class:
name → Contains → “Prod”
The following conditions are available for all class rules :
Condition |
---|
Equal |
Not Equal |
Contains |
Doesn’t Contain |
Begins With |
Ends With |
To add a class rule :
Navigate to Integration → ServiceNow, select a Service Now instance and from the actions dropdown select “Configure Syncronisation”
Select a schema from the table you wish to add a rules to and select “Confiure Classes”
Select a class from the list and from the “Actions” menu select “Configure Rules”
To add a rules click on the “Plus” icon on the top right of the table
Select the source field, the condition and the value.
Select Create.
Only 1 rules can be configured so delete the previous rule if one exists before adding a new one.
Once the rule has been created you can test it by selecting “Run Rule”