Managing WebLogic Integration Solutions

Trading Partner Management

This section provides the information you need to use the Trading Partner Management module of the WebLogic Integration Administration Console to manage trading partners and services, and to monitor messages and other indicators of trading partner activity. The Trading Partner Management module is divided into the following functional areas which can be accessed from the Trading Partner Management home page:

• Profile Management
  Allows administrators to configure the local and remote trading partners that conduct business transactions. The required basic information, security certificates, protocol bindings, and any custom properties required for the transactions are configured.
• Service Management
  Allows administrators to manage the services and service profiles that constitute the business processes offered or called by trading partners.
• Message Tracking
  Allows administrators to set the message tracking criteria and view summary and message content for the messages tracked.
• Partner Profile Import/Export
  Allows administrators to import or export trading partner management data (trading partners and services).
• Statistics
  Allows administrators to view summary statistics that reflect the level of trading partner activity.
• Configuration
  Allows administrators to configure the resources required and to set system defaults.

Note: You must be logged in as a member of the Administrators, IntegrationAdministrators, or IntegrationOperators group to create, change, or delete trading partner management data. See Default Groups, Roles, and Security Policies.

The following topics are provided:

• About Trading Partner Management
• Overview of the Trading Partner Management Module
• Configuring Trading Partner Management
• Adding Trading Partner Profiles
• Adding Certificates to a Trading Partner
• Adding Protocol Bindings to a Trading Partner
• Adding a Custom Extension to a Trading Partner
• Adding Services
• Adding Service Profiles to a Service
• Defining Trading Partner Profiles
• Defining Protocol Bindings
• Listing and Locating Trading Partners
• Listing and Locating Services
• Viewing and Changing Trading Partner Profiles
• Viewing and Changing Certificates
• Viewing and Changing Bindings
• Viewing and Changing a Custom Extension
• Viewing and Changing Services
• Viewing and Changing Service Profiles
• Enabling and Disabling Trading Partner and Service Profiles
• Importing Management Data
• Exporting Management Data
• Deleting Trading Partner Profiles and Services Using Bulk Delete
• Deleting Trading Partner Profiles
• Deleting Certificates, Bindings, or Custom Extensions
• Deleting Services
• Deleting Service Profiles from a Service
• Viewing Statistics
• Monitoring Messages

 

---

About Trading Partner Management

The basic building blocks of trading partner integration are trading partner profiles, services, and service profiles. In WebLogic Integration, a trading partner is understood as an entity that has an agreement with another entity to participate in a specific business transaction, or service, by playing a predefined role. A trading partner profile includes the trading partner's identifying information, and any certificates or protocol binding definitions required to conduct the business transactions.

A service represents a business process that is either offered by a local trading partner, or a business process that is being called via a control on a remote trading partner. In the case of a service offered by a local trading partner, this element directly corresponds to a Web service or process type deployed in the local domain. In the case of a service called by a local trading partner, the service corresponds to a control in the local domain that is used to invoke the remote service. Service profiles specify the protocol binding and URL endpoints for the local and remote trading partners that offer and call the service.

The WebLogic Integration Administration Console allows administrators to configure and manage the required profiles, certificates, and protocol bindings, and to monitor trading partner activity.

To learn more about:

• The entities and elements that comprise trading partner management data, see Appendix E, TPM Schema.
• How trading partner management data is used to support business transactions, see Introducing Trading Partner Integration.
• Building RosettaNet and ebXML solutions, see Tutorials for Trading Partner Integration.
• Building participant processes for ebXML or RosettaNet, see the Building ebXML Participant Business Processes or Building RosettaNet Participant Business Processes topic in Building Integration Applications in the WebLogic Workshop help.
• Security in Trading Partner Integration, see:
• Using WebLogic Integration Security in Deploying WebLogic Integration Solutions.
• Example: ebXML Security Configuration and Example: RosettaNet Security Configuration in Introducing Trading Partner Integration.
• Trading partner integration controls, see TPM Control, RosettaNet Control, and ebXML Control in Building Integration Applications in the WebLogic Workshop help.
• WebLogic Integration - Business Connect, the lightweight trading partner software for WebLogic Integration, see the WebLogic Integration - Business Connect documentation.

 

---

Overview of the Trading Partner Management Module

The following table lists the pages you can access from the Trading Partner Management module. The tasks and topics associated with each are provided.

 

 

---

Configuring Trading Partner Management

