The webMethods Chem eStandards Module (Chem Module) is an implementation of the Chem eStandards that use the Transport, Envelope, and Security features of the RosettaNet Implementation Framework (RNIF) version 1.1. Leveraging the webMethods platform process modeling and management capabilities and XML business document (referred to in this guide as a business document) recognition capabilities, the webMethods Chem eStandards Module enables you to implement open and common e‐business Chem eStandards processes and their implementation guidelines. The Chem Module consists of a set of design‐time and run‐time components, both sets of which are discussed in this chapter. For information about the design‐time components, see webMethods Chem eStandards Module Design-Time Architecture/Components ". For information about run‐time components, see " webMethods Chem eStandards Module Run-Time Architecture/Components ".

You implement a Chem eStandards process by importing the necessary Chem eStandards process archive, creating your webMethods Trading Networks TN XML document types and Trading Partner Agreements (TPAs), and then customizing one of process model templates as described in Customizing a Process Model Template. To customize a process model template, you assign services that you create to specific steps in the template. You also assign TN XML document types to steps that wait for business documents (referred to in this guide as wait steps), so that when thewebMethods Chem eStandards Module receives a business document during a conversation, or process, it can recognize the type of business document received. For more information about process models and Software AG Designer, the tool used to customize the process model templates, see the Software AG Designer Online Help. For more information about Chem eStandards Process Archives, see Importing Chem eStandards Process Archives. For the typical procedure for implementing a Chem eStandards process, see Getting Started.

The webMethods Process Engine, a facility of the webMethods Integration Server, manages the execution of Chem conversations. The Process Engine is the run‐time component that executes process logic, logs process data, and controls process execution order. During run time, the Process Engine uses the ConversationID associated with a business process to determine whether the process is active, or currently running. For more information about the Process Engine, see webMethods Chem eStandards Module Run-Time Architecture/Components and the webMethods Process Engine User's Guide. For more information about ConversationIDs, see Running a Conversation and the ConversationID

Every Chem Payload transaction in the Chem Module is associated with two Trading Partner Agreements (TPAs), one for the initiator/sender in a conversation and one for the fulfiller/receiver in a conversation. A TPA is a set of parameters that you can use to govern how business documents are exchanged between two trading partners. For example, a TPA for a Chem conversation contains parameters that control such things as signing, encoding, and validation of Chem Payload documents. For more information about TPAs, see Customizing Trading Partner Agreements and the webMethods Trading Networks Administrator’s Guide.