3.2 Blade Logic Operations Manager

The Blade Logic adapter interfaces with a Blade Logic Application server and a variety of management applications on that server to gather XML data and process them into the Managed Objects Normalized Data format (MOND). MOND is similar to MODL (Managed Objects Definition Language), which is an XML format for defining hierarchies. MOND defines an XML format for interpreting events, alarms, relationships, and performance data.

Refer to the following topics to integrate with Blade Logic Operations Manager:

3.2.1 Integrating Blade Logic Operations Manager

To integrate Blade Logic:

Create a Blade Login Operations Manager adapter for each instance of Blade Logic on the network.

For instructions, see Section 2.1, Creating an Adapter.
Modify the adapter properties.

For instructions, see Section A.2, Blade Logic Operations Manager.
Configure the Blade Logic Operations Manager Monitor.

For instructions, continue to Section 3.2.2, Configuring the Blade Logic Operations Manager Monitor.

3.2.2 Configuring the Blade Logic Operations Manager Monitor

To configure the Blade Logic Operations Manager Monitor:

In the Explorer pane, click Elements to expand it, then click the Blade Logic Operations Manager adapter to expand it.
Right-click the Operations Manager Server, then click Properties.
In the left pane, click Operations Manager Server.
In the Update Time field, to check the XML directory for new XML files, specify the time interval in milliseconds.
Click Select XML Directory to browse and select a directory for storing the XML files.

The Monitor collects all XML files from the selected directory.

Click Add XSLT Mapping to create XSLT to XML root tag mapping to open the XSLT mapping editor, then do the following:

Create the XSLT directly in the editing panel, or click Browse and select an existing XSLT, which you can edit and/or modify.

Enter as many mappings as you want the Monitor to format into the Managed Objects Normalized Data format (MOND) (see Section 3.2.3, Managed Objects Normalized Data (MOND) Format DTD).

Add the root tag of the XML files that this XSLT will translate.

The XML root tag is the first content tag in an XML file. The following is example code:

<?xml version="1.0" encoding="UTF-8"?>
   <dataroot xmlns:od="urn:schemas-microsoft-com:officedata" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  
    xsi:noNamespaceSchemaLocation="CI_Data.xsd" generated="2005-02-
    22T15:19:00">
   <CI_Data>
       <ID>1</ID>
       <Application>Enigma Corp</Application>
       <CI>mdkse</CI>
       <IT_Service>ABC</IT_Service>
       <Domain>AIX Web</Domain>
       <Location>BKDC2,RED2,FEDSA</Location>
   </CI_Data>
   <CI_Data>
      <ID>2</ID>
      <Application>Enigma Corp</Application>
      <CI> mdkse </CI>
      <IT_Service>ABC</IT_Service>
      <Domain>AIX Web</Domain>
      <Location> BKDC2,RED2,FEDSA </Location>
   </CI_Data> . . .

To save files read from the XML directory into a directory, select Retain temporary data files. Then, click Select Temp Directory to select the directory for storing temporary data files.
To enable debug tracing in the formula.trc file, select Enable debug tracing.
Click Apply.
In the Explorer pane, right-click the Operations Manager Server element, then select Manage > Start Monitoring to begin pushing XML data into the adapter.

3.2.3 Managed Objects Normalized Data (MOND) Format DTD

The following code is the DTD for the formatting of MOND output by XSLT translators for the Blade Logic adapter:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!--
The XML file can contain a "events" element that
surrounds one or more event objects.
-->
<!ELEMENT events (event)+ >

<!--
The event chunk contains name<->value pairs either as "name=value"
or as an xml <field name="field name">field value</field>.
The class is the element class.
The isalarm is "false" if only elements are to be generated, if it 
is set to "true" then alarms are created as well.
The severity denotes the severity of alarms if they are to be created
The state is the state of the alarm if alarms are being created
-->
<!ELEMENT event (#PCDATA|field)* >
<!ATTLIST event
          class CDATA #REQUIRED
          isalarm (true|false) "false"
          severity (unknown|ignore|ok|info|minor|major|critical) "ok" 
          state CDATA #IMPLIED> 

<!ELEMENT field (#PCDATA) >
<!ATTLIST field
          name CDATA #REQUIRED> 

<!--
The performance element contains "measures" which are tagged to 
elements.
-->
<!ELEMENT performance (measure)+ >

<!--
measures contain an attribute to the element that it applies to
and one or more values.
-->
<!ELEMENT measure (value)+ >
<!ATTLIST measure
          elementName CDATA #REQUIRED
          measureName CDATA #REQUIRED> 
<!--
values have a numerical value and a time attribute to give the actual 
measured value
-->
<!ELEMENT value (#PCDATA) >
<!ATTLIST value
          timevalue CDATA #REQUIRED> 


<!--
The relationship element has links that create relationship links
between 1 or more elements
-->
<!ELEMENT relationship (link)+ >

<!--
a link has 2 endpoints and a type, endpoints are references to elements
-->
<!ELEMENT link (endpoint1,endpoint2) >
<!ATTLIST link
          linktype CDATA #REQUIRED> 

<!ELEMENT endpoint1 (#PCDATA) >

<!ELEMENT endpoint2 (#PCDATA) >