Real Time Information Director User Documentation

Technical Overview of the Real Time Information Director
Hewlett-Packard Company 6 529618 - 002
The Real Time Information Director runs in a NonStop WebLogic Server (WLS)
environment on the NonStop Server. It consists primarily of a set of Enterprise Java
Beans (EJBs or MDBs), which provide access to the RTSC Data Store and optionally to
message de-duplication and cleansing services. When the Director application starts up,
beans are activated in each instance of NonStop WLS on the NonStop server. Thus the
Director inherits the scalability of NonStop WLS.
The Director retrieves messages from the JMS queue. It uses the metadata—either the
Format and Content Metadata for an incoming IDoc, or just the Content Metadata for
some other type of message—to set parameters in the appropriate prepared SQL
statement. Then it assigns a Document Handler appropriate to the message type. The
Document Handler inserts the data into the RTSC Data Store by executing the prepared
statement. Database inserts occur in the context of a transaction.
The Director can perform any of three types of insertions:
• Insert. All records related to a brand-new IDoc or other XML document are
inserted into the data store.
• Delsert. All records related to an IDoc or other XML document are deleted and
replaced by data from the incoming document.
• Upsert. Existing records related to an IDoc or other XML document are not
deleted, but data from the incoming document replaces the corresponding data in
existing records.
The Director can also insert history records, allowing you to track all changes made to a
given record.
You specify the type, or types, of insertion required when you create the metadata.
The next figure gives a similar, high-level view of how the Director might load an
Electronic Health Record (EHR) Data Store. In this case, a Clinical System sends a
Health Level 7 (HL7) message, which is transformed to XML by a SeeBeyond or TIBCO
Integration Server. In this case, the message is received by a servlet, which presents it to
the Director EJB. No format metadata is required because this solution does not involve
IDocs.
Updates to the Data Store could also come from a portal, using the interface illustrated
for Queries, later in this document.