Real Time Information Director User Documentation
RTID Deployment
Hewlett-Packard Company 13 529618 - 002
either Dispatch or appsdir_Dispatch_Ear
You should see the DispatchEJB, LoaderMDB and DispatchServlet listed.
• To verify the DispatchServlet is running you can run it from your web
browser by going to it’s url, for example
http://16.107.199.52:7011/
/RTIDServlet/Dispatch
On the page returned, you should see the Dispatch Server version and an
indication that it is connected to the Dispatch EJB.
Deploy Blaze or Trillium Enrichments (optional)
Blaze and Trillium enrichments that you can use as the basis for custom enrichments are
included as examples on the RTID CD. You’ll find these enrichments in the jar files
rtidblaze.jar and rtidtrillium.jar. If you intend you use them, you must add them to the
server classpath before starting the WebLogic server.
Blaze and Trillium enrichments also require the product jar files that implement Blaze or
Trillium functions in order to run. These files must also be added to the server classpath
before you run the application.
Execute Director Test Drivers
You can run various drivers to test your deployment and document definitions. For
example, you can use the QueueSend program to test deployment of the LoaderMDB
and the HttpPost driver to test deployment of the DispatchServlet.
Before running drivers, start a new OSS session, and execute the setenv.sh script to set up
the environment.
For more information about Director test drivers and how to use them, see the document
entitled RTID Extensibility and the Javadocs for individual drivers.
Deploy the Director in Production Mode
There are two options for running the WebLogic server in a production mode. One option
is to run WebLogic server as a Generic process and the other option is Clusters. Both
approaches are documented in the HP NonStop Server Platform Guide for WebLogic
Server 8.1.
The Generic process provides failover capabilities. For load-balancing, you can use
either WLS Clusters or the load-balancing features of Parallel TCP/IP.