The Trading Partner Management Configuration module allows you configure system resources, set the message tracking defaults, or refresh the keystore. See the appropriate topic for instructions:

• Configuring the Mode and Message Tracking
• Configuring a Proxy Host
• Configuring Secure Audit Logging
• Refreshing the Keystore
• Specifying the Certificate Verification Provider

Configuring the Mode and Message Tracking

The General Configuration page allows you to define the mode (test or production), and message tracking properties for trading partner integration.

 

To set the message tracking properties:

From the Trading Partner Management home page, select the Configuration module.
Set the message tracking properties as required. See the table following this procedure for settings.
Click Submit to save your changes and return to the Trading Partner Management home page.

The following table summarizes settings available on the General Configuration page.

 

Configuring a Proxy Host

The Proxy Configuration page allows you to define a proxy host for trading partner integration.

 

Note: A proxy server is used to protect local network addresses from hackers and restrict and monitor external network access from the network hosting WebLogic Integration.

To set the proxy host:

From the Trading Partner Management home page, select the Configuration module.
From the left panel, select Proxy Host.
In the Proxy Host field, enter the host name or IP address.
In the Port number of proxy server, enter the port.
Click Submit to save your changes and return to the Trading Partner Management home page.

Configuring Secure Audit Logging

The Audit Log Configuration page allows you to specify whether or not signed messages are logged to the secure audit log. If secure audit logging is enabled, the Secure Timestamp Configuration page allows you to specify the Java class that implements the secure timestamp class.

 

Note: The classes specified for secure audit logging and secure timestamp must be in the server classpath. Changes to the secure audit logging or secure timestamp configuration require server restart.

To enable or disable secure audit logging:

From the Trading Partner Management home page, select the Configuration module.
From the left panel, select Secure Audit Log.
Do one of the following:
• Select the Disable option button to disable secure audit logging.
• Select the Enable option button, then enter the class to be used in the Secure Audit Logging Class field.

Note: The default com.bea.wli.security.audit.DefaultAuditLogProvider class is provided.

Click Submit to save your changes and return to the Trading Partner Management home page.

To specify the Java class for secure time stamping:

From the Trading Partner Management home page, select the Configuration module.
From the left panel, select Secure Timestamp.

The Secure Timestamp Configuration page is displayed.




 

In the Secure Timestamp Class field, enter the class.

Note: If no class is entered, secure time stamping is disabled.

Click Submit to save your changes and return to the Trading Partner Management home page.

Refreshing the Keystore

The Refresh Keystore page allows you to refresh the KeyStores (identity and trust) in memory from the disk.

 

To refresh the keystore:

From the Trading Partner Management home page, select the Configuration module.
From the left panel, select Refresh Keystore.
Click the Refresh Keystore button to refresh the keystore and return to the Trading Partner Management home page.

Specifying the Certificate Verification Provider

The Certificate Verification Provider page allows you to specify the certificate verification provider for trading partner integration.

 

Trading partner integration provides a service provider interface that allows you to insert a Java class that implements an interface that calls out to a third-party service to verify trading partner certificates. Such an implementation, called a certificate verification provider (CVP), can call out to one of the following certificate verification applications:

• A Certificate Revocation List (CRL) implementation
• An Online Certificate Status Protocol (OCSP) implementation that interacts with a trusted third-party entity, such as a certificate authority, for real-time certificate status checking
• Your own certificate verification implementation

To learn how to implement the CVP, see "Using WebLogic Integration Security" in Deploying WebLogic Integration Solutions.

Note: The CVP class must be in the server classpath. Changes to the CVP configuration require server restart.

To specify the certificate verification provider:

From the Trading Partner Management home page, select the Configuration module.
From the left panel, select Certificate Verification Provider.
In the Certificate Verification Provider field, enter the CVP Java class.
Click Submit to save your changes and return to the Trading Partner Management home page.

 

---

Adding Trading Partner Profiles

The Add Trading Partner Profile page allows you to create a new trading partner profile.

 

To add a trading partner profile:

From the Trading Partner Management home page, select the Profile Management module.
From the left panel, select Create New.
Set trading partner profile properties as required. See Defining Trading Partner Profiles for a description of the available settings.
Click Submit.

The View and Edit Trading Partner Profile page is displayed with the new profile definition.

Note: If there is an error, the Add Trading Partner Profile page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

