bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

B2B Console Help

Configuring B2B Integration

The WebLogic Integration B2B Console allows you to control the parameters governing some aspects of B2B integration, such as messaging and security. You can also import and export XML files from the repository, customize the display of entities in the B2B Console, and specify other options.

This topic includes the following sections:

- Defining B2B Integration Parameters

- Defining Security

- Defining a Proxy Server

- Importing Repository Data

- Exporting Repository Data

- Setting Preferences

- Using Advanced Trading Partner Configuration Options

Defining B2B Integration Parameters

For complete information about configuring B2B integration, see Advanced Configuration Tasks in Administering B2B Integration.

To configure the WebLogic Integration B2B Console:

1. Click B2B, the top-level node in the navigation tree. The Configuration tabs are displayed in the right pane.

2. Select the General tab. The following fields are displayed on this tab.

   Table 2-1 General B2B Integration Tab Fields

   Field | Description
   --- | ---
   WLS Server Name | Read-only field for the name of the current WebLogic Server.
   Description | Brief description (no longer than 254 characters) of the active B2B engine. (Optional)
   Large Message Support | Use Large Message Support | Field for enabling Large Message Support, which improves throughput. By default, all messages are written to the database. Enabling large message support allows all messages to be written to the filesystem instead of to the database. Note: Writing many large messages to the database can degrade run-time performance.
   Location | If you are using large message support, enter the path of the directory containing the working files. Caution: The directory you specify must already exist and should be reserved for B2B integration messages.
   Minimum Size | If you are using large message support, indicate the minimum size required for a message for which large message support is enabled. (The default is 0 Kb.)

3. Modify the appropriate fields as required.

4. Click Apply. The values shown on the General tab are entered into the repository.

Defining Security

For complete information about security in WebLogic Server and B2B integration, see Configuring Security in Implementing Security with B2B Integration.

To configure the secure audit log:

1. Click B2B, the top-level node in the navigation tree. The Configuration tabs are displayed.

2. Select the Security tab. The following fields are displayed on this tab.

   Table 2-2 Security Fields

   Field | Description
   --- | ---
   System Password | User password for the WebLogic Integration run-time environment. For more information about the system password, see Starting, Stopping, and Customizing BEA WebLogic Integration.
   Audit Log Class | Fully qualified name of the Java class that implements the secure audit log.
   Certificate Verification Class | Fully qualified name of the Java class that implements the security verification class.
   Secure Timestamp Class | Fully qualified name of the Java class that implements the secure timestamp class.
   Certificate Authority Directory | Directory containing thecertificates of the all the trusted certificate authorities (CAs).

3. Modify the appropriate fields as required.

4. Click Apply. The values shown on the tab are entered into the repository.

Defining a Proxy Server

To define a proxy server:

1. Click B2B, the top-level node in the navigation tree. The B2B integration configuration and monitoring tabs are displayed.

2. Select the Proxy tab. The following fields are displayed on this tab.

   Table 2-3 Proxy Tab Fields

   Field | Description
   --- | ---
   Host | HTTP address of the proxy server. For example: http://myproxy.mycompany.com
   Port | Port number for the proxy server.

3. Modify the appropriate fields as required.

4. Click Apply. The values shown on the Proxy tab are entered into the repository.

Importing Repository Data

After you install WebLogic Integration, you can populate the database in any of the following ways:

- Using the WebLogic Integration B2B Console, manually enter the data for each entity. (Entities may include, for example, trading partners, conversations, collaboration agreements, and business protocols.) For more information, see the online help for the appropriate entity.

- Use the Bulk Loader to import data. The Bulk Loader loads the database using an XML configuration file. For more information, see Working with the Bulk Loader in Administering B2B Integration.

Note: You must use the following method if you need to import WebLogic Server users. (When you import data using the Bulk Loader, WebLogic Server users are not imported.)

- Using the WebLogic Integration B2B Console, import the data from a backup copy of a repository. The backup file is in XML format. This method is described in Using the Import Tab. For more information about creating a backup copy of a repository, see Exporting Repository Data.

Note: Before importing repository data, you must shut down the B2B engine (server) using the Shutdown command on the Windows menu. You cannot import data if the B2B engine is running.

Using the Import Tab

To import repository data:

1. Click B2B, the top-level node in the navigation tree. The Configuration tabs are displayed in the right pane.

