1SYNC Module Version 6.5 SP2.September 2008 | Understanding and using webMethods 1SYNC Module | Installing and Using 1SYNC Module | Configuring webMethods 1SYNC Module | Step 4: Integrate Back-End Applications with 1SYNC | Creating an Outbound Mapping Service
 
Creating an Outbound Mapping Service
You create an outbound mapping service to map back-end data to a request business document. The service forms the 1SYNC request message by mapping data from the internal request document that was received from the back-end system to the 1SYNC request message that is to be sent to 1SYNC. The outbound mapping service should perform the following actions:
*Convert the internal request document from the back-end system to an IData object.
If the internal request document is received from Trading Networks, you must request the content from Trading Networks, and then convert the content to an IData object. For more information about how to perform this action, see information about getting data from an external partner into a business process in Getting Started with BPM .
If the internal request document is a published IS document, it already will be in the business process pipeline as an IData object. For more information about getting data from internal systems into a business process, see Getting Started with BPM .
*Map data from the IData object for the internal request document to the 1SYNC request document.
The 1SYNC Module provides IS document types that define the different 1SYNC requests.
For example, for a subscription request, you map the internal request document to the wm.ip.sync.recs:docType_ns_catalogueItemSubscription document.