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.

Encoding

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.

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.

Certificate Name

Text entry field in which you can provide a name for the certificate.

Certificate Type

Field in which you specify which of the four types of certificate you want to use for mapping trading partner certificates to WebLogic Server users:

Client certificate

Digital certificate for a remote or local trading partner. Required when the SSL protocol 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

Full pathname of the server certificate field . (Required if Secure Socket Layer (SSL) is used; otherwise, optional.).

Available Signature Certificates

List of available certificates.

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.

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 type of signature certificate from the drop-down list. This is an optional field. The list in this field is generated from the Certificates tab. (Optional)

Nonrepudiation Protocol

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 available document exchanges.

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 Strength

If Encryption Certificate is selected, you can select 56- or 128-bit cipher strength. Note that 128-bit encryption is not available in all countries.

Cipher Algorithm

Read-only field containing the name of the algorithm. B2B Integration Release 2.1 supports only RSA.

Digital Signature (Nonrepudiation)

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.

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

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.

hub_receipt

Sender receives confirmation when the hub receives the message.

hub_routed

Sender receives confirmation when the message is routed on the hub.

destination

Sender receives confirmation when the message is sent to the designated recipient.

Message History

Stores old messages so the system can compare new messages and determine whether they should be resent. For more information, see the description of the Retries field. Valid values are 0-99. The default is 0.

Note: When active, this feature affects the run-time performance of the B2B engine.

Retries

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)

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.

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.

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

Available Delivery Channels

List of all available delivery channels.