Do one or more of the following:
• To add certificates to the trading partner, see Adding Certificates to a Trading Partner.
• To add bindings to the trading partner, see Adding Protocol Bindings to a Trading Partner.
• To add a custom extension to the trading partner, see Adding a Custom Extension to a Trading Partner.

 

---

Adding Certificates to a Trading Partner

The Add Certificate page allows you to add certificates to a trading partner profile.

Note: You can also add a certificate from the Add Trading Partner Binding or Edit Trading Partner Binding page by clicking the Add Certificate link to the right of the Signature Certificate drop-down list. If you are adding a certificate in this way, start with step 3 of the following procedure.

To select the type of certificate:

Do one of the following:
• Locate the trading partner as described in Listing and Locating Trading Partners, then click the trading partner name.
• From the Trading Partner Management home page, select the Profile Management module, then select Certificates from the left panel. On the Choose Trading Partner page, select the trading partner name from the Name drop-down list, then click Go.
Click the Add Certificate button.

The Add Certificate (Step 1 of 2) page is displayed.




 

Select one of the following options:
• Generate a certificate for TEST USE only
  Select this option to create a client, signature, or encryption certificate definition. The certificate generated is a self-signed certificate appropriate for use only in testing.
• Import certificate from file
  Select this option to create a client, signature, or encryption certificate definition, and to import the certificate file(s) from the local file system into the configured key store.
• Use alias for an already imported certificate
  Select this option to create a reference to an existing client, signature, encryption, or server certificate definition.
Click Next to display the Add Certificate (Step 2 of 2) page. Refer to the procedure appropriate to the selected type:
• Creating a Certificate for Testing
• Creating and Importing the Files for a Certificate
• Creating a Reference to an Existing Certificate

Creating a Certificate for Testing

After you select Generate a certificate for TEST USE only and click Next, the Add Certificate (Step 2 of 2) page is displayed.

 

This page allows you to create a client, signature, or encryption certificate definition. The certificate generated is appropriate for use only in testing.

To create a certificate for testing:

In the Name field, enter the name used to identify the certificate within the system. This name is also the entry name in the local keystore.
From the Type drop-down list, select the type:
• For a local trading partner, the options are CLIENT, SIGNATURE, or ENCRYPTION.
• For a remote trading partner, the options are CLIENT, SERVER, SIGNATURE, or ENCRYPTION.
From the Password Alias drop-down list, select the password alias for the password associated with the keystore entry. This alias is used to retrieve the required password from the password store. See Password Aliases and the Password Store.

Note: If you have not yet defined an entry for the password in the password store, click Add Alias. After you add the entry, you are returned to the Add Certificate page. The newly added alias is now included in the drop-down list.

Check the Import Certificate in Keystore check box.
Click Create Certificate.

The View and Edit Trading Partner Profile page is displayed. The certificate is included in the certificates summary table.

Note: If there is an error, the Add Certificate page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

Creating and Importing the Files for a Certificate

After you select Import certificate from file and click Next, the Add Certificate (Step 2 of 2) page is displayed.

 

This page allows you to create a client, signature, or encryption certificate definition, and to import the certificate files.

To create a certificate definition and import the certificate files:

In the Name field, enter the name used to identity the certificate within the system. This name is also the entry name in the local keystore.
From the Type drop-down list, select the type:
• For a local trading partner, the options are CLIENT, SIGNATURE, or ENCRYPTION.
• For a remote trading partner, the options are CLIENT, SERVER, SIGNATURE, or ENCRYPTION.
If you are importing a certificate for a local trading partner, select the alias for the password associated with the keystore entry from the Password Alias drop-down list. This alias is used to retrieve the required password from the password store. See Password Aliases and the Password Store.

Note: This step only applies if you are importing a certificate for a local trading partner.

Note: If you have not yet defined an entry for the password in the password store, click Add Alias. After you add the entry, you are returned to the Add Certificate page. The newly added alias is now included in the drop-down list.

Do one of the following to specify the location of the certificate file:
• Click the Browse button to the right of the Import Certificate Location field, then locate the certificate file. Select the file and click Open.
• Enter the path to the certificate file in the Import Certificate Location field.
To specify the location of the private key file for a LOCAL trading partner, do one of the following:
• Click the Browse button to the right of the Private Key Location field, then locate the private key file. Select the file and click Open.
• Enter the path to the private key file in the Private Key Location field.
Check the Import Certificate in Keystore check box.
Click Create Certificate.

The View and Edit Trading Partner Profile page is displayed. The certificate is included in the certificates summary table.

