Transports and Interfaces: Siebel Enterprise Application Integration > Java Message Service Transport > Detailed Input and Output Specifications >

Input Arguments Used by the Dispatch Step

Table 9 reflects the optionality of each input argument except user-defined properties and arguments used by the Dispatch step. An asterisk (*) denotes a required argument, OPT denotes an optional argument, and a dash (-) denotes an argument that is ignored.

Some special notes regarding particular values in Table 9:

• OPT²: These values are assigned to the reply message during the Send step.
• OPT⁵: One of 3 combinations is required for these method arguments: (DService && Dmethod), DWProcess, or DRuleSet.
• *¹: The JMSReplyTo header of the received message is ignored. The reply is always sent to the configured SendQueue. The JMSReplyTo header of the reply will be set to this value.
• -³: The JMSCorrelationID of the reply message cannot be set directly. The JMSCorrelationID of the reply message is set to the JMSCorrelationID of the received message, unless empty, in which case it is set to its JMSMessageID.
• -⁴: The JMSReplyTo header of the sent message is set to the value of the ReceiveQueue argument.
• +: An input argument that can also be used as an output argument.
• ++: For this input argument, a subsystem may be provided instead of the connection parameters. However, it must contain the same required method arguments as used for the connection parameters.
• +++: For this input argument, a subsystem may be provided instead of the dispatch parameters. However, it must contain the same required method arguments as used for the dispatch parameters.
• ++++: This input argument is used to process the output of the received message before dispatching.
• The ConnectionUsername and ConnectionPassword input parameters apply to IBM MQ only.
• The SendUsername, SendPassword, ReceiveUsername, ReceivePassword, TopicUsername, and TopicPassword input parameters apply to BEA WebLogic only.

In lieu of providing the arguments individually, the single argument ConnectionSubsystem may be provided. Its value must be the name of a valid named subsystem of type JMSSubsys, and it must include all of the arguments that are required by the method to which it is passed. See About the JMS Receiver for more information about that named subsystem.

JMS message properties are also supported as input arguments (properties) as described in JMS Headers and Properties.

Table 10 provides details for each input argument about the allowable values, default values, and special values, as well as the behavior if an invalid value is passed.