Open topic with navigation

TIBCO Flogo® Connector for IBM MQ 2.2.0

# IBM MQ Publish Activity

Use this activity to publish a message to a topic.

## Configuration

The Configuration tab has the following fields:

Field | Description
--- | ---
Connection | Select the connection appropriate for this flow
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 Deserializer | Select one of the options: String or JSON. If JSON is selected an 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 Value Deserializer field you selected on the Configuration tab. The values entered on the Input Settings tab are static and optional. They can be overridden on the Input tab.

The Input Settings tab has the following fields:

Field | Description
--- | ---
Topic Name | Enter the name of the administratively defined topic. For an indication of the actual topic string to which it relates, see the topic definition on the server. It is mandatory to provide a Topic field or a Topic Dynamic field either on the Input Settings tab or the Input tab.
Topic Dynamic | Enter the dynamic part of the topic name. The contents of this field are appended to the topic string represented by the Topic field. It is mandatory to provide a Topic field or a Topic Dynamic field either on the Input Settings tab or the Input tab.
Retain Publication | Enable this field to retain this publication for offline subscribers.
Schema for JSON Value | Enter a JSON schema for the message. This schema is displayed 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. Note: The messages that are expected to contain properties can be mapped here. It is necessary to map properties that are used in the flow.

## Input

The Input tab has the following fields:

Field | Description
--- | ---
Topic | (Optional) Map the name of the administratively defined topic. For an indication of the actual topic string to which it relates, see the topic definition on the server. It is mandatory to provide a Topic field or a Topic Dynamic field either on the Input Settings tab or the Input tab.
Topic Dynamic | (Optional) Map the dynamic part of the topic name. The contents of this field are appended to the topic string represented by the Topic field. It is mandatory to provide a Topic field or a Topic Dynamic field either on the Input Settings tab or the Input tab.
MessageString | Map a string to this field. It is copied to the body of the message.

MQMD Headers
Field | Description
--- | ---
CorrelId | Map a correlation ID here. If the value is base64 encoded it is decoded before being used, otherwise the bytes from the mapped string is used.
MsgId | Message IDs are normally generated by the queue manager to guarantee uniqueness, but can be overridden on the put. If the value is base64 encoded it is decoded before being used, otherwise, the bytes from the mapped string are 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 which is set to the message property. The default value is 0 but it can be overridden by the sending application.
Expiry | The number of tenths of a second for which the message stays on the queue before it is deleted.
ReplyToQ | The name of the queue to which a reply can be sent.
ReplyToQmgr | The name of the queue manager hosting the reply to the queue. This is only applicable for clustered queue managers.
UserIdentifier | Enter the user ID to be used when authorizing this message as it traverses the messaging system. For operations with report options, this field is mandatory. If a value is not provided here, it is taken from the connection resource if one is available there, and from the environment, if it is not.
AccountingToken | Enter a binary (base 64 encoded) accounting token to be used on host systems to assist in accounting for resources used by the application.
ApplIdentityData | Enter a string that can be used on all endpoints to identify this application. The maximum length is 32 bytes.
PutApplType | Enter value describing the sending application. For more information about this field on various platforms, see IBM MQMD documentation.
PutApplName | Enter the name of the application as determined by the client library.
ApplOriginData | Enter an additional information about the nature of the sending application.

## Output

The Output tab has the following fields:

Field | Description
--- | ---
CorrelId | The correlation ID for the sent message.
MsgId | The message ID for the sent message.

## Iterator

Use the Iterator tab to iterate a certain piece of logic multiple times. If you leave this tab blank, the activity is executed only once. For more information about Iterator, see "Using the Iterator in an Activity" in the TIBCO Flogo® apps documentation.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Flogo® Connector for IBM MQ

Copyright © 2019-2025. Cloud Software Group, Inc. All Rights Reserved.