Configuring Trading Partners

This topic includes the following sections:

• Introduction to Configuration of Trading Partners

• Creating a Trading Partner

• Modifying a Trading Partner

• Removing a Trading Partner

• Configuring a Trading Partner Party ID

• Configuring a Certificate for a Trading Partner

• Configuring a Document Exchange for a Trading Partner

• Configuring a Trading Partner Transport

• Configuring a Delivery Channel for a Trading Partner

 

---

Introduction to Configuration of Trading Partners

One of the basic building blocks of B2B e-commerce is the trading partner. A trading partner's identity must be defined in the context of the business purpose of the e-community. In the WebLogic Integration environment, a trading partner is understood as an entity that has an agreement with another entity to participate in a specific business exchange, or conversation, by playing a predefined role.

The WebLogic Integration B2B Console allows you to create, configure, and modify trading partners. This topic provides instructions for basic configuration of trading partners. Instructions for advanced configuration of trading partners are available in Using Advanced Trading Partner Configuration Options.

 

---

Creating a Trading Partner

To create a trading partner:

1. Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed.

2. Click the Create a new Trading Partner link at the top of the list. The display is modified to allow you to define a new trading partner.

3. Enter new values or modify the default values shown in the fields. No other tabs are activated until you enter the required information.

   Table 3-1 Fields on the Trading Partner Tab  

   Field	Description
   Name	Name of the trading partner you want to create or modify. Once an instance is created, this field is read-only. (Limit is 254 characters.)
   Description	Brief description of the trading partner. (Limit is 254 characters.) (Optional)
   Type	Choose local or remote. Indication of whether the trading partner is local (that is, running on the same machine as the B2B engine) or remote (that is, running on a machine other than the host machine for the B2B engine).
   Address	Address for the trading partner. (Limit is 254 characters.) (Optional)
   Email	E-mail address for the trading partner. (Limit is 254 characters.) (Optional)
   Phone	Phone number for the trading partner. (Limit is 254 characters.) (Optional)
   Fax	Fax number for the trading partner. (Limit is 254 characters.) (Optional)
   WLS User Name	Name of the WebLogic Server users to whom the trading partner certificate should be mapped when messages are sent by that trading partner. When this field is populated, a WebLogic Server user account is created. The default password is the username. This setting affects client-side security setting especially in relation to connections from remote trading partners. For complete information about the security features provided by WebLogic Server and B2B integration functionality, see Configuring Security in Implementing Security with B2B Integration.
   Encoding	Natural language to be used for communications with this trading partner. Messages sent by this trading partner are encoded in the language specified here. (Optional) The default is UTF-8 (English). For more information, see "A Note About Trading Partner Encoding" in Configuration Requirements in Administering B2B Integration.
   Status	Field in which you can specify whether you want the trading partner to be active or inactive.
   	Active	Trading partner is active and available for use by B2B integration users.
   	Inactive	Trading partner is inactive and unavailable for use.

   
    

4. Click Create. If the name of the trading partner is invalid, an error message is displayed. You must complete all required fields before you can create a new trading partner.

After you create a new trading partner, the General tab is refreshed and the information you entered is displayed. The other configuration tabs are also activated and the Create option is replaced by two new options: Apply and Reset. You can now configure additional elements for the trading partner. The new trading partner is displayed in the list of all trading partners.

 

---

Modifying a Trading Partner

To modify an existing trading partner:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select a trading partner. The configuration fields on the page for that trading partner are populated.

3. Select the tab containing the information you want to modify. For more information, see Creating a Trading Partner.

4. Click Add/Apply. The General tab is refreshed with the new information you entered. You can now modify elements on other configuration tabs, as needed.

 

---

Removing a Trading Partner

Note: A trading partner cannot be removed from the repository when an active collaboration agreement is using the party ID for that trading partner.

To remove a trading partner from the repository:

1. Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed.

2. Select one or more trading partners.

3. At the bottom of the window, select Remove.

 

