Sample implementation using JMS

This section describes a gateway implementation with an Enterprise Service Bus (ESB) using JMS.

The following diagram shows how the gateway can work with an Enterprise Service Bus using JMS:

Figure 1. Gateway acquiring data from the ObjectServer and sending it to target applications using JMS
Conceptual diagram showing the gateway acquiring data from the ObjectServer

In this example, the ObjectServer generates events whose data needs to be written in XML event format to two different applications, Application X and Application Y.

The flow of data between the ObjectServer and the applications is as follows:
  1. The ObjectServer generates two events, Netcool® Event 1 and Netcool Event 2, that must be written in XML format to the two different applications:

    Netcool Event 1 must be converted to XML format and written to Application X.

    Netcool Event 2 must be converted to XML format and written to Application Y.

  2. The gateway reads Netcool Event 1 and Netcool Event 2.
  3. The gateway uses the transformer module to convert Netcool Event 1 and Netcool Event 2 into XML events using the transformation defined by the transformers.xml file.

    For each event source, the transformers.xml file contains a transformer entry. Within this entry, the transformation name (which equates to the message ID of the Netcool event) determines which .xsl file to use to convert the event to XML format and to which endpoint to publish the XML event.

    The transformer module converts Netcool Event 1 into XML Event 1 (an event of type X).

    The transformer module converts Netcool Event 2 into XML Event 2 (an event of type Y).

  4. The gateway uses the transport module to publish XML Event 1 to Topic 1 and to publish XML Event 2 to Topic 2.
  5. Application X subscribes to Topic 1 and receives XML Event 1. Application Y subscribes to Topic 2 and receives XML Event 2.