SimpleJavaListener: IBM MQ SOAP Listener for Axis 1.4

Syntax and parameters for the IBM MQ SOAP listener for Axis 1.4.

Purpose

Starts the IBM MQ SOAP listener for Axis 1.4. Java™

Required parameters

URI platform: See URI syntax and parameters for web service deployment.
-?: Print out help text describing how the command is used.

Optional parameters

-a integrityOption

integrityOption specifies the behavior of IBM MQ SOAP listeners if it is not possible to put a failed request message on the dead-letter queue. integrityOption can take one of the following values:

DefaultMsgIntegrity: For non-persistent messages, the listener displays a warning message and continues to execute with the original message being discarded. For persistent messages, it displays an error message, backs out the request message so it remains on the request queue and exits. DefaultMsgIntegrity applies if the -a option is omitted, or if integrityOption is not specified.
LowMsgIntegrity: For both persistent and non-persistent messages, the listener displays a warning and continues to execute, discarding the message.
HighMsgIntegrity: For both persistent and non-persistent messages, the listener displays an error message, backs out the request message so it remains on the request queue and exits.

The deployment utility checks for the compatibility of the -x and -a flags. If -x none is specified, then -a LowMsgIntegrity must be specified. If the flags are incompatible the deployment utility exits with an error message and with no deployment steps having been undertaken.

-d msecs

msecs specifies the number of milliseconds for the IBM MQ SOAP listener to stay alive if request messages have been received on any thread. If msecs is set to -1, the listener stays alive indefinitely.

-i Context

Context specifies whether the listeners pass identity context. Context takes the following values:

passContext: Set the identity context of the original request message into the response message. The SOAP listener checks that it has authority to save the context from the request queue and to pass it to the response queue. It makes the checks at run time when opening the request queue to save context, and the response queue to pass context. If it does not have the required authority, or the MQOPEN call fails, and the response message is not processed. The response message is put on the dead-letter queue with the dead-letter header containing the return code from the failed MQOPEN. The listener then continues to process subsequent incoming messages as normal.
ownContext: The SOAP listener does not pass context. The returned context reflects the user ID under which the listener is running rather than the user ID which created the original request message.

The fields in the origin context are set by the queue manager, and not by the SOAP listener.

-n numThreads

numThreads specifies the number of threads in the generated startup scripts for the IBM MQ SOAP listener. The default is 10. Consider increasing this number if we have high message throughput.

-v

-v sets verbose output from external commands. Error messages are always displayed. Use -v to output commands that we can tailor to create customized deployment scripts.

-w serviceDirectory

serviceDirectory is the directory containing the web service.

-x transactionality

transactionality specifies the type of transactional control for the listener. transactionality can be set to one of the following values:

onePhase: IBM MQ one-phase support is used. If the system fails during processing, the request message is redelivered to the application. IBM MQ transactions ensure that the response messages are written exactly once.
twoPhase: Two-phase support is used. If the service is written appropriately the message is delivered exactly once, coordinated with other resources, within a single committed execution of the service. This option applies to server bindings connections only.
none: No transactional support. If the system fails during processing, the request message can be lost, even if persistent. The service might or might not have executed, and response, report or dead-letter messages might or might not be written.

The deployment utility checks for the compatibility of the -x and -a flags. See the description of the -a flag for details.

Java Example

java com.ibm.mq.soap.transport.jms.SimpleJavaListener
-u "jms:/queue?destination=myQ&connectionFactory=()
&initialContextFactory=com.ibm.mq.jms.Nojndi"
-n 20