Starting and Stopping RMC3 Data Collection on ERP LN

Use the following list as a guide in starting and stopping data collection using the RMC3 Middleware. Some installations may not use all components (for example, Query Server may not be used in your data collection system). The following list shows the components to start up, where they are usually running, and the steps/command to start and stop that component.
 
Start: Windows: double-click on RMC3Command40.jar (a desktop shortcut, or in the CC directory). (If installing on a new PC, copy the entire CC directory from the Data Collection PC. The first time you open a Command Client, you need to specify the server and port of the Command Server to which you want to connect: see File/Options.)
 
Stop: Press X in the upper right (or right-click and Close).
 
  • RMC3 Command Server (Data Collection PC, i.e., the machine where RMC3 Local, Command Server and MidL typically run)
Start: Windows: double-click on the shortcut to runcs.bat on the desktop. (The .bat file itself should be in the CC directory, e.g., C:\CRMC\RMC3\CC.)
 
Stop: Press Control-C in the Command window (or right-click and Close).
 
Start:  
  • Windows: runs as a Windows service, usually set to auto-start. (There should be a shortcut on the desktop to Services; or see Control Panel/Administrative Tools/Services. Open Services, and there will be a list of available services. Each RMC3 Local will be shown as ‘RMC3 Local Thread [thread name]’. The Status shows whether or not it’s running. The Startup Type is generally set to Automatic, at least for production threads.)
 
  • UNIX/Linux: login as the correct user, run runrmc3 script. (The script should be in $RMC3_RUN/bin, e.g., /usr/local/rmc3/bin.)
 
Note: RMC3 Local can also be started from the RMC3 Command Client, if properly configured.
 
Stop: Right-click on the Local in Command Client, and ‘Stop RMC3 Local’. (Or, go to the machine where Local is running, and stop the service [Windows]; or kill the process ID [UNIX/Linux].)
 
Start:  
  • Windows: double-click on the shortcut to startmidl.bat on the desktop. (The .bat file itself should be in the %RMC3_RUN%\bin directory, e.g., C:\CRMC\rmC3\Bin.)
 
  • UNIX/Linux: login as the correct user, run startmidl script. (The script should be in $RMC3_RUN/bin, e.g., /usr/local/rmc3/bin.)
 
Note: MidL can also be started from the RMC3 Command Client if properly configured.
 
Stop: Right-click on MidL in Command Client, and ‘Stop Application Server’. (Or, go to the machine where MidL is running, and press Control-C, or right-click and Close [Windows]; or kill the process ID [UNIX/Linux].)
 
 
Start: From a Worktop session, run tmboaserver, start Bus Component(s).
NOTE: If more than one Bus Component is used, each should be started from its own tmboaserver session, from a separate Worktop session.
 
Stop: Find the tmboaserver session (“Adapter for Baan”) corresponding to the Bus Component you wish to stop, and press Stop. NOTE: If a restart is required, restart the tmboaserver session, not just the Bus Component(s) within it.
If the Bus Component is started from a batch file, just close the window that it is running in.
Start: Windows: startqcentral.bat.  (There should be a shortcut to this file on the desktop; or see the %RMC3_RUN%\bin directory, e.g., C:\CRMC\rmC3\Bin.)
 
Stop: Press Control-C in the Command window (or right-click and Close).
 
NOTE: If any changes are made to the queryserver.xml file, both QueryCentral and the Local(s) corresponding to the affected thread(s) must be re-started, preferably in that order.
 
Start:
  • Windows: startqrun.bat. (There should be a shortcut to this file on the desktop; or see the %RMC3_RUN%\bin directory, e.g., C:\CRMC\rmC3\Bin.)
 
  • UNIX/Linux: login as the correct user, run startqrun script. (The script should be in $RMC3_RUN/bin, e.g., /usr/local/rmc3/bin.)
 
Stop:    Windows: press Control-C in the Command window (or right-click and Close).
UNIX/Linux: find the corresponding process ID, and kill it.
 
 
Note: the preferred sequence for starting the query pieces is Query Run, Query Central, and then Local. The two Query components should be started the first time from a command prompt, so if there are system errors, these will be seen on the screen.
 
 

Add Feedback