If you specified that your business process is started via the Subscribe to a Message Broker channel and start via an Event (Time, Email, File, Adapter, etc.) option (see To Define the Start Method for Your Business Process), your Start node is displayed as shown in the following figure:
A static subscription to a Message Broker channel is defined on the Subscription node. Your business process is started as the result of receiving a message from a Message Broker channel.
Note: In WebLogic Integration, subscriptions to Message Broker channels defined at a Start node are referred to as static subscriptions, and subscriptions defined using a Message Broker Subscription control are referred to as dynamic subscriptions. See "Note about Static and Dynamic Subscriptions" in @jpd:mb-static-subscription Annotation.
The following sequence concisely describes the message flow at run time:
Note: An asynchronous subscription start causes the subscribed business process to run in a different transaction from the publisher's transaction. In general, this is the recommended design pattern to use when you want to design your business process to start when it receives a message from a Message Broker channel. To learn about the scenarios for which a synchronous subscription start is recommended, see About Choosing Synchronous or Asynchronous Subscription Start Nodes.
To Complete the Design of Your Subscription Start Node
Tabs on the node builder include:
The following steps describe the tasks available on these tabs.
The data type and format of the data your subscription request method (that is, the data type for the method parameter) is specified automatically, based on the configuration of your channel file.
Note: If no appropriate channels are available for you to select, you must create a file that specifies the Message Broker channels for your application. To learn how to create this file, see How Do I Create Message Broker Channels?
Specifying a filter is optional. Filters can be applied to the data type the business process receives from the channel, or when you have specified a qualified metadata type in your channel configuration.
The field in the Specify Filter tab is populated with the data type for the subscription method parameter you specified on the preceding tab. If you specified your channel to be able to receive qualified metadata, the Qualified Metadata attribute is also listed and you can filter on that parameter instead.
To specify a filter:
Note: If you want to filter on an XMLObject parameter, you have to enter the XQuery statement in the Filter field or edit your source code directly.
This tab allows you to define one or more variables to hold the data that your business process receives from the channel.
The Client Sends field is populated with the parameter(s) you specified on the General Settings tab, in other words, the parameter type of the channel.
The node builder transformation screen is displayed; the data types expected by your method are displayed in the Client Sends pane.
Note: To remove a variable from the node builder pane, select the variable in the list and then click Remove. This action removes the variable from the node builder, not from your business process. The variable is still included in your business process; it is visible in the Variables pane in the Data Palette.
When designing a business process, you use a Transformation to create maps between disparate data types. Your project must contain an instance of a Transformation control (defined by a DTF file) for you to create the map.
The transformation tool displays a representation of the source schema and target schema in Source and Target panes. You can create a map between the data type of the method parameter and the data type of the variable, or variables, to which you want to assign the data. To learn how to create and test a map using the mapping tool, see Guide to Data Transformation.
Note: To return to node builder, in the Application pane, double-click the JPD file.
Note: To learn about changing the configuration you design in the Transformation pane of a node builder, see About Editing Node Configurations.
In the Design View, the icon indicates that you completed the configuration and design of this node. To learn about buffering on your subscription node, see Buffering Client Messages.
Subscription Start (Synchronous)
Sending Messages to Clients
Client Operations and Control Communication Methods
How Do I Create Message Broker Channels?
How Do I: Call a Business Process?
Message Broker Publish Control
Using Event Generators to Publish to Message Broker Channels