Sending an xCBL Request Document to MarketSite
This section explains how C1 OnRamp sends an xCBL request document to MarketSite.
1. Your back-end system or a scheduled service generates data and sends it to the Integration Server via the appropriate webMethods adapter.
2. The adapter receives the data and calls custom services you developed. The custom services map the data to an xCBL request document and pass the document to a C1 OnRamp send service.
3. The send service calls C1 OnRamp services that:
a. Optionally, validate the xCBL document.
b. If your back-end system does not handle DDIDs, look up the sender and recipient IDs provided by your back-end system and return the corresponding DDIDs.
c. Create an envelope containing the xCBL request document.
d. Create any necessary attachments and add them to the envelope.
4. MarketSite returns a reply envelope to the sendEnvelope service. The contents of the reply envelope depend on the request mode of the envelope you sent and on whether errors occur during processing, as follows:
If you sent the envelope synchrononously and no processing errors occur, MarketSite's reply envelope contains an xCBL response document and any attachments.
If you sent the envelope asynchronously and no processing errors occur, MarketSite's reply envelope contains an acknowledgement. (MarketSite sends an envelope containing an xCBL response document and any attachments to the C1 OnRamp
receiveEnvelope service later.)
For either request mode, if errors occur during processing, the envelope that MarketSite returns to the sendEnvelope service contains an error instead of an acknowledgement or xCBL response document.