SonicMQ - send a message
Search form
Description - Emits data using the Sonic version of JMS to a queue or topic
Runtime Class - com.ibi.agents.XDSonicEmitAgent
Configuration
This action requires a Generics Configuration as well as the following required parameters.
Parameter Groups
Parameter Type Description Type: string Class of message sent. Dynamic will select BytesMessage, TextMessage or MapMessage depending on the document contents.
Select from one of the following options:
- BytesMessage {bytes}
- Dynamic {dynamic}
- MapMessage {map}
- TextMessage {text}
Acknowledgement: string Makes the JMS Session transactional or else specifies how received messages are acknowledged
Select from one of the following options:
- Auto Acknowledge {auto} - the session automatically acknowledges a client's receipt of a message when it has either successfully returned from a call to receive or the message listener it has called to process the message successfully returns.
- Client Acknowledge {client} - the client acknowledges a message by calling a message's acknowledge method.
- Dups OK Acknowledge {dupsok} - Instructs the session to lazily acknowledge the delivery of messages.
- Session Transacted {trans} - Specifies that the session should use a local transaction
Priority: integer Outgoing message priority. Value must be between 0 and 9, with 9 most expedited. If omitted uses incoming priority.
* - denotes required
Parameter Type Description CorrelationID: string Value of the JMSCorrelationID header field
ReplyTo: string Value of the JMSReplyTo header field
Type: string Value of the JMSType header field
Protocol: string Special register namespace from which protocol headers for the outbound request will be taken.
Select from one of the following options:
- Default Namespace {default}
- None {none}
* - denotes required
Parameter Type Description Output Document: string
Select from one of the following options:
- Status Document {status} - Document that reflects the agent status
- Input Document {input} - Original document that was supplied to the object
* - denotes required
Output Events
Runtime Class - com.ibi.agents.XDSonicEmitAgent
Configuration
This action requires a Generics Configuration as well as the following required parameters.
Parameter Groups
Parameter Type Description Type: string Class of message sent. Dynamic will select BytesMessage, TextMessage or MapMessage depending on the document contents.
Select from one of the following options:
- BytesMessage {bytes}
- Dynamic {dynamic}
- MapMessage {map}
- TextMessage {text}
Acknowledgement: string Makes the JMS Session transactional or else specifies how received messages are acknowledged
Select from one of the following options:
- Auto Acknowledge {auto} - the session automatically acknowledges a client's receipt of a message when it has either successfully returned from a call to receive or the message listener it has called to process the message successfully returns.
- Client Acknowledge {client} - the client acknowledges a message by calling a message's acknowledge method.
- Dups OK Acknowledge {dupsok} - Instructs the session to lazily acknowledge the delivery of messages.
- Session Transacted {trans} - Specifies that the session should use a local transaction
Priority: integer Outgoing message priority. Value must be between 0 and 9, with 9 most expedited. If omitted uses incoming priority.
* - denotes required
Parameter Type Description CorrelationID: string Value of the JMSCorrelationID header field
ReplyTo: string Value of the JMSReplyTo header field
Type: string Value of the JMSType header field
Protocol: string Special register namespace from which protocol headers for the outbound request will be taken.
Select from one of the following options:
- Default Namespace {default}
- None {none}
* - denotes required
Parameter Type Description Output Document: string
Select from one of the following options:
- Status Document {status} - Document that reflects the agent status
- Input Document {input} - Original document that was supplied to the object
* - denotes required
Output Events
Configuration
This action requires a Generics Configuration as well as the following required parameters.Parameter Groups
| Parameter | Type | Description | |
|---|---|---|---|
| Type: | string | Class of message sent. Dynamic will select BytesMessage, TextMessage or MapMessage depending on the document contents.
Select from one of the following options:
|
Acknowledgement: | string | Makes the JMS Session transactional or else specifies how received messages are acknowledged
Select from one of the following options:
|
Priority: | integer | Outgoing message priority. Value must be between 0 and 9, with 9 most expedited. If omitted uses incoming priority. |
* - denotes required
| Parameter | Type | Description | |
|---|---|---|---|
| CorrelationID: | string | Value of the JMSCorrelationID header field | ReplyTo: | string | Value of the JMSReplyTo header field | Type: | string | Value of the JMSType header field | Protocol: | string | Special register namespace from which protocol headers for the outbound request will be taken.
Select from one of the following options:
|
* - denotes required
| Parameter | Type | Description | |
|---|---|---|---|
| Output Document: | string |
Select from one of the following options:
|
* - denotes required
Output Events
| Name | Description |
|---|---|
| OnFailConnection | Could not connect to the external system. |