Customizing a Process Model Template
To customize a process model template, you must first determine the appropriate process model template to use, based on the following criteria:
Your role in the PIP conversation, that is, initiator (sender) or fulfiller (receiver).
The number of actions in the PIP conversation (one action or two-actions).
For example, PIP 3A4 Request Purchase Order requires either the initiator or fulfiller version of the two-action asynchronous process model template. To determine whether a PIP is the one-action or two-action model, visit the RosettaNet Web site (
http://www.rosettanet.org), and look up the PIP specification that you imported.
After you determine the appropriate process model template to use, you are ready to customize the template.
To customize a process model template
1. Start Designer and import the required process model template from the directory: Integration Server_directory\packages\WmRosettaNet\ProcessModels. For help with this, or any step in this procedure, see Software AG Designer Online Help.
2. For each step that waits for an action document, replace the RosettaNet Dummy Doc Type with the TN XML document type that you imported/created.
For example, if you were using the PipTwoActionResponderModel.process template, you would replace the RosettaNet Dummy Doc Type in the Receive Internal Document and Receive External Document steps with the TN XML document types you imported/created for these steps.
Important:
You must select the property Allow this step to start new process instance for at least one receive step. For all the other steps, which must not start new process instances, unselect this property.
Note:
If you later change the name of a TN XML document type, you must also update the name of the TN XML document type in the process model, to avoid error.
3. Assign services as follows:
Assign outbound mapping and inbound mapping services to the
Outbound Map and
Inbound Map steps.
Assign error and exception handlers, if necessary.
Assign a service to the
Send to Back-End step, that will send a business document to your internal system.
When you customize a process model template, you must assign the services that the Inbound Map, Outbound Map, and Send to Back-End steps invoke. If you create your own error and exception handlers, you must also set these services as the ones that your error and exception steps invoke.
Important:
Some of the steps in the process model templates are set to invoke public services of RosettaNet Module. If you are customizing these steps to invoke your custom services, ensure that your custom service internally invokes the public service (originally invoked by the step).
5. Modify step labels and icons as appropriate.
6. Save the process model.
7. Build and upload the process model.
When you build and upload a process model, a process model package (containing services and triggers) and a Process Engine script (or fragment) are created on Integration Server.
8. Using Monitor, enable the process model, if the process model is not already enabled. For instructions, see webMethods Monitor User’s Guide.