Input/Output to Use
The input to the outbound mapping service is, indirectly, your back‐end business document, represented as an IData object.
Note:
You typically invoke the wm.estd.common.util:getBizDocFromEvent service to retrieve the BizDocEnvelope, which contains your back‐end business document, and then invoke the wm.ip.util:recordFromBizDoc service to extract the business document content from the BizDocEnvelope. This process returns your back‐end business document as an IData object.
The output from the outbound mapping service is the Chem eStandards payload in the
documents\Payload IData object in the pipeline. For instance, if you are mapping your back‐end documents to the OrderCreate Chem eStandards payload, the output of the mapping service would be
OrderCreate(OrderCreate) in the
documents\Payload IData object. See the figure in
Example of an Outbound Mapping Service:
Initiator (Sender)The output from the outbound mapping service must be placed in the documents\Payload IData object. The webMethods Chem eStandards Module has to convert a Chem eStandards IData object into an XML string before sending the Chem eStandards payload to the trading partner. Therefore, the webMethods Chem eStandards Module must know the precise location of the Chem eStandards IData object.
Note:
If the documents for your back‐end system have DTDs, you can automatically import an external DTD in Developer to provide a starting point for mapping. Simply create a new external payload and specify the source as XML,DTD, or XML Schema.
To define the request type in the outbound mapping service, set the parameter GlobalDocumentFunctionCode within the parameters document.
Use this Parameter Value | When the business document is... |
Request | A request for a business action to be performed by the partner. |
Acceptance | An acceptance for a business action performed by the sender. |
Response | A response to a requesting partner. |
Cancellation | The notification of cancellation to the requesting partner. |