Server Incident Enrichment module
Before you can use the Continuous Compliance for Server Automation, you must ensure that the Server Incident Enrichment module is properly integrated to work with the TrueSight Server Automation system, and the BMC Remedy ITSM systems. This integration requires that you modify the configuration of the module to ensure that the configuration items in the configuration groups match the information you entered when you configured the change and task templates in your BMC Remedy ITSM system.
For the Server Incident Enrichment module, you can control what information is included in the incident. For example, you can specify which BMC Remedy Service Desk, TrueSight Server Automation servers you want to connect to gather information to add to an incident.
- Incident Management configuration group for Server Incident Enrichment
- BladeLogic configuration group for Server Incident Enrichment
- Configuration Management group for Server Incident Enrichment
- Sample xml for Server Incident Enrichment configuration items
Incident Management configuration group for Server Incident Enrichment
Update the Platform configuration item to match the name of the incident platform as seen in the Incident Management module configuration (for example, BMC_AR_System ).
BladeLogic configuration group for Server Incident Enrichment
The following table lists the TrueSight Server Automation configuration items.
Configuration Item | Description |
|---|---|
Platform | Name of the BMC Remedy ITSM platform as seen in the Incident Management module configuration. For example, BMC_AR_System. |
Enable | Indicates if TrueSight Server Automation configuration is enabled in the current environment. Allowed values: true and false. |
BL_Connection_Details | An XML structure that holds the TrueSight Server Automation Adapter name. <connection-details> <adapter-name>BladeLogic Adapter</adapter-name> <timeout>TIMEOUT_IN_SECONDS</timeout> </connection-details> Note: If the TrueSight Server Automation job takes more than 5 minutes to complete, the process times out. To increase the time-out period, modify the <time-out> parameter. |
Default_TimeZone | Default timezone should match the timezone of the system that hosted TrueSight Server Automation. Time zones are interpreted as text if they have names. For time zones representing a GMT offset value, the following syntax is used: |
Configuration Management group for Server Incident Enrichment
The configuration values in the Configuration Management configuration group must match the values of the template you configured in BMC Remedy ITSM. BladeLogic ITSM Integration - Configuration Management configuration items lists Configuration Management configuration items.
Configuration Item | Description |
|---|---|
Platform | Name of the BMC Atrium CMDB platform as seen in the Configuration Management module configuration. For example, BMC_AR_System |
BL_Atrium_ Integration_ Enabled | Specifies how the configuration items are retrieved through TrueSight Server Automation Integration for Atrium. A value of true retrieves the configuration items using the CDMachineID. A value of false retrieves the configuration items using the CI name. |
BL_Computer Systems_ Mappings | Specifies the mappings between the configuration item name and the display name. See the following figure. |
Sample xml for Server Incident Enrichment configuration items
The following sections provide sample xml for Server Incident Enrichment configuration items.
BL_Computer Systems_ Mappings xml for Server Incident Enrichment
<!-- BMC_AR System Equipment Field Mappings -->
<asset-class type="enum-value">AssetClass</asset-class>
<assigned-to type="string-value">AssignedTo</assigned-to>
<creation-date type="time-value">CreateDate</creation-date>
<dataset-id type="string-value">DatasetId</dataset-id>
<description type="string-value">Description</description>
<disposal-date type="time-value">DisposalDate</disposal-date>
<domain type="string-value">Domain</domain>
<floor type="string-value">Floor</floor>
<hostname type="string-value">HostName</hostname>
<id type="string">RequestId</id>
<installation-date type="time-value">InstallationDate</installation-date>
<instance-id type="string">InstanceId</instance-id>
<ip-address type="string-value">LogicalID</ip-address>
<item type="string-value">Item</item>
<last-modified-by type="string-value">LastModifiedBy</last-modified-by>
<logs type="diary-value">MaintenanceLog</logs>
<manufacturer type="string-value">ManufacturerName</manufacturer>
<model type="enum-value">Model</model>
<modified-date type="time-value">ModifiedDate</modified-date>
<name type="string-value">Name</name>
<notes type="diary-value">Notes</notes>
<order-id type="string-value">OrderID</order-id>
<owner type="string-value">OwnerName</owner>
<part-number type="string-value">PartNumber</part-number>
<product-category type="enum-value">AcquiredMethod</product-category>
<purchase-date type="time-value">PurchaseDate</purchase-date>
<received-date type="time-value">ReceivedDate</received-date>
<reconciliation-id type="string-value">ReconciliationIdentity</reconciliation-id>
<region type="string-value">Region</region>
<requisition-id type="string-value">RequisitionID</requisition-id>
<room type="string-value">Room</room>
<schedule-type type="enum-value">ScheduleType</schedule-type>
<serial-number type="string-value">SerialNumber</serial-number>
<short-description type="string-value">ShortDescription</short-description>
<site type="string-value">Site</site>
<status type="enum-value">AssetLifecycleStatus</status>
<submitter type="string-value">Submitter</submitter>
<supplier type="string-value">SupplierName</supplier>
<supported-by-service type="string-value">Supported</supported-by-service>
<system-role type="string-value">SystemRole</system-role>
<tag-number type="string-value">TagNumber</tag-number>
<total-physical-memory type="string-value">TotalPhysicalMemory</total-physical-memory>
<type type="enum-value">Type</type>
<unit-price type="string-value">UnitPrice</unit-price>
<urgency type="enum-value">Urgency</urgency>
<users-affected type="string-value">UsersAffected</users-affected>
<version type="string-value">VersionNumber</version>
<cd-machine-id type="string-value">CDMachineID</cd-machine-id>
</mappings>
UI_Objects xml for Server Incident Enrichment
<ui-object name="Change Tracking Details by Asset Class">
<!-- Fully qualified path of the report folder in reporting server -->
<value>/content/package[@name='BladeLogic']/folder[@name='Change Tracking']/report[@name='Change Tracking Details by Asset Class']</value>
<!-- input parameters required for the report. -->
<static-parameters>
<parameter name="Asset Class" required="false" />
<parameter name="Policy Name" required="false" />
<parameter name="Asset Path" required="false" />
<parameter name="Change Type" required="false" />
<parameter name="Site Name" required="false" />
<!-- Object Type allowed values: Com Plus, Configuration, Custom Object, Dot Net Assembly,
Event Log, Extended Object, File, GPO, Metabase, OS Group, OS User, Registry,
Services, Software, System Info, VMWare -->
<parameter name="Object Type" required="true">File</parameter>
</static-parameters>
<!-- For Server Incident Enrichment the CI name shall be different for each report.
Therefore, users need to provide the name of the server parameter and its
value shall be dynamically decided by the workflow. -->
<dynamic-parameters>
<server>Server Name</server>
</dynamic-parameters>
</ui-object>
<ui-object name="Patch Analysis Detail by Server">
<value>/content/package[@name='BladeLogic']/folder[@name='Patch']/folder[@name='Patch Details']/report[@name='Patch Analysis Detail By Server']</value>
<static-parameters>
<parameter name="Patch Analysis Policy" required="false" />
<parameter name="Patch OS Name" required="false" />
<parameter name="Patch Site Name" required="false" />
</static-parameters>
<dynamic-parameters>
<server>Patch Server Name</server>
</dynamic-parameters>
</ui-object>
<ui-object name="Server Configuration details">
<value>/content/package[@name='BladeLogic']/folder[@name='Inventory']/report[@name='Server Configuration']</value>
<static-parameters>
<!-- Inventory Date format = YYYY-MM-DD HH:MM:SS -->
<parameter name="Inventory Date" required="true">2100-12-31 23:59:59</parameter>
<parameter name="Server Site Name" required="true">Primary</parameter>
<parameter name="OS Name" required="true">Windows</parameter>
</static-parameters>
<dynamic-parameters>
<server>Server Name</server>
</dynamic-parameters>
</ui-object>
<ui-object name="Job Activity Summary by Server">
<value>/content/package[@name='BladeLogic']/folder[@name='Job Activity']/folder[@name='Job Activity Summaries']/report[@name='Job Activity Summary by Server']</value>
<static-parameters>
<parameter name="Job Site Name" required="false" />
<parameter name="Patch Server Group" required="false" />
</static-parameters>
<dynamic-parameters>
<server>Compliance Server Name</server>
</dynamic-parameters>
</ui-object>
</ui-objects>
UI_Objects_v8_2 xml for Server Incident Enrichment
<ui-object name="Change Tracking Details by Asset">
<!-- Fully qualified path of the report folder in reporting server -->
<value>/content/package[@name='BladeLogic']/folder[@name='Change Tracking']/report[@name='Change Tracking Details by Asset']</value>
<!-- input parameters required for the report. -->
<static-parameters>
<parameter name="PromptCTAsset" required="true">FileSystem</parameter>
<parameter name="PromptCTOSName" required="true">All</parameter>
</static-parameters>
<!-- For Server Incident Enrichment the CI name shall be different for each report.
Therefore, users need to provide the name of the server parameter and its
value shall be dynamically decided by the workflow. -->
<dynamic-parameters>
<server>PromptCTServerName</server>
</dynamic-parameters>
</ui-object>
<ui-object name="Missing Patch Details">
<value>/content/package[@name='BladeLogic']/folder[@name='Patch']/report[@name='Missing Patch Details']</value>
<static-parameters>
<parameter name="PromptPatchPolicyName" required="false" />
<parameter name="PromptPatchOSName" required="true">Windows</parameter>
</static-parameters>
<dynamic-parameters>
<server>PromptPatchServerName</server>
</dynamic-parameters>
</ui-object>
<ui-object name="Server Configuration">
<value>/content/package[@name='BladeLogic']/folder[@name='Inventory']/report[@name='Server Configuration']</value>
<static-parameters>
<parameter name="PromptOSNAME" required="true">Windows</parameter>
<parameter name="PromptWindowsInfo" required="true">Default</parameter>
<parameter name="PromptHPUXInfo" required="fasle" />
<parameter name="PromptLINUXInfo" required="fasle" />
<parameter name="PromptSOLARISInfo" required="fasle" />
<parameter name="PromptAIXInfo" required="fasle" />
</static-parameters>
<dynamic-parameters>
<server>PromptServerName</server>
</dynamic-parameters>
</ui-object>
<ui-object name="Job Run Server Details">
<value>/content/package[@name='BladeLogic']/folder[@name='Job Activity']/report[@name='Job Run Server Details']</value>
<static-parameters>
<parameter name="PromptJAJobType" required="true">All</parameter>
<parameter name="PromptJAJobName" required="false" />
</static-parameters>
<dynamic-parameters>
<server>PromptJAServerName</server>
</dynamic-parameters>
</ui-object>
</ui-objects>