Socket

The Java Socket Gateway can read events from any ObjectServer table and forward them to a socket using a TCP connection. Typically, the gateway reads the alerts.status table or the alerts.journal table. Any program that listens to that socket (for example, Netcat) can receive those alerts.

In the gateway default mode of unbatched and unacknowledged event sending, see Sending events with the Socket Gateway, the gateway processes Insert, Delete, Update, Control (IDUC) cycles as follows:

  1. The gateway receives event data from the ObjectServer for each Delete, Insert and Update event that occurs in a single IDUC cycle. The IDUC cycles occur periodically and the cycle intervals can be configured using the Gate.RdrWtr.IducFlushRate property.

  2. Each instance of an Insert and Update is mapped into a pair of name value pairs, as defined by the gateway mapper file. For more information, see Map definition file.

    Note: Deletes are not part of the mapping phase.
  3. The gateway writer then processes the mapped event data, saves the event data to disk, and queues the event data to be sent to the target system.

For details about how to download the most recent version of the gateway, see the following Release Notice on the IBM® Software Support website:

https://www-304.ibm.com/support/docview.wss?uid=swg21625776

This guide contains the following sections: