Developing CA Gen WebSphere MQ Applications › Distributed Processing Server Implementation › Non-z/OS Environments

Non-z/OS Environments

The non-z/OS WebSphere MQ environments support a CA Gen DPS application execution in one of two ways. You can invoke a server manager by using one of the following methods:

• Started as a long-running daemon task.
• Invoked by a WebSphere MQ trigger monitor.

The difference between these two methods of execution is in how you invoke the server manager executable, and includes differences in the startup arguments. For information about the commands used to start the daemon, see Configuring Windows and UNIX Servers.

After the server manager starts, the server manager completes the following tasks:

1. Connects to its queue manager
2. Processes a request messages that has been delivered to the queue manager's local queue
3. Extracts the message ID and reply-to queue name from the request message
4. Incorporates the message ID into a response message (to become the correlation ID), and returns a reply message to the reply-to queue name.

The correlation ID in the reply message allows the CA Gen DPC to retrieve the corresponding response to a given request when the requesting DPC application is sharing a reply-to queue.

The non-z/OS CA Gen WebSphere MQ server managers support server-to-server flows using the WebSphere MQ Communication Runtime (the CFB MsgObj and WebSphere MQ CoopFlow). The server manager that initiates the flow takes on the role of the DPC.