Deploying Applications Using WLST

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. Deploying WebCenter Applications 7-23 Figure 7–16 Install Application Assistant Page

4. Using the Install Application Assistant Path field, locate the EAR file that

corresponds to the Web application or portlet producer application you want to install. Select the EAR file and click Next. Page 2 of the Install Application Assistant page displays see Figure 7–17 . Figure 7–17 Install Application Assistant - Page 2

5. Select Install this deployment as an application for both WebCenter Portal

applications and portlet producers and click Next. Page 3 of the Install Application Assistant displays see Figure 7–18 . 7-24 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter Figure 7–18 Install Application Assistant - Page 3 6. Select the deployment target to which to deploy the Web application and click Next .

7. Review the configuration settings you specified, and click Finish to complete the

installation. To change a producer URL 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.1.6.7 Saving and Reusing the Deployment Plan

A deployment plan contains the configuration data needed to deploy an archive to a Managed Server. You can create a deployment plan while youre building and testing your application, or when you deploy your EAR file using Fusion Middleware Control as described in Section 7.1.6.4, Deploying Applications Using Fusion Middleware Control. If there are deployment descriptors packaged within the EAR file, the deployment uses the data in these files. If you need to make any changes to the web.xml file, Oracle recommends that you create a deployment plan. Once created, a deployment plan can be saved as part of the application properties on the target Managed Server, and re-used when redeploying the application using Fusion Middleware Control, as described in Section 7.3.2, Redeploying WebCenter Applications Using Fusion Middleware Control, or using WLST as described in Section 7.3.3, Redeploying WebCenter Applications Using WLST.

7.1.7 Migrating Customizations and Data Between Environments

You can export and import customizations made to pages, WebCenter Services, and portlets PDK-Java and WSRP version 2 producers of a deployed application. For more information, see Chapter 37.2, Exporting and Importing WebCenter Portal Applications for Data Migration.