![]() |
![]() |
|
|
Configuring WebLogic Collaborate
You can set some general messaging and security parameters in the WebLogic Collaborate Administration Console. You can also import and export XML files from the repository, and set preferences and other options.
This topic includes the following sections:
Defining WebLogic Collaborate Parameters
For complete information about configuring WebLogic Collaborate, see Advanced Configuration Tasks in Administering BEA WebLogic Collaborate..
To configure the WebLogic Collaborate Administration Console:
Defining Security
For complete information about security in WebLogic Server and WebLogic Collaborate, see Configuring Security in Using BEA WebLogic Collaborate Security.
To configure the secure audit log:
Defining a Proxy Server
To define a proxy server:
Field |
Description |
---|---|
Host |
Enter the HTTP address of the proxy server used for WebLogic Collaborate. For example, http://myproxy.mycompany.com |
Port |
Enter the port number for the proxy server. |
Importing Repository Data
Once you have installed WebLogic Collaborate, you can populate the database three ways:
Note: To import WebLogic Server users, you must use the WebLogic Collaborate Administration Console. If you import the data using the Bulk Loader, WebLogic Server users are not imported.
Note: Before importing repository data, you must shut down WebLogic Collaborate using the menu command. You cannot import data if WebLogic Collaborate is running.
Caution: If the Initialize Database check box is selected, importing repository data will wipe out existing data. Select the Initialize Database option carefully.
To import repository data:
Setting the Transaction Level
The transaction level controls how repository data is imported and determines how the system rolls back the import if an error occurs during the import.
To set the transaction level:
Exporting Repository Data
You can export your existing data from the repository as an XML file. This is useful if you want to import the data into another repository, or use the data in another database.
To import repository data:
You can export different elements in the repository. First select one element and give the exported XML file a unique filename. Do the same for each exported element.
Note: The Reset button at the bottom of the dialog box resets the scope of export for all settings to the default, which is All.
For more information, see Working with the Bulk Loader in the WebLogic Collaborate Administration Guide.
Selecting the Scope of Export
When you export data from the repository,WebLogic Collaborate searches for dependant data. For example, if you want to export collaboration agreements, and then you also choose export referenced objects on the Browse dialog, the export will include the selected collaboration agreements, referenced trading partners, and business protocol definitions referenced by the trading partners. In this scenario, on the Scope of Export field, only Collaboration Agreements are selected but the referenced objects are also exported.
When exporting WebLogic Collaborate data, you can create more than one XML file containing different data. Depending on your selection, the XML file you create will have all repository data or only the data related to the entity you selected.
On the Export tab, click Browse to select the specific instances you want to export. Depending on the type of data you select, specific options may be active or inactive.
Choosing the Export Format
You can control how the repository data is exported. Select either Extensive or Standard. Extensive includes system information such as update-count and timestamps.
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 Collaborate Administration Console.
To set preferences:
Preferences are persistent between sessions of the WebLogic Collaborate Administration Console.
Hiding Advanced System Configuration Features
You can disable or enable display of certain WebLogic Collaborate Administration Console features:
To change the visibility of these features:
Controlling the Number of Items Displayed Per Page
Some pages of the WebLogic Collaborate Administration Console display lists of items. You can control the number of items displayed on each of these types of pages.
To change the number of items displayed:
Displaying Items in the Navigation Tree
You can control whether individual items are displayed under the top-level nodes in the navigation tree.
Note: Displaying a long list of entities in the navigation tree, such as individual Trading Partners, can affect performance of the WebLogic Collaborate console. Displaying entities on the navigation tree is by default disabled.
To enable or disable display of individual items:
Controlling WebLogic Collaborate Performance
You can set several parameters within WebLogic Collaborate that affect runtime performance or the performance of the administration console.
For information about WebLogic Collaborate runtime performance, see the following sections:
In addition, how entities are displayed in the navigation tree affects WebLogic Collaborate Administration Console performance. For information, see Using the Navigation Tree.
Using Advanced Trading Partner Configuration Options
You can use the advanced trading partner configuration options to modify a trading partner's XOCP filter and router, and extended properties. Most users do not need to modify these settings.
Configuring a Trading Partner XOCP Filter and Router
To view the advanced settings:
This tab is the same as one displayed for business protocol definitions, but when invoked in this way, the list of these filters and routers that is displayed is trading partner-specific. For details about fields, see Configuring Business Protocols.
For more information about XOCP filter and router in WebLogic Collaborate, see Advanced Configuration Tasks in Administering BEA WebLogic Collaborate.
Removing Trading Partner XOCP Filter or Router
To remove an XOCP filter or router from a trading partner:
For more information about XOCP filter and router in WebLogic Collaborate, see Advanced Configuration Tasks in Administering BEA WebLogic Collaborate.
Configuring Trading Partner Extended Properties
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. They are referenced using the named extended-property-set your give it.
To view Extended Properties settings:
For more information about XOCP filter and router in WebLogic Collaborate, see Advanced Configuration Tasks in Administering BEA WebLogic Collaborate.
Adding Extended Properties to a Trading Partner
You can add extended attributes to a trading partner. These extended attributes are in the form of name/value pairs.
To view the Extended Properties settings:
For more information about XOCP filter and router in WebLogic Collaborate, see Advanced Configuration Tasks in Administering BEA WebLogic Collaborate.
Removing Extended Properties from a Trading Partner
You can remove extended attributes from a trading partner. These extended attributes are in the form of name/value pairs.
To view the Extended Properties settings:
For more information about XOCP filter and router in WebLogic Collaborate, see Advanced Configuration Tasks in Administering BEA WebLogic Collaborate.
![]() |
![]() |
![]() |
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|