Configuring an AS4 outbound one-way push exchange profile

An exchange profile defines how messages are exchanged with a trading partner, and how those messages are processed internally. An one-way push exchange involves transfer of a single user message unit. An AS4 outbound one-way push exchange pattern is used by organizations to send catalog updates, promotions for new products, and updates on orders.

Before you begin

You also can import an exchange profile as a resource from another installation of AS4 Microservice. For more information, see ../reference/as4/meg_resource_commands.html. Also, through the user interface, you can upload an exchange profile that has been saved as an XML jumpstart file from another installation of AS4 Microservice.

About this task

When you create an AS4 outbound one-way push exchange profile, you must associate a conformance policy with the exchange profile, specify the message exchange pattern, participating organizations, receiver, destination, and connection settings. In an outbound one-way push exchange, your organization is the initiator or producer of the message that is sent to a partner.

The exchange profile uses the owner organization of the conformance policy. In the conformance policy, you must specify either the default B2B Master Organization owner organization or a customized owner organization.

When you are creating an exchange profile, you can browse to other pages or tabs of the user interface if required. The information that you have entered for the exchange profile is saved and you can complete the exchange profile configuration and deploy it at a later time. A progress bar on the Exchange Profiles collection page (Exchanges > Exchange Profiles) indicates the percentage of completion of the exchange profile. A percentage of 20 is allocated to each of the following components of the exchange profile:

  • Exchange profile name
  • Trading partner configuration
  • Trigger
  • Action
  • Deployment

When all the components are configured, the progress bar indicates 100 percent, denoting that the exchange profile configuration is complete and the exchange profile is deployed.

Procedure

