test

Sun B2B Suite ebXML Protocol Manager User's Guide

Importing and Configuring TPs in ePM

This section explains how import TPs, as well as how to enter values and use the ePM configuration parameters for the TPs in the sample scenario.

Note –

For procedures on how to create TPs, see the eXchange Integrator User’s Guide.

Getting Started

Before you begin, your Repository and your eXchange database (Oracle) must be running and accessible. Enterprise Designer does not need to be running, and you do not need to have any Logical Hosts running.

In addition, you must perform the following operations:

The rest of this section explains these operations. For detailed information on configuring ePM, see Increasing the Oracle Number of Processes.

Starting ePM

This section explains how to start running ePM.

ProcedureTo start eXchange ePM

  1. Start a new browser session (that is, do not clone a new window of an existing session)

  2. Enter a Repository URL, with epm appended, for example:

    • If your Repository were running local on port 12000, the URL is:


          http://localhost:12000/epm

    • For a Repository running on machine herMachine on port 33000, the URL is:


          http://herMachine:33000/epm

    • IP addresses are also permissible, for example:


          http://10.18.75.85:36271/epm

      The string epm is case sensitive. In other words, ePM, Epm, and EPM are all errors.

  3. When the sign-in window appears, enter Enterprise Manager user name and password and click Sign In.

    The initial ePM window appears.

Importing TPs

Your next step is importing the Atlanta and Berlin Company TPs (TP files), as explained under this section. Keeping track of the TPs, where they are sent from and where they are received depends on which company is the current company. See Current Company Viewpoint and TPs.

This sample scenario has the following TPs:

ProcedureTo import the tpBerlin to envAtlanta

  1. From the initial ePM window, on the upper left side, click Import.

    The Import New Trading Partner window appears.

  2. Open B2B Repository then open envAtlanta.

  3. Select bhAtlanta1.

  4. Enter tpBerlin as the name for the new TP.

  5. Browse to


     C:\temp\eXchange\Sample\ebXML\TradingPartners
 and select the envAtlanta_BerlinSME.xml file and click Import.

    On the Explorer tree tpBerlin appears under envAtlanta.

ProcedureTo locate tpBerlin in the ePM window

  1. In the upper left side of the ePM window, click Select.

    A new window opens, prompting you to select a B2B host and TP.

  2. Open the B2B Repository and envAtlanta and click bhAtlanta1.

  3. Click Search, then click OK.

    On the Explorer tree tpBerlin reappears under envAtlanta.

ProcedureTo import tpAtlanta to envBerlin

  1. Follow the same steps as those in the Importing TPs, with the following exceptions:

    • Under B2B Repository open envBerlin.

    • Select bhBerlin1 and enter tpAtlanta as the TP name.

    • Import the file envBerlin_AtlantaSME.xml.

ProcedureTo locate tpAtlanta in the ePM window

  1. Search for tpAtlanta under envBerlin and bhBerlin1.

Current Company Viewpoint and TPs

When you are configuring a TP and pointing it to envAtlanta, you must take the viewpoint of that Environment’s company. So, the Atlanta Company’s TP is tpBerlin.

Therefore, in terms of the companies, ToPartner means from the Atlanta Company and FromPartner to the Atlanta Company.

Conversely, When you are configuring a TP and pointing it to envBerlin, you must take the viewpoint of that Environment’s company. So, the Berlin Company’s TP is tpAtlanta.

Therefore, in terms of the companies, ToPartner means from the Berlin Company and FromPartner to the Berlin Company.

Configuring TP Parameters

When you import a TP, its related configuration parameter values are set in part based on parameters stored in the export file and in part based on the name of the TP. This section explains how to update these parameters under the following sections:

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.

IDC Parameters

You can set the parameters governing the current company’s internal message processing, when handling messages received and preparing messages to be sent. These properties are the IDC 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 –

IDC bindings are optional and not required for an ebXML Protocol Manager Project.

This section explains how to set the Internal Delivery Channel parameters used for the current company’s internal message processing.

Note –

In the sample scenario, tpBerlin (for the Atlanta Company) has no IDCs.

ProcedureTo configure the IDC parameters for the tpBerlin

  1. In the Explorer, click tpBerlin.

    The canvas displays the TP’s general properties.

  2. Click the Components tab.

    The current TP’s delivery channel parameters are displayed.

  3. Click the Internal Delivery Channels tab for the current TP.

    The IDC parameters appear. See the following tables.

    Binding Name 

    idcAtlanta_ebXML_Send_via_File 

    Direction 

    Sender 

    Transport Name 

    JMS 

    Binding Name 

    idcAtlanta_ebXML_Rcv_via_File 

    Direction 

    Receiver 

    Transport Name 

    JMS 

  4. To continue IDC configuration for tpBerlin, click the binding name for the first IDC (idcAtlanta_ebXML_Send_via_File), click the Sender Transport tab, and make changes as shown in the following table.

    FilePattern: * 

    *.txt 

    Directory: * 

    C:\temp\eXchange\Sample\Data\Atlanta\OutboundebXML\

  5. To finish IDC configuration for tpBerlin, click the binding name for the second IDC (idcAtlanta_ebXML_Rcv_via_File), click the Sender Transport tab, and make changes as shown in the following table.

    FilePattern: * 

    *.txt 

    Directory: * 

    C:\temp\eXchange\Sample\OutputebXML\

  6. When you are finished, click Save.

    Note –

    See Increasing the Oracle Number of Processes and the eXchange Integrator User’s Guide for more information.

Messaging Actions Parameters

You must also configure ebXML Protocol Manager’s messaging actions under the ePM Messaging Service Configuration. These settings control messaging actions (inbound and outbound) for an ebXML MAD.

Configure the Properties and Messaging Actions for the TPs, using the parameters under these tabs, for the appropriate Messaging Service.

These configuration parameters define settings that allow ebXML Protocol Manager to set up, control, and order the sending and receiving of messages. For information on how to configure these parameters, see Configuring Messaging Actions.