From the WebLogic Domain menu, select Metadata Repositories.

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. Deploying WebCenter Applications 7-13 Regardless of the tool you choose to deploy, you must supply the target information store locations for correct deployment. The application deployment fails if the MDS location is incorrect or not supplied. The application will still deploy, however, if the target producer is incorrectly specified. If you incorrectly specify the target producer, the portlets are not imported automatically and, consequently, are not operational. If that happens, do one of the following: ■ Edit the portlet producers connections post-deployment using Fusion Middleware Control see Section 23.2.1, Registering a WSRP Producer Using Fusion Middleware Control and Section 23.4.1, Registering an Oracle PDK-Java Producer Using Fusion Middleware Control or WLST commands see Section 23.2.2, Registering a WSRP Producer Using WLST or Section 23.4.2, Registering an Oracle PDK-Java Producer Using WLST , and redeploy the application. ■ Export and import the portlet customization using WLST commands see Section 37.2, Exporting and Importing WebCenter Portal Applications for Data Migration .

7.1.6.2 Choosing the Data Source

There are three basic options for data sources: ■ Deploying to a WebCenter Custom Portal Managed Server using pre-existing data sources ■ Deploying to a Managed Server using global data sources not named WebCenterDS or ActivitiesDS ■ Deploying to a Managed Server using local application context data sources of any name This section describes the benefits and drawbacks of each of these options: Deploying to a WebCenter Custom Portal Managed Server using pre-existing data sources This option requires the least effort in enabling a WebCenter Custom Portal application to access the required data sources, and is the recommended deployment path. To deploy using pre-existing data sources, deselect the Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment check box on the the Application Properties Deployment screen in JDeveloper. Table 7–3 Information Artifact Target Stores Information Artifact Target Information Store Application Binaries Target Server Instance Application Configuration MDS Application Metadata MDS Portlet Customizations Target Producer Note: If the application is deployed and the target producer is incorrectly specified but the target exists, the portlets are imported but to the wrong producer and the portlets are not operational.