ebXML Message Handler Service

The ebXML Message Handler service composes outgoing and decomposes incoming ebXML messages based on CPA and BPSS parameters.

The following table provides an overview of the ebXML Message Handler service:

System name	ebXML Message Handler service
Graphical Process Modeler (GPM) categories	Internet B2B > ebXML
Description	Composes outgoing and decomposes incoming ebXML messages based on CPA and BPSS parameters.
Business usage	For an outbound message the service is used to pack the required message in the specified format before sending it out. For an inbound message the service is used to unpack and validate MIME and SOAP structure of the message before passing it on.
Usage example	A business process that needs to compose or unpack ebXML message can invoke this service to handle both outbound and inbound ebXML processes. For more details see Parameters Passed from a Business Process.
Preconfigured?	No. This service must be installed and deployed before it can be invoked. There are no configuration parameters required.
Requires third-party files?	No
Platform availability	All supported Sterling Integrator platforms
Related services	No
Application requirements	No
Initiates business processes?	No
Invocation	Runs as part of a business process.
Business process context considerations	No
Returned status values	SUCCESS ebXML message is composed or decomposed successfully SUCCESS The original Acknowledgement of this request has been sent out. ERROR Failed to create ebXML MIME message structure ERROR Failed to digitally sign ebXML message ERROR Failed to encrypt ebXML message ERROR Failed to MIME ebXML message ERROR Could not find private cert in CPA before digitally signing the ebXML message ERROR Could not find encryption cert in CPA before encrypting the ebXML message ERROR Could not find public key from database ERROR There is no support transport protocol agreed in CPA ERROR There is no endpoint agreed in CPA ERROR Failed to crack ebXML inbound MIME message ERROR The inbound MIME message is not conforming to the SOAP structure ERROR The inbound MIME message does not have an end boundary ERROR There is no transport information to send original Acknowledgement
Restrictions	None

Business Process Example

The following example assumes that the nodes DBValues are found in the process data:

<process name="testEBXMLMSHService">
		 <sequence>
	     <operation>
          <participant name="ebXMLMSHService"/>
          <output message="ebXMLMSHInputMessage">
	             <assign to="." from="*"/>
          </output>
          <input message="ebXMLMSHOutputMessage">
              <assign to="." from="*"/>
          </input>
       </operation>
    </sequence>
</process>