2. Select the Import tab. The following fields are displayed on this tab.

   Table 2-4 Import Tab Fields

   Field | Description
   --- | ---
   File Name | Full path of the repository data XML file you want to import. You can type the pathname in the field or click Browse and select the appropriate file. You can import either an entity-specific file (containing only trading partners, collaboration agreements, conversations, and so on) or a repository data file that contains all B2B integration entities.
   Initialize Database | Field for specifying whether to initialize the repository data. Warning: If the Initialize Database option is selected, then when you subsequently import repository data, existing data is destroyed. Be careful about selecting the Initialize Database option.
   Yes | Clears the existing B2B integration data from the repository during the import. In other words, the imported data overwrites all existing data. If you select Yes, you are required to verify your choice during the import.
   No | Retains existing B2B integration data during the import. In other words, the imported data is added to the existing data. However, if the imported data describes elements and attributes that already exist in the repository, then the imported data overwrites the existing data for those specific values. (No is the default setting.)
   Transaction Level | Parameter that determines how the system rolls back an import if an error occurs during the import.
   All | Imports the repository data, including configuration data, in a single transaction. (This option is appropriate for small repositories.) If invalid data is detected in any of the B2B integration entities represented in the data file, the Bulk Loader utility rolls back the entire transaction and stops. The repository remains in exactly the same condition in which you found it before the import; no data is removed or added.
   Default | Imports the repository data, including configuration data, using multiple transactions. (This option is appropriate for large repositories.) If you choose this option, the import initiates a transaction for each of the following entities: trading partners, conversation definitions, collaboration agreements, business protocol definitions, and logic plug-ins. If invalid data is detected during a transaction for any entity, the import is rolled back for the current transaction only; importing continues for the next transaction.

3. Modify the appropriate fields as required.

4. Click Import. The data shown on the Import tab is imported into the repository.

5. You may now restart the B2B engine (server) by selecting the Start B2B command on the Windows menu.

Setting the Transaction Level

The transaction level controls how repository data is imported and determines how the system rolls back an import if an error occurs during the import.

To set the transaction level:

1. Click B2B, the top-level node in the navigation tree. The Configuration tabs are displayed in the right pane.

2. Select the Import tab. In the Transaction Level field, select Default or All. For a description of these values, see Table 2-4.

Exporting Repository Data

You can export existing data from the repository as an XML file. This technique is useful if you want to import the data into another repository or use it in another database. You can also export different elements in the repository. For each element to be exported, select the element and assign a unique name to the XML file in which that element will be exported. For more information, see Importing Repository Data.

To export repository data:

1. Click B2B, the top-level node in the navigation tree. The Configuration tabs are displayed in the right pane.

2. Select the Export tab. The following fields are displayed on this tab.

   Table 2-5 Exporting Repository Data

   Field | Description
   --- | ---
   Scope of Export | Specification of the data you want to export. When you export data, you can create only one XML file at a time. Your XML file may contain all repository data or only data for a specified entity.
   All | All data in the B2B integration repository, including configuration data.
   B2B | Configuration elements described on the Configuration tabs. Click Browse to select the instances of entities you want to export.
   Trading Partners | All trading partner-related data elements. Click Browse to select the instances of entities you want to export.
   Conversation Definitions | All conversation definition-related data elements. Click Browse to select the instances of entities you want to export.
   Collaboration Agreements | All collaboration agreement-related data elements. Click Browse to select the instances of entities you want to export.
   Business Protocol Definitions | All business protocol definition-related data elements. Click Browse to select the instances of entities you want to export.
   Logic Plug-ins | All logic plug-in-related data elements.
   Format | Indication of whether you want to export metadata with the repository data being exported. For more information about Bulk Loader formatting, see Working with the Bulk Loader in Administering B2B Integration.
   Extensive | Request for export of both repository data and system information, such as update-count and timestamps. Select Extensive if you plan to migrate the data to another system or environment.
   Standard | Request to export only repository data. Select Standard if you plan to make a backup of the repository or import the repository into another database.
   Business Connect Export file | Create an export file using the WebLogic Integration - Business Connect format. This export file is used for export information about a single trading partner from the WebLogic Integration repository to the WebLogic Integration - Business Connect lightweight client. This option is used only with the ebXML business protocol.
   Encoding | Type of encoding used during an export of the WebLogic Integration repository. When encoding is specified the resulting XML data contains a line that defines the encoding, for example: encoding="GB2312" In this example, GB2312 is the specified encoding for Chinese. When encoding is not specified the resulting XML data does not contain an encoding field. (Optional) For more information, see "A Note About Trading Partner Encoding" in Configuration Requirements in Administering B2B Integration
   Export all referenced entities | Request for automatic export of all entities referenced by the entities being exported explicitly, along with the latter entities. For details, see Selecting the Scope of Export.

