Importing and Exporting the Design-Time Repository

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. Importing and Exporting Data 7-5 Callout library JAR files are not copied during import or export. See Table 13–1, Callout Details for more information. If you export the design-time repository and then continue to make changes to the repository contents in the Oracle B2B interface, and if you later import the exported file the contents of which are now older, then updates are as follows: ■ If Replace Existing Metadata is not checked during import, then new data created in the Oracle B2B interface after the file was exported is left untouched. ■ If Replace Existing Metadata is checked during import, then the existing metadata is replaced with the zip file metadata this option works internally as purge and import. If an import fails, then the changes are rolled back and the design-time repository remains unchanged. A message appears indicating that the import was unsuccessful.

7.3 About the Exported File

Design-time repository contents that are exported to a file represent a copy of the current data. This file is no longer accessible for changes with the Oracle B2B user interface until it is imported back into Oracle B2B. Do not manually edit exported files.

7.3.1 Exported ZIP Files Containing Agreement Names in Multibyte Character Languages

If you select multiple agreements to export, and any of those agreement names are in a multibyte character language, then in the export ZIP file, which contains a separate ZIP file for each agreement, the ZIP file names for the agreement names in multibyte characters are garbled. This affects your ability to import the ZIP file back into Oracle B2B. Use one of the following approaches for working with this type of file: ■ To import a ZIP file containing multiple agreements, in which one or more of the agreement names are in a multibyte character language, use a UTF-8-based unzip tool, such as WinZip version 11.2, to unzip the export file. Then import the individual ZIP files into B2B. ■ Alternatively, you can export agreement names that use a multibyte character language one at a time one per ZIP file. Then import the individual ZIP files as you normally would. 7-6 Oracle Fusion Middleware Users Guide for Oracle B2B