SendMultipleMessages |
This API sends multiple messages.
SOAP request
Example request
<?xml version="1.0"?> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Body> <SendMultipleMessages xmlns="http://schemas.cordys.com/jmsconnector/operations/3.0"> <jmsmessage> <destination>activemq.DefaultError</destination> <reply2destination>activemq.DefaultError</reply2destination> <createcorrelationid>true</createcorrelationid> <jmstype>QUEUE</jmstype> <messagetype>TEXT</messagetype> <messageformat>TEXT</messageformat> <message>Test</message> <persistentdelivery>true</persistentdelivery> </jmsmessage> <jmsmessage> <destination>activemq.DefaultError</destination> <reply2destination>activemq.SampleQueue</reply2destination> <createcorrelationid>true</createcorrelationid> <jmstype>QUEUE</jmstype> <messagetype>TEXT</messagetype> <messageformat>TEXT</messageformat> <message>@nd Message</message> <persistentdelivery>true</persistentdelivery> </jmsmessage> </SendMultipleMessages> </SOAP:Body> </SOAP:Envelope>
Request parameters
Parameter | Description | Mandatory | Accepted input values |
---|---|---|---|
destination | Destination identifier to send a message | Y | For dynamic destinations, the physical-name attribute can be added to the element to send the message to that queue or topic. The value is provider-specific, for example, queue://manager.queue . |
reply2destination | Destination identifier to which the recipient must reply | N | For dynamic destinations, the physical-name attribute can be added. |
correlationid | Correlation ID to be used | N | |
persistentdelivery | Attribute on the API node | N | The default value is true. |
expiration | Attribute on the API node | N | The default is no expiration. Note: The message expiration is in milliseconds. |
priority | Attribute on the API node | N | Message priority value (-1 to 9). |
jmstype | JMS type to be used | N | The possible values are:
|
properties | Properties of the message | N | Multiple properties can be sent. Properties have the following attributes to be sent:
|
messageformat | Contains base64 if the message node content is Base64 encoded, or the name of one of the configured BTC protocol names | N | If not set or empty, the message is sent as plain text. |
message | Message to send |
Y | If Binary Transformation is configured, this is expected as XML. Otherwise, you can have the following situations:
|
SOAP response
Example response
<SendMultipleMessagesResponse xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://schemas.cordys.com/jmsconnector/operations/3.0"> <messageid>ID:F0BSD02-60376-1430734216105-1:1:26:1:1</messageid> <messageid>ID:F0BSD02-60376-1430734216105-1:1:26:2:1</messageid> </SendMultipleMessagesResponse>
Response parameters
Parameter | Description |
---|---|
messageid | List of IDs of the sent messages |