Sub-processes are Business Processes (BPs) called within the main BP of a Project, and are invoked within the same Integration Server. Use the Business Rule Designer to configure the input and output attributes for the sub-process.
Sub-processes are required when a BP contains a user activity; the sub-process defines the flow of data through the user activity. A sub-process exists within a main process, so incorporating a sub-process into a BP involves two steps:
In the following procedure, you create a WSD object to use in the sub-process. The WSD object functions as the interface to the sub-process or, in the case of a user activity, to the Visual Page Designer pageflow. For detailed information about using the Web Service Designer, see Sun Enterprise Service Bus topics.
Right-click the Repository and click New Project.
Name the Project.
Right-click the Project, point to New, and then click Web Service Definition.
Edit the WSD object as needed.
Right-click the Project, point to New, and then click Business Process.
Add a receive activity to the BP, and then link it to the Start element.
In the Project Explorer, expand the WSD object, expand PortTypes, and then expand PortType.
Click the PortType operation and drag it onto the empty receive activity.
If the operation includes an output message, a reply activity appears.
Add one or more empty activity to the canvas between the implement and reply activities.
Add links between the modeling elements in the sub-process, and then add business rules if needed.
Click Save.
Once you create the sub-process, you can add it to the main BP in the Project.
Create a new BP and add a receive activity, an empty activity, a reply activity, and any other activities required for the BP.
Expand the sub-process and drag the operation onto the empty receive activity.
Add links between the modeling elements in the main process and add business rules as needed.
Click Save.
If the sub-process is to be invoked as a synchronous request/reply web service, the Receive and Reply must be associated with the same partner, port type, and operation. These properties can all be configured in the property sheet for the user activity.