7
Importing and Exporting Data 7-1
7
Importing and Exporting Data
For design-time data, use the Oracle B2B interface to import and export B2B repositories.
This chapter contains the following topics:
■
Section 7.1, Importing and Exporting the Design-Time Repository
■
Section 7.2, What Is Copied When You Import or Export from the ImportExport Tab
■
Section 7.3, About the Exported File See
Chapter 19, B2B Command-Line Tools, for information on importing and
exporting data using ant.
7.1 Importing and Exporting the Design-Time Repository
Oracle B2B design-time data can be exported and saved to a ZIP file. The ZIP file can be imported back into Oracle B2B so that the data is available in the B2B interface. This
is useful when migrating data from a test environment to a production environment.
You can also export data from other areas of the Oracle B2B interface:
■
Click Partners Profile to export trading partner data. See Section 5.2, Creating
Trading Partner Profiles, for more information.
■
Click Partners and then select an agreement to export. See Section 6.4, Deleting
and Exporting Agreements, for more information.
■
Click Administration Manage Deployments to export deployed agreements. See
Section 9.2.3, Exporting an Active Agreement, for more information.
You can import sample files that use the following document types: Custom, EDI EDIFACT, EDI X12, HL7, and RosettaNet. See
Section 1.7, Oracle B2B Samples and Cookbooks,
for the download location and information about the scenarios presented in the samples.
Figure 7–1 shows the ImportExport tab, where you import and export design-time
data.
Caution: Do not manually edit exported files. If you do so, Oracle
B2B cannot guarantee their integrity.
7-2 Oracle Fusion Middleware Users Guide for Oracle B2B
Figure 7–1 Importing and Exporting Data
The image shows the following tabs on the Oracle B2B screen: ImportExport, Document, Deploy, Manage Deployments, Types, Batch, Downtime, Callout, Purge,
Listening Channel, and Configuration. The ImportExport tab is selected. The first area of the tab shows the Import field; to the right is a Browse button. Above the area
and to the right is the Import button. The second area of the tab shows the following radio buttons: Entire Repository and Active Agreements. The second area also shows a
Search drop-down list. Above the area and to the right is the Export button. The third area of the tab shows a table with the following columns: Agreement and Supported
Document.
When you import metadata, the updates to your existing B2B are incremental unless you select the Replace Existing Metadata option. To delete all existing data before
importing metadata, use the Purge tab under the Administration link. See
Chapter 14, Purging Data,
for more information.
To import data: 1.
Click the Administration link. 2.
Click the ImportExport tab. 3.
Click Browse to find the metadata repository ZIP file.
The default name for exported metadata is MDS_EXPORT_DD_MM_YEAR.zip. If you are importing a ZIP file that contains multiple ZIP files within it, you must
unzip the containing file and import each ZIP file separately. Individual ZIP files are created when you export multiple agreements at the same time.
4. If you select Replace Existing Metadata, then current metadata in the Metadata
Service MDS repository is overwritten. If it is not selected, then only new data is copied to the MDS repository.
Caution:
Complete export operations without interruption or idle time. Leaving the browser idle for more than a few minutes during
export operations can cause file corruption.
Importing and Exporting Data 7-3
5. Click Import.
Depending on the size of the design-time repository contents, this process can take time.
To export data:
1. Click the Administration link.
2. Click the ImportExport tab.
3. Select Entire Repository or Active Agreements.
The entire repository includes all data in the B2B design-time repository—agreements in all states, all trading partner configurations, and so on.
Active agreements are all deployed agreements that are not inactive, retired, or purged.
4. Optional Narrow the list of agreements by using the Search option.
a. Select Agreement or Document Type.
b.
Enter part or all of an agreement name or document type name and click Search
.
c. Click Search.
d.
Select one or more agreements from the search results. If you select multiple agreements, each agreement is exported in its own ZIP
file, and all the individual ZIP files are contained in the export ZIP file.
5. Click Export.
6. Select Open with or Save to Disk.
The system-provided file name is MDS_EXPORT_DD_MM_YYYY.zip. As shown in Figure 7–2
, you can choose whether you want to open the file or save it, in which case you can specify a file name and download location.
Note: If you export Active Agreements, and if this list has more than
one agreement, the export file indicates all.zip will consist of many zip files for example, a.zip, b.zip, and so on, each consisting of
separate Agreements. The underlying ZIP files, a.zip and b.zip, must be individually imported. If you attempt to import all.zip,
then the import will return following error:
Import of file all.zip failed. Error -: B2B-52321: No meta data found to import
Caution: Do not manually edit exported files.
7-4 Oracle Fusion Middleware Users Guide for Oracle B2B
Figure 7–2 Exporting Data
The image shows the File Download dialog box with Open, Save, and Cancel buttons.
7.2 What Is Copied When You Import or Export from the ImportExport Tab
Clicking Import imports whatever is in the export file that is, the file that was previously exported, which can possibly include B2BUser and ParameterValue
objects. A warning message is displayed to indicate that, if the file contains credential- and policy-related data, then the credential and policy stores must also be imported.
User information—including user permissions for document-type access see Section 1.4.2, Restricting Access to Document Types
—is not copied when you export a repository.
ParameterValue objects for passwords are copied when you export a repository. The B2B import and export functionality is separate from the credential store and
policy store import and export functionality. Use the Oracle WebLogic Server tools to import and export identity, credential, and policy stores.
Passwords are not copied when you import a repository. Passwords must be re-created in the destination B2B instance. Passwords are not copied when you export the
design-time repository.
