XML processing in M3 e-Collaborator

When customers submit an XML request document, they must target the HTTP communication channel in the M3 e-Collaborator configured for the e-Commerce Extension for MEC. The MEC with e-Commerce Extension for MEC together perform the following sequence:

  1. The MEC receives the document and applies the XSL transformation (if any) associated with the incoming port and document type. If a transformation error occurs then no response will be sent back to the client program.
  2. If the request document was not transformed and configured for schema validation, then the MEC validates the document against the appropriate schema. If validation fails, then no response will be sent back to the client program.
  3. The e-Commerce Extension for MEC will now take over. If the incoming document is in iXML 1.0 format, then it is transformed to version 2.0.
  4. The e-Commerce Extension for MEC examines the request to find out which credentials to use.
  5. The e-Commerce Extension for MEC breaks down the request into individual business object method calls.
  6. The e-Commerce Extension for MEC forwards each individual requests to the Gateway.JSP page for execution and receive the response of the execution.
  7. The e-Commerce Extension for MEC assembles all response documents into one document and return document control to the MEC.
  8. The MEC applies the XSL transformation (if any) associated with the outgoing port and document type (the port used is always the same as the incoming port, but the transformation applied is normally different for incoming and outgoing documents).
  9. The MEC returns the response document.