Click the edit icon for each connection and check that the connection settings are

Deploying WebCenter Applications 7-21 ■ targets specifies the target Managed Servers to which to deploy the application for example, CustomAppServer. You can optionally list multiple comma-separated targets. To enable you to deploy different modules of the application archive on different servers, each target may be qualified with a module name, for example, module1server1. This argument defaults to the server to which WLST is currently connected. ■ [stageMode] optionally defines the staging mode for the application you are deploying. Valid values are stage, nostage, and external_stage. ■ [planPath] optionally defines the name of the deployment plan file. The file name can be absolute or relative to the application directory. This argument defaults to the planplan.xml file in the application directory, if one exists. ■ [options] is an optional comma-separated list of deployment options, specified as name-value pairs. For more information about valid options, see the WLST deploy command in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. When you see the following message, the application has been successfully deployed and is ready to be accessed: Completed the deployment of Application with status completed

7.1.6.6 Deploying Applications Using the WLS Administration Console

You can use the WLS Administration Console to deploy a WebCenter Portal application or a portlet producer application. However, the Console does not offer a means to change ADF connections, including the essential MDS connection. To use the Console to deploy a WebCenter application, the MDS connection in the EAR file must be configured to the target deployment repository. Follow steps 1-5 in Section 7.1.6.5, Deploying Applications Using WLST , then follow the steps below to deploy a WebCenter Portal application or portlet producer application using the WLS Administration Console. Note: Since WLST does not prompt you to modify connections during deployment, the connection information in the EAR file is used to identify the target producer location in the last start-up. If that location is unreachable, correct the location after deploying the application by bringing up the target producers and restarting the application. Migration of portlet customizations starts automatically. If the producer connections point to incorrect producers for example, development producers, and those producers are reachable, the migration of portlet customizations starts using those producers. Since the migration completes, although incorrectly, restarting the application does not automatically restart the migration process. To remedy this, after deployment, use 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 to modify the producer URL endpoint, and then redeploy the application as described in Section 7.3.2, Redeploying WebCenter Applications Using Fusion Middleware Control. 7-22 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter To deploy a WebCenter Portal application or portlet producer application using the WLS Administration Console: 1. Log in to the WLS Administration Console. For information on logging into the WLS Administration Console, see Section 1.13.2, Oracle WebLogic Server Administration Console.

2. In the Domain Structure pane, click Deployments.

The Deployments Summary pane displays see Figure 7–15 . Figure 7–15 Deployment Summary Pane

3. On the Deployment Summary pane, click Install.

The Install Application Assistant page displays see Figure 7–16 . 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. 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 WLS Managed Server before deploying. For portlet producer applications, you can create a Managed Server instance, or optionally deploy to the WC_Portlet server.