1SYNC Module Version 6.5 SP2.September 2008 | Understanding and using webMethods 1SYNC Module | Installing and Using 1SYNC Module | Concepts | Run-Time Architecture and Components
 
Run-Time Architecture and Components
The following figure illustrates the 1SYNC run-time architecture and components, and the component relationships. For further explanation, see the table that follows the figure.
Component
Description
webMethods Integration Server
1SYNC Module is installed and runs on Integration Server. Integration Server contains the run-time elements that are generated from the automated controlled steps within the process model. The run-time elements are services, triggers, and process run-time scripts, or fragments.
For more information about Integration Server, see the webMethods Integration Server Administrator’s Guide for your release.
webMethods 1SYNC Module
During run time, 1SYNC Module receives a business document from a back-end system or trading partner. It invokes a Trading Networks service to recognize the business document, create a BizDocEnvelope and ConversationID, and save the BizDocEnvelope to the Trading Networks database.
webMethods Trading Networks (TN)
Trading Networks enables your enterprise to link with whom you want to exchange business documents using 1SYNC, thereby forming a business-to-business trading network.
During run time, 1SYNC Module uses Trading Networks services and TN document types to recognize business documents it receives, create BizDocEnvelopes, and save BizDocEnvelopes to the Trading Networks database.
1SYNC Module uses the trading partner profiles in Trading Networks to know, for example, the methods by which to send business documents to 1SYNC. 1SYNC Module uses TPAs in Trading Networks to store configuration information, such as the version of the 1SYNC transaction to use, whether to validate the outbound 1SYNC business document before sending it to 1SYNC, and so on.
For more information about Trading Networks, trading partner profiles, TN document types, and TPAs, see the webMethods Trading Networks Administrator’s Guide for your release. You also can find information about trading partner profiles in Defining Trading Partner Profiles in Trading Networks and information about TPAs in Defining a Trading Partner Agreement.
Trading Networks Database
The Trading Networks Database stores TN document type, TPA, and trading partner profile information, among other things.
webMethods Module for EDIINT
1SYNC Module uses webMethods Module for EDIINT to communicate with the 1SYNC Data Pool using the EDIINT AS2 version of the standard that uses HTTP (or HTTP/S) to transport documents. Module for EDIINT leverages various features of Trading Networks.
Module for EDIINT supports the following EDIINT features:
*Provides a mechanism by which to securely exchange business documents using EDIINT AS2.
*Enables business partners to set encryption types and key lengths at the business-partner level using the extended fields of the trading partner's Trading Networks profile. The choices include Triple DES, DES, RC2 (40 bits), RC2 (64 bits), and RC2 (128 bits).
*Provides the standard outbound encryption permutations (signed, encrypted, signed and encrypted, or plain) at the send-service level.
*Can send receipts of received business documents back to the sender as well as receive business document receipts. EDIINT receipts are known as MDNs (message disposition notifications). Module for EDIINT can send and receive synchronous or asynchronous, signed or unsigned MDNs.
For more information about Module for EDIINT, see the webMethods Module for EDIINT Installation and User’s Guide . For information about configuring Module for EDIINT for use with 1SYNC, see Setting Up EDIINT Interaction with 1SYNC.