3. Modify the appropriate fields as required.

4. Click Export.

5. If you want to restore the default setting (All) for the scope of all exports, select the Reset option. (Optional)

For more information, see Working with the Bulk Loader in Administering B2B Integration.

Selecting the Scope of Export

When you export data from the repository, you have the option of requesting a search for dependant data. For example, if you want to export collaboration agreements, and you also request (in the Browse dialog box) the export of referenced objects, the export will include the selected collaboration agreements, trading partners referenced by these agreements, and business protocol definitions referenced, in turn, by the trading partners. In this scenario, only Collaboration Agreements are selected in the Scope of Export fields on the Export tab, but referenced objects are also exported.

When exporting B2B integration data, you can create multiple XML files containing different data. You can create an XML file with either all repository data or only the data related to a specified entity.

On the Export tab, select Browse to display a list of instances. Select the instances you want to export. Depending on the type of data you select, specific options may be active or inactive.

Choosing the Export Format

WebLogic Integration allows you to export data with or without system information, such as the update-count and timestamps variables.

Specify one of the following formats:

- Standard — to export only repository data

- Extensive — to export both repository data and system information

- Business Connect Export File — to export information about a single trading partner from the WebLogic Integration repository into WebLogic Integration - Business Connect. (Available for the ebXML protocol only.)

Note: Use the Extensive format only if you plan to migrate the data to another system or environment.

Setting Preferences

The Preferences tab allows you to configure how entities are displayed in the WebLogic Integration B2B Console.

To set preferences:

1. Click B2B, the top-level node in the navigation tree. The Configuration tabs are displayed.

2. Select the Preferences tab. The following fields as displayed on this tab.

   Table 2-6 Fields on the Preferences Tab

   Field | Description
   --- | ---
   Number of items displayed per page (1 - 50) | Number of records displayed on each page of the B2B Console. The maximum limit is 50, the minimum is 1. The default is 5.
   Default Retry Value | Number of times you want WebLogic Integration to try to send a message. The default is 3.
   Default retry interval | Amount of time you want WebLogic Integration to wait before trying to resend a message. The default is 5000 milliseconds.
   Default time-out value | Amount of time a transaction remains valid (specified in days, hours, minutes, and seconds). After this period, WebLogic Integration terminates the transaction even if there are outstanding messages. The default is 5000 milliseconds. (Optional)
   Language | The natural language in which input is entered in the WebLogic Integration B2B Console. The default is English (UTF-8). Other choices are Default, Chinese, and two types of Japanese characters. Choose Default if the language that you want to use is not listed, which will use the default locale that is set for your system. Note: If you set the Language field to Default, you must specify the character set you are using in the Charset for Default Language field.
   Charset for Default Language | Specifies a character set that will be set as the default language for data display and input.
   Display advanced configuration controls | Field that allows you to control whether logic plug-ins are displayed on the configuration tabs. When you enable this option: The Trading Partners Advanced tab is displayed. In the navigation tree, the Logic Plug-Ins node is shown. The list of Business Protocol Definitions (displayed below the Business Protocols node) can be edited. When disabled, you can view the list, but you cannot add logic plug-ins to the definitions.
   Display entities on the navigation tree | Field that allows you to control whether individual entities, such as trading partners, are displayed as branches under the top-level nodes in the navigation tree. Note: Because the display of many entities (such as trading partners) in the navigation tree may degrade B2B integration performance, the display of entities in the navigation tree is disabled by default.

3. Modify the appropriate fields as necessary.

4. Click Apply.

Preferences persist between B2B Console sessions.

Displaying Advanced System Configuration Features

You can enable or disable the display of the following B2B Console features:

- Logic plug-in configuration

- Business protocol definition configuration

- Advanced configuration for trading partners

To change the visibility of these features:

1. Click B2B, the top-level node in the navigation tree.

2. Select the Configuration tab and then the Preferences tab.

3. Select or deselect the Display advanced configuration controls option to enable or disable, respectively, the features described earlier.

4. Click Apply.

Controlling the Number of Items Displayed Per Page

To change the number of items displayed on each B2B Console page:

1. Click B2B, the top-level node in the navigation tree.

2. Select the Configuration tab and then the Preferences tab.

3. In the Number of items displayed per page field, enter the desired value. The default is 5.

4. Click Apply.

Displaying Entities in the Navigation Tree

You can control whether individual items are displayed under the top-level nodes in the navigation tree.

