Undeploying WebCenter Applications Using Fusion Middleware Control

7-28 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter ■ Application Metadata -- which includes the customizations and personalizations on the application itself, such as those created when user edits a page and adds content to it. ■ Portlets Preferences-- which includes customizations and personalizations of the portlet instances. The following subsections explain how to preserve these three types of information about an application: ■ Section 7.3.1.1, Preserving Application Configuration ■ Section 7.3.1.2, Preserving Service and User Customizations ■ Section 7.3.1.3, Preserving Portlet Customizations

7.3.1.1 Preserving Application Configuration

In most cases, the end-points of services and portlet-producers are different in a test or staging environment than in a production environment. Therefore, when an application is redeployed to a production environment, you must reconfigure the application to work with the production environment services and producers or reuse the configuration used previously. Fusion Middleware facilitates this by storing the configuration information in the MDS repository. When you deploy the application for the first time, the base document of the application configuration is created in the MDS repository. This configuration is the set of all of the applications connections and their properties that are packaged in the EAR file. After the deployment, you may need to modify the connections using Fusion Middleware Control or WLST in response to production needs. This reconfiguration creates a layer of customization for the configuration changes in the MDS repository. When you redeploy the application, the configuration packaged with the application is laid down as the base document, but the customizations to the configuration are preserved. Therefore, the applications redeployment settings match the most recent configuration performed. However, customizations are completely preserved only when there are no changes in the base document. If you redeploy an application where the packaged connection information has changed, the following can be expected: ■ A new connection is added to the packaged configuration. The new connection should display without problems. ■ A connection has been removed in the packaged configuration. If you configured this connection after the last deployment, then the connection does not display after deployment, and you must re-create it. Note: You must delete runtime customizations customizations not done through JDeveloper before redeploying an updated application that has had major changes to artifacts such as pages, connections, or task flows. Note: To preserve application information, you must redeploy using the same MDS partition that was used or created using the initial deployment.