Overview

The Java Gateway for BMC Remedy ARS is a bidirectional gateway that creates requests in BMC Remedy ARS from alerts sent by the ObjectServer.

In a typical environment, users define workflows within BMC Remedy ARS to create trouble requests from the requests that the gateway creates. These trouble requests are updated, according to a predefined mapping, throughout the life-span of the alert. For each request that the gateway creates, BMC Remedy ARS sends back an associated request ID.

BMC Remedy ARS also passes back to the gateway any changes to the requests so that the gateway can update the original ObjectServer alert.

The following list describes some of the functions that the gateway supports:
  • Flexible port mapping to BMC Remedy ARS.
  • Flexible event filtering that allows you to specify which alerts the gateway uses to create the corresponding requests in BMC Remedy ARS.
  • Reporting within Tivoli Netcool/OMNIbus of BMC Remedy ARS operation failures.
  • Forwarding updates to BMC Remedy ARS requests when the associated events in Tivoli Netcool/OMNIbus are updated or deleted.
  • The ability for BMC Remedy ARS to pass back any changes to the requests, so that the gateway can update the original ObjectServer alert.
  • The gateway forwards journal entries from alerts in Tivoli Netcool/OMNIbus to BMC Remedy ARS.
  • Conversion of ObjectServer values and BMC Remedy ARS values. These conversions are bidirectional.
  • The gateway can perform two types of resynchronization: unidirectional and bidirectional.
  • The gateway provides JavaScript files for processing bidirectional updates (that is, updates from BMC Remedy ARS to the ObjectServer).
  • The gateway provides a store and forward capability to minimize any data loss should the gateway lose communication with BMC Remedy ARS.