Outgoing connections - JMS WebSphere MQ

Overview

Used to create, update, delete and browse through outgoing JMS WebSphere MQ connections.

Each outgoing connection represents a link through which MQ messages are sent by Zato services.

Creating or updating a connection (re-)establishes a link to a queue manager and there are as many connectors and connections to any queue manager as there are active outgoing connections and channels in a cluster.

For instance, if there is 1 definition and 5 outgoing connections using it, there will be 5 connector processes started in a cluster each maintaining 1 connection to the queue manager pointed to by the definition.

Sending messages to a queue manager is an asynchronous activity - messages are not rolled back to Zato services if there are any errors along.

../../_images/jms-wmq2.png

Create and Edit

../../_images/jms-wmq-create1.png
Header Notes
Name Connection name
Active Documented below
Definition JMS WebSphere MQ definition to read basic connection information from
Delivery mode Whether messages send should be persistent by default or not
Encoding (Optional) Default message encoding
Expiration (Optional) After how many milliseconds messages should expire

Each optional value can be overridden by a service making use of the outgoing connection.

Delete

../../_images/jms-wmq-delete2.png

Stops the underlying connector and deletes the connection from ODB.

The ‘Active’ flag

If an outgoing connection is made inactive and there are services still making use of it, the messages services send will be lost.

You need to ensure no service is able to reach an outgoing connection before it’s turned off - otherwise you will lose messages.

Also an inactive outgoing connection closes its underlying link to a queue manager but the connector’s process continues to run.