About the RosettaNet Participant Business Process File

The RosettaNet participant business process file provides a head start for building public participant business processes for RosettaNet conversations. Although this file is not required to build RosettaNet participant business processes, it includes the nodes and business process annotations needed to integrate easily with RosettaNet initiator business processes.

The RosettaNet participant business process is intended to serve as an example of the type of processes you can build for RosettaNet message exchange. The file consists of the following nodes:

Example Node Name
Example Node Types
Description

Start

Start

This marks the beginning of your business process. In the Property Editor of the Start node, you can define the following properties:

  • protocol-name
  • protocol-version
  • pip-name
  • pip-version
  • pip-role

To learn more about these properties, see Configuring Business Process Properties (Required).

To learn about Start nodes, see Starting Your Business Process.

On Error Message

(global error handling)

Message Path

Use the Message Path to interrupt an executing process upon delivery of a message from either a client or a control. This allows the process to halt the current stream of execution and take the specified alternate actions. To learn more about Message Paths, see Adding Message Paths.

On Error

(Global message path)

Client Request

Use this node, or any other nodes in its place, to handle the error processing you want to take place when an error message is received. To learn about Client Request nodes, see Receiving Messages From Clients

Alert local administrator

(Global message path)

Perform

Use this node, or any other nodes in its place, to send a failure message to an administrator. To learn more about Perform nodes, see Writing Custom Java Code in Perform Nodes

Receive Message

Client Request

Starts the RosettaNet participant business process upon receiving a RosettaNet message from the initiator. To learn about Client Request nodes, see Receiving Messages From Clients.

Send receipt acknowledgment.

Client Response

Sends an acknowledgement to the initiator that the request message was received. To learn about Client Response nodes, see Interacting With Resources Using Controls.

Send private message

(Invoke private process group)

Perform

Use this node, or any other nodes in its place, to send a request to the private process. To learn more about Perform nodes, see Writing Custom Java Code in Perform Nodes.

Receive private message

(Invoke private process group)

Perform

Use this node, or any other nodes in its place, to receive a response from the private process. To learn more about Perform nodes, see Writing Custom Java Code in Perform Nodes.

Send reply

(Retry block)

Client Response

Use this node, or any other node in its place, to send the response back to the initiator. To learn about Client Response nodes, see Sending Messages to Clients.

Receive receipt acknowledgment

(Retry block)

Client Request

Use this node, or any other node in its place, to listen for an acknowledgment from the initiator process. To learn more about Client Request nodes, see Receiving Messages From Clients.

OnTimeout

(Timeout path on Retry block)

Timeout Path

Use the Timeout Path to interrupt the execution of an iteration of the nodes in the Retry block group after a certain amount of time has lapsed. To learn more about grouping nodes, see Grouping Nodes in Your Business Process. To learn more about Timeout Paths, see Adding Timeout Paths.

Check retries

(Timeout path on Retry block)

Condition

Use this node, or any other nodes in its place, to select a path of execution based on the evaluation of one or more conditions, in this case, the number of iterations of the Retry block group. To learn more about Decision nodes, see Defining Conditions For Branching.

Notification of Failure

(Timeout path on Retry block)

Perform

Place this node, or any other node in its place, inside the Decision node to handle failure notifications to the initiator if an iteration of the Retry block group times out. This node is where you would normally invoke a PIP0A1 notification of failure. To learn more about Perform nodes, see Writing Custom Java Code in Perform Nodes. To learn more about customizing this node, see Setting Up the Notification of Failure (Required).

Finish

Finish

Ends the RosettaNet participant business process. To learn about Finish nodes, see Specifying Endpoints in Your Business Process.

To learn more about how to customize the nodes in the RosettaNet participant template, see Customizing a RosettaNet Participant Business Process.

This business process is modeled on the Two-Action Activity (Asynchronous) choreography that is specified in the RosettaNet Implementation Framework Core Specification (version V02.00.01). To learn about this choreography, see the following URL:

http://www.rosettanet.org

Related Topics

Creating a RosettaNet Participant Business Process

Customizing a RosettaNet Participant Business Process

Previous Document Next Document