Note: Because the display of many entities (such as trading partners) in the navigation tree may degrade B2B integration performance, the display of entities in the navigation tree is disabled by default.

To enable or disable the display of individual items:

1. Click B2B, the top-level node in the navigation tree.

2. Select the Configuration tab and then the Preferences tab.

3. Select or deselect the Display entities on the navigation tree option to show or hide respectively, individual items in the navigation tree. By default, this option is not selected.

4. Click Apply.

Controlling B2B Integration Performance

WebLogic Integration provides several parameters that you can set to improve the run-time performance of B2B integration and/or the B2B Console:

- When you configure trading partner document exchanges using XOCP binding, two options, Confirmed Delivery and Message History, affect the run-time performance of B2B integration functionality. For more information, see Configuring XOCP 1.1 for a Document Exchange (Deprecated).

- You can choose to have messages written to either the database or the filesystem. For more information, see Defining B2B Integration Parameters.

In addition, B2B Console performance is affected by how entities are displayed in the navigation tree. For details, see Using the Navigation Tree.

Using Advanced Trading Partner Configuration Options

The B2B Console provides advanced configuration options to modify the setting for a trading partner's XOCP filter and router, and extended properties. Most users do not need to modify these settings.

Configuring a Trading Partner's XOCP Filter and Router (Deprecated)

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

To view a list of the XOCP filters and routers associated with a particular trading partner:

1. Do one of the following:

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

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

2. Select the Advanced tab. Select the XOCP Filter and Routers tab if it is not active.

   A list of the filters and routers associated with the specified trading partner is displayed. For details about the fields on this tab, see Configuring Business Protocols.

For more information about the XOCP filter and routers used in B2B integration, see Advanced Configuration Tasks in Administering B2B Integration.

Removing a Trading Partner's XOCP Filter or Router

To remove an XOCP filter or router from a trading partner:

1. Do one of the following:

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

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

2. Select the Advanced tab. Select the XOCP Filters and Routers tab if it is not active.

3. In the list labeled XOCP Filter Chain or XOCP Router Chain, select the one(s) you want to delete. Click Remove.

For more information about the XOCP filters and routers used in B2B integration, see Advanced Configuration Tasks in Administering B2B Integration.

Configuring Extended Properties for a Trading Partner

Use the Extended Properties tab to define special conditions for processing a trading partner definition. For example, you can use an XPath expression to modify filtering and routing rules. These properties are included in the message-context documents generated by the business protocol router and filter logic plug-ins.

To view the extended properties set for a particular trading partner:

1. Do one of the following:

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

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

2. Click the Configuration tab if it is not active. Select the Advanced tab, and then the Extended Properties tab. The following fields are displayed on the Extended Properties tab:

   Table 2-7 Fields on the Extended Properties Tab

   Field | Description
   --- | ---
   Property Name | Name of the new extended property you want to create for this trading partner.
   Property Value | Value for the extended property.
   Attributes | Custom attributes you can add to B2B integration.
   Name | Name of the attribute you want to add.
   Value | Value of the attribute you want to add.
   Attributes | List of available attributes (shown as name/value pairs in the form name=value).
   Extended Properties | Lists of existing extended properties for this trading partner. If you click a property in the list, the rest of the fields on this tab are propagated with the information appropriate for that property.

3. Modify the appropriate fields as necessary.

4. Click Add/Apply.

For more information about the XOCP filters and routers used in B2B integration, see Advanced Configuration Tasks in Administering B2B Integration.

Adding Extended Properties to a Trading Partner

You can add extended properties (in the form of name/value pairs) to a trading partner. To add an extended property:.

1. Do one of the following:

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

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

2. Select the Advanced tab. Select the Extended Properties tab if it is not active.

3. Enter a name, a value, and name/value pairs for the new property. For a complete description of the extended properties fields, see Using Advanced Trading Partner Configuration Options.

4. Click Add/Apply. Your new property is added to the repository.

For more information about the XOCP filters and routers used in B2B integration, see Advanced Configuration Tasks in Administering B2B Integration.

Removing Extended Properties from a Trading Partner

You can remove extended properties (in the form of name/value pairs) from a trading partner. To remove an extended property:

1. Do one of the following:

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

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

2. Select the Advanced tab. Select the Extended Properties tab if it is not active.

3. In the list of extended properties, select the one(s) you want to delete. Click Remove.

For more information about the XOCP filters and routers used in B2B integration, see Advanced Configuration Tasks in Administering B2B Integration.