In the Database Connection section, enter the following information:

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. 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.