JMSOutput node

Use the JMSOutput node to send messages to JMS destinations.

This topic contains the following sections:

Purpose

The JMSOutput node acts as a JMS message producer, and can publish all six message types that are defined in the Java Message Service Specification, version 1.1. Messages are published by using method calls, which are described in the JMS specification.

The JMSOutput node is contained in the JMS drawer of the palette, and is represented in the workbench by the following icon:

JMSOutput node icon

Using the JMSOutput node in a message flow

The following sample contains a message flow in which the JMSOutput node is used. Look at this sample for an example of how to use the JMSOutput node. You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.

Message flows that handle messages that are received from connections to JMS providers must always start with a JMSInput node. If you include the JMSOutput node in a message flow, you do not need to include a JMSInput node; but if you do not include a JMSInput node, you must include the MQJMSTransform node to transform the message to the format that is expected by the JMSOutput node.

If you are propagating JMS messages and creating a message flow to use as a subflow, use an instance of the JMSOutput node as the last node to create an out terminal for the subflow.

Controlling the type of the JMS output message

In the JMS message tree, the JMS message type is represented by the PayloadType field of the Message_MetaData subfolder. To control the type of JMS message that is created by the JMSOutput node, use ESQL code to set the Payload value, as shown in the following example:
SET OutputRoot.JMSTransport.Transport_Folders.Message_MetaData.PayloadType=Payload value

For more information about the JMS message tree and payload values, see Representation of messages across the JMS Transport.

Making the JMS provider client available to the JMS nodes

Configurable services are defined for a number of JMSProviders. You can choose one of the predefined services, or you can create a new service for a new provider, or for one of the existing providers.

To display one or more of the defined configurable services, use the mqsireportproperties command. The following example displays all configurable services that are available for a single broker:
mqsireportproperties brokerName -c AllTypes -o AllReportableEntityNames -r 
  • If you want to use the WebSphere® MQ JMS Provider, and you have installed WebSphere MQ in the default location on the broker system, the properties are already set and you do not have to make any changes.
  • If you want to use the WebSphere MQ JMS Provider, and you have installed WebSphere MQ in a different (non default) location, or if you want to use one of the other defined services, you must set the jarsURL property to identify the location of the service JAR files on the broker system.

    Use the mqsireportproperties command to view the provider properties, and the mqsichangeproperties command to set or modify the properties.

  • If no service is defined for your JMS provider, or if you want to create another service for an existing JMS provider, use the mqsicreateconfigurableservice command to identify the new service and set its properties.
  • When you configure the node, select the appropriate service from the list of predefined services shown for the JMS provider name property, or type in the name of your new service.

Using the Message Destination Mode

The JMSOutput node acts as a message producer and supports the following message scenarios:

Sending a datagram message

A datagram is a self-contained, independent entity of data that carries sufficient information to be routed from the source to the destination computer, without reliance on earlier exchanges between the source and destination computer and the transporting network. The following instructions describe how to send a datagram message:
  1. On the Basic tab, set the message destination depending on the message model that is being used. Set one of the following properties to a valid JNDI administered object name:
    • Publication Topic
    • Destination Queue
  2. Leave the Reply To Destination field blank.
The node resolves the name of the JNDI administered object, which is supplied in either Publication Topic or Destination Queue, and sends the message to that JMS Destination.

Sending a reply message

The sender of a message might want the recipient to reply to the message. In this case, the JMSOutput message can treat the outgoing message as a reply, and route it according to the value that is obtained from the JMSReplyTo property from the request message. You can modify the value of the JMSReplyTo property in the MbMessage; for example, using a Compute node or a JavaCompute node. This action allows dynamic routing of messages from the JMSOutput node. The node sends the message to the JMS Destination name that is set in the JMSReplyTo field of the MbMessage Tree.

The JMSReplyTo value in the MbMessage Tree represents the name of the JMS Destination that is resolved from JNDI. For example:
queue://QM_mn2/myJMSQueue4
In this case, the value is the JMS-provider specific representation of a JMS Destination for the WebSphere MQ JMS provider.
If you do not want to specify a resolved JMS destination name, the JMSOutput node can also accept a JNDI administered object name in the JMSReplyTo field. However, the node must resolve an administered object name through JNDI before it can route the message to the underlying JMS Destination. In this case, the value in the JMSReplyTo field must be prefixed with the string: jndi:\\. For example:
jndi:\\jmsQ4
where jmsQ4 is the name of the JNDI-administered object.

Performance might be slightly impacted when you use this method because of the need to look up the administered object in JNDI.

Sending a request message

