Changing the System Data Source Using System MBeans to Manage an MDS Repository

Managing the Metadata Repository 14-19 To transfer the metadata from one partition to another, you export the metadata from the partition and then import it into the other partition. You can use Fusion Middleware Control or WLST to transfer the metadata, as described in the following topics: ■ Transferring Metadata Using Fusion Middleware Control ■ Transferring Metadata using WLST

14.3.8.1 Transferring Metadata Using Fusion Middleware Control

To use Fusion Middleware Control to transfer metadata: 1. From the navigation pane, expand the farm, expand Application Deployments, then select the application. 2. From the Application Deployment menu, choose MDS Configuration. The MDS Configuration page is displayed, as shown in the following figure: 3. In the Export section, select one of the following: ■ Export metadata documents to an archive on the machine where this web browser is running. Click Export. The export operation exports a zip file. Depending on the operating system and browser, a dialog box is displayed that asks you if you want to save or open the file. ■ Export metadata documents to a directory or archive on the machine where this application is running. Enter a directory location or archive to which the metadata can be exported. 14-20 Oracle Fusion Middleware Administrators Guide The target directory or archive file .jar, .JAR, .zip or .ZIP to which to transfer the documents selected from the source partition. If you export to a directory, the directory must be a local or network directory or file where the application is physically deployed. If you export to an archive, the archive can be located on a local or network directory or file where the application is physically deployed, or on the system on which you are executing the command. If the location does not exist in the file system, a directory is created except that when the names ends with .jar, .JAR, .zip or .ZIP, an archive file is created. If the archive file already exists, the exportMetadata operation overwrites the file. Click Export. Then, in the Confirmation dialog box, click Close. If you check Exclude base documents, this operation exports only the customizations, not the base documents. See Section 14.3.1 for information about base documents and customizations. 4. If the production application is on a different system, copy the exported metadata to that system. 5. From the navigation pane for the production system, expand the farm, expand Application Deployments , then select the application. 6. From the Application Deployment menu, choose MDS Configuration. The MDS Configuration page is displayed 7. In the Import section, select one of the following: ■ Import metadata documents from an archive on the machine where this web browser is running. ■ Import metadata documents from a directory or archive on the machine where this application is running. Enter the location of the directory or archive that contains the exported metadata. If you specify a directory, include the subdirectory with the partition name in the specification. The directory or archive file must be a local or network directory or file where the application is physically deployed. 8. Click Import. 9. In the Confirmation dialog box, click Close.

14.3.8.2 Transferring Metadata using WLST

To use WLST to transfer metadata: 1. Export the metadata from the original partition using the exportMetadata command: exportMetadataapplication=sampleApp, server=server1, toLocation=tmpmyreposmypartition, docs= This command exports a versioned stripe of the metadata documents from the metadata partition to a file system directory. Only customization classes declared in the cust-config element of adf-config.xml are exported. If there is no cust-config element declared in adf-config.xml, all customization classes are exported. To export all customizations, use the option restrictCustTo=. 2. If the production application is on a different system, copy the exported metadata to that system.