|
|
Importing and Exporting B2B Integration Components
Before trading partners can participate in conversations hosted by a WebLogic Integration B2B application, they must set up their environments to meet the requirements of the application. Specifically, they must populate their systems with various components on which a B2B application depends, such as trading partner definitions, conversation definitions, collaboration agreements, and workflows. You can facilitate this aspect of environment setup by creating the necessary B2B components and delivering them to your trading partners.
This section explains how to export and import the components necessary to implement B2B applications. It includes the following topics:
B2B Integration Components
The components of a WebLogic Integration B2B application include:
A collaborative workflow includes the template definition and any associated:
It is common for multiple trading partners to use the same component. For example, all parties who are assigned the same role in a collaboration agreement for a given conversation definition require the same conversation definition and public workflow template. To participate in a peer-to-peer exchange, each trading partner must have a trading partner definition for itself and the other party.
To facilitate trading partner setup, one partner can define the required components, and then export them so they become available for import by other trading partners. Trading partner definitions, collaboration agreements, and conversation definitions can be exported and imported through the WebLogic Integration B2B Console. Collaborative workflows can be exported and imported through the WebLogic Integration Studio.
Although many components of a business collaboration are identical when used by different trading partners, some require minor modification after import. For example, if a trading partner definition for a remote trading partner is exported by a local trading partner and then imported by the remote trading partner, the remote trading partner must change the value of the trading partner type property from remote to local before the imported definition can be used.
Workflow templates and conversations typically require modification of the specified organization because different trading partners have different organizational structures in the Studio.
Export and Import Overview
To export the components required by a participant in a B2B exchange:
Typically, you can simply export the required collaboration agreement with the Export all referenced entities option set. This option ensures that all necessary conversation definitions and trading partners are exported along with the specified collaboration agreement.
Note: When you use the Export all referenced entities option, only the referenced objects are exported. For example, although many delivery channels may be associated with a particular trading partner definition, when you export a collaboration agreement with the Export all referenced entities option set, only those parts of the trading partner definition required for the collaboration agreement (that is, only the required party identifiers, delivery channels, document exchanges, transports, and certificates) are exported.
The export procedure is described in Exporting from the B2B Console.
The workflow export procedure is described in Exporting a Workflow Package.
To import and modify the exported components for use:
One or more XML files may be provided. The import procedure is described in Importing to the B2B Console.
The workflow import procedure is described in Importing a Workflow Package.
Exporting from the B2B Console
To export entities from the B2B Console:
The B2B page is displayed in the right pane. It contains several high-level tabs.
Figure 4-2 Entity Selection Page
Select individual instances of the entity by selecting them on this page. Then click the OK button to return to the Export tab.
The default format is standard. The extensive format includes system information, such as the total number of updates (update-count) and timestamps.
The specified entities are exported to an XML file. When the export is complete, a message is displayed as a link at the bottom of the page, as shown in the following figure.
Figure 4-3 Notification of Successful Export
The Save As dialog box is displayed, allowing you to select the location or rename the file. (The default filename is exportConfig.xml.)
Importing to the B2B Console
Before importing data, you must shut down the B2B engine, as described in Starting and Stopping the B2B Engine from the B2B Console in Starting, Stopping, and Customizing BEA WebLogic Integration.
To import to the B2B Console:
The B2B page is displayed in the right pane. It contains several high-level tabs.
The Upload File dialog box is displayed.
Note: If an entity has the same name as an entity in the repository, it is overwritten.
Exporting a Workflow Package
The WebLogic Integration Studio allows you to select and export template definitions and related workflow components. The components you select are packaged in a Java Archive (JAR) file known as a workflow package.
When you export a workflow package, you can:
The Studio supports the export of template definitions, business operations, business calendars, plug-ins, event key tables, and XML repository items. The only elements that cannot be exported are the organizations, users, and roles defined in the Studio. When you export a template definition, it is disassociated from the current organization. When a template definition is imported into a target system, a new organization must be selected for the template.
To export a workflow package from the Studio:
The Export: Select File dialog box is displayed.
Note: If you specify a JAR file by selecting it from a list invoked through the Browse option, the export overwrites the file.
The Export: Select Components to Export dialog box is displayed, as shown in the following figure.
Figure 4-5 Export: Select Components to Export Dialog Box
The dialog box displays a list of all items currently defined. When you select an item, items referenced by it are automatically selected.
Note: Items in the XML repository are not automatically selected; you must select them manually.
When the export operation is complete, the Export: Review Export Summary dialog box displays the following message:
Components were exported to JAR file: path/filename.jar
Importing a Workflow Package
To import a workflow package from the Studio:
The Import: Select File dialog box is displayed.
The Open dialog box is displayed.
You are returned to the Import: Select File dialog box.
The Import: Select Components to Import dialog box is displayed, as shown in the following figure.
Figure 4-6 Import: Select Components to Import Dialog Box
The dialog box lists all the items contained in the JAR file.
If the name of any item is the same as that of an existing item, the Import Confirmation dialog box is displayed, as shown in the following figure.
Figure 4-7 Import: Review Import Summary Dialog Box
Figure 4-8 Import: Review Import Summary
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|