The JMSOutput node can send a message to a JMS Destination with the expectation of a response from the message consumer that processes the request. The following instructions describe how to send a request message:
  1. On the Basic tab, set the message destination depending on the message model that is being used. Set one of the following properties to a valid JNDI-administered object name:
    • Publication Topic
    • Destination Queue
  2. The JMSReplyTo destination in the outgoing message can be derived from the JMSReplyTo field of the MbMessage Tree that is passed to the node. Alternatively, this value can be overridden by a JNDI-administered object name that is set in the Reply To Destination node property.

    To allow the JMSOutput node to set the JMSReplyTo property dynamically in the outgoing message, leave the Reply To Destination field blank on the Basic tab, and set the JMSReplyTo value in the MbMessage using a Compute node or a JavaCompute node.

The node looks first for a value in the JMSReplyTo field of the MbMessage. If the node finds the value, it passes this value into the JMSReplyTo field of the outgoing message. However, if the Reply To Destination field of the Basic tab has been specified, this value overrides anything that is set previously in the JMSReplyTo property of the outgoing message, after first resolving the name of the JNDI-administered object.

The node resolves the name of the JNDI-administered object that is supplied in either Publication Topic or Destination Queue, and sends the message to that JMS Destination.

Configuring for coordinated transactions

When you include a JMSOutput node in a message flow, the value that you set for Transaction Mode defines whether messages are sent under syncpoint.

  • If you set the Transaction Mode to Global, the message is sent under external syncpoint coordination; that is, within a WebSphere MQ unit of work. Any messages that are sent subsequently by an output node in the same instance of the message flow are put under syncpoint, unless the output node overrides this setting explicitly.
  • If you set the Transaction Mode to Local, the message is sent under the local syncpoint control of the JMSOutput node. Any messages that are sent subsequently by an output node in the flow are not put under local syncpoint, unless an individual output node specifies that the message must be put under local syncpoint.
  • If you set the Transaction Mode to None, the message is not sent under syncpoint. Any messages that are sent subsequently by an output node in the flow are not put under syncpoint, unless an individual output node specifies that the message must be put under syncpoint.
When you want to send messages under external syncpoint, you must perform additional configuration steps, which need to be applied only the first time that a JMSOutput or JMSInput is deployed to the broker for a particular JMS provider:
  • On distributed systems, the external syncpoint coordinator for the broker is WebSphere MQ. Before you deploy a message flow in which the Transaction Mode is set to Global, modify the queue manager .ini file to include extra definitions for each JMS provider resource manager that participates in globally coordinated transactions:
    • Windows platform On Windows® systems, if you have WebSphere MQ Version 5 installed:
      1. Start WebSphere MQ Services.
      2. Right-click the queue manager name and click Properties.
      3. Click the Resource properties tab.
      4. Set the SwitchFile property to the following value:
        install_dir/bin/ JMSSwitch.dll  
        XAOpenString=Initial Context,location JNDI,Optional_parms
        ThreadOfControl=THREAD 
    • Windows platform On Windows systems, if you have WebSphere MQ Version 6.0 installed:
      1. Start WebSphere MQ Explorer.
      2. Right-click the queue manager name in the left pane and click Properties.
      3. Click XA resource managers in the left pane.
      4. Set the SwitchFile property to the following value:
        install_dir/bin/ JMSSwitch.dll  
        XAOpenString=Initial Context,location JNDI,Optional_parms
        ThreadOfControl=THREAD 
      For more information, see the System Administration Guide section of the WebSphere MQ Version 6 information center online or the Version 5.3 book on the WebSphere MQ library Web page.
    • Linux platformUNIX platform On Linux® and UNIX® systems, add a stanza to the queue manager's .ini file for each JMS provider.
      For example:
      XAResourceManager:
      Name=Jms_Provider_Name 
      SwitchFile=/install_dir/bin/JMSSwitch.so
      XAOpenString=Initial Context,location JNDI,Optional_parms
      ThreadOfControl=THREAD
      Where:
      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.
      XAOpenString can have the following values:
      • Initial Context is the value that is set in the JMSInput node basic property Initial context factory.
      • location JNDI is the value that is set in the JMSInput node basic property Location of JNDI. This value must include the leading keyword, which is file://, iiop:// or ldap://
      The following parameters are optional:
      • LDAP Principal matches the value that is set for the broker by using the mqsicreatebroker or mqsichangebroker commands.
      • LDAP Credentials matches the value that is set for the broker by using the mqsicreatebroker or mqsichangebroker commands.
      • Recovery Connection Factory Name is the JNDI administered connection factory that is defined in the bindings file. If a value is not specified, a default value for recoverXAQCF must be added to the bindings file. In either case, the Recovery Connection Factory must be defined as an XA Queue Connection Factory for the JMS provider that is associated with the Initial Context Factory.

      The optional parameters are comma-separated and are positional. Therefore, any parameters that are missing must be represented by a comma.

      1. Update the Java™ CLASSPATH environment variable for the broker's queue manager to include a reference to xarecovery.jar; for example:
        install_dir/classes/xarecovery.jar
      2. Update the Java PATH environment variable for the broker's queue manager to point to the bin directory, which is where the switch file is located; for example:
        install_dir/bin

      For more information, see the System Administration Guide section of the WebSphere MQ Version 6 information center online or the Version 5.3 book on the WebSphere MQ library Web page.

      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.

    • z/OS platform On z/OS®, the external syncpoint manager is Resource Recovery Services (RRS). The only JMS provider that is supported on z/OS is WebSphere MQ JMS. The only transport option that is supported for WebSphere MQ JMS on z/OS is the bind option.

      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.