Note: If there is an error, the Add Certificate page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

Creating a Reference to an Existing Certificate

After you select Use alias for an already imported certificate and click Next, the Add Certificate (Step 2 of 2) page is displayed.

 

This page allows you to create a reference to an existing client, signature, encryption, or server certificate definition.

To create a reference to an existing certificate definition:

In the Name field, enter the name used to identity the certificate within the system.
From the Type drop-down list, select CLIENT, SERVER, SIGNATURE, or ENCRYPTION.
From the Password Alias drop-down list, select the password alias for the password associated with the keystore entry. This alias is used to retrieve the required password from the password store. See Password Aliases and the Password Store.

Note: If you have not yet defined an entry for the password in the password store, click Add Alias. After you add the entry, you are returned to the Add Certificate page. The newly added alias is now included in the drop-down list.

Click Add.

The View and Edit Trading Partner Profile page is displayed. The certificate reference is included in the certificates summary table.

Note: If there is an error, the Add Certificate page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

 

---

Adding Protocol Bindings to a Trading Partner

The Add Binding page allows you to add bindings to a trading partner profile.

To add a binding to a trading partner profile:

Do one of the following:
• Locate the trading partner as described in Listing and Locating Trading Partners, then click the trading partner name.
• From the Trading Partner Management home page, select the Profile Management module, then select Bindings from the left panel. On the Choose Trading Partner page, select the trading partner name from the Name drop-down list, then click Go.
Click the Add Binding button.

The Add Binding (Step 1 of 2) page is displayed.




 

Select the ebXML 1.0, ebXML 2.0, RosettaNet 1.1, RosettaNet 2.0, or Web Service option button.
Click Create Binding to display the Add Binding (Step 2 of 2) page.
Set the binding properties as required. See Defining Protocol Bindings for a description of the available settings.
Click Add Binding.

The View and Edit Trading Partner Profile page is displayed. The binding is included in the binding summary table.

Note: If there is an error, the Add Binding page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

If the new binding is:
• An ebXML 1.0 or ebXML 2.0 binding, you can configure signature transforms as described in Configuring Signature Transforms for ebXML Bindings.
• A RosettaNet 1.1 or 2.0 binding, you can configure the notification of failure roles as described in Configuring PIP Notification of Failure Roles for RosettaNet Bindings.

 

---

Adding a Custom Extension to a Trading Partner

The default properties associated with a trading partner can be augmented to support application-specific requirements through the addition of a custom extension. A custom extension is modeled in the repository so that defined properties can be retrieved as subtrees within an XML document. The properties can be retrieved using the TPM control.

The extension is composed of a user-defined root element that contains well-formed XML elements and attributes that define the required properties. The user-defined root element is a child of the <extended-property-set> element, which is the last child of the <trading-partner> element. The following example shows the XML representation of a trading partner with a custom extension.

Custom Extension Example

...
<trading-partner
	name="ABC"
	business-id-type="duns"
	business-id="123123123"
	phone="+1 123 456 7890">
	email="admin@abc.com"
	<address>123 ABC Street., Anytown, CA 95131</address>
	<extended-property-set
	 name="ABC International Extension"
	 description="Contact">
		<myxmlelement>
			<business-contact>Joe Smith</business-contact>
			<phone type="work">+1 123 456 7654</phone>
			<phone type="cell">+1 321 654 4567</phone>
			<city>Anytown</city>
			<state>California</state>
		</myxmlelement>
	</extended-property-set>
</trading-partner>
...

An administrator can add a custom extension as described in the following procedure, or by importing a trading partner data file that contains an XML representation of the extended properties as described in Importing Management Data.

To add custom properties to a trading partner profile:

Do one of the following:
• Locate the trading partner as described in Listing and Locating Trading Partners, then click the trading partner name.
• From the Trading Partner Management home page, select the Profile Management module, then select Custom Extension from the left panel. On the Choose Trading Partner page, select the trading partner name from the Name drop-down list, then click Go.
Click the Add Custom Extension button.

The Add Custom Extension page is displayed.




 

In the Name field, enter a name for the custom extension.
In the Description field, enter an optional description.
In the XML field, enter the XML document.

The extension is composed of a user-defined root element that contains well-formed XML elements and attributes that define the required properties. For example, the XML highlighted in bold in the Custom Extension Example constitutes a valid entry.

Click Create Custom Extension.

The View and Edit Trading Partner Profile page is displayed. The custom extension is displayed in the Custom Extension summary table.

