Running the RRS Server

Before running RRS, the DELMIA RRS server daemon must be started on the RRS server machine.

This task shows you how to:

Running the DELMIA UNIX and Interix-based Windows RCS Server

This task describes the steps required to run the UNIX- and Interix-based servers.

  1. Log on to the RRS server machine and go to the RRS server's bin directory on the server machine:
    cd <rcs_home_dir>/<RRS_Cntr_Type>/bin
  2. Start the RRS server daemon:
    ./rcssrv_<RRS_Cntr_Type> -tcp <port_num>

    where rcssrv_<RRS_Cntr_Type> is the name of the RRS server executable, e.g., rcssrv_FANUC_RJ2__4.2 for FANUC RJ2 4.2 RCS, and <port_num> is the IP port that the RRS server will be listening for RRS connection requests from an RRS client.

    Note that the RRS server executable file name on the RCS manufacturer's distribution tape may not follow the naming convention described here. Please see the RRS server-specific pages in the Customizing section to see if this may be the case.

    <port_num> must match the <port> field of the corresponding RRS server entry in the DELMIA RRS product's RRS servers file.

    By default, the RRS server creates the log file /usr/tmp/rcssrv_<RRS_Cntr_Type>.log and the process ID file /usr/tmp/rcssrv_<RRS_Cntr_Type>.pid. Note that on Windows RCS servers these files are created on the same drive that the RRS server executable is located on.

    All RRS server startup/termination and RRS connection messages are recorded in the log file. The RRS server daemon's process ID is stored in the process ID file. Optionally, by using the -log <Log_File> and -pid <Process_ID_File> options on the RRS server command line, user-specified log and process ID file names can be used instead of the defaults.

  3. Log off the RRS server machine.

    The RRS server daemon will continue to run in the background. Once the RRS server daemon is up (unless it gets killed due to a reboot, for example), the RRS server does not require further intervention by the user.

    To terminate the RRS server deamon and clean up associated processes and files, execute the following command on the RRS server machine: kill `cat /usr/tmp/rcssrv_<RRS_Cntr_Type>.pid`

    where /usr/tmp/rcssrv_<RRS_Cntr_Type>.pid may need to be replaced with the user-specified <Process_ID_File> if the -pid flag was used when the RRS server daemon was first started.

    Note:

    On Windows Interix RRS server machines, you must either:

    • first change to the directory on the drive where the RRS server executable is located before issuing the above kill command, or
    • explicitly specify the the drive letter in the pid file's pathname in the above kill command.

Running DELMIA Win32-based Windows RRS Server

This task describes the steps required to run the Win32-based server.

Before running the DELMIA RRS product, the DELMIA Win32-based Windows RCS server application/service must be started on the RRS server machine. The following sections describe starting the server as either a Windows application or service.

On the RRS server machine, navigate to the RRS server's bin folder:
cd <rcs_home_dir>\RRS_Cntr_Type\bin

Starting as a Windows application

This task describes how to run the Win32-based server as a Windows application. In this mode of operation, the RRS server is active only while the command shell that it is running in is active, i.e. if the command shell is killed or if the user logs off, the RRS server will stop operating.

To start the RRS server in this mode, inside a command shell type: .\rcssrv_<RRS__Cntr__Type>.exe -tcp <port_num>

Starting as a Windows service

This task describes how to run the Win32-based server as a Windows service. In this mode of operation, the RRS server will stay active even if the user who brought up the RRS server logs off.

To start the RRS server as a service, log into an administrator account and then inside a command shell type: .\rcssrv_<RRS_Cntr_Type>.exe -service -tcp <port_num>

This will install and start a new Windows service named rcssrv_<RRS_Cntr_Type>. This new service can be monitored and controlled through the Windows Control Panel > Services utility. To stop and uninstall this Windows service, type:.\rcssrv_<RRS_Cntr_Type>.exe -remove

If the Windows service is stopped through the Windows Control Panel > Services utility, it can be restarted using the same utility by entering the appropriate -tcp <port_num> flag in the Startup Parameters text entry field of the Control Panel > Services utility.

For both cases above, rcssrv_<RRS_Cntr_Type>.exe is the name of the DELMIA Win32-based RRS server executible (e.g., rcssrv_FANUC_RJ3__5.XX.exe for FANUC RJ3 5.XX RCS). <port_num> is either an IP port number or a network service name (identifying an IP port number) that the RRS server will be listening for RRS connection requests from an RRS client. Note that the RRS server executible file name on the RRS manufacturer's distribution tape may not follow the naming convention described here. Refere to the appropriate RRS module-specific section of this manual to see if this may be the case.

By default, the Win32 RRS server creates the RCS log file C:/tmp/rcssrv_<Controller_Type__Version>.log and the process ID file C:/tmp/rcssrv_<Controller_Type__Version>.pid. All RRS server startup/termination and RRS connection messages are recorded in the RRS log file. The RRS server application's process ID is stored in the process ID file. Optionally, by using the -log <RRS_Log_File> and -pid <Process_ID_File> options on the RRS server command line, user-specified RRS log and process ID file names can be used instead of these defaults.

Assuming the RRS server executibles follow the default file naming convention mentioned above, both Interix-based and Win32-based RRS server executibles for a given RRS module can simultaneously reside in the same <rcs_home_dir>\<RRS_Cntr_Type>\bin folder. You can then selectively bring up either version based on the instructions provided above.