Customizing a Process Model Template
To customize a process model template, you must first determine the appropriate process model template to use. This depends on two criteria:
Your role in the Chem eStandards conversation (that is, as initiator or fulfiller).
The number of transactions in the Chem eStandards conversation (that is, one-action or two-action).
For example, the
OrderCreate process would require the initiator or fulfiller version of the two-action asynchronous process model template. To determine whether a Chem eStandards process is a one-action or two-action model, visit the CIDX Web site (
http://www.cidx.org), and look up the specification for the type of Chem eStandards Process Archive that you imported to the
Integration Server.
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. For more information about any of the following steps, see the webMethods Service Development Help for your release.
Note:
To start Designer, Integration Server must be running.
2. Select File > Import.
3. Go to: Integration Server_directory \packages\WmChem\ProcessModels.
where Integration Server_directory is the installation directory in which the Integration Server is installed.
4. Choose the process model template you want to work from, and import the template.
5. Rename the template file name.
6. Each wait step is preceded by a receive step. Some receive steps receive CIDX (RosettaNet) specific documents (for example, ReceiptAcknowledgement RNIF 1.1), and some receive the Chem eStandards payload document. Drag and drop the appropriate TN doc type from Integration Server browser into the process model to change the receive steps corresponding to Chem eStandards payload. For example, if you are using the Two-Action Initiator.xml process model template, you would replace the Chem eStandards Dummy Doc Type for the Wait for Internal Request Document and Wait for External Response Document steps with the TN XML document types you created for these steps.
7. If a wait step has a join type of Complex, drag and drop an appropriate TN doc type to replace the preceding receive step.
8. Assign services, that is:
Assign outbound mapping and inbound mapping services to the
Outbound Mapping and
Inbound Mappingsteps.
Assign error and exception handlers, if necessary.
Assign a service that will send a business document to your back‐end system to the
Send to Back-End step.
For information about how to assign the service that a step invokes, see the next section, Assigning the Service that a Step Invokes.
9. Set timeout and retry count values if you want these values to be different than the Chem eStandards specification. For information about how to set timeout and retry values using Designer, see
Setting Timeout and Retry Count
Values. 10. Enter a value for the Description property. The description should briefly explain the use of the process model. For information about setting this property, see the Software AG Designer Online Help.
11. Modify step labels and icons as appropriate. For information about how to modify step labels and icons, see the Software AG Designer Online Help.
12. Save the process model.
13. Build and upload the process model. For instructions about how to build and upload a process model, see the Software AG Designer Online Help.
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.
14. Use Monitor to enable the process model. For instructions about how to enable a process model, see webMethods Monitor User’s Guide.