What is the RTserver launch sequence under WIndows?
Article ID: KB0085477
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
Start->Programs->SmartSockets->Command Prompt launches ssvars32.bat which sets Paths and "sits" while the Command Prompt Window is open.
If you do a $ps in the Command Prompt Window prior to launching RTserver you will see:
752 0:00 "C:\WINNT\System32\cmd.exe" /E:8192 /KC:\SS62r2\bin\i86_w32\ssvars32.bat
RTadmin reads the "rtserver.cm" file and converts the conn_names option to server_names. After spawning the RTserver process it tries to connect to the RTserver (using the function TipcSrvIsRunning()). In this way RTadmin acts like an RTclient.
NOTE: When using "tcp:_any" in the conn_names option in rtserver.cm, RTadmin will not connect to RTserver because "tcp:_any" in the server_names option does not resolve to any specific RTserver. Barring this, RTadmin will connect to RTserver and verify that it can receive connections. You can verify this by setting the trace level in the rtserver to verbose and you should see in the RTserver window that a client has connected and then disconnected. This is RTadmin.
So the launch sequence is:
1) rtserver.bat in RTBATPATH gets called.
2) rtserver.bat calls rtadmin.exe with the argument of rtservero.exe %1 ... and then exits.
RTadmin was created for backwards compatibility for some of the command line arguments (and behavior) that the 5.x RTserver used to support but which 6.x no longer does. For example, The 6.x RTserver.exe will always come up in the foreground and no longer supports -no_daemon flag. It is RTadmin's job to start the RTserver in the background to maintain the same behavior as in 5.x. Do not remove RTadmin if you plan on only running RTserver on a host machine.
Start->Programs->SmartSockets->Command Prompt launches ssvars32.bat which sets Paths and "sits" while the Command Prompt Window is open.
If you do a $ps in the Command Prompt Window prior to launching RTserver you will see:
752 0:00 "C:\WINNT\System32\cmd.exe" /E:8192 /KC:\SS62r2\bin\i86_w32\ssvars32.bat
RTadmin reads the "rtserver.cm" file and converts the conn_names option to server_names. After spawning the RTserver process it tries to connect to the RTserver (using the function TipcSrvIsRunning()). In this way RTadmin acts like an RTclient.
NOTE: When using "tcp:_any" in the conn_names option in rtserver.cm, RTadmin will not connect to RTserver because "tcp:_any" in the server_names option does not resolve to any specific RTserver. Barring this, RTadmin will connect to RTserver and verify that it can receive connections. You can verify this by setting the trace level in the rtserver to verbose and you should see in the RTserver window that a client has connected and then disconnected. This is RTadmin.
So the launch sequence is:
1) rtserver.bat in RTBATPATH gets called.
2) rtserver.bat calls rtadmin.exe with the argument of rtservero.exe %1 ... and then exits.
RTadmin was created for backwards compatibility for some of the command line arguments (and behavior) that the 5.x RTserver used to support but which 6.x no longer does. For example, The 6.x RTserver.exe will always come up in the foreground and no longer supports -no_daemon flag. It is RTadmin's job to start the RTserver in the background to maintain the same behavior as in 5.x. Do not remove RTadmin if you plan on only running RTserver on a host machine.
Issue/Introduction
What is the RTserver launch sequence under WIndows?
Feedback
Yes
No
Powered by
