Understanding a Metadata Repository

Managing the Metadata Repository 14-7 Because versioning of metadata is not supported for file-based repositories, the tip version which is also the only version is exported from a file-based repository. ■ The import operation imports metadata documents from a file system directory or archive to a MDS Repository partition. If you exported to a directory, the directory must be accessible from the host where the application is running. If you exported to an archive, the archive can be located on the system on which you are executing the command. If the target repository is a database-based repository, the metadata documents are imported as new tip versions. If the target repository is a file-based repository, the metadata documents are overwritten. Table 14–1 lists the logical roles needed for each operation. The roles apply whether the operations are performed through the WLST commands, Fusion Middleware Control, or MBeans. Note: ■ To use the custom WLST MDS commands, you must invoke the WLST script from the Oracle Common home. See Section 3.5.1.1 for more information. ■ For more information about the custom WLST MDS commands, see Metadata Services MDS Custom WLST Commands in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. Table 14–1 MDS Operations and Required Roles Operation Logical Role Clear cache Operator role for application Clone metadata partition Admin role for domain Create metadata label Admin role for application Create metadata partition Admin role for domain Delete metadata Admin role for application Delete metadata label Admin role for application Delete metadata partition Admin role for domain Deregister metadata database repository Admin role for domain Deregister metadata file repository Admin role for domain Export metadata Operator role for application Import MAR Admin role for application Import metadata Admin role for application List metadata label Monitor role for application Promote metadata label Admin role for application Purge metadata Admin role for application Purge metadata labels Admin role for application Register metadata database repository Admin role for domain Register metadata file repository Admin role for domain 14-8 Oracle Fusion Middleware Administrators Guide For information about how these roles map to WebLogic Server roles, see Mapping of Logical Roles to WebLogic Roles in the Oracle Fusion Middleware Application Security Guide.

14.3.2 Registering and Deregistering a Database-Based MDS Repository

The following topics describe how to register and deregister a database-based MDS Repository: ■ Registering a Database-Based MDS Repository Using Fusion Middleware Control ■ Deregistering a Database-Based MDS Repository

14.3.2.1 Registering a Database-Based MDS Repository

Before you can deploy an application to an MDS Repository, you must register the repository with the Oracle WebLogic Server domain. You can register a database-based MDS Repository using Fusion Middleware Control or WLST, as described in the following topics: ■ Registering a Database-Based MDS Repository Using Fusion Middleware Control ■ Registering a Database-Based MDS Repository Using WLST

14.3.2.1.1 Registering a Database-Based MDS Repository Using Fusion Middleware Control

You create a database-based MDS Repository using RCU, as described in Section 14.2 . To register a database-based MDS Repository using Fusion Middleware Control: 1. From the navigation pane, expand the farm, then WebLogic Domain. 2. Select the domain. 3. From the WebLogic Domain menu, choose Metadata Repositories. The Metadata Repositories page is displayed, as shown in the following figure: 4. In the Database-Based Repositories section, click Register. The Register Database-Based Metadata Repository page is displayed.