Navigating to Dependent Components

7-2 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter ■ Section 7.1.4, Creating a Managed Server ■ Section 7.1.5, Creating and Registering the Metadata Service Repository ■ Section 7.1.6, Deploying the Application to a WebLogic Managed Server ■ Section 7.1.7, Migrating Customizations and Data Between Environments ■ Section 7.1.8, Configuring Applications to Run in a Distributed Environment

7.1.1 Deployment Roadmap

The flow chart and table in this section provide an overview of the prerequisites and tasks required to deploy a WebCenter Portal application to an Oracle WebLogic Managed Server. Figure 7–1 shows the steps to deploy a WebCenter Portal application, and the roles that will carry them out. Figure 7–1 Deploying a WebCenter Portal Application to a Managed Server Table 7–1 shows the tasks, sub-tasks and who will need to carry them out to deploy a WebCenter portal application from JDeveloper. Deploying WebCenter Applications 7-3

7.1.2 Deployment Prerequisites

You can deploy WebCenter Portal applications to any WebLogic Managed Server instance that is provisioned with the Oracle WebCenter libraries. Before deploying, you must: ■ Prepare the application EAR file, as described in Section 7.1.3, Preparing the Application EAR File. ■ Create a WebLogic Managed Server, as described in Section 7.1.4, Creating a Managed Server. Table 7–1 Deploying a WebCenter Portal Application to a Managed Server Actor Task Sub-task Notes Developer 1. Package the Application 1.a Select the data source type package database connections You can use either a global data source or an application-level data source. If using a global data source, then you need to create the data source in the WLS Administration Console before deploying. If using an application-level data source, then you need to add credential mappings in the WLS Administration Console after deploying. 1.b Package application security data This sub-task consists of packaging the credentials, identity data, and application policies. 1.c Create deployment profiles This sub-task consists of creating the WAR and EAR files. Administrator 2. Prepare the Target Environment 2.a Create and provision the Managed Server 2.b Create and register the MDS repository 2.c Configure the target environment 2.d Create the server connection Developer 3. Deploy the Application to a Managed Server The final step is to deploy the application to the Managed Server using either Fusion Middleware Control, WLST, or the WLS Admin Console. 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 optionally create a new WebLogic Managed Server or deploy to the WC_Portlet server. 7-4 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter ■ Create and register a Metadata Service MDS repository, as described in Section 7.1.5, Creating and Registering the Metadata Service Repository. After completing these steps, continue by deploying the application as described in Section 7.1.6, Deploying the Application to a WebLogic Managed Server.

7.1.3 Preparing the Application EAR File

Before you deploy an application, you must first create a deployment profile. The deployment profile packages or archives the WebCenter Portal application and its associated files so that the application can be deployed to an Oracle WebLogic Managed Server as an EAR file. For information on how to create a deployment profile and the resulting EAR file for an application, see Packaging and Deploying a WebCenter Portal Application to a WebLogic Managed Server in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

7.1.3.1 EAR File Contents

The EAR file packages multiple information artifacts, which include: ■ The application itself: the physical pieces of the application such as .jspx, .jar, and .class files. ■ Application Configuration – which contains the URL endpoints and properties of connections to services and producers that are configured for this application. ■ Application Metadata – which is an export of the application metadata created during the design time of the application. ■ Portlet Customizations – which contain customization settings and data for portlets. This information is maintained within the producer, but is exported when an application with registered producers is packaged. This customization data is packaged with the rest of the metadata of a WebCenter Portal application.

7.1.4 Creating a Managed Server

Before deploying a WebCenter Portal application, you must create a WebLogic Managed Server based on the Oracle WebCenter Custom Portal template that contains all the required shared libraries and a MDS Repository. If a WebCenter Portal application has been portletized it should be deployed to the Oracle WebCenter Custom Services Producer server WC_CustomServicesProducer. A portletized application cannot be deployed to the Oracle WebCenter Custom Portal server as it lacks the required portlet libraries. Note that the Oracle WebCenter Custom Services Producer and Oracle WebCenter Custom Portal servers have not only the MDS schema targeted to them but also WebCenter and Activities. For instructions on how to create a new managed server, see Extending an Existing Domain in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter. For instructions on how to create a new domain, see Creating a New Domain in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter. Note: You must delete runtime customizations customizations not done through JDeveloper before deploying an updated application that has had major changes to artifacts such as pages, connections, or task flows.