IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Publication node

Use the Publication node to filter output messages from a message flow and transmit them to subscribers who have registered an interest in a particular set of topics.

This information contains the following sections:

Purpose
Using this node in a message flow
Terminals and properties

Purpose

Use the Publication node to publish a message through the WebSphere® MQ queue manager associated with the broker. Applications that expect to receive publications must register a subscription.

The message being published must be:

A Publish command message
A Delete Publication command message, or
Have at least one topic present in the standard properties of the message.

The Publication node uses the topic, or topics, and any options present in the command message to publish the message. The WebSphere MQ queue manager delivers the publication to all subscribing applications matching the topic, and any other options specified on their subscriptions.

The Publication node is contained in the Routing drawer of the palette, and is represented in the IBM® Integration Toolkit by the following icon:

Using this node in a message flow

Look at the following samples to see how to use this node:

You can view information about samples only when you use the product documentation that is integrated with the IBM Integration Toolkit or the online product documentation. You can run samples only when you use the product documentation that is integrated with the IBM Integration Toolkit.

For an example of how to use this node, assume that you have written a publishing application that publishes stock updates on a regular basis. The application sends the messages to the broker on an MQInput node, and the message flow provides a conversion from the input currency to a number of output currencies. Include a Publication node for each currency that is supported, and set the Subscription Point property to a value that reflects the currency in which the stock price is published by the node; for example, Sterling, or USD.

Terminals and properties

When you have put an instance of the Publication 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.

The Publication node terminals are described in the following table.

Terminal	Description
In	The input terminal that accepts a message for processing by the node.
NoMatch	If no subscribers are matched on any of the published topics, the original message is propagated here.
Out	If at least one subscriber is matched by WebSphere MQ on at least one of the published topics, the original message is propagated here.

The following tables describe the node properties. The column headed M indicates whether the property is mandatory; 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 Publication node Description properties are described in the following table.

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

Property	M	C	Default	Description
Implicit Stream Naming	Yes	No	Cleared	Select Implicit Stream Naming to take the name of the WebSphere MQ queue on which the message was received by the message flow as the stream name. This property provides compatibility with earlier versions of WebSphere MQ Publish/Subscribe, and applies to messages with an MQRFH header when MQPSStream is not specified. Clear the check box if you do not want this action to be taken.
Subscription Point	No	No		The subscription point value for the node. If you do not specify a value for this property, the default subscription point is assumed. Set a subscription point for a Publication node to restrict the forwarding of its publications to those subscribers that specify the subscription point in their subscription (as described in the example scenario in Using this node in a message flow). For more information, see Subscription points.

The Monitoring properties of the node are described in the following table.

Property	M	C	Default	Description
Events	No	No	None	Events that you have defined for the node are displayed on this tab. By default, no monitoring events are defined on any node in a message flow. Use Add, Edit, and Delete to create, change or delete monitoring events for the node; see Configuring monitoring event sources using monitoring properties for details. You can enable and disable events that are shown here by selecting or clearing the Enabled check box.

ac04590_.htm |

Last updated Friday, 21 July 2017