This topic contains the following sections:
Use the JMSInput node to receive messages from JMS destinations. JMS destinations are accessed through a connection to a JMS provider. The JMSInput node acts as a JMS message consumer and can receive all six message types that are defined in the Java Message Service Specification, version 1.1. Messages are received by using method calls, which are described in the JMS specification.
The JMSInput node is represented in the workbench by the following icon:
Message flows that handle messages that are received from connections to JMS providers must always start with a JMSInput node. If you include an output node in a message flow that starts with a JMSInput node, it can be any of the supported output nodes (including user-defined output nodes); you do not need to include a JMSOutput node. However, if you do not include a JMSOutput node, you must include the JMSMQTransform node to transform the message to the format that is expected by the output node.
If you are propagating JMS messages and creating a message flow to use as a subflow, you cannot use a standard input node; you must use an instance of the JMSInput node as the first node in order to create an In terminal for the subflow.
You can use the -c parameter on the mqsichangeproperties command to change the property settings for an object name that already exists in the broker persistent store. For a JMS provider, this object name is a JMS Provider name. Use the mqsideleteconfigurableservice command to delete a JMS provider resource that was created by the mqsicreateconfigurableservice command.
You can use the -c parameter on the mqsireportproperties command to report on the properties of any JMS provider resource (both default and user-defined).
When you have put an instance of the JMSInput node into a message flow, you can configure it. To display its properties, either double-click the node, or right-click the node and click Properties.
All mandatory properties that do not have a default value defined are marked with an asterisk.
Configure the JMSInput node as follows:
com.sun.jndi.fscontext.RefFSContextFactory, which defines the file-based initial context factory for the WebSphere MQ JMS provider.
To identify the name of the Initial Context Factory for the JMS provider, refer to the JMS provider documentation.
When you enter a value for Location JNDI Bindings, ensure that it complies with the following instructions:
For information about constructing the JNDI administered objects bindings file, refer to the documentation that is supplied with the JMS provider.
Leave Message Set blank for XML, XMLNS, JMS, , and BLOB parsers.
Leave Message Type blank for XML, XMLNS, JMS, , BLOB, and parsers.
Leave Message Format blank for XML, XMLNS, JMS, , and BLOB parsers.
Leave this property blank if you do not want the input node to make a selection based upon application property. Refer to JMS message selectors for a description of how to construct the message selector.
Leave this property blank if you do not want the input node to make a selection based on JMSTimeStamp.
Valid values for message priority are from 0 (lowest) to 9 (highest); for example, you can enter 5 to receive messages of priority 5. You can also qualify the selector; for example, > 4 to receive messages with a priority greater than 4, or BETWEEN 4 AND 8 to receive messages with a priority in the range 4 to 8.
Leave this property blank if you do not want the input node to make a selection based on JMSPriority.
Enter a specific Message ID, or enter a conditional selector; for example, enter > WMBRK123456 to return messages where the Message ID is greater than WMBRK123456.
Leave this property blank if you do not want the input node to make a selection based on JMSMessageID.
Enter a specific Correlation ID or enter a conditional string; for example, WMBRKABCDEFG returns messages with a Correlation ID that matches this value.
Leave this property blank if you do not want the input node to make a selection based on JMSCorrelationID.
For each message that is received successfully, the JMSInput node routes the message to the Out terminal. If this action fails, the message is retried. If the retry threshold is reached, where the threshold is defined by the BackoutThreshold property of the node, the message is routed to the Failure terminal. You can connect nodes to the Failure terminal to handle this condition. If you have not connected nodes to the Failure terminal, the message is written to the backout destination. If a backout destination has not been provided, the node issues a BIP4669 error message and stops processing further input.
If the message is caught by the JMSInput node after an exception has been thrown elsewhere in the message flow, the message is routed to the Catch terminal. If you have not connected nodes to the Catch terminal, the node backs out messages for re-delivery until the problem is resolved, or the backout threshold is reached.
You must define a backout destination. If you do not define a backout destination, the node issues a BIP4669 error message and stops processing further input.
When you include a JMSInput node in a message flow, the value that you set for Transaction Mode defines whether messages are received under syncpoint.
The JMS provider can supply additional .jar files that are required for transactional support. Refer to the JMS provider documentation. For example, on distributed systems, the WebSphere MQ JMS provider supplies an extra .jar file: com.ibm,mqetclient.jar. You must add this .jar file to the broker shared-classes directory. Refer to Making the JMS provider client available to the JMS nodes in this topic.
install_dir/bin/ JMSSwitch.dll XAOpenString=Initial Context,location JNDI,Optional_parms ThreadOfControl=THREAD
install_dir/bin/ JMSSwitch.dll XAOpenString=Initial Context,location JNDI,Optional_parms ThreadOfControl=THREAD
XAResourceManager: Name=Jms_Provider_Name SwitchFile=/install_dir/bin/ JMSSwitch.so XAOpenString=Initial Context,location JNDI,Optional_parms ThreadOfControl=THREADWhere:
The optional parameters are comma separated and are positional. Therefore, any parameters that are missing must be represented by a comma.
install_dir/classes/xarecovery.jar
install_dir/bin
Refer to the WebSphere MQ System Administration Guide for more information.
To use the same queue manager for both the broker and the JMS provider, ensure that your WebSphere MQ installation is at the minimum required level: Version 5.3 CSD12 or Version 6 FixPack 1.
Syncpoint control for the JMS provider is managed with RRS syncpoint coordination of the queue manager of the broker. You do not need to modify the .ini file.
The terminals of the JMSInput node are described in the following table.
Terminal | Description |
---|---|
Failure | The output terminal to which the message is routed if an error occurs. Even if the Validation property is set, messages propagated to this terminal are not validated. |
Out | The output terminal to which the message is routed if it is successfully retrieved. |
Catch | The output terminal to which the message is routed if an exception is thrown downstream and caught by this node. |
The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the bar file to deploy it).
The Description properties of the JMSInput node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Node name | No | No | The node type | The name of the node. |
Short Description | No | No | A brief description of the node. | |
Long Description | No | No | Text that describes the purpose of the node in the message flow. |
The JMS Connection properties of the JMSInput node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Initial Context Factory | Yes | Yes | com.sun.jndi.fscontext.RefFSContextFactory | This property is the starting point for a JNDI name
space. A JMS application uses the initial context to obtain and look up the
connection factory and queue or topic objects for the JMS provider. The default value is that value used when WebSphere MQ Java is used as the JMS provider. |
Location JNDI Bindings | Yes | Yes | The system path or the LDAP location for the bindings file. | |
Connection Factory Name | Yes | Yes | The name of the connection factory that is used by the JMSInput node to create a connection to the JMS provider. | |
Backout Destination | No | Yes | The destination that is used by the JMSInput node when a message cannot be processed by the message flow because of errors in the message. | |
Backout Threshold | No | Yes | 0 | The value that controls when a re-delivered message is put to the backout destination. |
The Advanced properties of the JMSInput node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Transaction Mode | Yes | No | none | This property controls whether the incoming message is received under external syncpoint, local syncpoint, or out of syncpoint. Valid values are none, local, and global. |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac24820_ |