Configuring the Gateway for JDBC and Gateway for Message Bus

Edit online

Configure the Gateway for JDBC to run in reporting mode, so it can forward event data to the Db2® database for archiving. Configure the Gateway for Message Bus gateway to forward event data to Operations Analytics - Log Analysis and run it in Operations Analytics - Log Analysis mode.

Before you begin

  • Install the Db2 database and configure the REPORTER schema so that the Gateway for JDBC can connect.
  • Install the gateways on the same host as Tivoli® Netcool®/OMNIbus core components (that is, server 1).
  • Install Operations Analytics - Log Analysis and obtain the URL for the connection to the Gateway for Message Bus.

Procedure

  • Configure the Gateway for JDBC. This involves the following steps:
    • Obtain the JDBC driver for the target database from the database vendor and install it according to the vendor's instructions. The drivers are usually provided as .jar files.
    • To enable the gateway to communicate with the target database, you must specify values for the Gate.Jdbc.* properties in the $OMNIHOME/etc/G_JDBC.props file. This is the default properties file, which is configured for reporting mode, that is supplied with the gateway.

    Here is a sample properties file for the Gateway for JDBC.

    # Reporting mode properties
Gate.Jdbc.Mode: 'REPORTING'
# Table properties
Gate.Jdbc.StatusTableName: 'REPORTER_STATUS'
Gate.Jdbc.JournalTableName: 'REPORTER_JOURNAL'
Gate.Jdbc.DetailsTableName: 'REPORTER_DETAILS'
# JDBC Connection properties
Gate.Jdbc.Driver: 'com.ibm.db2.jcc.DB2Driver'
Gate.Jdbc.Url: 'jdbc:db2://server3:50000/REPORTER'
Gate.Jdbc.Username: 'db2inst1'
Gate.Jdbc.Password: 'db2inst1'
Gate.Jdbc.ReconnectTimeout: 30
Gate.Jdbc.InitializationString: ''
# ObjectServer Connection properties
Gate.RdrWtr.Username: 'root'
Gate.RdrWtr.Password: 'netcool'
Gate.RdrWtr.Server: 'AGG_V'
  • Configure the Gateway for Message Bus to forward event data to Operations Analytics - Log Analysis. This involves the following steps:
    • Creating a gateway server in the Netcool/OMNIbus interfaces file
    • Configuring the G_SCALA.props properties file, including specifying the .map mapping file.
    • Configuring the endpoint in the scalaTransformers.xml file
    • Configuring the SSL connection, if required
    • Configuring the transport properties in the scalaTransport.properties file
  • If you do not want to use the default configuration of the Gateway for Message Bus (an IDUC channel between the ObjectServer and Operations Analytics - Log Analysis and supports event inserts only), configure event forwarding through the AEN client. This support event inserts and reinserts and involves the following steps:
    • Configuring AEN event forwarding in the Gateway for Message Bus
    • Configuring the AEN channel and triggers in each ObjectServer by enabling the postinsert triggers and trigger group
  • Start the Gateway for Message Bus in Operations Analytics - Log Analysis mode.
    For example:
    $OMNIHOME/bin/nco_g_xml -propsfile $OMNIHOME/etc/G_SCALA.props
    The gateway begins sending events from Netcool/OMNIbus to Operations Analytics - Log Analysis.
  • Start the Gateway for JDBC in reporter mode.
    For example: 
    $OMNIHOME/bin/nco_g_jdbc -jdbcreporter
  • As an alternative to starting the gateways from the command-line interface, put them under process control.