ebXML Request Response Service
The ebXML Request Response service generates unique conversation IDs and message IDs that are used in an ebXML conversation.
The following table provides an overview of the ebXML Request Response service:
| System name | ebXMLRequestResponse |
|---|---|
| Graphical Process Modeler (GPM) categories | All Services, Internet B2B > ebXML |
| Description | Returns the name of a business process to be run. |
| Business usage | Used with ebXML messaging. Creates unique values of conversation and message IDs. |
| Usage example | A business process that is creating an ebXML message needs to generate a dialog or message ID if the current message is part of a group of messages, which should be treated as part of the same dialog. |
| 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 | Runs as part of a business process. |
| Business process context considerations | None |
| Returned status values | None |
| Restrictions | None |
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 asssociateRequest.
| Field | Description |
|---|---|
| PartyId | Unique value that identifies a trading partner relationship as defined in the CPA specification. Required. |
| ConversationId | Identifies a set of business transactions as defined in the CPA specification. |
| MessageId | Identifies a business transaction as defined in the CPA specification. |
| handler | Handler, that is, the ID of the ebXML Request Response service. Numeric. Valid value is a system-generated ID. |
Business Process Example
The following is an example of a business process that uses the ebXML Request Response service:
<operation>
<participant name="ebXMLRequestResponse"/>
<output message="associateRequest">
<assign to="PartyId" from="string(cpa/counterParty/eb:PartyId)"/>
<assign to="handler" from="thisProcessInstance/node()"/>
</output>
<input message="associateResponse">
<assign to="conversationId" from="ConversationId/node()"/>
<assign to="messageId" from="MessageId/node()"/>
</input>
</operation>Implementing the ebXML Request Response Service
To implement the ebXML
Request Response service, complete the following tasks:
- Activate your license for the ebXML Request Response service. See Installing Sterling B2B Integrator.
- Create an ebXML Request Response service configuration. See Managing Services and Adapters.
- Use the ebXML Request Response service in a business process.