jmsReceiveMsg script operation
Receives a JMS Message. Times
out after TIMEOUT milliseconds. If INBOUNDQUEUE is not null, looks
on that queue. If ctx is provided, INBOUNDQUEUE is assumed to be a
JNDI name: otherise INBOUNDQUEUE is assumed to be a queue name in
vendor-specific format. If INBOUNDQUEUE is null, and MESSAGETORECEIVEREPLYFOR
is not null, looks on the queue defined in the "Reply-To" field of
MESSAGETORECEIVEREPLYFOR. If INBOUNDQUEUE is null and MESSAGETORECEIVEREPLYFOR
is null, throws an AustinException. We now know which queue will be
used. If MESSAGESELECTOR and MESSAGETORECEIVEREPLYFOR are both null,
selects the first message from that queue. Otherwise selects the first
message from the queue (if any) fulfilling all of the conditions defined
by MESSAGESELECTOR and MESSAGETORECEIVEREPLYFOR. If MESSAGETORECEIVEREPLYFOR
is not null, rejects any message not having a correlation ID equal
to MESSAGETORECEIVEREPLYFOR's message ID. If MESSAGESELECTOR is not
null, rejects any message not fulfilling the condition defined in
messageSelector. If no appropriate message is found, returns null.
jmsReceiveMsgFromQueue script operation
Receives a JMS Message. Times out after
TIMEOUT milliseconds. If INBOUNDQUEUE is not null, looks on that queue. If
INBOUNDQUEUE is null, and MESSAGETORECEIVEREPLYFOR is not null, looks on the
queue defined in the "Reply-To" field of MESSAGETORECEIVEREPLYFOR. If INBOUNDQUEUE
is null and MESSAGETORECEIVEREPLYFOR is null, throws an AustinException. We
now know which queue will be used. If MESSAGESELECTOR and MESSAGETORECEIVEREPLYFOR
are both null, selects the first message from that queue. Otherwise selects
the first message from the queue (if any) fulfilling all of the conditions
defined by MESSAGESELECTOR and MESSAGETORECEIVEREPLYFOR. If MESSAGETORECEIVEREPLYFOR
is not null, rejects any message not having a correlation ID equal to MESSAGETORECEIVEREPLYFOR's
message ID. If MESSAGESELECTOR is not null, rejects any message not fulfilling
the condition defined in messageSelector. If no appropriate message is found,
returns null.
jmsSendMsg script operation
Sends message MSG and returns
MSG or null. The message is sent to the queue specified by OUTBOUNDQUEUE,
unless OUTBOUNDQUEUE is null. If ctx is provided, OUTBOUNDQUEUE is
assumed to be a JNDI name. If ctx is not provided, OUTBOUNDQUEUE is
assumed to be a queue name in vendor-specific format. If OUTBOUNDQUEUE
is null, MSG is sent to the reply-to queue of MESSAGETOREPLYTO, if
MESSAGETOREPLYTO is provided. If OUTBOUNDQUEUE is null and MESSAGETOREPLYTO
is not provided, throws an AustinException. If MESSAGETOREPLYTO is
provided, the message id is read from it. PROPERTIES is a map from
string keys to string values. There is one special (non-JMS) key:
"TRIGO_INCOMING_REPLY_QUEUE". "TRIGO_INCOMING_REPLY_QUEUE" indicates
the queue name to which an external application should send replies
to this message. If ctx is provided, the value of "TRIGO_INCOMING_REPLY_QUEUE"
is assumed to be a JNDI name; otherwise it is assumed to be a queue
name in vendor-specific format.
jmsSendMsgToQueue script operation
Sends message MSG and returns MSG or
null. The message is sent to the queue specified by OUTBOUNDQUEUE, unless
OUTBOUNDQUEUE is null. If OUTBOUNDQUEUE is null, MSG is sent to the reply-to
queue of MESSAGETOREPLYTO, if MESSAGETOREPLYTO is provided. If OUTBOUNDQUEUE
is null and MESSAGETOREPLYTO is not provided, throws an AustinException. If
MESSAGETOREPLYTO is provided, the message id is read from it. PROPERTIES is
a map from string keys to string values with a single key value that is acted
on. This special (non-JMS) key is "TRIGO_INCOMING_REPLY_QUEUE" whose value
is a javax.jms.Queue object to which an external application should send replies
to this message.
IBM InfoSphere Master Data Management, Version 11.3
Last updated: 9 May 2014