Managing services

Service objects are a way of defining programs to be executed when a queue manager starts or stops. The programs can be split into the following types:

• Servers: A server is a service object that has the parameter SERVTYPE specified as SERVER. This is a program that will be executed once a specified queue manager is started.
  Only one instance of a server process can be executed concurrently. While running, the status of a server process can be monitored using the MQSC command, DISPLAY SVSTATUS. Typically, server service objects are definitions for programs such as dead letter handlers or trigger monitors. Potential programs can include those not supplied with WebSphere® MQ. Additionally, a server service object can include a command to shut down the program concurrently with queue manager shut-down.

• Commands: A command service object is the definition of a program to be executed when a specified queue manager is started or stopped. A command is a service object that has the parameter SERVTYPE specified as COMMAND. Multiple instances of a command process can be executed concurrently.

Command service objects differ from server service objects: once the program is executed, the queue manager does not monitor the program. Typically, such programs are short lived and specifically designed to start one or more additional tasks.

Select Services from the Navigation Panel to open its Summary View:

Summary view operations available from the Operations drop-down menu are: Copy As New Service, Start, Stop, Delete, Permissions, Audit, Tag Service.

To access the selected Service's Properties Editor, click on the Service Name. Status, Type and Start Mode are the most immediately relevant. Service type relates directly to the generic description at the start of this section.