---

Configuring a Trading Partner Party ID

Use trading partner party IDs to specify the business entities that take part in a business conversation. A trading partner can have a number of party IDs to identify parties in different collaboration agreements. For example, company XYZ could create a trading partner named XYZTradingPartner; this trading partner could participate in a number of conversations, say, a request for a quote and a purchase order requisition.

Creating a New Party ID

A party ID is a character string that is used, with a name, to identify a trading partner in the context of a collaboration agreement. You can use party IDs to define elements unique to your business. For example, you might want to enter a Dun and Bradstreet's Universal Numbering System (DUNS) number as a party ID for a specific trading partner.

To create a new party ID:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab, and then the Party IDs tab. The following fields are displayed on the Party ID tab:

   Table 3-2 Fields on the Party ID Tab

   Field	Description
   Party ID	Unique, descriptive party ID composed of any combination of character. A party ID is used with a trading partner name to identify a party in a collaboration agreement. For example, Dell DUNS. (Required)
   Business ID	Descriptive name for the business ID you want to associate with this party ID. For example, DUNS. (Optional)
   Business ID Type	Meaningful name for the business ID type that describes the relationship between the business ID and the party ID. For example, a company's Dun & Bradstreet number. (Optional)
   Available Party IDs	List of all existing party IDs.

   
    

3. Modify the appropriate fields, as necessary.

4. Click Add/Apply. Your new party ID is added to the list of available party IDs.

Modifying a Party ID

To modify an existing party ID:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab, then select the Party ID tab if it is not active. Any available party IDs are listed.

3. Select the party ID you want to modify. The configuration fields for that ID are populated.

4. Modify the required fields.

5. Click Add/Apply.

Removing a Party ID

To remove a party ID:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab. Select the Party ID tab if it is not active. A list of available party IDs is displayed.

3. Select the party IDs you want to delete.

4. Click Remove.

 

---

Configuring a Certificate for a Trading Partner

WebLogic Integration supports the use of digital certificates to make transactions among trading partners secure. These certificates, along with private keys, support the following three security features for B2B integration functions:

• SSL authentication

• Digital signatures

• Data encryption for RosettaNet

For complete information about the security features provided by WebLogic Server and B2B integration functionality, see Configuring Security in Implementing Security with B2B Integration.

Adding a Certificate Reference and Importing a Certificate into the Keystore

If you want to use a certificate in your application, you must create a reference to it in the WebLogic Integration repository. You also have the option of importing that certificate, along with the private key associated with it, into the Keystore.

To create a certificate reference in the repository and import the certificate, with its private key, into the Keystore, complete the following procedure:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab. If the Certificates tab is not active, select it now. Click the Create a Certificate Entry link.

   If the current trading partner is local, see Table  3-3 for descriptions of the fields that are now displayed on the Certificates tab.

   If the current trading partner is remote, see Table  3-4 for descriptions of the fields that are now displayed on the Certificates tab.

   Table 3-3 Fields on the Certificates Tab for a Local Trading Partner

   Field	Description
   Certificate Name	Specify the name of the certificate in the WebLogic Integration repository. The name you specify is also used as the Keystore alias.
   Certificate Type	Specify the type of the WebLogic Integration trading partner certificate:
   	Client certificate	Digital certificate for this remote trading partner. Required when the SSL protocol with mutual authentication is used.
   	Signature certificate	Required for each trading partner if nonrepudiation is configured for the conversation.
   	Encryption certificate	Required for each trading partner when business message encryption is used for the collaboration. Note that encryption support is available only with the RosettaNet protocols.
   Certificate Location	Location (full pathname) of the certificate file to be imported into the WebLogic Server Keystore.
   Private Key Location	Location (full pathname) of the private key file. WebLogic Integration extracts the private key from the private key file after verifying the private key password is correct. The private key is then used by the local trading partner to digitally sign a message to be sent to a remote trading partner or to decrypt a message received from a remote trading partner. This field is required only by the local trading partner who is using the one of the following security features: SSL, digital signatures, and encryption.
   Private Key Password	Enter the password for the private key. If the private key is not password protected, enter the password of the Keystore. The correct password must be entered before WebLogic Integration can import the private key into the Keystore. This field is required if a value is entered in the Private Key Location field.

   
    

   Table 3-4 Fields on the Certificates Tab for a Remote Trading Partner

   Field	Description
   Certificate Name	Specify the name of the certificate in the WebLogic Integration repository. The name you specify is also used as the Keystore alias.
   Certificate Type	Specify the type of the WebLogic Integration trading partner certificate:
   	Client certificate	Digital certificate for a remote or local trading partner. Required when the SSL protocol with mutual authentication is used.
   	Server certificate	Digital certificate for a remote trading partner. Required when the SSL protocol is used.
   	Signature certificate	Required for each trading partner if nonrepudiation is configured for the conversation.
   	Encryption certificate	Required for each trading partner when business message encryption is used for the collaboration. Note that encryption support is available only with the RosettaNet protocols.
   Certificate Location	Location (full pathname) of the certificate file to be imported into the WebLogic Server Keystore.

   
    