Connecting the terminals

Connect the In terminal of the JMSOutput node to the node from which outbound messages are routed.

Connect the Out terminal of the JMSOutput node to another node in the message flow to process the message further, to process errors, or to send the message to an additional destination.

Terminals and properties

When you have put an instance of the JMSOutput node into a message flow, you can configure it; see Configuring a message flow node. The properties of the node are displayed in the Properties view. To display the properties of the node in the Properties dialog, 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.

The terminals of the JMSOutput node are described in the following table.
Terminal Description
In The input terminal that accepts a message for processing by the node.
Failure The output terminal to which the message is routed if an error occurs. Even if the Validation property is set, messages that are 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 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 JMSOutput node are described in the following table.
Property M C Default Description
Node name No No The node type, JMSOutput 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 JMSOutput 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.

Enter an Initial context factory value. A JMS application uses the initial context to obtain and look up the JNDI administered objects for the JMS provider. The default value is 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, see the JMS provider documentation.

Location JNDI Bindings No Yes   The system path or the LDAP location for the bindings file. The bindings file contains definitions for the JNDI-administered objects that are used by the JMSOutput node.
When you enter a value for Location JNDI Bindings, ensure that it complies with the following instructions:
  • Construct the bindings file before you deploy a message flow that contains a JMSOutput node.
  • Do not include the file name of the bindings file in this field.
  • If you have specified an LDAP location that requires authentication, configure both the LDAP principal (userid) and LDAP credentials (password) separately. These values are configured at broker level. For information about configuring these values, see mqsicreatebroker command and mqsichangebroker command.
  • The string value must include the leading keyword, which is one of:
    • file://
    • iiop://
    • ldap://

For information about constructing the JNDI-administered objects bindings file, see the documentation that is supplied with the JMS provider.

Connection Factory Name No Yes   The name of the connection factory that is used by the JMSOutput node to create a connection to the JMS provider. This name must already exist in the bindings file.
The Advanced properties of the JMSOutput node are described in the following table.
Property M C Default Description
New Correlation ID No Yes   If the JMSOutput node is required to generate a new Correlation ID for the message, select New Correlation ID. If you leave the check box cleared, the Correlation ID of the output message is taken from the JMSCorrelationID field in the JMSTransport_Header_Values section of the message tree.
Transaction Mode Yes No None This property controls whether the incoming message is received under syncpoint.
  • Select None if the outgoing message is to be treated as non persistent. If you select this value, the message is sent using a non-transacted JMS session that is created using the Session.AUTO_ACKNOWLEDGE flag.
  • Select Local if the input node that received the message must coordinate the commit or roll-back of JMS messages that have been sent by the JMSOutput node, along with any other resources, such as DB2® or WebSphere MQ, that perform work within the message flow. If you select this value, the node uses a transacted JMS session.
  • Select Global if the JMSOutput node must participate in a global message flow transaction that is managed by the broker's external syncpoint coordinator. The syncpoint coordinator is the broker's queue manager on distributed systems, and RRS (Resource Recovery Services) on z/OS. If you select this value, any messages that are received by the node are globally coordinated using an XA JMS session.
Delivery Mode No Yes Non Persistent This property controls the persistence mode that a JMS provider uses for a message. Valid values are:
  • Automatic: the mode from the input message is inherited
  • Persistent: the message survives if the JMS provider has a system failure
  • Non Persistent: the message is lost if the JMS provider has a system failure
Message Expiration (ms) No Yes 0 This property controls the length of time, in milliseconds, for which the JMS provider keeps the output JMS message. The default value, 0, is used to indicate that the message must not expire.
Message Priority No Yes 4 This property assigns relative importance to the message and it can be used for message selection by a receiving JMS client application or a JMSOutput node.

Valid values for message priority are from 0 (lowest priority) to 9 (highest priority). The default value is 4, which indicates medium priority. Priorities in the range 0 to 4 relate to typical delivery. Priorities in the range 5 to 9 relate to graduations of expedited delivery.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:39:55

ac24830_