Setting Routers

In any deployed configuration of Component Servers, one or more Servers act as routers and distribute requests among those Servers that have the appropriate service, transaction type, and routing data. You specify whether a Server is a router when you launch the Server processes (see Configuring, Starting, and Stopping the Server Executable).

Each client must specify one or more routers as well. You do this with the API ostc::addRouter(). On Windows platforms, you can use the executable ostcSetRouter.exe instead of this API.

Example

      ostc::addRouter(argv[1]);

argv[1] is a character string specifying the host machine of the router Component Server, as well as the port on which it is listening for thin client requests.

The string has the syntax

      host:port 

When a client calls ostc_Session::doOperation(), a router tells the client which Component Server to send requests to. The router makes this determination based on

• The specified service name
  
• A round-robin schedule of Component Server processes that match the specified service name.
  

Click here for the example in context.

ostcSetRouter.exe

Windows only: With this executable you can add and remove routers:

ostcsetrouter -add host:port 
ostcsetrouter -remove host:port 
ostcsetrouter -clear 

The -clear switch removes all routers.

Running this utility affects the Windows NT registry.