Real Time Information Director User Documentation

Test the configuration, end-to-end, using the JMS or HTTP adapters of your chosen EAI tool.9.
Test the batch input functions, using the webMethods built-in file service, the XI File Adapter, or
the SeeBeyond File e*Way, to transfer data from the EAI platform to the NonStop Server, and
using the Delsert program to load the data into the data store.
For information about running the Delsert program, see the document entitled RTID Extensibility.
10.
Monitor Director performance, control error logging, and load new metadata classes dynamically,
using the Director Management Client, as described in the document entitled RTID Management.
11.
Troubleshoot problems as they arise, using strategies and tools described in the document entitled
RTID Management. If the Director reports a metadata inconsistency, you’ll also need to consult
the document entitled RTID Extensibility for information about modifying and deploying revised
metadata.
12.
Writing Director Clients
A client can invoke the Director programmatically to load and/or query the data store through a servlet,
an EJB, or direct invocation of a class called the Dispatcher. The Director also supports a low-level API
that operates on objects rather than on XML documents. For information about these programmatic
interfaces, see the document entitled RTID Message Format and Programmatic Interfaces.
A client can monitor Director behavior, load metadata, control error logging and statistics gathering, and
set operational parameters by using the Director management interface. That interface is described in the
document entitled RTID Management.
Adding Document Types or Subscriptions
Once you have confirmed the adequacy of your configuration, it is a simple matter to add new document
types and define new subscriptions. Just remember that, whenever you add a document or subscription or
define a new query, you might have to
Modify the data model to define new tables or fields
Enhance the metadata to describe new mappings
Deploy the new metadata, and reload the database schema if necessary
Create a subscription input file, if you are adding a subscription
Define any needed message types or flows in the EAI design tools
Register new subscriptions, and delete any that are obsolete