3. Enter the configuration information for the certificate:

   Enter the appropriate fields for a local trading partner, based on the information provided in Table  3-5.

   Enter the appropriate fields for a remote trading partner, based on the information provided in Table  3-6.

   Table 3-5 Certificates Tab Fields for a Local Trading Partner

   If the certificate . . .	Enter values in these fields . . .	Is the field required or optional?
   Has not been imported into the Keystore	Certificate Name (becomes the Keystore alias name)	Required
   	Certificate Type	Required
   	Certificate Location	Required
   	Private Key Location	Required
   	Private Key Password	Required
   Has already been imported into the Keystore	Certificate Name (alias name in the Keystore for this certificate)	Required
   	Certificate Type	Required
   	Certificate Location	Optional
   	Private Key Location	Optional
   	Private Key Password	Required

   
    

   Table 3-6 Fields to Enter in the Certificates Tab for a Remote Trading Partner

   If the certificate . . .	Enter values in these fields . . .	Is the field required or optional?
   Has not been imported into the Keystore	Certificate Name (becomes the Keystore alias name)	Required
   	Certificate Type	Required
   	Certificate Location	Required
   Has already been imported into the Keystore	Certificate Name (alias name in the Keystore for this certificate)	Required
   	Certificate Type	Required
   	Certificate Location	Optional

   
    

4. If the certificate has not already been imported into the Keystore, select the Save the certificate to the Keystore checkbox.

5. Click Add.

Removing a Certificate Reference

To remove a certificate reference in the WebLogic Integration repository:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab. Select the Certificates tab if it is not active. A list of available certificates is displayed.

3. Select the certificate references you want to delete from the WebLogic Integration repository. If you also want to remove the certificate from the Keystore, select the Remove the Certificate from the Keystore checkbox.

4. Click Remove.

 

---

Configuring a Document Exchange for a Trading Partner

Use the Document Exchange tab for a specified trading partner to define the business protocol binding information that the parties in a collaboration agreement use when exchanging documents.

To create a trading partner document exchange:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab. Select the Doc Exchange tab if it is not active.

3. Select a Business Protocol Binding. The remainder of this procedure depends on your selection. For more information, see the following sections:

   • Configuring cXML for a Document Exchange (Deprecated).

   • Configuring RosettaNet 1.1 for a Document Exchange.

   • Configuring RosettaNet 2.0 for a Document Exchange.

   • Configuring XOCP 1.1 for a Document Exchange (Deprecated).

   • Configuring ebXML 1.0 for a Document Exchange.

For complete information about using certificates in document exchange IDs, see Configuring Security in Implementing Security with B2B Integration.

Configuring cXML for a Document Exchange (Deprecated)

