ebXML Business Service Handler (BSI) service

The ebXML Business Service Handler service interprets and runs activities that are defined in the BPSS.

The following table provides an overview of the ebXML Business Service Handler (BSI) service:

System name ebXMLBSIService
Graphical Process Modeler (GPM) categories All Services, Internet B2B - ebXML
Description Invokes the Business Service Handler to interpret and execute activities defined in the BPSS.
Note: BPSS 1.05 is supported.
Business usage
  • Executes either inbound or outbound processing for BPSS.
  • Determines start, finish and transition activities.
  • Invokes appropriate services to do document schema validation.
Usage example A business process that needs to execute activities specified in the BPSS.
Preconfigured? Yes
Requires third-party files? No
Platform availability All supported Sterling B2B Integrator platforms
Related services No
Application requirements No
Initiates business processes? No
Invocation Not applicable
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 BSI service to the business process:

Parameter Description
wfc Contents of the updated business process context. Required.

Output from Business Process to Service

The following table describes the output from the business process to the ebXML BSI service:

Parameter Description
wfc The contents of the business process context. Required.

Business Process Example

The following example assumes that the relevant activity_state (if needed) is set.

<operation> 
    <participant name="ebXMLBSIService"/> 
    <output message="XOut"> 
        <assign to="." from="*"/> 
    </output> 
    <input message="XIn"> 
        <assign to="." from="*"/> 
    </input> 
</operation>

Output Parameters

This section contains information about calling the ebXML service for outbound and inbound activities.

Output Parameters – Outbound Processing

In processing outbound activities, there are two possible ways of calling the ebXML BSI service. The first way, with the activity_flag set to pre indicates preprocessing of activities before the internal process runs. The second way, with the activity_flag set to post, indicates postprocessing of activities after the internal process runs. 

<assign to="activity_state" from="'pre'"/> 
<operation name="One"> 
    <participant name="ebXMLBSIService"/> 
    <output message="Xout"> 
         <assign to="." from="*"/> 
    </output> 
    <input message="Xin"> 
         <assign to="." from="*"/> 
    </input> 
</operation> 
<assign to="activity_state" from="'post'"/> 
<operation name="One"> 
    <participant name="ebXMLBSIService"/> 
    <output message="Xout"> 
         <assign to="." from="*"/> 
    </output> 
    <input message="Xin"> 
         <assign to="." from="*"/> 
    </input> 
</operation>

Output Parameters – Inbound Processing

When processing inbound activities, just call the service, as shown in the following example: 

<operation name="One"> 
   <participant name="ebXMLBSIService"/> 
   <output message="Xout"> 
       <assign to="." from="*"/> 
   </output> 
   <input message="Xin"> 
         <assign to="." from="*"/> 
   </input> 
</operation>

Implementing the ebXML BSI Service

To implement the ebXML BSI service for use in a business process:
  1. Create an ebXML BSI service configuration. See Managing Services and Adapters.
  2. Use the ebXML BSI service in a business process.