Note: If there is an error, the Add Custom Extension page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

 

---

Adding Services

The Add Service page allows you to create a new service definition.

 

To add a service:

From the Trading Partner Management home page, select the Service Management module.
From the left panel, select Create New.
Do one of the following:
• To locate a newly deployed ebXML or RosettaNet processes and associated controls, click the Browse button to the right of the Name field. Click the name of the process or control to select it. Skip to step 6. (The Type and Business Protocol are specified based on the process or control you select.)
• To specify a Web service, enter the service URI in the Name field.
From the Type drop-down list, select Service Control, Process, or Web Service to specify the type of service.
From the Business Protocol drop-down list, select EBXML, ROSETTANET, or WEBSERVICE to specify the service protocol.
In the Description field, enter an optional description of the service.
Click Add Service.

The View and Edit Service Details page is displayed with the new definition.

Note: If there is an error, the Add Service page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

To add service profiles to the service, see Adding Service Profiles to a Service.
If the Business Protocol is ROSETTANET, you can define the RosettaNet service defaults as described in the following section.

Adding Defaults to a RosettaNet Service

Once you have created a the service definition for a RosettaNet service, you can add service defaults from the View and Edit Service Details page.

To add RosettaNet Service Defaults:

Locate the service as described in Listing and Locating Services.
Click the service name to select it.

The View and Edit Service Details page is displayed.




 

Click Add Defaults.
Define the defaults as required. The following table describes the available settings.

Service Content Schema Location	Location of the schemas on the file system You must enter a valid path.
Use DTD for Validation	True	Use DTD over schemas for validating documents received and sent.
	False	Do not use DTD for validation.
Validate Service Content	True	Validate service content for each message
	False	No validation is performed. Selecting False improves performance.
Validate Service Header	True	Validate service header for each message
	False	No validation is performed. Selecting False improves performance.


 
Click Set Defaults to save the settings and return to the View and Edit Service Details page.

 

---

Adding Service Profiles to a Service

The View and Edit Service Details page allows you to add service profiles to a service.

 

To add service profiles to a service:

Locate the service as described in Listing and Locating Services.
Click the service name to select it.

The View and Edit Service Details page is displayed.

Click the Add Service Profile button.

The Add Service Profile page is displayed.




 

From the Status drop-down list, select Enabled or Disabled.
From the Message Tracking Level drop-down list, select one of the following:
• ALL
  Message metadata and a reference to message contents in the document store are persisted in message tracking tables. Both message metadata and contents are available for view in the Message Tracking module of the console.
• DEFAULT
  The tracking level for this profile is set to the system default tracking level. See Configuring the Mode and Message Tracking.
• METADATA
  Only message metadata is persisted in message tracking tables. Message contents are not tracked and are not available for view in the Message Tracking module of the console.
• NONE
  No message tracking information is sent to the message tracking JMS queue, therefore, no message history is stored in repository and no information is available for view in the Message Tracking module of the console.
Configure the Local trading partner as follows:
From the Name drop-down list, select the name of the trading partner.
From the Binding drop-down list, select the binding. Only bindings of the same type as the Business Protocol defined for the service are allowed.

The Endpoint field displays the URL for the transport endpoint for the selected binding.

Configure the Remote trading partner as follows:
From the Name drop-down list, select the name of the trading partner.
From the Binding drop-down list, select the binding. Only bindings of the same type as the Business Protocol defined for the service are allowed.

The Endpoint field displays the URL for the transport endpoint for the selected binding.

Click Submit.

You are prompted with the following message" "Do you wish to configure authentication?"

Do one of the following:
• Click Yes. Go to step 4 of "To add HTTPS authentication to a service profile" or "To add HTTP authentication to a service profile" in Adding Authentication to a Service Profile.
• Click No. You can configure authentication later as described in Adding Authentication to a Service Profile.

The View and Edit Service Details page is displayed. The new profile is displayed in the service profile summary table.

Note: If there is an error, the Add Service Profile page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

Adding Authentication to a Service Profile

The View Service Profile page allows you to configure the authentication properties for the local and remote trading partners.

When you add authentication to a service profile, the required authentication configuration is added to each respective trading partner binding. The authentication configuration associated with a binding can be updated or deleted as described in Updating or Deleting Authentication.

The following table summarizes the available modes of authentication by transport protocol and describes the authentication properties added to each trading partner binding.

 

