Features of the IBM Tivoli Netcool/OMNIbus Java Gateway for BMC Remedy ARS

Event forwarding

The gateway uses the Insert, Delete, Update, or Control (IDUC) communication protocol to retrieve events from ObjectServer tables. The gateway can replicate the data in any table between the ObjectServer and the destination server. Details of the tables to be replicated are stored in the table replication definition file. The events retrieved from these tables are based on the table replication definition file configuration, including their filtering. Retrieved events are then passed through a mapper to assign values to target fields that the gateway is required to populate and update on the BMC Remedy ARS system. The mappers are specified in the table replication definition file and defined in the map definition file.

Table Replication contains more information on replicating data between the ObjectServer and BMC Remedy ARS

See the IBM Tivoli Netcool/OMNIbus Administration Guide and the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide for more information on IDUC.

Mapping table data

The gateway writes the alerts received from the various tables in the ObjectServer onto BMC Remedy ARS in a format defined by the mappers defined in the map definition file. Each of the maps defines how to map an alert into a request in BMC Remedy ARS (as defined by the Gate.Remedy.Form property).

Mapping contains more information on the map definition file.

Unidirectional and bidirectional resynchronization

The gateway can perform two types of resynchronization: unidirectional and bidirectional. There is also an automatic mode that causes the gateway to perform either unidirectional or bidirectional synchronization, depending on whether its cache is empty on startup.

Resynchronization provides additional information about unidirectional and bidirectional resynchronization.