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, which 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 an JMSInput node, it can be any of the supported output nodes (including user-defined output nodes); you do not have to include an 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.
For distributed platforms, copy the java .jar files and any native libraries for the JMS provider client into a the broker shared-classes directory. For example, on Windows C:\Documents and Settings\All Users\Application Data\IBM\MQSI\shared-classes. This ensures that the java class path for the JMS nodes is set correctly.
For z/OS, there is no shared-classes directory. Instead you must specify each JMS provider java .jar file in the class path in the BIPPROF member of the broker’s PDS (Partitioned Data Set). Then update the LIBPATH with any native libraries, and submit the BIPGEN JCL job to update the broker ENVFILE.
When you have put an instance of the JMSInput node into a message flow, you can configure it. Right-click the node in the editor view and click Properties. The basic properties of the node are displayed in the properties dialog.
All mandatory properties that do not have a default value defined are marked with an asterisk on the properties dialog.
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 is compliant 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, JMSMap, JMSStream, , and BLOB parsers.
Leave this property blank if you do not want the input node to select 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 select 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 select 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 the WMBRK123456.
Leave this property blank if you do not want the input node to make a selection based on JMSMessageID.
Enter FALSE if the input node accepts only messages that have not been redelivered by the JMS Provider.
Enter TRUE if the input node accepts only messages that have been redelivered by the JMS Provider.
Leave this property blank if you do not want the input node to select based on JMSRedelivered.
Enter a specific Correlation ID or enter a conditional string; for example, WMBRKABCDEFG returns messages whose Correlation ID matches this value.
Leave this property blank if you do not want the input node to select based on JMSCorrelationID.
If you want to Use XMLNSC Compact Parser for XMLNS Domain select the check box.
For Mixed Content Retain Mode, Comments Retain Mode, and Processing Instructions Retain Mode, the drop-down boxes offer the following choices:
Click Cancel to close the dialog and discard all the changes that you have made to the properties.
For each message that is received successfully, the JMSInput node routes the message to the out terminal. If this fails, the message is retried. If the retry threshold is reached, where the threshold is defined by the BackoutThreshold attribute 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, an error message is issued and the node stops processing further input. The error message is bip4669.
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 will backout message 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 instance, on Distributed (non z/OS) platforms, the WebSphere MQ JMS provider supplies an extra jar file com.ibm,mqetclient.jar. This jar must also be added 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
XAResourceManager: Name=Jms_Provider_Name SwitchFile=/install_dir/bin/ JMSSwitch.so XAOpenString=Initial Context,location JNDI,Optional_parms ThreadOfControl=THREADWhere:
Name is an installation defined name that identifies a JMS provider Resource Manager.
SwitchFile is the file system path to the JMSSwitch library that is supplied in the bin directory of the broker.
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
XA cannot use the same queue manager for both the broker and the provider until WebSphere MQ Version 5.3, CSD12 and WebSphere MQ 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 from the WebSphere MQ queue. |
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 on the properties dialog 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 Basic properties of the JMSInput node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Initial Context Factory | Yes | com.sun.jndi.fscontext.RefFSContextFactory | This 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 which is used when WebSphere MQ Java is used as the JMS provider. |
|
Location JNDI Bindings | Yes | The system path or the LDAP location for the bindings file. | ||
Connection Factory Name | 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 | 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 | 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 is used to determine whether the incoming message is received under external syncpoint, local syncpoint, or out of syncpoint. Valid values are none, local, and global. |
The Description properties of the JMSInput node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
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. |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac24820_ |