To add HTTPS authentication to a service profile:

Locate the service as described in Listing and Locating Services.
Click the service name to select it.

The View and Edit Service Details page is displayed.

In the Service Profiles table, click the View link for the service profile entry. (The View link is in the third column from the right.)

The View Service Profile page is displayed.

Click Configure Authentication.

You are prompted to select the authentication mode for the local and remote trading partners as shown in the following figure:




 

Note: Although it is not enforced, typically the same type of authentication is selected for both the local and remote trading partner.

Select the One Way, One-Way with Basic, or Mutual option button to specify the type for the Local trading partner.
Select the One Way, One-Way with Basic, or Mutual option button to specify the type for the Remote trading partner.
Click the Next button.
Select the certificate(s), or enter the username and password alias, required for the selected type. The following table summarizes the settings by authentication type.

Authentication Type	Local	Remote
One-Way	No local setting.	Select the Server Certificate from the drop-down list.
One-Way with Basic	Enter the Username required to access the remote endpoint. Select the Password Alias from the drop-down list.	Select the Server Certificate from the drop-down list.
Mutual	Select the Client Certificate from the drop-down list.	Select the Client Certificate from the drop-down list. Select the Server Certificate from the drop-down list.


 

Note: If the certificate has not yet been added, click the Add Certificate link to the right of the drop-down list. See Adding Certificates to a Trading Partner for instructions. Once the certificate has been added, it is available for selection. Similarly, if the password alias has not been added, click the Add Alias link to the left of the drop-down list. See Adding Passwords to the Password Store for instructions. Once the alias has been added, it is available for selection.

To preview to the configuration, click Preview config. To learn more about the preview function, see Previewing the Authentication Configuration:.
Click Add.

Authentication is added and the View and Edit Service Details page is displayed.

Note: If there is an error, the Add Authentication page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

To add HTTP authentication to a service profile:

Locate the service as described in Listing and Locating Services.
Click the service name to select it.

The View and Edit Service Details page is displayed.

In the Service Profiles table, click the View link for the service profile entry. (The View link is in the third column from the right.)

The View Service Profile page is displayed.

Click Configure Authentication.

The authentication mode is displayed as shown in the following figure:




 

Click the Next button.
Enter the Username required to access the remote endpoint.
Select the Password Alias from the drop-down list.

Note: If the password alias has not been added, click the Add Alias link to the left of the drop-down list. See Adding Passwords to the Password Store for instructions. Once the alias has been added, it is available for selection.

To preview to the configuration, click Preview config. To learn more about the preview function, see Previewing the Authentication Configuration:.
Click Add.

Authentication is added and the View and Edit Service Details page is displayed.

Note: If there is an error, the Add Authentication page is redisplayed. A message indicating the problem is displayed above the input requiring correction.

Previewing the Authentication Configuration:

The verification of certificates and exchange of public keys that occurs in order to set up a secure channel over which to communicate is known at the SSL handshake. When you configure authentication, you have the option of previewing the configuration.

For the HTTPS transport protocol, the preview provides a summary of the handshake configured as shown in the following figures:

 

 

 

For HTTP basic authentication, the preview displays the configuration as shown in the following figure:

 

 

---

Defining Trading Partner Profiles

The Add Trading Partner Profile and Edit Trading Partner Profile pages allow you to define the properties of a profile. The following table summarizes the available settings.

 

 

---

Defining Protocol Bindings

The Add Binding and Edit Binding pages allow you to define the properties for a protocol binding. For example, the Add Binding page for ebXML 2.0 is shown in the following figure.

 

The following sections describe the available settings for each protocol type and a special case regarding Trading Partner Endpoint definition:

• Defining an ebXML 1.0 or 2.0 Binding
• Defining a RosettaNet 1.1 or 2.0 Binding
• Defining a Web Service Binding
• Defining Endpoints for Projects Containing Multiple JPDs Having the Same Name

Defining an ebXML 1.0 or 2.0 Binding

The following table describes the settings available for an ebXML 1.0 or 2.0 binding.

Note: When exchanging ebXML messages with a trading partner that uses WebLogic Integration - Business Connect, you can only use one version of ebXML Message Service protocol (either ebXML 1.0 or ebXML 2.0). WebLogic Integration - Business Connect uses the same HTTP endpoint for a given trading partner regardless of the ebXML version. You cannot configure more than one protocol binding for a given partner in WebLogic Integration that uses the same HTTP endpoint.