Register the MDS schema using the following command:

7-14 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter If your application has existing database connections configured for WebCenterDS andor ActivitiesDS and these are not named webcenterCustomPortal and activitiesCustomPortal respectively, either the database connections should be deleted from the application prior to deployment, or the database connections should be created and named following the naming convention. Deploying to a Managed Server using global data sources not named WebCenterDS or ActivitiesDS Use this deployment path when the application is not intended to run on a Managed Server created with the WebCenter Custom Portal template, or is intended to run against custom data sources not named WebCenterDS or ActivitiesDS. For this option the WebCenter Custom Portal application should have had database connections created and associated as either the WEBCENTER or ACTIVITIES schema. The Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment check box on the Application Properties Deployment screen in JDeveloper should be deselected. The global data sources intended to be used on the WLS server requires them to be created with the JNDI names matching those of the database connections created for the application in the JDeveloper project. For more information, see Creating a JDBC Data Source on OTN. Deploying to a managed server using local application context data sources of any name Use this deployment path if the application local context data sources are sufficient. This choice requires only that the WebCenter Custom Portal application has a database connection created for and associated with WebCenterDS andor ActivitiesDS depending on which services are being used in the application. The Application Properties Deployment screen in JDeveloper should have the Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment check box selected.

7.1.6.3 Deploying Applications Using Oracle JDeveloper

You can deploy WebCenter Portal applications to a WebLogic server instance directly from a development environment using Oracle JDeveloper, if you have the necessary credentials to access the WebLogic server. For more information, see Creating a WebLogic Managed Server Connection and Deploying a WebCenter Portal Application to a Managed Server in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

7.1.6.4 Deploying Applications Using Fusion Middleware Control

When deploying a WebCenter Portal application using Fusion Middleware Control you must know the location of the WebCenter application archive, and whether a deployment plan exists for the application. See Section 7.1.6.7, Saving and Reusing the Deployment Plan for more information about deployment plans. Deploying WebCenter Applications 7-15 To deploy a WebCenter Portal application using Fusion Middleware Control: 1. Log in to Fusion Middleware Control. See Section 6.1, Displaying Fusion Middleware Control Console.

2. In the Navigation pane, expand WebLogic Domain and click the domain in which

your target Managed Server was created.

3. From the WebLogic Domain menu, select Application Deployment Deploy.

The Select Archive page displays see Figure 7–8 . Figure 7–8 Select Archive Page 4. In the Archive or Exploded Directory section, do one of the following: ■ Select Archive is on the machine where this web browser is running and enter the location of the archive or click Browse to find the archive file. ■ Select Archive or exploded directory is on the server where Enterprise Manager is running and enter the location of the archive or click Browse to find the archive file. 5. In the Deployment Plan section, do one of the following: ■ Select Create a new deployment plan when deployment configuration is done to automatically create a new deployment plan after the redeployment process. Note: Metadata repository and ADF connection details specified during deployment are not stored as part of the deployment plan. You will need to specify these deployment properties each time you deploy the application. If you plan on updating and deploy the application frequently and want to maintain these configuration changes, it is recommended that you make those configuration changes post-deployment using WLST or Fusion Middleware Control. Such configuration changes are saved in the deployment plan and persisted in the MDS repository and do not need to be set again when you redeploy the application.