Note: The cXML business protocol is deprecated in this release of WebLogic Integration. For information about the feature that is replacing the cXML business protocol, see BEA WebLogic Integration Release Notes.

To create a trading partner document exchange ID using the cXML 1.1 binding:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab, then select the Doc Exchange tab.

3. In the Business Protocol Binding field, select cXML 1.1. The cXML values are shown in the following table.

   Table 3-7 cXML Fields on the Document Exchange Tab    

   Field	Description
   Document Exchange Name	Unique name for the document exchange ID. This ID is used to associate business protocol binding information.
   Business Protocol Binding	Select cXML 1.1 from the drop-down list. You can associate one business protocol with each document exchange ID. The chosen protocol is bound to the trading partner document exchange name specified in the Document Exchange Name field.
   Business Protocol Definition	Business protocol associated with the business protocol binding specified in the previous field.
   Shared Secret	Information used to validate that the party sending the data is authentic.
   Signature Certificate	Type of signature certificate selected from the drop-down list.
   Available Document Exchanges	List of available document exchanges.

   
    

4. When you finish adding or updating the document exchange, click Add/Apply.

Configuring RosettaNet 1.1 for a Document Exchange

To create a trading partner document exchange ID using the RosettaNet 1.1 binding:

1. Do one of the following:

   • Click Trading Partners in the navigation tree to display the Trading Partners page, then locate and click the appropriate trading partner.

   • Click a trading partner listed in the navigation tree. (This option is available only if the Display entities on the navigation tree option is selected on the WebLogic Integration B2B Console Preferences tab as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab. Select the Doc Exchange tab if it is not active.

3. In the Business Protocol Binding field, select RosettaNet 1.1. The default values for all the fields on the Doc Exchange tab are shown in the following table.

   Table 3-8 RosettaNet 1.1 Fields on the Doc Exchange Tab  

   Field	Description
   Document Exchange Name	Unique name for the document exchange ID. This ID is used to associate business protocol binding information.
   Business Protocol Binding	Select RosettaNet 1.1 from the drop-down list. You can associate one business protocol with each document exchange ID. The chosen protocol is bound to the trading partner document exchange name specified in the Document Exchange Name field.
   Business Protocol Definition	Business protocol associated with the business protocol binding specified in the previous field.
   Digital Signature (Nonrepudiation)	Type of digital signature to be used: signature certificate, nonrepudiation protocol, hash function, or signature algorithm. Select the desired type from the drop-down list provided with this field. (Required)
   	Signature Certificate	Select the signature certificate from the drop-down list. This is an optional field. The list in this field is generated from the Certificates tab.
   	Nonrepudiation Protocol	Business protocol associated with the signature certificate. If Signature Certificate is selected, the value in this field is PKCS7; otherwise the field is empty. For complete information about nonrepudiation, see Implementing Nonrepudiation in Implementing Security with B2B Integration. (Read only)
   	Hash Function	Function used for encrypting passwords exchanged by trading partners. If Signature Certificate is selected, the value is SHA1; otherwise the field is empty. The hash function used by both the RosettaNet and XOCP protocols in B2B integration is SHA1. (Read only)
   	Signature Algorithm	Algorithm used for encrypting the signature certificates exchanged by trading partners. If Signature Certificate is selected, the value is RSA; otherwise the field is empty. The signature algorithm used by both the RosettaNet and XOCP protocols in B2B integration is RSA. (Read only)
   Available Document Exchanges	List of available document exchanges.

   
    

4. Click Add/Apply.

Configuring RosettaNet 2.0 for a Document Exchange

To create a trading partner document exchange ID using the RosettaNet 2.0 binding:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab, then select the Doc Exchange tab.

3. In the Business Protocol Binding field, select RosettaNet 2.0. The default values for all the fields on the Doc Exchange tab are shown in the following table.

   Table 3-9 RosettaNet 2.0 Fields on the Doc Exchange Tab  

   Field	Description
   Document Exchange Name	Enter a unique name for the document exchange ID. This ID is used to associate business protocol binding information.
   Business Protocol Binding	Select RosettaNet 2.0 from the drop-down list. You can associate one business protocol with each document exchange ID. The chosen protocol is bound to the trading partner document exchange name specified in the Document Exchange Name field.
   Business Protocol Definition	The business protocol associated with the business protocol binding specified in the previous field.
   Encryption	Encryption values.
   	Encryption Certificate	Certificate required for each trading partner when business message encryption is configured. Encryption support is available only with the RosettaNet protocols.
   	Encryption Level	If Encryption Certificate is selected, you can specify the parts of a business message that you want to have encrypted. Choose PAYLOAD if you want to encrypt only the XML business document(s) part of the message. Choose ENTIRE_PAYLOAD if you want to encrypt the business documents and all attachments in the message.
   	Cipher Algorithm	Type of encryption cipher algorithm that is available from the drop-down list. The following cipher algorithms are supported: RC5 — If RC5 is selected, the algorithm object identifier passed to the RSA security code is RC5-0x10-32-16/CBC/PKCS5Padding. If the algorithm object identifier is equal to RC5-0x10-32-16/CBC/PKC5Padding, then an RC5 in CBC mode, with the PKCS5 padding algorithm, is used to encrypt the message. DES — If DES is selected, the algorithm object identifier passed to the RSA security code is DES/CBC/PKC5Padding. If the algorithm object identifier is equal to DES/CBC/PKC5Padding, then a DES in CBC mode with the PKCS5 padding algorithm, is used to encrypt the message. 3DES — If 3DES is selected, the algorithm object identifier passed to the RSA security code is 3DES_EDE/CBC/PKC5Padding. If the algorithm object identifier is equal to 3DES_EDE/CBC/PKC5Padding, then a Triple DES in EDE mode, with the PKCS5 padding algorithm, is used to encrypt the message. A domestic license is required.
   Digital Signature (Nonrepudiation)	Type of digital signature that is required. For complete information about nonrepudiation, see Implementing Nonrepudiation in Implementing Security with B2B Integration.
   	Signature Certificate	Type of signature certificate from the drop-down list. The list in this field is generated from the Certificates tab. (Optional)
   	Nonrepudiation Protocol	Business protocol associated with the signature certificate. If Signature Certificate is selected, the value is PKCS7; otherwise, the value is an empty string. (Read-only)
   	Hash Function	Function used for encrypting passwords exchanged by trading partners. If Signature Certificate is selected, the value is SHA1; otherwise, the value is null. The hash function used by both the RosettaNet and XOCP protocols in B2B integration is SHA1. (Read-only)
   	Signature Algorithm	Algorithm used for encrypting the signature certificates exchanged by trading partners. If Signature Certificate is selected, the value is RSA; otherwise, the value is null. The signature algorithm used by both the RosettaNet and XOCP protocols in B2B integration is RSA. (Read-only)
   Available Document Exchanges	List of existing document exchanges.

   
    

4. Click Add/Apply.

For complete information about using certificates in document exchange IDs, see Configuring Security in Implementing Security with B2B Integration.

Configuring XOCP 1.1 for a Document Exchange (Deprecated)

Note: The XOCP business protocols is deprecated in this release of WebLogic Integration. For information about the feature that is replacing the XOCP business protocol, see BEA WebLogic Integration Release Notes.

To create a trading partner document exchange ID using the XOCP binding:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab. Select the Doc Exchange tab if it is not active.

3. In the Business Protocol Binding field, select XOCP 1.1. The default values for all the fields on the Doc Exchange tab are shown in the following table.

   Table 3-10 XOCP Fields on the Doc ExchangeTab  

   Field	Description
   Document Exchange Name	Unique name for the document exchange ID. This ID is used to associate business protocol binding information.
   Business Protocol Binding	Select XOCP 1.1 from the drop-down list. You can associate one business protocol with each document exchange ID. The chosen protocol is bound to the trading partner document exchange name specified in the Document Exchange Name field.
   Business Protocol Definition	Business protocol associated with the business protocol binding specified in the previous field.
   End Point Type	Type of connection to be used between this trading partner and other B2B integration instances. For more information, see Configuration Requirements in Administering B2B Integration.
   Confirmed Delivery	Select this option if you want the system to return a receipt whenever a selected message delivery type (hub_receipt, hub_routed, or destination) is confirmed. Note: When active, this feature affects the run-time performance of the B2B engine. For more information, see Configuration Requirements in Administering B2B Integration.
   	HUB_RECEIPT	Sender receives confirmation when the hub receives the message. This option causes the smallest amount of performance degradation.
   	HUB_ROUTED	Sender receives confirmation when the message is routed on the hub. This option causes a medium amount of performance degradation.
   	DESTINATION	Sender receives confirmation when the message is sent to the designated recipient. This option is the most expensive and causes the greatest amount of performance degradation.
   Message History	Number of sender message IDs to be stored in an internal list by the WebLogic Integration. WebLogic Integration maintains an internal list of the message IDs of the last set of messages sent. The length of the list is determined by the number entered in this field. This list is not currently available externally. The larger the number specified in this field, the greater the amount of performance degradation. If the default value, 0, is specified, run-time performance is not affected.
   Retries	Enter a value in the text field for the desired retry values. For more information, see Setting Preferences.
   	Default Retry Value	Number of times you want WebLogic Integration to try to send a message. The default is 3.
   	Default retry interval	The amount of time you allow to elapse between attempts to send the same message. The default is 5000 milliseconds.
   	Default timeout value	Amount of time a transaction remains valid (in days, hours, minutes, and seconds). After this interval, WebLogic Integration terminates the transaction even if outstanding messages remain. The default is 5000 milliseconds. (Optional)
   Digital Signature (Nonrepudiation)	Select a type of digital signature. For details, see Implementing Nonrepudiation in Implementing Security with B2B Integration.
   	Signature Certificate	The type of signature certificate to be used. A choice of valid types is presented on a drop-down list that is generated from the Certificates tab. If none is selected, the related fields (Nonrepudiation Protocol, Hash Function, and Signature Algorithm) are not visible. (Optional)
   	Nonrepudiation Protocol	The business protocol associated with the signature certificate. (Read-only)
   	Hash Function	The function used for encrypting passwords exchanged by trading partners. The hash function used by both the RosettaNet and XOCP protocols for B2B integration is SHA1. (Read-only)
   	Signature Algorithm	The algorithm used for encrypting the signature certificates exchanged by trading partners. The signature algorithm used by both the RosettaNet and XOCP protocols for B2B integration is RSA. (Read-only)
   Available Document Exchanges	List of available document exchanges.

   
    

4. Click Add/Apply.

For complete information about using certificates in document exchange IDs, see Configuring Security in Implementing Security with B2B Integration.

Configuring ebXML 1.0 for a Document Exchange

To create a trading partner document exchange ID using the ebXML binding:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. The Trading Partners page is displayed. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner. (This option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab. Select the Doc Exchange tab if it is not active.

3. In the Business Protocol Binding field, select ebXML-1.0. The following table describes the fields that are displayed on the Doc Exchange tab for ebXML.

   Table 3-11 ebXML Fields on the Doc ExchangeTab  

   Field	Description
   Document Exchange Name	Unique name for the document exchange ID. This ID is used to associate business protocol binding information.
   Business Protocol Binding	Select ebXML-1.0 from the drop-down list. You can associate one business protocol with each document exchange ID. The chosen protocol is bound to the trading partner document exchange name specified in the Document Exchange Name field.
   Business Protocol Definition	Only one Business Protocol Definition (named ebXML) is available for the ebXML business protocol. It is the only selection available on the drop-down list in this field.
   Delivery Semantics	Determines whether message must be delivered reliably.
   	BestEffort	Select BestEffort from the drop-down list if a reliable message delivery is not required. BestEffort means that WebLogic Integration attempts to deliver the message but delivery is not guaranteed.
   	OnceAndOnlyOnce	Select OnceAndOnlyOnce from the drop-down list if reliable message delivery is required. OnceAndOnlyOnce means that WebLogic Integration guarantees that the message is delivered once and only once.This option is the default.
   Retries	Enter a value in the text field for the desired retry values. For more information, see Setting Preferences.
   	Number of Retries	Number of times you want WebLogic Integration to try to send a message. The default is 3.
   	Interval	The amount of time you allow to elapse between attempts to send the same message. The default is 60000 milliseconds (60 seconds).
   	TimeToLive	Amount of time, in seconds, in which a message should be delivered and processed by the recipient. After this interval, WebLogic Integration stops trying to send the message. The default 0 which means no time limit is desired.
   Digital Signature (Nonrepudiation)	Ignore this field; ebXML does not support digital signatures (nonrepudiation).
   Available Document Exchanges	List of available document exchanges.

   
    

4. Click Add/Apply.

For complete information about using certificates in document exchange IDs, see Configuring Security in Implementing Security with B2B Integration.

Removing a Document Exchange

To remove a trading partner document exchange:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. A list of trading partners is displayed in the right pane. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner.

   Note: The second option is available only if the Display entities on the navigation tree option is selected on the Preferences tab, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed.

2. Select the Configuration tab and then, if it is not active, select the Doc Exchange tab. A list of the available document exchanges is displayed.

3. Select the document exchange you want to delete. Click Remove.

   Note: You may remove multiple document exchanges simultaneously by selecting more than one before clicking Remove.

 

---

Configuring a Trading Partner Transport

A trading partner transport defines the business protocol binding information to be used by the parties to a collaboration agreement when they exchange documents. Transports are included in the delivery channels for each trading partner. This information includes the transport protocol and security parameters for the relevant business transaction. Each transport is assigned a unique ID.

For more information, see Configuring a Delivery Channel for a Trading Partner

Creating a New Transport

When you configure a transport for a trading partner, you bind the trading partner's transport to a transport security protocol.

To create a new transport:

1. Do one of the following:

   • Click the Trading Partners node in the navigation tree. A list of trading partners is displayed in the right pane. Select the appropriate trading partner.

   • Click the navigation tree node for the desired trading partner.

   Note: The second method is available only if the Display entities on the navigation tree option is selected on the Preferences tab in the B2B Console, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed in the right pane.

2. Select the Configuration tab, and then select the Transport tab.

3. On the Transport tab, enter data in the fields required, as specified in the following table.

   Table 3-12 Trading Partner Transport Protocol Fields  

   Field	Description
   Transport Name	Enter a unique transport name.
   Transport Protocol	The security protocol for the transport: HTTP-1.1 or HTTPS-1.1. The HTTPS-1.1 protocol uses SSL and can be selected only if a client or server certificate is defined
   Endpoints	Enter Uniform Resource Identifiers (URIs) to create a chain of configured endpoints for the trading partner transport.
   	URI Endpoint	Enter a URI and click Set
   	Endpoint Chain	Peruse the ordered list. Use the up and down arrows to rearrange the order of endpoints in the chain. To remove an endpoint, select it and click Remove.
   Security Protocol	Enter the name of a security protocol. If you specify HTTPS-11, the SSL-3.0 protocol will be used. (Read-only)
   Available Transport IDs	List of available transports created using this tab.

   
    

   For complete information about using certificates in document exchange IDs, see Configuring Security in Implementing Security with B2B Integration.

4. When you finish modifying the transport protocol configuration, click Add/Apply.

Modifying a Transport

To modify an existing transport:

1. Select a trading partner by performing one of the following steps:

   • In the navigation tree, click the Trading Partners node. A list of trading partners is displayed in the right pane. Select the appropriate trading partner.

   • In the navigation tree, select a trading partner.

   Note: The second method is available only if the Display entities on the navigation tree option is selected on the Preferences tab in the B2B Console, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed in the right pane.

2. Select the Configuration tab. Select the Transport tab if it is not active. A list of available transports is displayed.

3. Select the transport protocol ID you want to modify. The configuration fields for the ID of the specified protocol are displayed and populated.

4. Modify the required fields and click Add/Apply.

Removing a Transport

To remove a new transport:

1. Select a trading partner by performing one of the following steps:

   • In the navigation tree, click the Trading Partners node. A list of trading partners is displayed in the right pane. Select the appropriate trading partner.

   • In the navigation tree, select a trading partner.

   Note: The second method is available only if the Display entities on the navigation tree option is selected on the Preferences tab in the B2B Console, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed in the right pane.

2. Select the Configuration tab, then select the Transport tab. A list of available transports is displayed.

3. Select the transport protocol you want to delete. Click Remove.

   Note: You may remove multiple transport protocols simultaneously by selecting more than one before clicking Remove.

 

---

Configuring a Delivery Channel for a Trading Partner

A delivery channel is a definition of how a trading partner sends and receives messages. It is configured by referencing the transport and document exchange elements. For more information, see Configuring a Document Exchange for a Trading Partner and Configuring a Trading Partner Transport.

To create a new delivery channel:

1. Select a trading partner by performing one of the following steps:

   • In the navigation tree, click the Trading Partners node. A list of trading partners is displayed in the right pane. Select the appropriate trading partner.

   • In the navigation tree, select a trading partner.

   Note: The second method is available only if the Display entities on the navigation tree option is selected on the Preferences tab in the B2B Console, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed in the right pane.

2. Select the Configuration tab, then select the Delivery Channels tab.

3. On the Delivery Channels tab, enter data in the fields required, as specified in the following table.

   Table 3-13 Trading Partner Delivery Channel Fields  

   Field	Description
   Delivery Channel Name	Enter a unique name. This name is used to associate . . . characteristics.
   Transport	Select, from the drop-down list, a transport for the delivery channel. You can associate one transport with each delivery channel.
   Document Exchange	Select, from the drop-down list, a document exchange method for the delivery channel. You can associate one document exchange with each delivery channel.
   Routing Proxy	If, on the Document Exchange tab, you select End Point Type as the value of Hub, the Routing Proxy option is selected. For more information, see Configuration Tasks in Administering B2B Integration. (Read-only)
   Available Delivery Channels	List of all available delivery channels.

   
    

4. Click Add/Apply.

Modifying a Delivery Channel

To modify an existing delivery channel:

1. Select a trading partner by performing one of the following steps:

   • In the navigation tree, click the Trading Partners node. A list of trading partners is displayed in the right pane. Select the appropriate trading partner.

   • In the navigation tree, select a trading partner.

   Note: The second method is available only if the Display entities on the navigation tree option is selected on the Preferences tab in the B2B Console, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed in the right pane.

2. Select the Configuration tab, then select the Delivery Channels tab. A list of available delivery channels is displayed.

3. Select the delivery channel you want to modify. The configuration fields for the protocol associated with the specified ID are populated.

4. Modify the required fields and click Add/Apply.

Removing a Delivery Channel

To remove a delivery channel:

1. Select a trading partner by performing one of the following steps:

   • In the navigation tree, click the Trading Partners node. A list of trading partners is displayed in the right pane. Select the appropriate trading partner.

   • In the navigation tree, select a trading partner.

   Note: The second method is available only if the Display entities on the navigation tree option is selected on the Preferences tab in the B2B Console, as described in Displaying Entities in the Navigation Tree.)

   The Trading Partner page is displayed in the right pane.

2. Select the Configuration tab, then select the Delivery Channels tab. A list of available delivery channels is displayed.

3. Select the ID of the delivery channel you want to delete. Click Remove.