ebXML Validation Service
The ebXML Validation service validates inbound ebXML messages to make sure that it conforms to the ebXML structure and verify the validity of the digital signature.
The following table provides an overview of the ebXML Validation service:
System name | ebXMLValidationService |
---|---|
Graphical Process Modeler (GPM) categories | All Services, Internet B2B > ebXML |
Description | Validates inbound ebXML message to make sure it
conforms to the ebXML structure and verify the validity of the digital
signature. If there is a message level exception found, returns error
list. Supported ebXML stacks are: Note: ebMS 2.0 is supported.
|
Business usage | Used for ebXML Messaging to validate inbound message level content. |
Usage example | A business process that needs to validate ebXML inbound message can invoke this service by passing the required parameters. |
Preconfigured? | No |
Requires third-party files? | No |
Platform availability | All supported Sterling B2B 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 | None |
Restrictions | No |
Persistence level | System default |
Testing considerations | None |
Output from Service to Business Process
The following table describes the output from the ebXML Validation service to the business process:
Parameter | Description |
---|---|
errors | Error List. Valid value is eb:ErrorList or eb:Error. Optional. |
Output from Business Process to Service
The following table describes the output from the business process to the ebXML Validation service:
Parameter | Description |
---|---|
inboundMIME | Node contains the inbound ebXML message. Required. |
CPA | Node contains the CPA info based on the inbound ebXML message service/action. Required. |
BPSSParam | Node contains the BPSS parameters information based on the return of BPSSHandler. Optional. |
InboundDocId | Node contains the document-id of the inbound ebXML message. Required. |
Business Process Example
The following example illustrates using the ebXML Validation service in a business process:
<process name="testEBXMLValidationService">
<sequence>
<operation name="ebXMLValidation">
<participant name="ebXMLValidationService"/>
<output message="ebXMLValidationInputMessage">
<assign to="inboundMIME" from="InboundMIME/node()"/>
<assign to="CPA" from="cpa/node()"/>
<assign to="BPSSParam" from="bpssParams/node()"/>
<assign to="InboundDocId"
from="string(inbound-mime-document/doc:document-id)"/>
</output>
<input message="ebXMLValidationOutputMessage">
<assign to="." from="errors"/>
</input>
</operation>
</sequence>
</process>
Implementing the ebXML Validation Service
To implement the ebXML Validation
service for use in a business process:
- Create an ebXML Validation service configuration. See Managing Services and Adapters.
- Use the ebXML Validation service in a business process.