To create an AS4 outbound one-way push exchange profile, complete the following steps:

  1. Log in to AS4 Microservice as the Master Account Administrator.
  2. Click Exchanges > Exchange Profiles.
  3. On the Exchange Profiles page, click New > AS4 Outbound.
  4. On the New Exchange Profile page, specify values for the following fields and click Save.
    Field Description
    Profile name Specify a unique name for the outbound one-way push exchange profile.
    Select the message exchange pattern for the profile Select AS4 Outbound One-Way/Push message exchange pattern.
    Conformance policy

    Specify the conformance policy that you want to associate with the exchange profile. For a message exchange, a conformance policy defines the settings for the owner organization, security, reception awareness, error handling, notification, and file size optimization. Select the conformance policy that suits your requirements.

    Use one of the following methods to specify a conformance policy:

    • To specify an existing conformance policy, click Select. The Conformance Policy list includes three default conformance policies (Minimal Client, Light Client, and EbHandler) and the custom conformance policies that you have configured.
    • To create a new conformance policy, click Add Conformance Policy.

    After you specify a conformance policy, click Save.
  5. Click Edit corresponding to the Basic Properties section, specify values for the following fields, and click Save.
    Note: When configuring the exchange profile, do not assign the value Any to the following fields:
    • Service
    • Service type
    • Sender ID
    • Receiver ID
    • Sender ID type
    • Receiver ID type
    Any is a reserved value. It is used for exchange profile look up when the any of the preceding fields do not have a user assigned value.
    Field Description
    Name The name that is entered in the Profile name field is populated here.
    Description Optional: Type a description for the exchange profile.
    Service Optional: You can specify a mutually agreed on (between your organization and the partner) service or a service assigned by a standards organization, for which the exchange profile can be used. For example, if catalog updates service is specified, the exchange profile is used for receiving catalog updates.

    Example of a service is urn:example.org:services:CatalogUpdates.
    Service type Optional: The service type indicates how the participating organizations interpret the service.

    For example, the catalog updates service can have new product updates, existing product updates, products removed from the catalog, and so on.

    Example of a service type is, NewProductUpdates.
    Agreement URI Optional: Type the URI of the location of the agreement (related to the p-mode parameter configuration and operation) between your organization and the partner. The URI must be agreed on by both the partners.

    Example of an agreement URI is, http://registry.example.com/cpa/123456.
    Processing mode ID Optional: Specify the mutually agreed on processing mode ID that is used to identify the processing mode configuration of the conformance policy.

    Example of a processing mode ID is SupplierOrderProcessing.PMode.
    Override party ID Optional: Select the Allow business partner ID to be overridden check box to override the business partner ID that is specified in the exchange profile and use the ID that is specified in the business document object (BDO) by the business application or in an user exit.
  6. Click Participating Organizations to specify the participating organizations.
    Field Description
    Owner Organization The owner organization is specified by default from the owner organization in the conformance policy of the exchange profile. In an AS4 outbound one-way push exchange profile, the owner organization is the initiator or producer of a message.
    Sender ID Optional: Click New and type a sender ID. The sender ID is the unique business identifier that is used to identify the owner organization. The ID can be mutually agreed on or assigned by an international code designator. For example, a DUNS ID.

    If sender ID type is not specified, the sender ID must be a valid unique resource identifier (URI).
    Owner role Optional: The owner role is specified by default. To customize the role, remove the default role and enter a new one.
    Sender ID type Optional: Click New and specify a sender ID type.

    The sender ID type indicates the area or domain to which the content of the sender ID of the trading partner organization belongs to.

    It is recommended that the value of the sender ID type be an URI. For example, urn:oasis:names:tc:ebxmlcppa: partyid-type:duns. However, the type can be any text or term that is mutually agreed on with the partner.
    Trading Partner Organization Click Select and select the trading partner organization. In an outbound exchange profile, the trading partner is the consumer or responder of the message.

    To create a new trading partner organization, click New Organization.

    Alternatively, you can select Use Anonymous Partner for authentication and authorization, instead of configuring a partner organization in the system. The anonymous partner allows you to represent more than one partner through the anonymous partner mechanism. This mechanism supports many trading partners (or individual users) without needing to configure an organization (identity representation in the system), specific certificates, and exchange details for each one.
    Trading partner role Optional: The trading partner role is specified by default. To customize the role, remove the default role and enter a new one.
    Receiver ID Optional: Click New and type a receiver ID. The receiver ID is the unique business identifier that is used to identify the trading partner. The ID can be mutually agreed on or assigned by an international code designator. For example, a DUNS ID.

    If receiver ID type is not specified, the receiver ID must be a valid unique resource identifier (URI).
    Receiver ID type Optional: Click New and specify a receiver ID type.

    The receiver ID type indicates the area or domain to which the content of the receiver ID of the owner organization belongs to.

    It is recommended that the value of the receiver ID type be an URI. For example, urn:oasis:names:tc:ebxmlcppa: partyid-type:duns. However, the type can be any text or term that is mutually agreed on with the partner.
  7. Click Outbound Push Request and specify Trigger and Action settings for the outbound push request.
    1. In the Trigger section, specify the messaging receiver that receives the push request message along with the business document object (BDO) and attachments from the business application.
    2. In the Action section, specify the HTTP or HTTPS destination of the trading partner where the push request message is packed and sent.
    Field Description
    Select Receiver Click Select and select the messaging receiver.

    To select a different messaging receiver, click Remove and select a new receiver.

    To create a new AS4 receiver, click New Messaging Receiver.
    Select destination Select the HTTP or HTTPS destination where the push request is sent.

    For Anonymous Partner, select URL overriding and provide the destination URL in BDO. The documents are delivered to the specified URL using the configuration available in the Exchange Profile.

    In future, the Credentials parameters is provided during runtime.
    Connection Settings For information about configuring connection settings for outbound push request, see Configuring connection settings for outbound push request in outbound one-way push exchange.

    To edit the connection settings, click Edit.

    To remove the connection settings, click Remove.

    Anonymous Partner:

    If you want to use encryption, you must provide an encryption certificate in the BDO as part of the Receiving Partner. You can add encryptAlgoNameWithKeyStrength, encryptKeyTransportAlgorithm, securityTokenReferenceType properties also in BDO as part of Receiving Partner. Valid values for these properties are:
    • encryptAlgoNameWithKeyStrength: AES_128, AES_256, AES_128_GCM, TRIPLE_DES_168
    • encryptKeyTransportAlgorithm: RSA-1_5, RSA-OAEP-MGF1P, RSA-OAEP
    • securityTokenReferenceType: BINARY_SECURITY_TOKEN_SINGLE_CERT, X509_KEY_IDENTIFIER, ISSUERNAME_AND_SERIALNUMBER, SKI_KEY_IDENTIFIER
    For example: 
    <PartnerProperties>
<Property name="encryptAlgoNameWithKey
Strength" value="AES_128" /> 
<Property name="encryptKeyTransport
Algorithm" value="RSA-OAEP" /> 
<Property name="securityTokenReference
Type" value="X509_KEY_IDENTIFIER" /> 
</PartnerProperties>

    If you want to use signing, the application uses the Embedded Certificate for signature verification.

    In future, for Forward Proxy and Basic Authentication, credentials will be provided during runtime.
  8. In the Deploy Exchange Profile section, click Deploy to deploy or enable the exchange profile.
    If the exchange profile configuration is incomplete, a list of items that must be configured to complete the exchange profile configuration is displayed in the Deploy Exchange Profile section. The Deploy button is enabled only when all the sections of the exchange profile are in Complete status.
    Note: When you update an exchange profile after deploying, the percentage complete shows as 80%, but the status shows as Deployed. For the updates to take effect and the percentage complete to show as 100 percent, you must redeploy the exchange profile.