WebSphere Message Brokers
File: ac04645_
Writer: Terry Cowling

Reference topic

This build: July 31, 2007 21:17:29

Passthrough node

This topic contains the following sections:

Purpose

Use the Passthrough node to enable versioning of a subflow at run time. Use the Passthrough to add a label to your message flow or subflow. By combining this label with keyword replacement from your version control system, you can identify which version of a subflow is included in a deployed message flow. You can use this label for your own purposes. If you have included the correct version keywords in the label, you can see the value of the label:
  • Stored in the broker archive (BAR) file, using the mqsireadbar command
  • As last deployed to a particular broker, on the properties of a deployed message flow in the Message Broker Toolkit
  • At run time, if you enable user trace for that message flow

The Passthrough node does not process the message in any way. The message that it propagates on its Out terminal is the same message that it received on its In terminal.

The Passthrough node is represented in the workbench by the following icon:

Passthrough node icon

Using this node in a message flow

Use this node to identify a subflow; for example, if you develop an error processing subflow to include in several message flows, you might want to modify that subflow. However, you might want to introduce the modified version initially to just a subset of the message flows in which it is included. Set a value for the instance of the Passthrough node that identifies which version of the subflow you have included.

Configuring the Passthrough node

When you have put an instance of the Passthrough 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 for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.

Configure the Passthrough node as follows:

  1. Optional: On the Description tab, enter a short description, a long description, or both. You can also rename the node on this tab.
  2. On the Basic tab, specify in Label the identifier for this node. Enter a value that defines a unique characteristic; for example, the version of the subflow in which the node is included.

Terminals and properties

The Passthrough node terminals are described in the following table.

Terminal Description
In The input terminal that accepts a message for processing by the node.
Out The input terminal that delivers a message to the subflow.

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 Passthrough node Description properties are described in the following table.

Property M C Default Description
Node name No No The node type, Passthrough 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 Passthrough node Basic properties are described in the following table.

Property M C Default Description
Label No No   The label (identifier) of the node.
Related concepts
Message flows overview
Related reference
Input node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:17:29

ac04645_ This topic's URL is: