Real Time Information Director User Documentation

RTID Deployment
Hewlett-Packard Company 17 529618 - 002
10. If you don’t see the success message, check the <RTID_APP_HOME>/rtidstderr.log
and see why the WebLogic server failed to start.
Stop the Director Generic Process
1. Open a new OSS session, using the SUPER user id to logon to OSS.
2. Change directory to <RTID_APP_HOME>/scripts.
3. Set the environment variables
. ./setenv.sh
4. Stop the Director Generic process using the following command:
stop.sh
This script first stops the Director Generic process and then stops the Director
WebLogic server associated with that Generic process.
Load Balance the Director on the NonStop Server Using Parallel
TCP/IP
The Director can be scaled and load balanced by configuring several Director WebLogic
servers and exposing them as a single entity to applications that use the Director.
Specifically, using the features of Parallel TCP/IP, we can configure multiple WebLogic
servers to listen on the same IP address and port. The Director clients use this shared
URL to communicate with the Director. The load balancing is provided by the Parallel
TCP/IP subsystem, which round robins the requests to each of the Director WebLogic
servers. The shared URL should be used only by the applications that send documents to
the Director for loading into the database.
In addition to the shared URL used by most Director clients, you need to assign a
management URL. To manage the individual WebLogic instances, for example to
administer the WebLogic server using the WebLogic console or to use the Director
Management Interface, we need a unique URL for each WebLogic instance. The
management url is configured as an additional Network Channel in the WebLogic
configuration.
In the figure below, both server1 and server2 use the shared URL on port 7011. Server1
uses port 8011 for the management URL, and Server2 uses 8021 for the management
URL.