 |
On platforms that support both 32- and 64-bit, use the rtserver64 command to run the 64-bit RTserver.
|
RTserver is an independent TIBCO SmartSockets process that can be run anywhere on the network. The sections that follow describe how to work with RTserver.
RTserver, by default, runs as a background process (on OpenVMS and Windows, this is known as a detached process). RTserver can be started manually by the user from the operating system prompt, or it can be started automatically when an RTclient process first tries to connect to RTserver. For details on invoking RTserver, see the TIBCO SmartSockets Utilities reference.
By default, RTserver is not started automatically by a client process. You can modify this behavior by adding or changing the prefix of the logical connection name. See the section on logical connection names in the publish-subscribe chapter of the TIBCO SmartSockets User’s Guide for more details.
On UNIX, you can start the RTserver manually to run as a background process with the rtserver command. Enter rtserver at the operating system prompt:
|
On platforms that support both 32- and 64-bit, use the rtserver64 command to run the 64-bit RTserver.
|
On Windows, you can start the RTserver at the TIBCO SmartSockets command prompt ($) or go the Start menu, select Programs, and select the TIBCO SmartSockets program folder. Select RTserver.
Specifying the -check argument starts the non-optimized version of RTserver, which performs additional validation and checking. The optimized version is faster because there is no checking, but it is much harder to diagnose a problem. During all your development and testing, you should run RTserver with the checking turned on. Even in your production environment, you might prefer to run the check version of RTserver. The optimized version is best for enterprise applications where speed is the most important factor.
To stop RTserver, issue the rtserver command with its -stop argument on the computer where RTserver is running. Add the argument -server_names node to stop RTserver on a remote node. This command connects to a running RTserver and requests that RTserver gracefully shut down.
The rtserver -stop command shuts down RTserver even if there is a project running, although by default any RTclient automatically restarts RTserver. To stop RTserver and all RTclients that are connected to that RTserver, use rtserver with the -stop_clients argument. To stop RTserver and all RTservers that are connected to that RTserver, use rtserver with the -stop_servers argument. To stop RTserver, all RTclients that are connected to that RTserver, and all RTservers that are connected to that RTserver, use rtserver with the -stop_all argument.
Both RTservers and RTclients use a concept called options to specify easily changeable parameters that are used by the programs. An example of an RTserver option is Client_Max_Buffer, which is the maximum number of bytes (of a message) that RTserver buffers for one of its clients.
RTserver options can be set to specific values by defining them in the rtserver.cm command file. Option values that have been specified in the command file are set each time RTserver is started, or they can be modified from the RTserver command interface using the setopt command.
For more details about RTserver options, see the TIBCO SmartSockets User’s Guide.
|
TIBCO SmartSockets™ Tutorial Software Release 6.8, July 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |