Integrating with IBM Operations Analytics - Log Analysis

The Gateway for Message Bus includes a separate set of configuration files for operating with IBM Operations Analytics - Log Analysis.

To run the gateway with IBM Operations Analytics - Log Analysis, use the following steps:

  1. Create a gateway server named G_SCALA in the Tivoli Netcool/OMNIbus interfaces file. See Configuring the gateway server.
  2. Copy the default properties file (G_SCALA.props) supplied with the gateway to the following location: $OMNIHOME/etc
  3. Set the following properties as shown:
    • Set the Name property to G_SCALA.
    • Set the PropsFile property to $OMNIHOME/etc/G_SCALA.props.
  4. Set the Gate.MapFile property to the map file that corresponds to the version of Network Manager Insight Pack you are running in IBM Operations Analytics - Log Analysis.
    Note: The Gate.MapFile property specifies a map file that configures the gateway to send data required by the OMNIbus1100 datasource. If your gateway is running with Network Manager Insight Pack Version 1.1.0.x and higher that is deployed against IBM Operations Analytics - Log Analysis, use the xml.map file. Otherwise, if your gateway is running with OMNIbus Insight Pack Version 1.3.0.0 and Version 1.3.0.1 and higher and Network Manager Insight Pack Version 1.3.0.0 and higher that is deployed against IBM Operations Analytics - Log Analysis, use the xml1300.map file. By default, the G_SCALA.props file supplied with the gateway specifies the xml.map file.

    Otherwise, if your gateway is running with OMNIbus Insight Pack Version 1.3.0.2 and higher and Network Manager Insight Pack Version 1.3.0.0 and higher that is deployed against IBM Operations Analytics - Log Analysis, use the xml1302.map file.

    To specify the xml1300.map or xml1302.map file:

    1. Remove the comment (#) from the following line (depending on which map file you are using):
      Gate.MapFile : '$OMNIHOME/gates/xml/scala/xml1300.map'

Gate.MapFile : '$OMNIHOME/gates/xml/scala/xml1302.map'
    2. Add a comment (#) to the following line:
      #Gate.MapFile : '$OMNIHOME/gates/xml/scala/xml.map'
  5. Change the endpoint specified in the scalaTransformers.xml file to the URL of your data collecting application.
  6. Configure the SSL connection between the gateway and the data collecting application associated with the IBM Operations Analytics - Log Analysis. See Configuring the SSL transport for the IBM Operations Analytics - Log Analysis.
  7. Edit the properties in the scalaTransport.properties file to suit your environment. See Configuring transport module properties files.
  8. Run the gateway using the following command:

    $OMNIHOME/bin/nco_g_xml -propsfile $OMNIHOME/etc/G_SCALA.props

    .
  9. Troubleshoot any problems that occur. See Troubleshooting the IBM Operations Analytics - Log Analysis integration.
    Note: By default, the NmosObjInst column is defined in the ObjectServer alerts.status table and is populated by Network Manager. The enriched value is required by the Network Manager Insight Pack Version 1.3.0.0 and higher to perform end to end searches. The OMNIbus Insight Pack Version 1.3.0.0 and higher and Network Manager Insight Pack Version 1.3.0.0 and higher share the same data source definitions. Therefore, the OMNIbus Insight Pack Version 1.3.0.0 and higher requires a value for the NmosObjInst column in the alerts.status table even though the value is not used.

    By default, the NmosObjInst column is installed in the ObjectServer schema for the alerts.status table. If the NmosObjInst column is not deleted from the alerts.status table, the default xml1300.map definition file can be used. However, if the NmosObjInst column has been deleted from the alerts.status table, you need to either add an integer column called NmostObjInst to the alerts.status table or modify the xml1300.map definition file. See Failed to find column NmosObjInst for instructions on how to modify the xml1300.map definition file if you choose this option.