Mapping instances to devices

To map the instances to devices, add one of the following types of information to the first line of your script:

<metadata>I2D=true</metadata>, or
<metadata>I2D=true,devicetype=VirtualMachine</metadata>

If devicetype is specified, the corresponding device name will be consistently displayed for all devices created for each instance in BMC Helix Operations Management. If the device mapping is enabled, all the instances based on the script output must be defined as:

FQDN/IPAddress*InstanceName

Where FQDN/IPAddress maps the instance to the console as a device based on the FQDN/IPAddress; InstanceName represents the device's display name. If InstanceName is not provided, the FQDN/IPAddress will be used as the instance name.

For example, the following portion of a script illustrates how to monitor both the response code and response time of web servers:

<metadata>I2D=true</metadata>WebServer=finance.domain.com/10.10.10.11*FinanceApp,ResponseTime=2,ResponseCode=200WebServer=callCenter.domain.com/10.10.10.12*CallCenterApp,ResponseTime=3,ResponseCode=200

or

<metadata>I2D=true,devicetype=VirtualMachine</metadata>
WebServer=finance.domain.com/10.10.10.11*FinanceApp,ResponseTime=2,ResponseCode=200WebServer=callCenter.domain.com/10.10.10.12*CallCenterApp,ResponseTime=3,ResponseCode=200

According to this script, the console would create two new devices: finance.domain.com and callCenter.domain.com. These devices would correspond to the instances named FinanceApp and CallCenterApp, respectively.


Note

If one or more of the script instance names are not defined as (FQDN/IPAddress*InstanceName), the script does not populate the instances and their associated attributes, and you will receive an error message.



 

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