test

Sun B2B Suite ebXML Protocol Manager User's Guide

Configuring Companies’ Cryptographic Features

This section explains how to configure the eXchange Service’s cryptographic features.

Note –

To use ebXML Protocol Manager’s cryptographic features, make sure you have installed the appropriate . jar files, as explained under After You Install.

Since the sample assumes you are using cryptographic features (encryption, decryption, signatures, and verifications), additional steps are required for configuring these features for bhAtlanta1 eXchange Service and bhBerlin1 eXchange Service.

Note –

If the Logical Host is running while you are configuring private keys, you must apply any changes you make by selecting the Environment Explorer tree, then right-clicking lhAtlanta or lhBerlin (whichever is current) and, on the context menu, click Apply.

ProcedureTo configure the private key for the Atlanta Company

  1. On the envAtlanta Environment Explorer tree, right-click envAtlanta_ks_store.

  2. On the context menu, click Manage Private Keys.

    A Private Keys dialog box appears.

  3. Click Import.

    An Import Private Keys dialog box appears.

  4. Enter the following information, all lower-case:

    • Alias: privatekey1

    • Password: companya

  5. Browse to and select the CompanyA-Key.p12 file (see Extracted Files and Directories).

  6. Click OK, then click Close.

  7. Right-click bhAtlanta1 eXchange Service and, on the context menu, click Properties.

    A Properties dialog box appears. This dialog box allows you to configure the public and private keys for the current B2B host’s XDC named xdc_Atlanta_ebXML_via_HTTP.

  8. Using the drop-down menus, select privatekey1 under the Signature Key and Decryption Key columns. See Configuring Companies’ Cryptographic Features.

  9. Click OK.

    Note –

    If privatekey1 does not appear in the drop-down list, click the ellipsis [...] and click Import. Using the alias privatekey1 , import the CompanyA-Key.p12 file with the previously given password.

  10. When you are finished, click Save All.

ProcedureTo configure the public certificate for the Atlanta Company

  1. On the envAtlanta Environment Explorer tree, right-click envAtlanta_ks_store.

  2. On the context menu, click Manage Public Certificates.

    A Public Certificates dialog box appears.

  3. Click Import.

    An Import Public Certificates dialog box appears.

  4. Enter the following information, all lower-case:

  5. Alias: signkey

  6. Browse to and select the CompanyB-Cert.der file (see Extracted Files and Directories).

  7. Click OK, then click Close.

  8. When you are finished, click Save All.

    Note –

    Additionally, if the Logical Host is running, you must, on the Environment Explorer tree, right-click lhAtlanta or lhBerlin and, on the context menu, click Apply.

ProcedureTo configure the private key and public certificate for the Berlin Company

  1. Follow the envAtlanta steps provided under the Configuring Companies’ Cryptographic Features and the Configuring Companies’ Cryptographic Features with envBerlin, with the following exceptions:

    • For the envBerlin key store password, enter companyb.

    • Import the CompanyB-Key.p12 file

    • Import the CompanyA-Cert.der file.

      Note –

      See Extracted Files and Directories.

Results

The appropriate cryptographic information is now configured and associated with the following XDCs for each B2B Host: