ebXML Profile Service
The ebXML Profile service returns a specified business process name to be run. The service is used to reuse a business process and to prevent more than one instance of the same business process from being started.
The following table provides an overview of the ebXML Profile service:
System name | ebXMLProfile |
---|---|
Graphical Process Modeler (GPM) categories | All Services, Internet B2B > ebXML |
Description | Returns the name of a business process to be run. |
Business usage | Used in conjunction with ebXML messaging. It determines the business process to be run based on the CPA ID, service and action values passed as part of the ebXML message. |
Usage example | A business process that correctly validates an ebXML message needs information about what other business process needs to be run in response to the ebXML message. |
Preconfigured? | Must be installed and deployed before it can run. There are no configuration parameters required. |
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 | None |
Returned status values | None |
Restrictions | No |
Notes | The output message is a node containing the business
process to be run.
|
Parameters Passed from Business Process to Service
The following parameters need to be passed to the service when it runs with the output message set to getCallbackRequest.
Field | Description |
---|---|
CPAId | Unique value that identifies a trading partner relationship as defined in the CPA specification. |
Service | Identifies a set of business transactions as defined in the CPA specification. |
Action | Identifies a business transaction as defined in the CPA specification. |
Business Process Example
The following example shows how the ebXML Profile service might be used in a business process:
<operation>
<participant name="ebXMLProfile"/>
<output message="getCallbackRequest">
<assign to="CPAId" from="InboundMIME/mime:message/mime:body/mime:message[1]
/mime:body/SOAP-ENV:Envelope/SOAP-ENV:Header/eb:
MessageHeader/eb:CPAId/text()"/>
<assign to="Service" from="InboundMIME/mime:message/mime:body/mime:
message[1]/mime:body/SOAP-ENV:Envelope/SOAP-ENV:Header/eb:
MessageHeader/eb:Service/text()"/>
<assign to="Action" from="InboundMIME/mime:message/mime:body/mime:message[1]
/mime:body/SOAP-ENV:Envelope/SOAP-ENV:Header/eb:MessageHeader/
eb:Action/text()"/>
</output>
<input message="getCallbackResponse">
<assign to="Client" from="callback/node()"/>
</input>
</operation>
Implementing the ebXML Profile Service
To implement the ebXML Profile
service, complete the following tasks:
- Activate your license for the ebXML Profile service. See Installing Sterling B2B Integrator.
- Create an ebXML Profile service configuration. See Managing Services and Adapters.
- Use the ebXML Profile service in a business process.