Real Time Information Director User Documentation

RTID Subscriptions
Hewlett-Packard Company 2 529618 - 002
Introduction
Subscription Module Overview
The Real Time Information Director (RTID, or Director) provides the basis for a real-
time solution that integrates systems and applications across the enterprise. For example,
the Real Time Supply Chain (RTSC) solution integrates multiple Supply Chain instances.
At the center of any real-time solution is the data store, which is used to capture data
from throughout the enterprise and to provide data to interested applications throughout
the enterprise.
You use the Subscription Module (SubServ) of the Director to deliver documents to
applications that subscribe to events in the data store. Document formats are defined in
metadata files. An application can specify any of these formats as the type of document
to be delivered each time a subscription is triggered.
A subscription has three attributes:
• A SQL statement to define the event in the data store that triggers the subscription
• The name of a JMS Queue or Topic to which a document is delivered when this
event occurs
• The name of the type of document to be delivered to the client when this event
occurs
Subscriptions are registered and stored in the Subscription Store (SUBINFO) shown in
Figure 1. The RegSubs.sh program provided with the Subscription module allows users
to add new subscriptions, browse existing subscriptions, and delete subscriptions. All of
these operations can be carried out even when the foundation layer components are
deployed and running.
A subscription is triggered whenever the specified database event occurs. A database
event can trigger one or more subscriptions. Each subscription triggered by the same
event can deliver the same or different documents. Subscriptions triggered by different
events can deliver the same document. A database event occurs whenever an incoming
document is processed by the Director and inserted into the data store.
When the event corresponding to a subscription occurs, the specified document is created
and delivered as a message to a JMS Queue or Topic. An application that is capable of
reading from this Queue or Topic can then retrieve this message.