ebXML configuration

You can define the ebXML configuration for ebMS transactions by importing CPA files or associating CPA entries to the B2B gateway. The ebXML configuration is applicable for only ebMS2 messages.

A CPA file is an XML document that enumerates the valid, visible, and enforceable interactions that two partners require to collaborate and interchange B2B documents with the ebMS protocol. The file contains communication protocol, reliable messaging process information, request and response security, message transport, and document envelope details.

You can use the CPA import wizard or send SOAP request to the XML management interface to import CPA files. After a CPA file is imported, the DataPower® Gateway automatically generates CPA entries and associates the entries to the B2B gateway.

CPA-enforced B2B gateway

A B2B gateway is promoted to CPA-enforced when it is associated with a CPA entry. When a B2B gateway is CPA-enforced, the behavior of the request and response of business level documents and MSH level signals is enforced by the CPA configurations.

CPA-enforced ebMS messaging enriches transactions by the imported CPA collaborations and the messaging characteristics, security constraints, and transport protocols that are defined in CPA sender and CPA receiver. The message flow can be an inbound or outbound request where the response is synchronous or asynchronous.

For inbound ebMS messages, the DataPower Gateway identifies the CPA receiver action through the CPA ID and service values that are extracted from the inbound message.

For outbound ebMS messages, the DataPower Gateway identifies the CPA sender action in the following process:
  1. Match the internal partner and external partner according to the business ID of the partners.
  2. Identify the CPA entry according to the internal partner and external partner pair. The CPA entry is matched as follows.
    1. If the CPA ID and service values are set by the b2b-ebms-cpa-id and b2b-ebms-service service variables, the CPA entry is matched against these variable values.
    2. If the CPA ID and service values are not set by variables, the external partner profile is checked for CPA bindings. The CPA entry is matched by examining the internal partner profile of the binding. The CPA entry that is associated with the internal partner profile from which the outbound messages are sent.
    3. If no CPA bindings are matched, the default CPA collaboration is used. This CPA collaboration is defined by the default CPA ID and default service of the external partner profile.
    4. If the default CPA ID and default service values are not specified for the external partner profile, the first CPA collaboration in the CPA entry table of the B2B gateway is selected.
  3. Match the CPA sender action that is specified in the matched B2B CPA collaboration object. The CPA sender action is matched as follows.
    • If CPA sender action is set by the b2b-ebms-action service variable, the DataPower Gateway uses the action uses is set by the variable.
    • When a CPA binding is matched, the DataPower Gateway matches the action that is specified in the CPA binding. When the action is not specified, or the action is not defined in the service of the CPA binding, the first action in the action list of the service is used.
    • When the default CPA settings are matched, the DataPower Gateway uses the default action. When the default action is not specified, the first action in the action list of the service is used.
    • When the first CPA entry in the B2B gateway configuration is used, the DataPower Gateway uses the first action in the action list of the service.