Click Next, and click OK when prompted by the Prerequisites pop-up.

Deploying WebCenter Applications 7-11 ■ User Name - enter a username for the database which is assigned the SYSDBA role for example, SYS. ■ Password - enter the password for the user. ■ Role - select a database role for example, SYSDBA.

7. Click Query.

A table is displayed that lists the schemas and their metadata repositories that are available in the database. 8. Select a repository, then enter the following information: ■ Repository Name - enter a name for the MDS schema. ■ Schema Password - enter the schema password you specified when you created the schema.

9. Click OK.

The repository is registered with the Oracle WebLogic Server domain.

7.1.5.3 Registering an MDS Schema Using WLST

You can also use WLST to register a database-based MDS repository from the command line using the registerMetadataDBRepository command. To register an MDS schema using WLST:

1. Start WLST as described in

Section 1.13.3.1, Running Oracle WebLogic Scripting Tool WLST Commands.

2. Register the MDS schema using the following command:

registerMetadataDBRepositoryname=mds_name, dbVendor=db_vendor, host=host_ name , port=port_number, dbName=db_name, user=username, password=password, targetServers=target_ server Where: ■ mds_name is the name of the MDS schema to register. ■ db_vendor is the vendor of the database being used. ■ host_name is the fully qualified server name of the database server of the Database Server. ■ port_number is the port number of the Database Server. ■ db_name is the name of the database being used to store the MDS. ■ username is the database schema user name. ■ password is the database schema password. ■ target_server is the name of the target server. For multiple targets, separate the target server names with a comma. Be sure to include the WLS administration server in the list of targets so that the MDS database repository name appears in the Deployment Plan dialog when you deploy your application to it. For example, to register the MDS schema mds1 on the Oracle database orcl on the target server server1 with the host ID of example.com, you would use the following command: registerMetadataDBRepositoryname=mds1, dbVendor=ORACLE, 7-12 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter host=example.com, port=1521,dbName=orc1, user=username, password=password, targetServers=server1,AdminServer

7.1.6 Deploying the Application to a WebLogic Managed Server

For WebCenter applications created in JDeveloper, follow the process described in Extending an Existing Domain in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter to create and provision a new Oracle WebCenter Custom Portal server, or if portletized, Oracle WebCenter Custom Services Producer server before deploying. WebCenter Portal applications can be deployed in several ways as described in the following sections: ■ Section 7.1.6.1, Choosing the Information Artifact Store ■ Section 7.1.6.2, Choosing the Data Source ■ Section 7.1.6.3, Deploying Applications Using Oracle JDeveloper ■ Section 7.1.6.4, Deploying Applications Using Fusion Middleware Control ■ Section 7.1.6.5, Deploying Applications Using WLST ■ Section 7.1.6.6, Deploying Applications Using the WLS Administration Console ■ Section 7.1.6.7, Saving and Reusing the Deployment Plan

7.1.6.1 Choosing the Information Artifact Store

As explained in Section 7.1.3, Preparing the Application EAR File, the packaged EAR file consists of several information artifacts, which includes the application binaries, the application configuration, the application metadata, and the portlet customizations. During the deployment, these information artifacts must be moved to the right information store in the instance where application is deployed. The target information stores for these artifacts are as described in Table 7–3 : Table 7–2 Deployment Targets Application Type Managed Server Name WebCenter Portal application WC_CustomPortal Portletized WebCenter Custom Portal Oracle WebCenter Custom Services Producer Non-WebCenter Portal Portlet Producer application WC_Portlet For portlet producer applications, you can either create a Managed Server instance or deploy to the WC_Portlet server. Note: Oracle does not recommend deploying WebCenter Portal applications to any of the preconfigured Managed Servers created during the installation, or to the Administration Server.