Sun B2B Suite AS2 Protocol Manager User's Guide

Configuring the TPs in the Sample Scenario

This section explains how to configure the ePM parameter settings for the Atlanta and Berlin TPs in the sample scenario.

Configuring the Atlanta TP

This section explains how to configure the ePM parameters for the Atlanta TP, ePM port No. 18001. Keep in mind that the Atlanta TP is Berlin, that is, Atlanta (envA) trades data with its partner, Berlin (envB).

ProcedureTo Configure the Atlanta TP Parameters

  1. In ePM Explorer, select Transaction Profiles > AS2AGProfile > Pass Through Inbound FromPartner.

  2. In the Settings tab under Pass Through Inbound FromPartner, configure Cryptography Settings as shown in Figure 6–9 and as follows:

    • Business Protocol Decryption Key: [None]

    • Delivery Protocol Decryption Key: [None]

    • Business Protocol Signature Verification Certificate: [None]

    • Delivery Protocol Signing Verification Certificate: companya_cert

    • Signature Protocol: [None]

    For details, see Figure 6–9.

    Figure 6–9 Atlanta TP Inbound Cryptography Settings

    Atlanta TP Inbound Cryptography Settings

  3. In the Settings tab, configure settings for Delivery Protocol — Inbound FromPartner settings as shown in Figure 6–10 and as follows:

    • Decryption Handler: Decryption handler BPs

    • Signature Validation Handler: Signature validation handler BPs

    • Decompression Handler: Decompression handler BPs

    For details, see Figure 6–10.

    Figure 6–10 Atlanta TP Delivery Protocol — Inbound FromPartner Settings

    Atlanta TP Delivery Protocol — Inbound
FromPartner Settings

  4. In the Overrides tab, configure inbound overrides as shown in the following figures:

    ePM Atlanta Overrides Inbound, Screen 1ePM Atlanta Overrides Inbound, Screen 2ePM Atlanta Overrides Inbound, Screen 3ePM Atlanta Overrides Inbound, Screen 4
  5. In ePM Explorer, select Transaction Profiles > AS2AGProfile > Pass Through Outbound ToPartner.

  6. In the Settings tab under Pass Through Outbound ToPartner, configure Cryptography Settings as shown in Figure 6–11 and as follows:

    • Business Protocol Signing Key: [None]

    • Delivery Protocol Signing Key: companya

    • Business Protocol Encryption Certificate: [None]

    • Delivery Protocol Encryption Certificate: companya_cert

    • Encryption Protocol: [None]

    For details, see Figure 6–11.

    Figure 6–11 Outbound Atlanta TP Cryptography Settings

    Outbound Atlanta TP Cryptography Settings

  7. In ePM Canvas, configure Delivery Protocol — Outbound ToPartner settings as shown in Figure 6–12 and as follows:

    • Encryption Handler: Encryption handler BPs

    • Signing Handler: Signing handler BPs

    • Compression Handler: Compression handler BPs

    For details, see Figure 6–12.

    Figure 6–12 Atlanta TP Delivery Protocol — Outbound ToPartner Settings

    Atlanta TP Delivery Protocol — Outbound
ToPartner Settings

  8. In the Overrides tab, configure TP overrides under Delivery Protocol — Outbound ToPartner as shown in Figure 6–13 and as follows:

    • Use Encryption: Yes

    • Use Signature: Yes

    • Use Compression: Yes

    For details, see Figure 6–13.

    Figure 6–13 Atlanta TP Delivery Protocol — Outbound ToPartner Override Settings

    Atlanta TP Delivery Protocol — Outbound
ToPartner Override Settings (Screen 1)

  9. In the Overrides tab, configure additional outbound overrides as shown in the following figures:

    ePM Atlanta Overrides Outbound, Screen 2ePM Atlanta Overrides Outbound, Screen 3ePM Atlanta Overrides Outbound, Screen 4

Configuring the Berlin TP

This section explains how to configure the ePM parameters for the Berlin TP, ePM port No. 28001. Keep in mind that the Berlin TP is Atlanta, that is, Berlin (envB) trades data with its partner, Atlanta (envA).

ProcedureTo Configure the Berlin TP Parameters

  1. In ePM Explorer, select Transaction Profiles > AS2AGProfile > Pass Through Inbound FromPartner.

  2. In the Settings tab under Pass Through Inbound FromPartner, configure settings for Delivery Protocol — Inbound FromPartner as shown in Figure 6–14 and as follows:

    • Decryption Handler: Decryption handler BPs

    • Signature Validation Handler: Signature validation handler BPs

    • Decompression Handler: Decompression handler BPs

    For details, see Figure 6–14.

    Figure 6–14 Delivery Protocol — Inbound FromPartner Settings

    Delivery Protocol — Inbound FromPartner
Settings

  3. In the Settings tab, configure settings for ACK — Delivery Protocol — Outbound ToPartner as shown in Figure 6–15 and as follows:

    • Encryption Handler: Encryption handler BPs

    • Signing Handler: Signing handler BPs

    • Compression Handler: Compression handler BPs

    For details, see Figure 6–15.

    Figure 6–15 ACK — Delivery Protocol — Outbound ToPartner Settings

    ACK — Delivery Protocol — Outbound
ToPartner Settings

  4. In the Overrides tab, configure inbound overrides as shown in the following figures:

    Berlin Inbound Overrides, Screen 1Berlin Inbound Overrides, Screen 2Berlin Inbound Overrides, Screen 3Berlin Inbound Overrides, Screen 4Berlin Inbound Overrides, Screen 5
  5. In the Overrides tab, configure TP overrides under Delivery Protocol — Outbound ToPartner as shown in Figure 6–16 and as follows:

    • Use Encryption: No

    • Use Signature: No

    • Use Compression: No

    For details, see Figure 6–16.

    Figure 6–16 Delivery Protocol — Outbound ToPartner Settings

    Berlin Delivery Protocol — Outbound ToPartner
Settings (Screen 1)

  6. In the Overrides tab, configure additional outbound overrides as shown in the following figures:

    Berlin Outbound Overrides, Screen 2Berlin Outbound Overrides, Screen 3Berlin Outbound Overrides, Screen 4