Generating an inverse AS4 exchange profile configuration

In AS4 Microservice, you can generate the inverse configuration of an inbound AS4 exchange profile to send to your trading partner. Your trading partner can use the generated configuration in the received file to create a corresponding outbound AS4 exchange profile.

Before you begin

You can generate an inverse AS4exchange profile only if all the components of the exchange profile are configured. Ensure that all the sections of the exchange profile are completed.

About this task

With the Generate Inverse function, you can quickly and easily generate and send the configuration of an inbound exchange profile in an XML format to your trading partner. You can share the XML file with your trading partner either through an email or upload the file to a specified location. The trading partner uses the generated inverse exchange profile to configure a corresponding outbound exchange profile. To generate an inverse exchange profile, complete the following procedure:
Note: After you generate an inverse exchange profile configuration, it is suggested not to import (Create From Inverse) the exchange profile configuration into the same AS4 Microservice instance. The generated inverse exchange profile configuration is intended to be used by a trading partner to create a corresponding outbound exchange profile.
For a complete list of XML elements associated with generating an inverse exchange profile and creating an exchange profile from a generated inverse configuration, see ../administering/as4/meig_as4_jumpstartxmlelements.html.

Procedure

  1. Log in to AS4 Microservice. You must have exchange profile read permissions to generate an inverse profile configuration.
  2. Click Exchanges > Exchange Profiles.
  3. On the Exchange Profiles page, click the AS4 inbound exchange profile for which you want to generate an inverse configuration profile.
    Important: Only deployed AS4 exchange profiles support the generation of inverse profiles.
  4. On the detailed view page for that exchange profile, click the Deploy Exchange Profile section and click Generate Inverse.
  5. Conditional: If user authorization and authentication with user credentials is enabled for the exchange profile that you are exporting, click Yes to include the user credential in the XML file.
  6. Conditional: If multiple users are associated with the exchange profile, select the required user.
  7. Save the XML file to the appropriate location.
    The following table provides a list of components for which the inverse are generated when you complete the Generate Inverse task.
    Table 1. Exchange profile components for which the inverse are generated
    Parameter Configuration of the inbound exchange profile that is generated Configuration in the generated XML file

    Exchange profile direction

    Inbound

    Outbound

    Owning organization

    AS4 Microservice master organization.

    The owner organization role is changed to the trading partner organization role.

    Trading partner organization

    Trading partner

    The trading partner role is changed to the owner organization role.

    Receiver ID

    Receiver ID of the owner organization.

    The receiver ID is changed to sender ID.

    Sender ID

    Sender ID of the trading partner organization.

    The sender ID is changed to the receiver ID.

    If trading partner is anonymous, the value for sender ID is not provided in the exported file.

    Service

    The service for which the exchange profile is used.

    The service remains the same.

    Agreement URI

    The mutually (between the owner organization and the trading partner) agreed on location where the p-mode and other message exchange-related information is uploaded or posted.

    The agreement URI remains the same.

    P-Mode ID

    The mutually agreed on identifier that is used to identify the processing-mode (p-mode) configuration for the conformance policy.

    The p-mode ID remains the same.

    AS4 receiver information

    The AS4 receiver information includes the AS4 service URI and the host server port information.

    For example, if the port number of the HTTP or HTTPS server that you have associated with the AS4 receiver is 63000, and the URI of the AS4 receiver is /test-uri, then the URL of the AS4 receiver that is exported is, http://hostname:63000/test-uri.

    Note: The host name can be replaced with the IP address. Also, the IP address or the port can be of a proxy server or an external load balancer.

    The HTTP or HTTPS server information is used as the HTTP or HTTPS destination information.

    Conformance policy - security settings

    The following outbound, inbound, and user authentication security settings are exported:
    • Outbound exchanges signing configuration
    • Inbound exchanges signing configuration
    • User authentication credentials (if user authentication checking is enabled)

    If Outbound exchanges use X.509 certificate to sign the data is enabled in the conformance policy that is associated with the inbound exchange profile, the public key of the certificate that is used to sign outbound messages is exported. If primary and secondary certificates are associated with the certificate alias, both the certificates are exported.

    If Inbound exchanges require signed messages is enabled in the conformance policy that is associated with the inbound exchange profile, the setting is applied to the outbound exchanges. A corresponding setting must be configured in the conformance policy of the trading partner.

    If Enable user authentication checking is enabled in the conformance policy that is associated with the inbound exchange profile, the same setting is applied to the outbound exchange profile. The user credentials that are associated with the conformance policy are also exported. If multiple users are associated with the exchange profile, a single, selected credential is exported.

    Conformance policy - Reception awareness settings

    The reception awareness settings of the conformance policy

    If Require receipt is enabled in the conformance policy, the same setting is applied to the outbound exchange profile.

    Receipts are sent to the corresponding HTTP or HTTPS server in the exported file.

    Connection settings

    User name and password

    User name and password credentials are exported.

    Pull destination name

    Pull destination name is exported.

    If a default pull destination is specified in the inbound exchange profile, the pull destination name is not specified in the exported file.

    Pull destination name is exported.

    Error destination (push)

    AS4 receiver

    The HTTP or HTTPS server that is associated with the AS4 receiver (of the inbound exchange profile) is used to send ebMS errors.

    Error destination (pull)

    AS4 receiver

    The HTTP or HTTPS server that is associated with the AS4 receiver (of the inbound exchange profile) is used to send ebMS errors.