Jolt 1.2 Developer's Guide

Notification Data Buffers
When a client receives notification, it is accompanied by a data buffer. The data buffer can be of any NonStop
TM
TUXEDO data buffer type. Jolt
clients (i.e., the handler) will receive these buffers as a JoltMessage object and should use the appropriate JoltMessage class get*() methods to
retrieve the data from this object.
The Jolt Repository does not need to have the definition of the buffers used for notification. However, the Jolt client application programmer will
need to know field names beforehand.
The Jolt system does not provide functionality equivalent to tptypes() in NonStop
TM
TUXEDO, so in effect a Jolt client is limited to receiving a
"known" buffer type. For FML and VIEW buffers, the data will be accessed using the get*() methods with the appropriate field name, for example,
enter:
getIntDef ("ACCOUNT_ID", -1);
For STRING and CARRAY buffers, the data will be accessed by the same name as the buffer type, e.g.,:
getStringDef ("STRING", null);
getBytesDef ("CARRAY", null);
STRING and CARRAY buffers contain only a single data element: this complete element is returned in the get*() methods above.
NonStop
TM
TUXEDO Event Subscription
NonStop
TM
TUXEDO brokered event notification allows NonStop
TM
TUXEDO programs to post events without needing to know what other
programs are supposed to receive notification of an event's occurrence. The Jolt event notification allows Jolt client applications to subscribe to
NonStop
TM
TUXEDO events that are broadcast or posted using the NonStop
TM
TUXEDO tpnotify() or tpbroadcast() calls.
Jolt clients are only able to subscribe to events and notifications that are generated by other components in NonStop
TM
TUXEDO (such as a
NonStop
TM
TUXEDO Service or Client). Jolt 1.2 clients are not able to send events or notifications.
Supported Subscription Types
Jolt 1.2 only supports notification types of subscriptions. The Jolt onReply() method is called when a subscription is fulfilled. The Jolt 1.2 API does
not support dispatching a service routine or enqueueing a message to an application queue when a notification is received.
Subscribing to Notifications
If a Jolt client subscribes to a single event notifications, the client receives both unsolicited messages and event notification. Subscribing to an event
implicitly enables unsolicited notification. This means that if the application creates a JoltUserEvent object for Event "X", the client will
automatically receive notifications directed to it as a result of tpnotify() or tpbroadcast().