test

Sun B2B Suite ebXML Protocol Manager User's Guide

XDC Parameters

You must set the configuration properties governing the Atlanta or Berlin Company’s message exchange with the appropriate TP using the companies’ XDCs, both named ebXMLProtocol_delivery_channel1. These properties are the XDC parameters.

Before you begin to configure these parameters, be sure to display the appropriate TP’s name in the ePM Explorer (lower left side of the window).

Note –

The channels named External Delivery Channels (XDCs) in Enterprise Designer are named Delivery Channels in ePM. When referring to this component in ePM, the text still uses the term XDC, except when referring to specific text in the user interface.

This section explains how to set the Delivery Channel (external) parameters governing message exchange for tpAtlanta and tpBerlin.

ProcedureTo configure the XDC parameters for the current TP

  1. In the Explorer (lower left) side of ePM, click tpAtlanta or tpBerlin.

    The canvas displays the TP’s general properties.

  2. Click the Components tab.

    The selected TP’s XDC parameters for that tab appear (see the following table.).

    Binding Name 

    tpAtlanta: xdc_Berlin_ebXML_via_HTTP

    tpBerlin: xdc_Atlanta_ebXML_via_HTTP

    ToPartner Transport Name 

    HTTP 

    FromPartner Transport Name 

    HTTP 

    Packager Name 

    ebXML 

  3. Click the appropriate binding name. You are now entering parameters for this current binding.

    Note –

    The General parameters allow you to define general eXchange settings. See the eXchange Integrator User’s Guide for information on these parameters.

  4. Click the ToPartnerTransport tab.

    The tab’s parameters appear. These parameters allow you to supply information needed to transport data to the TP, that is, allowing the TP to receive data.

  5. For Use Synchronous Channel and Track For Auditing, enter false for both TPs.

  6. For All Purpose End Point, enter:


    http://<machine_ID><port_no>

    Where:

    • machine_ID: The name or IP address of the TP’s destination machine.

    • port_no: The name of the TP’s destination port number.

  7. Enter the value for Destination URL. The URL syntax used for this parameter is:


    http://<machine_ID><port_no>/<dep_profile>_servlet_<MSH_type>/    <MSH_type>

    Where:

    • machine_ID: The name or IP address of the TP’s destination machine.

    • port_no: The TP’s destination machine port number.

    • dep_profile: The current deployment profile name.

    • MSH_type: The message service handler type, in this case, ebXMLMSH.

      For the sample, enter:


      tpBerlin: http://<Atlanta_machine_ID>:<Atlanta_port_no>/dpInEbxmlBerlin_servlet_ebXMLMSH/ebXMLMSH

tpAtlanta: http://<Berlin_machine_ID>:<Berlin_port_no>/dpInEbxmlAtlanta_servlet_ebXMLMSH/ebXMLMSH

  8. Leave the rest of the parameters blank.

  9. When you are finished, click Save.

    Note –

    Be sure to click Save after you are finished configuring the parameters on each tab.

  10. Click the FromPartnerTransport tab.

    The tab’s parameters appear. These parameters allow you to supply information needed to transport data from the TP.

  11. Enter the values under the FromPartnerTransport tab in the same way as you do the ToPartnerTransport tab (see steps earlier in this procedure). Keep in mind that these are the values that allow you to send data from the TP.

  12. Click the ToPartner Packaging tab, and enter values for tpBerlin as shown in the following table.

    Note –

    The parameters listed in ePM before Soap Media Type are standard eXchange parameters. See the eXchange Integrator User’s Guide. for information on how to configure these parameters.

    Parameter 

    Value 

    SOAP Media Type 

    Multipart/Related 

    Digital Envelope Protocol 

    http://www.w3.org/2001/04/xmlenc# 

    Non-repudiation Protocol 

    XMLDSIG 

    Signature Algorithm 

    http://www.w3.org/2000/09/xmldsig#rsa-sha1 

    Digest Method/HashFunction 

    http://www.w3.org/2000/09/xmldsig#-sha1 

    Canonicalization Method 

    http://www.w3.org/TR/2001/REC-xml-c14n-20010315 

    Encryption Algorithm 

    DES3 

    Signature Type 

    SoapEnveloped 

    Ack Signature Required 

    perMessage 

    Ack Request is Per Message 

    true 

    Duplicate Elimination is Per Message 

    true 

    SOAP Actor 

    urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH 

    Sync Reply 

    mshSignalsOnly 

    Language 

    en-us 

  13. Click the FromPartner Packaging tab and edit the parameters as listed in the following table.

    Note –

    The parameters listed in ePM before Signature Type are standard eXchange parameters. See the eXchange Integrator User’s Guide for information on how to configure these parameters.

    Parameter 

    Value 

    Digital Envelope Protocol 

    http://www.w3.org/2001/04/xmlenc# 

    Non-Repudiation Protocol 

    XMLDSIG 

    Signature Type 

    SoapEnveloped 

    Ack Signature Required 

    perMessage 

    Ack Request is Per Message 

    true 

    Duplicate Elimination is Per Message 

    true 

    SOAP Actor 

    urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH 

    Sync Reply 

    mshSignalsOnly 

    Language 

    en-us 

  14. With the ToPartnerPackaging tab open, click Import (to the right of the Encryption Key text box) to import the current company’s public certificate.

    The Import a Certificate dialog box appears. Import the certificate as follows:

    • For Certificate Name, enter the appropriate certificate alias.

    • For Import from file, click Browse and navigate to the current company’s certificate file. See Extracted Files and Directories for file names.

    Note –

    If you are importing a certificate using ePM, you must apply the changes made during this step to the current Environment or restart the Logical Host. Otherwise, the certificate does not appear in the . keystore file.

  15. Repeat step 13 for the FromPartnerPackaging tab.

  16. When you are completely finished, click Save.