How To Start and Stop IA daemons

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

IA daemons – Stopping and Starting

Version 1.1

1. Introduction

This is a description of how to stop and start the IA daemons. These daemons comprise the IA autodispense testing capability on High Volume systems.

This document describes the steps necessary to :

a) stop all IA daemons

b) Start all IA daemons

c) Restart the Simulator to NAK every order item

d) Restart the simulator to ACK avery order item

2. Prerequisites

· High Volume build 5.4.1 +, which includes the IA AutoDispense software

· access to the UNIX application server for the relevant IA environment

· project user id and password (qacf/qacf)

· Optionally, know the port numbers being used for sending and receiving messages form and to the services

3. Steps

3.1 Stop All IA daemons

  1. Determine whether or not any IA daemons are running

ps –ef | grep IA

  2. Note the process Ids (PIDs) of the IA daemons ( RMS, Simulator and Symphony, see notes)

  3. Stop the RMS router daemon

cd /qacf/java/rms/ia_adisp

  4. Stop the Symphony Service daemon

cd /qacf/java/rms/ia_adisp/symphony

  5. Stop the Simulator daemon

kill nnnnn where nnnnn is the process id of a process. Repeat for each of the processes.

3.2 Start All IA daemons

1. login as qacf

2. cd to the IA directory:

cd /qacf/java/rms/ia_adisp

3. Start the Simulator

cd simulator

4. Start the Symphony Service

cd /qacf/java/rms/ia_disp/symphony

5. Start the RMS router

cd /qacf/java/rms/ia_adisp

3.3 Start simulator to ACK all items

1. Determine if the simulator is ACKing or NAKing

2. Kill the simulator

ps –ef | grep RunEcho

kill nnnnn

3. Start the simulator

cd /qacf/java/rms/ia_adisp/simulator

3.4 Start simulator to NAK all items

1. Determine if the simulator is ACKing or NAKing

2. Kill the simulator

ps –ef | grep RunEcho

'kill nnnnn

3. Start the simulator

cd /qacf/java/rms/ia_adisp/simulator

4. Notes

1. Output from the ps command

The first number in the ‘ps’ output line for a process is the Process Identifier (PID). This is the number needed when killing the process.

2. Names of daemons

The Java classes that comprise the daemons are as follows:


Java class name

Print Server








3. start scripts not returning

The start scripts do not “return”, that is after executing a script the user is not prompted to enter a new command. The window you are using muyst be preserved for the duration of the running of the daemon. To perofrm other UNIX command syou ahve to start an additional UNIX session

4. order of daemon start up

The recommended order for starting the daemons is as follows:

a) Print Server

b) Simulator

c) Symphony

d) RMS router

5. Port Numbers

The daemons and MailRx use TCP ports to communicate, as follows




specified by

MailRx RMS


sending and receiving XML RPC packets

Symphony Service


sending and receiving XML RPC packets and sending XML requests (to the simulator)



recieving and sending XML requests and responses, and sending XMLRPC requests to MailRx

command line (-D) options in simulator command