Starting a server in test mode

A local server can be launched from ITE task manager. This is acheived by invoking a local process to execute the server startup script from the install directory that was obtained from the registration panel. The local server startup script can be modified automatically to ensure the server starts up as a test server with the flags -design and -test. A remote server cannot be started in this way, therefore the server launch option is disabled if the registered server is a remote server. In this case, the server should be launched manually from a command line.

Note:
If a server (either local or remote) is launched externally from a command line, ITE will query the server for its running mode (test, design, or both) and adjust itself accordingly to accomodate the server.

Both local and remote servers can be shut down from ITE because server shutdown is implemented as an IDL call. This implies that the server should be connected and logged in before a shutdown operation is requested.

Working with console output

The server console output is redirected from the server process to the InterChange Server console window in ITE for local servers if the server is launched from ITE. For remote servers and local servers started from a command line outside of ITE, the console output cannot be captured this way. To overcome the problem, the server console output will be transported over CORBA. ITE will request the console redirection explicitly with a call back handle and can terminate the service by another IDL call. The server notifies ITE about every message.

Remote console redirection can be turned on or off if you find your performance degraded by console logging. Console redirection is turned on by default.

Note:
The console output over wire is only intended for the servers started manually (servers not started by ITE). For servers launched by ITE (local servers), the console will be redirected to the console viewer.

Copyright IBM Corp. 1997, 2004