Configuring B2B Integration

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.)

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.)

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).

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).

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

Field

Description

Host

HTTP address of the proxy server. For example:

http://myproxy.mycompany.com

Port

Port number for the proxy server.

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.

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.

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.

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.

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.

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.

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.

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.