RosettaNet Module allows you to create process models to completely customize document processing. A process model visually depicts the individual steps and system interactions of a business process, using the Trading Networks assets that you create. RosettaNet Module provides process templates that you can modify to match your own system processes.

RosettaNet Module process templates are at Integration Server_directory\packages\WmRosettaNet\ProcessModels directory. The elements required to implement a specific RosettaNet process includes IS document types, TN XML document types and Trading Partner Agreements. You can create these elements using PIP Tools, after importing the required PIP specification zip file (provided by RosettaNet Standard) via PIP Tools. You can configure individual process steps that are triggered by a certain event, for example, a receive step that stops processing until it receives a specific business document (such as an acknowledgment) from your partner or a wait step, that executes the steps to process a document. Wait steps are dependent on the successful execution of receive steps; a wait step must follow a receive step. For more information about wait steps, refer to the pub.estd.rosettaNet:waitStepInit service.

Designer is the tool you use to import and configure business process. Process Engine executes the appropriate process model for a given RosettaNet transaction, and monitors the flow of conversations, ensuring that correct documents are exchanged and in the right order. Process Engine works with Monitor to store all conversation and transactional data, while Trading Networks identifies documents, processes them based on the sender and document type, executes any processing rules, and invokes any assigned transformation services.

For specific details about configuring process models in RosettaNet Module, see Customizing Process Model Template. For more information about RosettaNet Process Archives, see Importing PIP Specification/PIP Archives. For detailed information about process models and Designer, see webMethods Service Development Help.