IBM MQ Put Activity
Use this activity to place messages on to a queue.
Configuration
The Configuration tab has the following fields:
| Field | Description |
|---|---|
| Connection | Select the connection appropriate for this flow |
| GenCorrelationID | Enable to generate a unique correlation ID when the message is sent. This unique ID is displayed on the output schema for reference by any activity that needs it. |
| Context Support | Select any one of the available options: Default, Identity, or All context to access the corresponding fields. Specific permissions are required on the server to set values in the fields corresponding to these contexts. |
| Message Type | Select one of the available options: Datagram, Request, or Reply to configure an appropriate type of message. |
| Value Deserialiazer | Select one of the options:
String or
JSON.
If JSON is selected a entry area for the JSON schema is provided. |
Input Settings
The Input Settings tab displays the input schema of the activity as a tree structure. The schema varies according to the object that you selected on the Configuration tab. You can provide the input values in the Flogo Connector for mapping input fields directly or use Mapper to map the input values to a field from the output of a preceding activity in the flow.
The Input Settings tab has the following fields:
| Field | Description |
|---|---|
| Destination | Enter the queue name to which the message will be sent. It can be overridden on the input tab. |
| Destination Queue Manager | Enter the name of the queue manager which owns the queue. Only supported for clustered queue managers. Can be overridden on the Input tab. |
| Schema for JSON Value | Enter a JSON schema for the message if the value deserializer was set to JSON. This schema will be presented on the Input tab. |
| Properties | Click Add Row button to add each string property. Properties are displayed on the input schema under the MessageProperties node. |
Input
The Input tab has the following fields:
| Field | Description |
|---|---|
| queue | Map a dynamic queue for the PUT operation. |
| queueMgr | Map a dynamic queue manager for the PUT operation. It is only supported for clustered queue managers. |
| MessageString | Map a string to this field. It will be copied to the body of the message. |
| CorrelId | If GenCorrlationID is not specified on the Configuration tab then a value can be mapped here. If the values is base64 encoded it will be decoded before being used, otherwise the bytes from the mapped string will be used. |
| MsgId | Message IDs are normally generated by the queue manager in order to guarantee uniqueness, but can be overridden on the put. If the values is base64 encoded it will be decoded before being used, otherwise the bytes from the mapped string will be used. |
| Encoding | Specifies the encoding of floating point data in the message. |
| CodedCharSetId | Specifies the encoding for string data in the message and its properties |
| Format | A free form of a string variable which describes the format of the message. The default value is MQSTR. |
| Priority | An integer field describing the queue manager's delivery priority. The default value is 4. |
| Expiry | Enter the number of tenths of a second for which the message stays on the queue before it is deleted. |
| ReplyToQ | Enter the name of the queue to which a reply can be sent. |
| ReplyToQmgr | Enter the name of the queue manager hosting the reply to the queue. This is only applicable for clustered queue managers. |
Copyright © Cloud Software Group, Inc. All rights reserved.
