IBM MQ
You can configure IBM MQ as either a source or a target.
To configure the connection details for IBM MQ in your Micro-Integration, see IBM MQ Connection Parameters
You must also define at least one Micro-Integration Flow that specifies:
-
the endpoints where data is consumed from and published to. For more information, see Micro-Integration Flow Parameters.
-
how the header and payload fields should be mapped. For more information, see Mapping Headers and Payloads
For a listing of available message headers, see IBM MQ Message Headers.
IBM MQ Connection Parameters
The following tables describe the connection parameters for IBM MQ. The parameters differ depending on whether you choose to use a native connection or a JNDI lookup.
Native Connection
| Field | Description |
|---|---|
| Connection Name | The name of the connection to IBM MQ, such as the hostname or IP address. For example, 123.123.123.123(1414), where 123.123.123.123 is the host and 1414 is the port. Defaults to localhost(1414). |
| Username | The username to authenticate with IBM MQ. |
| Password | The password to authenticate with IBM MQ. |
| Queue Manager | The name of the queue manager on IBM MQ. For example: QM1. |
| Channel | The channel on IBM MQ. For example, DEV.APP.SVRCONN. |
| Additional Connection Properties |
(Optional) The IBM MQ connection properties (refer to the IBM MQ documentation). Click Add Context if you need to specify additional context properties. |
JNDI Lookup
| Field | Description |
|---|---|
| JNDI Context |
The IBM MQ connection properties (refer to the IBM MQ documentation). The required connection properties are as follows:
(Optional) Click Add Context if you need to specify additional contexts. |
| Connection Factory Name | The name of the JMS connection factory that defines the properties for the connection. |
| Username | The username to authenticate with IBM MQ. |
| Password | The password to authenticate with IBM MQ. |
Micro-Integration Flow Parameters
You must configure the endpoint parameters for each Flow. Each Flow can have different settings, but they all share the connection details of the parent Micro-Integration. These parameters differ depending on whether IBM MQ is configured as a source or a target.
IBM MQ Source Parameters
The following table describes the parameters for configuring IBM MQ as a source.
| Field | Description |
|---|---|
| Destination Type | Select TOPIC or QUEUE when the destination name is known, otherwise use UNKNOWN for a JNDI lookup. |
| Destination | The binding identifier of the queue in IBM MQ. For example: my-ibmmq-target-queue_mqConnector_mq_sourceQ_10. |
| Durable Subscription Name |
The name of the durable subscription multiple consumers can bind to. Durable subscriptions accumulate messages even when all consumers are offline, ensuring that no messages are lost. This field is required when Destination Type is TOPIC. It is also required if Destination Type is UNKNOWN and the destination resolves to a topic. |
IBM MQ Target Parameters
The following table describes the parameters for configuring IBM MQ as a target.
| Field | Description |
|---|---|
| Destination Type | Select TOPIC or QUEUE when the destination name is known, otherwise use UNKNOWN for a JNDI lookup. |
| Destination | The binding identifier of the queue in IBM MQ. For example: my-ibmmq-source-queue_mqConnector_mq_sourceQ_10. |
| Transacted | Indicates whether the JMS producer publishes messages from a received batch using a local transaction. Setting transacted to true provides duplicate protection in case of producer failures. The option is enabled by default. |