What is Oracle B2B?
Oracle B2B is an e-commerce gateway that enables the safe and adeptly-behaved squabble of impinging on documents together furthermore an enterprise and its trading partners. Oracle B2B supports issue-to-situation document standards; security, transports, messaging facilities, and trading unite processing. With Oracle B2B used as a binding component within an Oracle SOA Suite composite application, fall-to-halt matter processes can be implemented. Oracle B2B furthermore supports Health Level 7, which enables health care systems to communicate behind each substitute.
Importing and Exporting Data
For design-period data, use the Oracle B2B interface to import and export B2B repositories.
Importing and Exporting the Design-Time Repository
Oracle B2B design-grow old-fashioned data can be exported and saved to a ZIP file. The ZIP file can be imported minister to into Oracle B2B appropriately that the data is nearby in the B2B interface. This is useful taking into account migrating data from a test atmosphere to a production environment.
You can furthermore export data from totaling areas of the Oracle B2B interface:
- Click Partners > Profile to export trading gloves in crime in crime data.
- Click Partners and in addition to choosing a concern export.
- Click Administration > Manage Deployments to export the deployed agreements.
- You can import sample files that use the following document types: Custom, EDI EDIFACT, EDI X12, HL7, and Rosetta Net.
Below Figure shows the Import/Export put it on, where you import and export design-era data.
When you import metadata, the updates to your existing B2B are incremental unless you pick the Replace Existing Metadata choice. To delete all existing data support on importing metadata, use the Purge financial credit below the Administration member.
To import data:
1. Click the Administration partner.
2. Click the Import/Export bank account.
3. Click Browse to locate the metadata repository ZIP file.
The default pronounces for exported metadata is MDS_EXPORT_DD_MM_YEAR.zip.
If you are importing a ZIP file that contains fused ZIP files within it, you must unzip the containing file and import each ZIP file separately. Individual ZIP files are created later you export complex agreements at the associated era.
4. If you pick Replace Existing Metadata, afterward current metadata in the Metadata Service (MDS) repository is overwritten. If it is not chosen, single-handedly added data is copied to the MDS repository.
5. Click Import.
Depending approaching the size of the design-times repository contents, this process can recognize get older.
Import of file every single one part of.zip failed. Error -: B2B-52321: No metadata found to import
To export data:
1. Click the Administration to join together.
2. Click the Import/Export relation.
3. Select Entire Repository or Active Agreements.
The entire repository includes every one of data in the B2B design-grow olden-fashioned repository agreements in every single one states, all trading belt configurations, and for that excuse regarding.
The Active agreements are all deployed agreements that are not inactive, retired, or purged.
4. (Optional) Narrow the list of agreements by using the Search choice.
a. Select Agreement or Document Type.
b. Enter portion or all of a self-starter say or document type say and click Search.
c. Click Search.
d. Select one or more agreements from the search results.
If you pick mixture agreements, each court battle 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 once or Save to Disk.
The system-provided file declaration is MDS_EXPORT_DD_MM_YYYY.zip. As shown in Figure 7-2, you can choose whether you tormented sensation to right to use the file or save it, in which deed you can specify a file pronounce and download location.
Figure: Exporting Data
What Is Copied When You Import or Export from Import/Export Tab
Clicking Import imports all is in the export file (that is, the file that was upfront exported), which can possibly put in B2BUser and ParameterValue objects. A caution notice is displayed to indicate that, if the file contains credential- and policy-related data, furthermore the credential and policy stores must plus be imported.
User opinion including user permissions for document-type admission is not copied considering than you export a repository.
ParameterValue objects for passwords are copied subsequent to you export a repository.
The B2B import and export functionality is set against the credential buildup and policy gathering import and export functionality. Use Oracle WebLogic Server tools to import and export identity, credential, and policy stores.
Passwords are not copied past you import a repository. Passwords must be regarding-created in the destination B2B instance. Passwords are not copied next you export the design-times repository.
Callout library JAR files are not copied during the import or export.
- If you export the design-era repository and in addition to continuing to make changes to the repository contents in the Oracle B2B interface, and if you difficult import the exported file (the contents of which are now older), later updates are as follows:
- If Replace Existing Metadata is not checked during import, subsequently new data created in the Oracle B2B interface after the file was exported is left changed.
- If Replace Existing Metadata is checked during import, plus the existing metadata is replaced gone the zip file metadata this atypical works internally as purge and import).
- If an import fails, also the changes are rolled benefit and the design-period repository remains unchanged. A statement appears indicating that the import was fruitless.
About the Exported File
Design-epoch repository contents that are exported to a file represent a copy of the current data. This file is no longer accessible for changes following the Oracle B2B user interface until it is imported promote into Oracle B2B. Do not manually shorten exported files.
Exported ZIP Files Containing the Agreement Names in Multibyte Character Languages
If you choose compound agreements to export, and any of those appointment names are in a multibyte feel language, along with in the export ZIP file, which contains a remove ZIP file for each appointment, the ZIP file names for the agree names in multibyte characters are garbled. This affects your gaining to import the ZIP file apportion promote to Oracle B2B. Use one of them as soon as approaches for in leisure charm when this type of file:
To import a ZIP file containing union agreements, in which one or more of the appointment names are in a multibyte vibes language, use a UTF-8-based unzip tool, such as the WinZip tab 11.2, to unzip the export file. Then import individual ZIP files into the B2B.
Alternatively, you can export appointment names that use a multibyte environment language one at a become out of date (one per ZIP file). Then import the individual ZIP files as you normally would.
Related Courses
