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
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 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:
- 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.
Page
|
Associated Tasks
|
Topics
|
Trading Partner Management
|
Trading Partner Management Home Page
|
Select a trading partner management module (Profile Management, Service Management, Message Tracking, Partner Profile Import/Export, Statistics, or Configuration). Return to this page at any time by selecting
from the navigation bar.
|
Trading Partner Management
|
Profile Management: Partner Profiles
|
View and Edit Trading Partner Profiles
|
View a list of trading partners. Trading partner name, type (remote or local), business ID, description, and status of the service profiles associated with the partner (enabled or disabled) are displayed.
|
Listing and Locating Trading Partners
|
Filter the list by name. Use ? to match any single character or * to match zero or more characters.
|
Delete one or more trading partners.
|
Deleting Trading Partner Profiles
|
Enable or disable the trading partner profile.
|
Enabling and Disabling Trading Partner and Service Profiles
|
Add a New Trading Partner
|
Add a trading partner.
|
Adding Trading Partner Profiles
|
View and Edit Trading Partner Profile
|
View a partner profile. The name, business ID, business type, trading partner type (local or remote), status, description, and contact information are displayed.
|
Viewing and Changing Trading Partner Profiles
|
View summary information for the protocol bindings associated with the trading partner. Add a new binding or select a binding for edit.
|
Viewing and Changing Bindings
|
View summary information for the certificates associated with the trading partner. Add a new certificate or select a certificate for edit.
|
Viewing and Changing Certificates
|
View summary information for a custom extension. Update the existing custom extension, or add a new custom extension if one does not exist.
|
Viewing and Changing a Custom Extension
|
Edit Trading Partner Profile
|
Update trading partner properties. Change the description, business ID, business type, trading partner type (local or remote), status (enabled or disabled), contact information, or user identity.
|
Viewing and Changing Trading Partner Profiles
|
Profile Management: Bindings
|
Add Binding
|
Add a new protocol binding to the selected trading partner.
|
Adding Protocol Bindings to a Trading Partner
|
View Binding Details
|
View the properties of a binding.
|
Viewing and Changing Bindings
|
Edit Binding
|
Edit the properties of a binding.
|
Viewing and Changing Bindings
|
Profile Management: Certificates
|
Add Certificate
|
Add a new certificate to the selected trading partner.
|
Adding Certificates to a Trading Partner
|
View and Edit Trading Partner Certificate
|
View the properties of a certificate or update a certificate.
|
Viewing and Changing Certificates
|
Edit Certificate
|
Update a certificate by importing certificate files.
|
Viewing and Changing Certificates
|
Profile Management: Custom Extension
|
Add Custom Extension
|
Add custom properties to the trading partner.
|
Adding a Custom Extension to a Trading Partner
|
View and Edit Custom Extension
|
View the custom properties for a trading partner.
|
Viewing and Changing a Custom Extension
|
Edit Custom Extension
|
Change the custom properties for a trading partner.
|
Viewing and Changing a Custom Extension
|
Service Management: Services
|
View and Edit Services
|
View a list of services. Service name, business service name, description, type, business protocol, and description are displayed.
|
Viewing and Changing Services
|
Filter the list by service name. Use ? to match any single character or * to match zero or more characters.
|
Delete a service.
|
Deleting Services
|
Add Service
|
Add a service definition for a newly deployed service. Assign the name, type, and business protocol. Optionally assign a description.
|
Adding Services
|
View and Edit Service Details
|
View service properties. The type, business protocol, description, version, and associated service profiles are displayed.
|
Viewing and Changing Services
|
Select a service profile to view or edit.
|
Edit Service Details
|
Update service properties. Change the type, business protocol, description or version. Add service profiles.
|
Viewing and Changing Services
|
Add Service Profile
|
Define a service profile to be added to the service. Enable or disable, specify the message tracking level, and specify the binding and URL endpoint for the local and remote trading partners.
|
Adding Service Profiles to a Service
|
View Service Profile
|
View the properties of a service profile.
|
Viewing and Changing Service Profiles
|
Edit Service Profile
|
Update a service profile. Enable or disable the service, change the message tracking level, or change the binding and URL endpoint for the local and remote trading partners.
|
Viewing and Changing Service Profiles
|
Add Authentication
|
Add authentication to a service profile.
|
Adding Authentication to a Service Profile
|
Message Tracking
|
View Messages
|
View the list of messages. Event ID, time of event, direction (inbound or outbound), and status are displayed.
|
Monitoring Messages
|
Filter the Displayed Messages
|
Configure the filter for the messages displayed on the View Messages page. Criteria include trading partner sender and receiver, tracking start time and interval, and status.
|
Filtering the Messages Displayed
|
Message Details
|
View message properties and link to detail, such as header, status, or message part data.
|
Filtering the Messages Displayed
|
Import/Export
|
Import Trading Partner Management Data
|
Select a trading partner management file for import, and set the import properties.
|
Importing Management Data
|
Export Trading Partner Management Data
|
Select trading partners and services for export, and set the export properties.
|
Exporting Management Data
|
Bulk Delete
|
Select trading partner profiles and services to delete and set the delete properties.
|
Deleting Trading Partner Profiles and Services Using Bulk Delete
|
Statistics
|
Trading Partner Management Statistics
|
View summary statistics. Trading partner count, service count by type (process, service control, or Web service), service profile count, number of conversations, and a count of the sent and received messages are displayed.
|
Viewing Statistics
|
Configuration
|
General Configuration
|
Set the message tracking properties. Specify the tracking level (all, metadata, or none), directory used to store the messages, and whether or not to trace raw messages.
|
Configuring the Mode and Message Tracking
|
Set the trading partner integration mode (test or production).
|
Proxy Configuration
|
Configure a proxy host.
|
Configuring a Proxy Host
|
Audit Log Configuration
|
Enable or disable secure audit logging. If enabled, specify the secure audit logging class.
|
Configuring Secure Audit Logging
|
Secure Timestamp Configuration
|
Specify the Java class used for secure time stamping.
|
Configuring Secure Audit Logging
|
Refresh Keystore
|
Refresh the KeyStores (identity and trust) in memory from the disk.
|
Refreshing the Keystore
|
Certificate Verification Provider
|
Specify the certificate verification provider.
|
Specifying the Certificate Verification Provider
|
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
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.
Setting
|
Description
|
Required/ Optional
|
From the Message Tracking Level drop-down list, select All, Metadata, or None.
|
The default message tracking level for trading partner integration. If the tracking level for a service profile is set to Default (see Adding Service Profiles to a Service), the tracking level for the service profile defaults to the setting specified here. The options are:
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.
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 or history is stored in repository and no information is available for view in the Message Tracking module of the console.
|
Required
|
From the Mode drop-down list, select Test or Production.
|
The trading partner integration mode. In Test mode service profiles are not required for sending and receiving business messages between collocated trading partners. Default bindings for both partners can be used in test mode.
|
Required
|
In the Directory field, enter the path.
|
The path to a directory used to store messages.
|
Required if Trace Raw Message is set to Yes.
|
Select the Trace Raw Messages Yes or No option button.
|
When set to Yes, messages are also stored in their raw format (the format of the message as it is sent over the wire). This setting can be useful for debugging purposes.
|
Required
|
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.
- 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.
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:
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:
- 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
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.
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:
- 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.
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.
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:
- 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.
- 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.
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.
- 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:
- Click the service name to select it.
The View and Edit Service Details page is displayed.
- 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:
- 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.
You are prompted with the following message" "Do you wish to configure authentication?"
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.
Transport Protocol
|
Authentication Mode
|
Local Trading Partner (LocalTP) Configuration
|
Remote Trading Partner (RemoteTP) Configuration
|
HTTP
|
Basic
|
Client Trading Partner: RemoteTP
|
Client Trading Partner: LocalTP
Username and Password Alias: RemoteTP username and password (the password alias for the password is specified). The username and password required to access the RemoteTP transport endpoint.
|
HTTPS
|
One-Way
|
Client Trading Partner: RemoteTP
|
Client Trading Partner: LocalTP
Server Certificate: RemoteTP server certificate to be used for SSL authentication.
|
One-Way with Basic
|
Client Trading Partner: RemoteTP
|
Client Trading Partner: LocalTP
Username and Password Alias: RemoteTP username and password (the password alias for the password is specified). The username and password required to access the RemoteTP transport endpoint.
Server Certificate: RemoteTP server certificate to be used for SSL authentication.
|
Mutual
|
Client Trading Partner: RemoteTP
Client Certificate: RemoteTP client certificate to be used for SSL mutual authentication.
|
Client Trading Partner: LocalTP
Client Certificate: LocalTP client certificate to be used for SSL mutual authentication.
Server Certificate: RemoteTP server certificate to be used for SSL authentication.
|
To add HTTPS authentication to a service profile:
- 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.
- 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.
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:
- 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:
- 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.
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.
Setting
|
Description
|
Required/ Optional
|
In the Name field, enter the name.
|
The name used to identify the trading partner within the system. Do not use spaces.
Note: This field is only available on the Add Trading Partner Profile page. It cannot be edited on the Edit Trading Partner Profile page.
|
Required
|
In the Description field, enter a description.
|
An optional description. This value is for administrative purposes only. It is not included in messages.
|
Optional
|
In the Business ID field, enter an appropriate identifier.
|
Identifier for the trading partner. The value is used to identify the partner in message exchanges.
|
Required
|
In the Business ID Type field, enter the type of Business ID.
|
The type or naming convention for the Business ID. For example, if the value entered for Business ID is a D-U-N-S number, enter DUNS for the Business ID Type.
|
Optional
|
Check or uncheck the Default Trading Partner check box.
|
When checked, the trading partner is designated the default trading partner for sending or receiving messages for the local host system. Default Trading Partner can only be checked if Type is set to LOCAL. Only one LOCAL trading partner can be designated the default.
The default is unchecked.
|
Optional
|
From the Type drop-down list, select LOCAL or REMOTE.
|
Specifies whether the trading partner is hosted locally or represents an external, remote trading partner.
The default is LOCAL.
|
Optional
|
From the Status drop-down list, select ENABLED or DISABLED.
|
Specifies whether or not to allow business messages to be sent or received by the partner
You cannot set the Status to DISABLED until all service profiles associated with the partner are disabled. If you attempt to set the Status to DISABLED, you are prompted to disable any enabled service profiles before the change takes effect.
Setting the Status to ENABLED does not automatically enable the service profiles associated with the trading partner. After you enable the trading partner profile, you must enable the associated service profiles as described in Enabling and Disabling Trading Partner and Service Profiles.
The default is ENABLED.
|
Optional
|
In the Email field, enter an email address.
|
A contact email address for the trading partner.
|
Optional
|
In the Address field, enter a mailing address.
|
A mailing address for the trading partner.
|
Optional
|
In the Phone field, enter a telephone number.
|
A contact telephone number for the trading partner.
|
Optional
|
In the Fax field, enter a fax number.
|
A fax number for the trading partner.
|
Optional
|
In the WLS User Name field, enter a valid user name.
|
The user name that is used to authorize remote trading partners at the transport level. This user must exist in the default security realm. See Listing and Locating Users. The value applies only if Type is set to Remote.
|
Optional
|
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
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.
Setting
|
Description
|
Required/ Optional
|
In the Name field, enter the binding name.
|
The name used to identify the binding within the system. The name must be unique within the trading partner profile. When you add a new binding, a default name is automatically generated using the following convention:
<partner>-<protocol>-<qualifier>
For example:
acme-ebxml20-4
If you choose to change the default name, make sure the name you choose is unique.
Note: This field is only available on the Add Binding page. It cannot be edited on the Edit Binding page.
|
Required
|
Check or uncheck the Default Binding check box.
|
When checked, the binding is designated as the default binding for the ebXML protocol. Only one binding of the same protocol version can be designated the default binding.
The default is unchecked.
|
Optional
|
Transport Configuration
|
From the Transport Protocol drop-down list, select the HTTP or HTTPS.
|
The transport protocol for sending and receiving messages.
The default is HTTP.
|
Optional
|
From the Transport Protocol Version, select the version.
|
The version of the transport protocol.
If HTTP is selected for the Transport Protocol, select 1.0 or 1.1. The default is 1.0.
If HTTPS is selected for Transport Protocol, 1.1 is currently the only option.
|
Optional
|
In the Endpoint field, enter the URL for the transport endpoint.
|
The URL or URI for the transport endpoint.
For information about specifying an endpoint as a URI, see Defining Endpoints for Projects Containing Multiple JPDs Having the Same Name.
|
Required
|
In the Timeout field, enter the transport timeout.
|
The transport timeout for the specified Endpoint. The default value is 0, which indicates no timeout.
|
Optional
|
Quality of Service
|
From the Delivery Semantics drop-down list, do one of the following:
For ebXML 2.0, select BESTEFFORT, ONCEANDONLYONCE, ATLEASTONCE, or ATMOSTONCE
|
The reliable message service behavior:
BESTEFFORT Best effort. No reliable messaging.
ONCEANDONLYONCE Once and only once reliable messaging. Select this option for messaging that requires acknowledgement and duplicate elimination.
ATLEASTONCE At least once reliable messaging. Select this option for messaging that requires acknowledgement, but not duplicate elimination.
ATMOSTONCE At most once reliable messaging. Select this option for messaging that requires duplicate elimination, but not acknowledgement.
|
Required
|
In the Retry Count field, enter the number of retries.
|
The maximum number of retries for sending a reliably delivered message. The default is 0.
The value is ignored if BESTEFFORT or ATMOSTONCE is selected for Delivery Semantics. If ONCEANDONLYONCE or ATLEASTONCE is selected, the message is retried until the acknowledgement is received or the number of retries specified in the Retry Count field is exhausted.
|
Required if ONCEANDONLYONCE or ATLEASTONCE is selected,
|
In the Retry Interval field, enter the interval.
|
The time interval before a message is resent following a timeout waiting for a message acknowledgement.
The following are examples of valid entries: 500 ms or 500 msecs, 5 s, or 5 sec, or 5 secs 5 m or 5 mins 5 h or 5 hours 5 d or 5 days
Any combination of the above are also valid. For example:
1 d 5 h 1 sec 500 ms
The default is 1 min.
|
Required if Retry Count is 1 or greater.
|
In the Persist Duration, enter the interval.
|
Specifies the duration for which messages have to be stored persistently for the purpose of duplicate elimination.
The following are examples of valid entries: 500 ms or 500 msecs, 5 s, or 5 sec, or 5 secs 5 m or 5 mins 5 h or 5 hours 5 d or 5 days
Any combination of the above are also valid. For example:
1 d 5 h 1 sec 500 ms
The default is 0.
|
Required if ONCEANDONLYONCE or ATMOSTONCE is selected,
|
Note: When defining an ebXML binding for a local trading partner, set the values for Retry Count, Retry Interval, and Persist Duration to the same values as the remote trading partner.
|
XML Digital Signature Configuration for Non-Repudiation
|
From the Signature Certificate drop-down list, select an existing certificate or NONE.
If you have not yet added the certificate, click Add certificate and follow the instructions in Adding Certificates to a Trading Partner.
|
The name of the signature certificate used to digitally sign messages. NONE indicates no digital signature.
|
Optional
|
Check or uncheck the Signature Required check box.
|
When checked, the message is digitally signed using the signature certificate of the trading partner sending the message. The default is unchecked.
Archiving of signed messages in a secure audit log is controlled by the secure audit logging configuration. See Configuring Secure Audit Logging.
|
Optional
|
Check or uncheck the Signature Receipt Required check box.
|
When checked, the message is acknowledged by a digitally signed receipt acknowledgement message using the signature certificate of the trading partner sending the acknowledgement. The default is unchecked.
Archiving of signed messages in a secure audit log is controlled by the secure audit logging configuration. See Configuring Secure Audit Logging.
|
Optional
|
Note: Within WebLogic Integration, the ebXML protocol supports non-repudiation by digitally signing outbound messages and acknowledgements based on the settings for the Signature Required and Signature Receipt Required properties of the binding. In addition to the preceding properties:
|
Defining a RosettaNet 1.1 or 2.0 Binding
The following table describes the settings available for a RosettaNet 1.1 or 2.0 binding.
Setting
|
Description
|
Required/ Optional
|
In the Name field, enter the binding name.
|
The name used to identify the binding within the system. The name must be unique within the trading partner profile. When you add a new binding, a default name is automatically generated using the following convention:
<partner>-<protocol>-<qualifier>
For example:
acme-rosettanet20-4
If you choose to change the default name, make sure the name you choose is unique.
Note: This field is only available on the Add Binding page. It cannot be edited on the Edit Binding page.
|
Required
|
Check or uncheck the Default Binding check box.
|
When checked, the binding is designated as the default binding for the RosettaNet protocol. Only one binding of the same protocol version can be designated the default binding.
|
Required
|
Transport Configuration
|
From the Transport Protocol drop-down list, select the HTTP or HTTPS.
|
The transport protocol for sending and receiving messages.
|
Required
|
From the Transport Protocol Version, select the version.
|
The version of the transport protocol.
If HTTP is selected for the Transport Protocol, select 1.0 or 1.1.
If HTTPS is selected for Transport Protocol, 1.1 is currently the only option.
|
Required
|
In the Endpoint field, enter the URL for the transport endpoint.
|
The URL or URI for the transport endpoint.
For information about specifying an endpoint as a URI, see Defining Endpoints for Projects Containing Multiple JPDs Having the Same Name.
|
Required
|
In the Timeout field, enter the transport timeout.
|
The transport timeout for the specified endpoint. The default value is 0, which indicates no timeout.
|
Required
|
Quality of Service
|
In the Retry Count field, enter the number of retries.
|
The number of times a RosettaNet message should be retried in case of failure. The default is 0.
|
Required
|
In the Retry Interval field, enter the interval.
|
The amount of time to wait between subsequent retries. The default is 1 min.
The following are valid entries: 500 ms or 500 msecs, 5 s, or 5 sec, or 5 secs 5 m or 5 mins 5 h or 5 hours 5 d or 5 days
Any combination of the above are also valid. For example:
1 d 5 h 1 sec 500 ms
The default is 60 seconds.
|
Required for if Retry Count is 1 or greater.
|
In the Process Timeout, enter the interval.
|
Specifies the amount of time a PIP can be active without completion before timing out. The default is 0.
|
Optional
|
Note: The values specified for Retry Count, Retry Interval, and Process Timeout are not directly enforced by the RosettaNet messaging runtime. These values can be accessed from a business process that implements a RosettaNet process.
|
Message-Level Encryption (RosettaNet 2.0 Only)
|
From the Encryption Certificate drop-down list, select an existing certificate or NONE.
If you have not yet added the certificate, click Add certificate and follow the instructions in Adding Certificates to a Trading Partner.
|
The name of the encryption certificate used to encrypt and decrypt messages. NONE indicates no message-level encryption. The default is NONE.
|
Optional
|
From the Encryption Level drop-down list, select NONE, PAYLOAD, or ENTIRE_PAYLOAD.
|
The encryption level specifies how much of the message content is to be encrypted. Select PAYLOAD to encrypt only the XML business document(s) part of the message.
Select ENTIRE_PAYLOAD if you want to encrypt the business documents and all attachments in the message.
The default is NONE.
|
Optional
|
From the Cipher Algorithm drop-down list, select NONE, RC5, DES, 3DES, or RC2.
|
Type of cipher algorithm:
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.
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.
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.
If RC2 is selected, the algorithm object identifier passed to the RSA security code is RC2/CBC/PKCS5Padding . If the algorithm object identifier is equal to RC2/CBC/PKCS5Padding , then RC2 in CBC mode, with the PKCS5 padding algorithm at a key size of 40 bits (RC2-40), is used to encrypt the message.
The default is NONE.
|
Required if Encryption Level is PAYLOAD or ENTIRE_PAYLOAD
|
XML Digital Signature Configuration for Non-Repudiation
|
From the Signature Certificate drop-down list, select the certificate.
|
The name of the signature certificate to be used for digitally signing messages. If you have not yet added the certificate, click Configure. To learn how to add a certificate, see Adding Certificates to a Trading Partner for instructions.
|
|
Check or uncheck the Signature Required check box.
|
When checked, the message is digitally signed using the signature certificate of the trading partner sending the message. The default is unchecked.
Archiving of signed messages in a secure audit log is controlled by the secure audit logging configuration. See Configuring Secure Audit Logging.
|
Required
|
Check or uncheck the Signature Receipt Required check box.
|
When checked, the message is acknowledged by a digitally signed receipt acknowledgement message using the signature certificate of the trading partner sending the acknowledgement. The default is unchecked.
Archiving of signed messages in a secure audit log is controlled by the secure audit logging configuration. See Configuring Secure Audit Logging.
|
Required
|
From the Hash Function drop-down list, select None, SHA1, or MD5.
|
Message digest algorithm used for the acknowledgement message.
If SHA1 or None is selected, the Secure Hash Algorithm 1 (SHA-1), which produces a 160-bit hash, is used.
If MD5 is selected, the Message Digest 5 (MD5) message hash algorithm, which produces a 128-bit hash, is used.
The default is None.
Note: Non-repudiation of receipt requires an acknowledgement of the received RosettaNet business message to be sent. The acknowledgement must be digitally signed and include an MD5 or SHA-1 digest of the message being acknowledged.
|
Required
|
Note: Within WebLogic Integration, the RosettaNet protocol supports non-repudiation by digitally signing outbound messages and acknowledgements based on the settings for the Signature Required, Signature Receipt Required, and Hash Function properties of the binding. For all RosettaNet messages, the non-repudiation protocol is PKCS7.
In addition to the preceding properties:
|
Defining a Web Service Binding
The following table describes the settings available for a Web service binding.
Setting
|
Description
|
Required/ Optional
|
In the Name field, enter the binding name.
|
The name used to identify the binding within the system. The name must be unique within the trading partner profile. When you add a new binding, a default name is automatically generated using the following convention:
<partner>-<protocol>-<qualifier>
For example:
acme-webservice-4
If you choose to change the default name, make sure the name you choose is unique.
Note: This field is only available on the Add Binding page. It cannot be edited on the Edit Binding page.
|
Required
|
Transport Configuration
|
From the Transport Protocol drop-down list, select the HTTP or HTTPS.
|
The transport protocol for sending and receiving messages.
|
Required
|
From the Transport Protocol Version drop-down list, select the version.
|
The version of the transport protocol.
If HTTP is selected for the Transport Protocol, select 1.0 or 1.1.
If HTTPS is selected for Transport Protocol, 1.1 is currently the only option.
|
Required
|
In the Endpoint field, enter the URL for the transport endpoint.
|
The URL or URI for the transport endpoint.
For information about specifying an endpoint as a URI, see Defining Endpoints for Projects Containing Multiple JPDs Having the Same Name.
|
Required
|
In the Timeout field, enter the transport timeout.
|
The transport timeout for the specified endpoint. The default value is 0, which indicates no timeout.
|
Required
|
Defining Endpoints for Projects Containing Multiple JPDs Having the Same Name
When you have multiple JPD files with the same name within the same Java package, that is,. in the same project, you should use the actual URI to identify the absolute endpoint of the participant process.
To use this feature, you must first add the B2B-TransportServletFilter
to your web.xml
file by adding the following lines of code:
<!-- WLI-B2Bi filter-begin. DO NOT EDIT -->
<filter>
<filter-name>TransportServletFilter</filter-name>
<filter-class>com.bea.b2b.transport.http.TransportServletFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>TransportServletFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<!-- WLI-B2Bi filter-end. -->
After you have edited your web.xml
file, define your trading partner's endpoint URL accordingly.
Listing and Locating Trading Partners
The View and Edit Trading Partner Profiles list displays the following information for each trading partner:
Property
|
Description
|
Trading Partner Name
|
The name assigned to the trading partner. The name is a link to the View and Edit Trading Partner Profile page for the partner.
|
Type
|
The trading partner type (local or remote).
|
Business ID
|
Identifier for the trading partner. The value is used to identify the partner in message exchanges.
|
Description
|
An optional description. This value is for administrative purposes only. It is not included in messages.
|
Status
|
Status of the trading partner:
A green light
indicates that the trading partner profile is enabled. If there are any service profiles associated with the trading partner, they may, or may not, be enabled (the system does not enforce the status of the service profiles for an enabled trading partner).
|
To list and locate trading partners:
- From the Trading Partner Management home page, select the Profile Management module.
- To locate a specific trading partner do one of the following:
- Filter by trading partner name. Enter the search target (use
?
to match any single character or *
to match zero or more characters.), then click Search. The partners matching the search criteria are displayed.
- Resort the list. Ascending
and descending
arrow buttons indicate sortable columns. Click the button to change the sort order.
- Scroll through the pages. Use the controls in the lower left corner. Go to a page by selecting the page number or by using the arrow buttons to go to the next
, previous
, first
, or last
page.
Listing and Locating Services
The View and Edit Services list displays the following information for each service:
Property
|
Description
|
Service Name
|
The service URI or control name. The name is a link to the View and Edit Service Details page for the service.
|
Business Service Name
|
The business service name as defined for the process. For an ebXML process, this is the ebxml-service-name specified in the @jpd:ebxml Annotation. For a RosettaNet process, this is the pip-name specified in the @jpd:rosettanet Annotation. The business service name is empty for Web services.
|
Description
|
An optional description. This value is for administrative purposes only. It is not included in messages.
|
Type
|
The type of service (process, service control, or Web service).
|
Business Protocol
|
Business protocol (ebXML, RosettaNet, or Web service).
|
To list and locate services:
- From the Trading Partner Management home page, select the Service Management module.
- To locate a specific service do one of the following:
- Filter by service name. Enter the search target (use
?
to match any single character or *
to match zero or more characters.), then click Search. The services matching the search criteria are displayed.
- Resort the list. Ascending
and descending
arrow buttons indicate sortable columns. Click the button to change the sort order.
- Scroll through the pages. Use the controls in the lower left corner. Go to a page by selecting the page number or by using the arrow buttons to go to the next
, previous
, first
, or last
page.
Viewing and Changing Trading Partner Profiles
The View and Edit Trading Partner Profile page allows you to view and change the properties of the profile.
The following table summarizes the information displayed on the View and Edit Trading Partner Profile page.
Property
|
Description
|
Administrator Can Set (Yes/No)
|
Name
|
The name used to identify the trading partner within the system.
Note: You cannot update the name of an existing trading partner. To change the name, you must delete the partner, then recreate it with the new name.
|
No
|
Business ID
|
Identifier for the trading partner. The value is used to identify the partner in message exchanges.
|
Yes
|
Business ID Type
|
The type or naming convention for the Business ID (for example, DUNS for a D-U-N-S number).
|
Yes
|
Type
|
Trading partner type (local or remote).
|
Yes
|
Status
|
Status of the trading partner:
Enabled indicates that the trading partner can send and receive messages. If there are any service profiles associated with the trading partner, they may, or may not, be enabled (the system does not enforce the status of the service profiles for an enabled trading partner).
|
Yes
|
Description
|
An optional description. This value is for administrative purposes only. It is not included in messages.
|
Yes
|
Default Trading Partner
|
Indicator of whether or not the trading partner is designated the default trading partner for sending or receiving messages for the local host system (true or false).
This field is only displayed for a local trading partner.
|
Yes
|
Email
|
A contact email address for the trading partner.
|
Yes
|
Address
|
A mailing address for the trading partner.
|
Yes
|
Phone
|
A contact telephone number for the trading partner.
|
Yes
|
Fax
|
A fax number for the trading partner.
|
Yes
|
WLS User Name
|
The user name that is used to authorize remote trading partners at the transport level. (The WLS User name is only displayed for remote trading partners.)
|
Yes
|
Bindings
|
Binding table
|
Entry for each binding configured for the trading partner.
|
Yes
|
Name
|
The name assigned to the binding. The name is a link to the View Binding Details page.
|
Business Protocol
|
The business protocol (ebXML, RosettaNet, or Web service).
|
Default Binding
|
Indicator of whether or not this is the designated default binding for the local host system (true or false).
|
Protocol Version
|
The protocol version. The value can be 1.0 or 2.0 (ebXML), 1.1 or 2.0 (RosettaNet), or No Data (Web service).
|
Delete
|
A Delete link that can be used to delete the entry.
|
Certificates
|
Certificate table
|
Entry for each certificate configured for the trading partner.
|
Yes
|
Name
|
The name assigned to the certificate. The name is a link to the View and Edit Trading Partner Certificates page.
|
Type
|
Type of certificate (client, signature, encryption, or server)
|
Delete
|
A Delete link that can be used to delete the entry.
|
Custom Extension
|
Custom Extension table
|
Entry for the custom extension, if one exists.
|
Yes
|
Name
|
The name assigned to the custom extension. The name is a link to the View and Edit Custom Extension page.
|
Delete
|
A Delete link that can be used to delete the entry.
|
To view trading partner properties:
- Click the trading partner name.
The View and Edit Trading Partner Profile page is displayed.
To change trading partner properties:
- On the View and Edit Trading Partner Profile page, click Edit profile.
- If any service profiles for the trading partner are enabled, you are prompted to disable them before the change can take effect. Click Disable to disable the service profiles and continue.
The View and Edit Trading Partner Profile page is displayed with the new profile definition.
Note: If there is an error, the edit page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
- Do one or more of the following as required:
Viewing and Changing Certificates
The View and Edit Trading Partner Certificates page allows you to:
- View the properties of a certificate.
- Import certificate files to update a certificate.
For example, the View and Edit Trading Partner Certificates page for a signature certificate is shown in the following figure.
To view a certificate for a trading partner:
- 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.
- In the certificate table, click the certificate name.
The View and Edit Trading Partner Certificates page is displayed.
To import files to update a certificate:
- On the View and Edit Trading Partner Certificate page, click Edit Certificate.
The Edit Certificate page is displayed.
For example, the Edit Certificate page for a signature certificate is shown in the following figure.
- If required, update the Password alias. From the Password Alias drop-down list, select a new password alias.
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 Edit 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.
- If any service profiles are enabled, you are prompted to disable them before the change can take effect. Click Disable to disable the service profiles and continue.
The View and Edit Trading Partner Certificate page is displayed.
Note: If there is an error, the Edit Certificate page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
Viewing and Changing Bindings
The View Binding Details page allows you to:
- View the properties of a binding.
- Change the properties of a binding.
- Configure signature transforms for ebXML bindings.
- Configure the trading partner and delivery channel for the PIP Failure Notifier or PIP Failure Report Administrator roles for RosettaNet bindings.
For example, the View Binding Details page for a RosettaNet 2.0 binding is shown in the following figure.
The following table summarizes the information displayed on the View Binding Details page.
Property
|
Description
|
Property Applies To
|
Administrator Can Set (Yes/No)
|
Name
|
The name used to identify the binding within the system.
Note: You cannot update the name, business protocol, or business protocol version of an existing binding. To change the these properties, you must delete the binding, then recreate it with the new values.
|
All binding types
|
No
|
Business Protocol
|
The business protocol (ebXML, RosettaNet, or Web service).
|
All binding types
|
No
|
Business Protocol Version
|
The protocol version. The value can be 1.0 or 2.0 (ebXML), 1.1 or 2.0 (RosettaNet), or No Data (Web service).
|
ebXML 1.0/2.0 RosettaNet 1.1/2.0
|
No
|
Default Binding
|
Indicator of whether or not the binding is designated as the default binding for the protocol (true or false). Only one binding of the same protocol version can be designated the default binding.
|
ebXML 1.0/2.0 RosettaNet 1.1/2.0
|
Yes
|
Transport Configuration
|
Transport Protocol
|
The transport protocol for sending and receiving messages:
|
All binding types
|
Yes
|
Transport Protocol Version
|
The version of the transport protocol.
|
All binding types
|
Yes
|
Endpoint URL
|
The URL for the transport endpoint.
|
All binding types
|
Yes
|
Timeout
|
The transport timeout for the specified endpoint. A value of 0 indicates no timeout.
|
All binding types
|
Yes
|
Quality of Service
|
Retry Count
|
The maximum number of retries for sending a reliably delivered message.
|
ebXML 1.0/2.0 RosettaNet 1.1/2.0
|
Yes
|
Retry Interval
|
The retry interval:
|
ebXML 1.0/2.0 RosettaNet 1.1/2.0
|
Yes
|
Persist Duration
|
The duration for which messages have to be stored persistently for the purpose of duplicate elimination.
|
ebXML 1.0/2.0
|
Yes
|
Process Timeout
|
The amount of time a PIP can be active without completion before timing out.
|
RosettaNet 1.1/2.0
|
Yes
|
Delivery Semantics
|
The reliable message service behavior:
|
ebXML 1.0/2.0
|
Yes
|
Digital Signature Configuration for Non-Repudiation
|
Signature Required
|
Indicator of whether or not the message is digitally signed using the signature certificate of the trading partner sending the message (true or false).
|
ebXML 1.0/2.0 RosettaNet 1.1/2.0
|
Yes
|
Signature Receipt Required
|
Indicator of whether or not the message is acknowledged by a digitally signed receipt acknowledgement message using the signature certificate of the trading partner sending the acknowledgement (true or false).
|
ebXML 1.0/2.0 RosettaNet 1.1/2.0
|
Yes
|
Signature Certificate
|
The name of the signature certificate used to digitally sign messages.
|
ebXML 1.0/2.0 RosettaNet 1.1/2.0
|
Yes
|
Non Repudiation Protocol
|
The predefined non-repudiation protocol (PKCS7).
|
RosettaNet 1.1/2.0
|
No
|
Hash Function
|
The message digest hash function (SHA1 or MD5).
|
RosettaNet 1.1/2.0
|
Yes
|
Signature Algorithm
|
The predefined signature algorithm (RSA).
|
RosettaNet 1.1/2.0
|
No
|
Message-Level Encryption Configuration
|
Encryption Certificate
|
The name of the encryption certificate used to encrypt and decrypt messages. None indicates no message-level encryption.
|
RosettaNet 2.0
|
Yes
|
Cipher Algorithm
|
Type of cipher algorithm (RC5, DES, 3DES, or RC2). See Defining a RosettaNet 1.1 or 2.0 Binding for a description of the values.
|
RosettaNet 2.0
|
Yes
|
Encryption Level
|
The encryption level specifies how much of the message content is to be encrypted.
|
RosettaNet 2.0
|
Yes
|
Authentication
|
Authentication table
|
Entry for each authentication configured for the binding. See Adding Authentication to a Service Profile.
|
All binding types
|
Yes
|
Mode
|
Basic, one-way, one-way with basic, or mutual.
|
Client TP
|
The name of the trading partner that this authentication applies to.
|
Delete
|
A Delete link that can be used to delete the entry.
|
PIP Failure
|
PIP failure notification table
|
Entry for PIP notification of failure:
|
RosettaNet 1.1/2.0
|
Yes
|
Failure Type
|
Type of failure (Failure Report Admin or Failure Notifier).
|
Trading Partner
|
The trading partner name of the PIP Failure Notifier or PIP Report Administrator role. This specifies the party used to start the Notification of Failure Error (PIP0A1).
|
Trading Partner Binding
|
The trading partner binding.
|
Delete
|
A Delete link that can be used to delete the entry.
|
To view binding properties:
- 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.
- In the binding table, click the binding name.
The View Binding Details page is displayed.
To change binding properties:
- On the View Binding Details page, click the name of the binding.
The Edit Binding page is displayed.
- If any service profiles for the trading partner are enabled, you are prompted to disable them before the change can take effect. Click Disable to disable the service profiles and continue.
The View Binding Details page is displayed with the updated properties.
Note: If there is an error, the Edit Binding page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
- Do one or more of the following as required:
Updating or Deleting Authentication
The authentication required for an exchange is configured as part of the service profile definition, but can only be updated or deleted from the respective binding definitions for the service profile participants. Although you can delete any type of authentication from a binding, the properties that can be edited are limited. The following table summarizes the changes that can be made by authentication type.
Table 9-1 Changes by Authentication Type
Authentication Type
|
If the authentication is configured for the local trading partner in the service profile . . .
|
If the authentication is configured for remote trading partner in the service profile . . .
|
Basic
|
No properties can be edited.
|
You can enter a new user name in the Username field or select a new alias from the Password Alias drop-down list.
|
One-Way
|
No properties can be edited.
|
You can select a new certificate from the Server Certificate drop-down list.
|
One-Way with Basic
|
No properties can be edited.
|
You can enter a new user name in the Username field or select a new alias from the Password Alias drop-down list.
You can select a new certificate from the Server Certificate drop-down list.
|
Mutual
|
You can select a new certificate from the Client Certificate drop-down list.
|
You can select a new certificate from the Client Certificate drop-down list.
You can select a new certificate from the Server Certificate drop-down list.
|
To learn more about adding authentication to a service profile, see Adding Authentication to a Service Profile. The following procedures describe how to update or delete an authentication from the View Binding Details page.
To display the View Binding Details page:
Do one of the following to display the View Binding Details page:
- Locate the trading partner as described in Listing and Locating Trading Partners, then click the trading partner name. On the View and Edit Trading Partner Profile page, click the name of the binding in the Bindings table.
- 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 name of the binding in the Bindings table.
- Locate the Service as described in Listing and Locating Services, then click the service name to select it. On the View and Edit Service Details page, click the name of the binding in the Local Binding or Remote Binding column of the Service Profiles table.
To delete authentication from the View Binding Details page:
- In the Authentication section of the View Binding Details page, click the Delete link for the entry to be deleted.
The entry is removed from the Authentication table.
Note: After you have deleted authentication from the binding of a participant in a service profile, you can reconfigure it as described in Adding Authentication to a Service Profile. In this case, options are only offered for configuring authentication for the participant whose authentication was deleted.
To update authentication from the View Binding Details page:
- In the Authentication section of the View Binding Details page, select the authentication entry by clicking the type.
The authentication configuration is displayed.
- Click Edit Authentication.
- Depending on the type of authentication, you can do one or more of the following. See Table 9-1 for summary of the changes that can be made by authentication type:
- Select a new certificate from the Server Certificate drop-down list. If the certificate has not yet been added, click Add Certificate. See Adding Certificates to a Trading Partner for instructions. Once the certificate has been added, it is available for selection.
- Select a new certificate from the Client Certificate drop-down list. If the certificate has not yet been added, click Add Certificate. See Adding Certificates to a Trading Partner for instructions. Once the certificate has been added, it is available for selection.
- Enter a new user name in the Username field and select a new alias from the Password Alias drop-down list. If the password alias has not yet been added, click Add Alias. See Adding Passwords to the Password Store for instructions. Once the password alias has been added, it is available for selection.
The View Binding Details page is displayed.
Configuring Signature Transforms for ebXML Bindings
The ebXML protocol supports non-repudiation by digitally signing outbound messages and acknowledgements based on the settings for the Signature Required and Signature Receipt Required properties of the binding. Optional XPath filtering transforms can be applied to the message for signing purposes as described in the following procedure.
Note: A default transform is defined which cannot be deleted. The default XPath expression ensures that, while signing and verifying signed messages, XMLDSig processing engines exclude all elements with SOAP:actor
attributes targeting the nextMSH
or next SOAP node. The default transform is required to exclude SOAP:actor
and other dynamic information used in routing which can invalidate a signature.
To learn more about the digital signature implementation, see Using WebLogic Integration Security in Deploying WebLogic Integration Solutions.
To configure signature transforms for XML digital signatures:
- 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.
- In the binding table, click the binding name.
The View Binding Details page is displayed.
- In the XML Digital Signature Configuration for Non-Repudiation section, click Configure Signature Transforms.
The Configure Signature Transforms for XML DSIG page is displayed.
- To add new transforms, do the following:
- Enter the XPath expression in the XPath Transforms field.
The Configure Signature Transforms for XML DSIG page is displayed with the new transform.
- Repeat steps a to c as required to add additional transforms.
- To sort the XPath transforms:
- Move the position of a condition by clicking the up or down arrow
to the right of the condition.
- To delete XPath transforms:
- Click the Delete link to the right of the transform.
A confirmation message is displayed.
- Click OK to confirm and delete the transform.
- When all changes are complete, click Cancel to return to the View Binding Details page.
Configuring PIP Notification of Failure Roles for RosettaNet Bindings
From the View Binding Details page you can add PIP Failure Notifier and PIP Report Administrator roles, edit existing roles, or delete roles.
To add a notification of failure role:
- 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.
- In the binding table, click the binding name.
The View Binding Details page is displayed.
- In the PIP Failure section, click Add pip failure.
The Add PIP Failure page is displayed.
- From the Failure Type drop-down list, select Failure Report Admin or Failure Notifier.
- From the Name drop-down list, select the trading partner name of the PIP Failure Notifier role (if Failure Notifier is selected) or PIP Report Administrator role (if Failure Report Admin is selected).
- From the Binding Name drop-down list, select the binding.
The View Binding Details page is displayed with the addition.
Note: If there is an error, the Add PIP Failure page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
To edit a notification failure role:
- 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.
- In the binding table, click the binding name.
The View Binding Details page is displayed.
- In the PIP Failure section, click the Failure Type (Failure Notifier or Failure Report Admin).
The View or Edit PIP Level Failure page is displayed.
The Edit PIP Failure page is displayed.
- From the Name drop-down list, select a new trading partner name.
- From the Binding Name drop-down list, select a new binding.
- If any service profiles for the trading partner are enabled, you are prompted to disable them before the change can take effect. Click Disable to disable the service profiles and continue.
The View Binding Details page is displayed with the update.
Viewing and Changing a Custom Extension
The View and Edit Custom Extension page allows you to view and update the custom extension for a trading partner.
To view the custom extension:
- 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.
- In the custom extension table, click the custom extension name.
The View and Edit Custom Extension page is displayed.
To change the custom extension:
- On the View and Edit Custom Extension page, click Edit Custom Extension.
The Edit Custom Extension page is displayed.
- In the Description field, enter or update the optional description.
- In the XML field, update 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.
The custom extension is displayed in the Custom Extension summary table.
Note: If there is an error, the Edit Custom Extension page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
Viewing and Changing Services
The View and Edit Service Details page allows you to view and change service properties. For RosettaNet services, you can also add, edit, or delete the RosettaNet service defaults from this page.
The following table summarizes the information displayed on the View and Edit Service Details page.
Property
|
Description
|
Administrator Can Set (Yes/No)
|
Name
|
The service URI or control name. The name is a link to the View and Edit Service Details page for the service.
|
No
|
Business Service Name
|
The business service name as defined for the process. For an ebXML process, this is the ebxml-service-name set in the @jpd:ebxml annotation. For a RosettaNet process, this is the pip-name set in the @jpd:rosettanet annotation. The business service name is empty for Web services.
|
No
|
Description
|
An optional description. This value is for administrative purposes only. It is not included in messages.
|
Yes
|
Business Protocol
|
Business protocol (ebXML, RosettaNet, or Web service).
|
Yes
|
Type
|
The type of service (process, service control, or Web service).
|
Yes
|
Service Profiles
|
Service profile table
|
Entry for each service profile:
|
Yes
|
Local Trading Partner
|
Name of the local trading partner. The name is a link to the View and Edit Trading Partner Profile page for the partner.
|
Remote Trading Partner
|
Name of the remote trading partner. The name is a link to the View and Edit Trading Partner Profile page for the partner.
|
Local Binding
|
Local binding.
|
Remote Binding
|
Remote binding.
|
Message Tracking Level
|
Message tracking level for the service profile (all, default, metadata, or none). For a description of the value, see Adding Service Profiles to a Service.
|
Status
|
Status of the service profile (enabled or disabled).
|
View
|
A View link that displays the View Service Profile page. To learn more, see Viewing and Changing Service Profiles.
|
Statistics
|
A link to the Trading Partner Management Statistics page for the service profile.
|
To view a service:
- Click the service name to select it.
The View and Edit Service Details page is displayed.
To change service properties:
- On the View and Edit Service Details page, click Edit Service.
The Edit Service Details page is displayed.
- 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.
- If any service profiles are enabled, you are prompted to disable them before the change can take effect. Click Disable to disable the service profiles and continue.
The View and Edit Service Details page is displayed with the new definition.
Note: If there is an error, the Edit Service Details page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
To view and edit the defaults for RosettaNet service:
- On the View and Edit Service Details page, click View Service Defaults to view the current settings.
- Click Submit to save your changes.
To delete the defaults for a RosettaNet service:
- On the View and Edit Service Details page, click View Service Defaults to view the current settings.
- Click Delete to delete the current defaults.
You are prompted to confirm.
- Click OK to confirm and delete the RosettaNet service defaults.
The defaults are deleted and you are returned to the View and Edit Service Details page.
Viewing and Changing Service Profiles
The View and Edit Service Details page allows you to:
- View a list of the service profiles defined for the service.
- View the properties of a selected service profile.
- Edit a selected service profile.
To view a service profile:
- 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.
To change a service profile:
- On the View Service Profile page, click Edit Service Profile.
The Edit Service Profile page is displayed.
- To change the status, select Enabled or Disabled from the Status drop-down list,
- To change the Message Tracking Level, select one of the following from the drop-down list.
- 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 the repository and no information is available for view in the Message Tracking module of the console.
- To update binding for the Local trading partner, select a new binding from the Binding drop-down list. 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.
- To update binding for the Remote trading partner, select a new binding from the Binding drop-down list. 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.
- If the service profile is enabled, you are prompted to disable it before the change can take effect. Click Disable to disable the service profiles and continue.
The View and Edit Service Details page is displayed. The new profile is displayed in the service profile summary table. To enable to service profile, see Enabling and Disabling Trading Partner and Service Profiles.
Note: If there is an error, the Edit Service Profile page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
Enabling and Disabling Trading Partner and Service Profiles
You can enable and disable trading partners and service profiles in the following ways:
- Disable a trading partner, and all the service profiles associated with the trading partner, from the View and Edit Trading Partner Profiles list.
- Enable a trading partner, and all the service profiles associated with the trading partner, from the View and Edit Trading Partner Profiles list.
- Disable an enabled trading partner from the View and Edit Trading Partner Profile page. If there are any enabled service profiles associated with the trading partner, you are prompted to disable them in order to disable the trading partner.
- Enable a disabled trading partner profile from the View and Edit Trading Partner Profile page.
Note: Only the trading partner profile is enabled. The associated service profiles are not automatically enabled when you enable a trading partner in this way.
- Enable or disable individual service profiles from the Edit Service Profile page.
In addition to the above:
- When you update a trading partner profile, certificate, or binding, if any of the service profiles for the trading partner are enabled, you are prompted to disable them before the change can take effect.
- When you update a service profile, if it is enabled, you are prompted to disable it before the change can take effect.
The following procedures describe the various methods for enabling and disabling trading partner and service profiles.
To disable trading partners, and the associated service profiles, from the View and Edit Trading Partner Profiles list:
- Click the check box to the left of each trading partner to select.
The Disable Trading Partner Service Profile page is displayed, listing the service profiles that must be disabled.
- Click Disable to disable the service profiles.
You are returned to the View and Edit Trading Partner Profiles list. A red light
in the status column indicates that the trading partners cannot send or receive messages.
To enable trading partners, and the associated service profiles, from the View and Edit Trading Partner Profiles list:
- Click the check box to the left of each trading partner to select.
The Enable Trading Partner Service Profiles page lists the service profiles that can be enabled.
Note: You can selectively enable profiles by deselecting the profiles that you do not want to enable.
- Click Enable to enable the selected service profiles.
You are returned to the View and Edit Trading Partner Profiles list. A green light
in the status column indicates that the trading partners can now send or receive messages.
To disable a trading partner, and the associated service profiles, from the View and Edit Trading Partner Profile page:
- Click the trading partner name.
The View and Edit Trading Partner Profile page is displayed.
- From the Status drop-down list, select DISABLED.
- If any service profiles for the trading partner are enabled, you are prompted to disable them before the change can take effect. Click Disable to disable the service profiles and continue.
The View and Edit Trading Partner Profile page is displayed with the updated status.
Note: If there is an error, the edit page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
To enable a trading partner from the View and Edit Trading Partner Profile page:
Note: The associated service profiles are not automatically enabled.
- Click the trading partner name.
The View and Edit Trading Partner Profile page is displayed.
- From the Status drop-down list, select ENABLED.
The View and Edit Trading Partner Profile page is displayed with the updated status.
Note: If there is an error, the edit page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
To disable or enable a service profile from the Edit Service Profile page:
- 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 Edit Service Profile.
The Edit Service Profile page is displayed.
- From the Status drop-down list, select Disabled or Enabled.
The View and Edit Service Details page is displayed. The updated status is displayed in the service profile summary table.
Note: If there is an error, the Edit Service Profile page is redisplayed. A message indicating the problem is displayed above the input requiring correction.
Importing Management Data
You can add or update management data (trading partner profiles, service definitions, and service profiles) by importing an XML representation of the data contained in a trading partner management (TPM) file. Whether you use the console or the Bulk Loader command line utility to import, the TPM file must either:
- Conform to the
tpm.xsd
schema.
Or
- Contain a single trading partner profile exported from WebLogic Integration - Business Connect or from WebLogic Integration using the business connect format.
When you export TPM data using the console or the Bulk Loader utility, a file suitable for import is created. To learn more about the required structure, and how the file is used in import, export, and bulk delete operations, see Using the Trading Partner Bulk Loader.
Note: You cannot import certificate private key information for a local trading partner. Certificates with public keys can only be loaded for remote trading partners.
In the following procedure, it is assumed that the required TPM file has been created. If the file contains entities (trading partners or services) that already exist, the entities are updated as described in Using the Trading Partner Bulk Loader. Otherwise the entities are added. If the entity being updated is in active use, then the operation will fail with an error message.
To add or update management data by importing XML:
- From the Trading Partner Management home page, select the Partner Profile Import/Export module.
The Import Trading Partner Management Data page is displayed.
- Click the Browse button to the right of the File Name field, then locate the TPM file. Select the file and click Open.
- Enter the path to the TPM file in the File Name field.
- Specify the Transaction Level by selecting one of the following option buttons:
- All
Imports the data in a single transaction. If invalid data is detected the entire transaction is rolled back.
- Default
Imports data using multiple transactions. The import initiates a transaction for each trading partner or service. If invalid data is detected during a transaction for any entity, the import is rolled back for the current transaction only; importing stops with the rolled back transaction.
- Specify the Import Format by selecting one of the following option buttons:
- WLI Standard
Imports the data that conforms to the TPM.xsd
schema.
- Business Connect
Imports data that has been exported from WebLogic Integration - Business Connect or from WebLogic Integration using business connect format.
- If the TPM file contains data for existing trading partners, you are prompted to disable any service profiles in use for the trading partners. If prompted, click Disable to disable the service profiles and continue.
When the import process is complete, the following message is displayed.
- Click OK to dismiss the message box.
Exporting Management Data
Before trading partners can participate in transactions hosted by WebLogic Integration, they must set up their environments to meet the requirements of the application. To facilitate trading partner setup, one partner can define the required components (trading partner profiles, service definitions, and service profiles), and then export them so they become available for import by other trading partners.
To export trading partner management data:
- From the Trading Partner Management home page, select the Partner Profile Import/Export module.
- From the left panel, select Export.
The Export Trading Partner Management Data page is displayed.
- Specify the Export Format by selecting one of the following option buttons:
- WLI Standard
Export data that conforms to the TPM.xsd
schema.
- Business Connect
Export for import by WebLogic Integration - Business Connect.
Note: If you are exporting for import to WebLogic Integration - Business Connect, you can only export one trading partner profile at a time. Before continuing, verify that a single trading partner is selected.
- If you checked the Trading Partners or Services check box, do one of the following:
- Check the Export All Referenced Entities check box to export all entities referenced by the selected trading partners or services. For trading partners, referenced entities include the entities referenced by any service profile the trading partner is referenced in. For services, referenced entities include the trading partner profiles referenced in the service profiles. (A trading partner profile always includes it's bindings, certificates, and custom extension.)
Note: Although it is not required, if you are exporting selected services, it is standard practice to check the Export All Referenced Entities option. If you selected the Business Connect format, do not check Export All Referenced Entities.
- Uncheck the Export All Referenced Entities check box to export only the selected trading partners or services.
- Uncheck the Export Certificate Key Information check box to suppress the export of certificate key information.
- Check the Export Certificate Key Information check box to export certification key information.
A download of the file is initiated. The dialog box that is displayed is browser-dependent, but typically, you are prompted to open or save the file.
For example, Internet Explorer displays the following dialog box.
- Specify the location and name of the file, then click Save.
The file is saved to the specified location.
Deleting Trading Partner Profiles and Services Using Bulk Delete
You can delete trading partner management data in bulk from the Delete Trading Partner Management Data page.
To delete trading partner management data:
- From the Trading Partner Management home page, select the Partner Profile Import/Export module.
- From the left panel, select Bulk Delete.
The Delete Trading Partner Management Data page is displayed.
- Specify the Transaction Level by selecting one of the following option buttons:
- All
Deletes the data in a single transaction. If an error is encountered, the entire transaction is rolled back.
- Default
Deletes the data using multiple transactions. A delete transaction is initiated for each trading partner or service. If an error is encountered during the transaction for any entity, the transaction is rolled back; deleting stops with the rolled back transaction.
- Check the Delete All Referenced Entities check box to delete all entities referenced by the selected trading partners or services. For trading partners, referenced entities include the entities referenced by any service profile the trading partner is referenced in. For services, referenced entities include the trading partner profiles referenced in the service profiles. (A trading partner profile always includes it's bindings, certificates, and custom extension.)
Note: Although it is not required, if you are exporting selected services, it is standard practice to check the Export All Referenced Entities option.
- Uncheck the Export All Referenced Entities check box to export only the selected trading partners or services.
When the process is complete, the Trading Partner Management home page is displayed.
Deleting Trading Partner Profiles
You can delete trading partner profiles from the View and Edit Trading Partner Profiles list or from the View and Edit Trading Partner Profiles page. When you delete a trading partner, you must also delete all associated service profiles.
To delete one or more trading partners from the View and Edit Trading Partner Profiles list:
- Click the check box to the left of each trading partner to select.
- If the selected trading partners are referenced in any service profiles, you are prompted to delete the them. Click Delete All to delete the service profiles and continue.
The View and Edit Trading Partner Profiles list is displayed. The deleted trading partners are no longer listed.
To delete a trading partner from the View and Edit Trading Partner Profile page:
- Click the trading partner name to select it.
- On the View and Edit Trading Partner Profile page, click Delete.
A confirmation message is displayed.
- If the trading partner is referenced in any service profiles, you are prompted to delete the them. Click Delete All to delete the service profiles and continue.
The View and Edit Trading Partner Profiles list is displayed. The deleted trading partner is no longer listed.
Deleting Certificates, Bindings, or Custom Extensions
You can delete certificates, bindings, or custom extension from the Trading Partner Management Profile page.
To delete a certificate:
- 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.
- In the certificate table, click the Delete link for the entry to be deleted.
A confirmation dialog box is displayed.
A dialog box is displayed with the following question: "Do you want to remove the certificate from the keystore also?"
- Click OK to remove the certificate from the keystore, or Cancel to leave the certificate in the keystore.
- If any service profiles for the trading partner are enabled, you are prompted to disable them before the change can take effect. Click Disable to disable the service profiles and continue.
The certificate summary table is displayed. The deleted certificate has been removed.
To delete a binding:
- 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.
- In the binding table, click the Delete link for the entry to be deleted.
A confirmation dialog box is displayed.
- If any service profiles for the trading partner are enabled, you are prompted to disable them before the change can take effect. Click Disable to disable the service profiles and continue.
The binding summary table is displayed. The deleted binding has been removed.
To delete a custom extension:
- 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.
- In the custom extension table, click the Delete link for the entry to be deleted.
A confirmation dialog box is displayed.
The custom extension summary table is displayed. The table is now empty.
Deleting Services
You can delete a service from the View and Edit Services list.
To delete a service:
- Click the Delete link for the service to be deleted. (The Delete link is in the right-most column.)
A confirmation dialog box is displayed.
- If the service includes any service profiles, you are prompted to delete the them. Click Delete All to delete the service profiles and continue.
The View and Edit Services list is displayed. The deleted service has been removed.
Deleting Service Profiles from a Service
You can delete service profiles from the View And Edit Service Details page.
To delete service profiles:
- Click the service name to select it.
The View and Edit Service Details page is displayed.
- In the service profile table, click the Delete link for the entry to be deleted. (The Delete link is in the second column from the right.)
A confirmation dialog box is displayed.
The View and Edit Service Details page is displayed. The deleted service profile has been removed from the service profile table.
Viewing Statistics
You can view summary statistics from the Trading Partner Management Statistics page. You can view statistics for the entire system or for a specific service profile.
To view statistics for the system:
- From the Trading Partner Management home page, select the Statistics module.
The Trading Partner Management Statistics page displays the following statistics:
To view statistics for a service profile:
- Click the service name to select it.
The View and Edit Service Details page is displayed.
- In the service profile table, click the Statistics link for the profile. (The Statistics link is in the right-most column.)
The Trading Partner Management Statistics page displays the following statistics:
Monitoring Messages
You can monitor the exchange of business messages from the Message Tracking module. The message data available is dependent on:
From the message tracking module, you can:
- View a list of the business messages exchanged.
- Filter the list.
- View message detail, including header or part content, for selected messages.
In the following procedures, it is assumed that the desired message data is available.
Listing and Locating Messages
You can view a summary listing of the business messages exchanged on View Messages page.
To view a list of the messages:
- From the Trading Partner Management home page, select the Message Tracking Module.
The View Messages page is displayed.
- Do one or more of the following:
- Filter the messages on the list as described in Filtering the Messages Displayed.
- Sort the list by time of the event. Click the ascending
and descending
arrow button to change the sort. order.
- View the details of a selected message as described in Viewing Message Detail.
Filtering the Messages Displayed
The messages displayed on the View Messages page can be filtered as described in the following procedure. The filter you set remains in effect until you update it, or until the server is restarted.
To filter the messages displayed on the View Messages page:
- From the Trading Partner Management home page, select the Message Tracking Module.
The View Messages page is displayed.
- Select Configure View from the Go drop-down list in the upper right corner.
- Click Go to display the Filter the Displayed Messages page.
- To specify an explicit start and end time, click the Start Time option button, then select the start and end times from the drop-down lists.
- To specify an interval relative to the current time, click the For Last option button, then enter the interval.
- Do one or more of the following:
- To filter by recipient, select the trading partner from the For Trading Partner drop-down list.
- To filter by sender, select the trading partner from the To Trading Partner drop-down list.
- To filter by status, select ALL, SUCCEEDED, or FAILED from the Status drop-down list.
Viewing Message Detail
You can view message detail from the Message Details page.
To view message detail:
- From the Trading Partner Management home page, select the Message Tracking module.
The View Messages page is displayed.
- Select the Event ID to display detail for the selected message.
The message detail is displayed as shown in the following figure. You can view the message header, status description, message part headers, message part data, or details for the process instance or type.
Note: The information available is dependent on the message tracking level for the service profile. To learn more about the message tracking levels, see Adding Service Profiles to a Service.