Removing an Applications Credential Map

Deploying WebCenter Applications 7-29 ■ A connection property has been changed in the packaged configuration. The customized properties are used. Connection customizations are managed at the individual connection level, and not at the properties level.

7.3.1.1.1 Preserving Configuration Across Deployment Using WLST

If you use WLST commands to configure the WebCenter Portal application, you can easily combine them into a script to remove all the connections and re-create them for the configuration of the production instance. Using this approach, you can always reconfigure an application to the target configuration without worrying about the details in the packaged configuration.

7.3.1.2 Preserving Service and User Customizations

Application metadata can change post-deployment due to customizations done by users at run time. When you redeploy the application, in most circumstances, you must preserve this customization information so that users see exactly what they were seeing before. Application and user customizations are stored in the MDS repository, and the same rules apply for preserving application metadata as for preserving configuration settings. When the application is redeployed, the base documents for all application artifacts are replaced with what is packaged in the EAR file. However, customizations are retained. There is no impact to this information unless the base artifact is changed, in which case the same rules apply as for configuration settings, which are: ■ If new elements are added to the package, then they appear as they are. ■ If elements are removed from the package, for which customizations were created, those customizations are ignored. ■ If elements are changed, then the effect depends on what exactly is changed, but must be verified.

7.3.1.3 Preserving Portlet Customizations

Portlet customizations are packaged with the metadata in the EAR file. Application startup after deployment kicks off the portlet customization migration to the target producers. The target producers are identified by resolving connection customizations. If you have modified your producer connections before redeployment, then those modified connections are used to identify target producers. Note that if you redeploy an EAR file with the same checksum that is, the same file as the pre-existing one, portlet customization and personalizations are not overwritten.

7.3.2 Redeploying WebCenter Applications Using Fusion Middleware Control

This section describes how to redeploy a WebCenter Portal application using Fusion Middleware Control. To redeploy a WebCenter Portal application using Fusion Middleware Control: Best Practice Note: In some cases, you may want to export all application and user customizations in a production application instance and import it into a test or staging instance. You can then test the application against those customizations to see that the new changes do not have an undesired impact. 7-30 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter 1. Log in to Fusion Middleware Control. For more information, see Section 6.1, Displaying Fusion Middleware Control Console.

2. From the Navigation pane, expand the farm, then WebLogic Domain, and then

the domain. 3. Select the server to which to redeploy the application, and then right click and select Application Deployment - Redeploy from the menu. The Select Application page displays see Figure 7–20 . Figure 7–20 Select Application Page

4. Select the application that you want to redeploy.

5. Click Next to display the Select Archive page see

Figure 7–21 . Figure 7–21 Select Archive Page 6. In the Archive or Exploded Directory section, do one of the following: ■ Select Archive is on the machine where this web browser is running and enter the location of the archive or click Browse to find the archive file. ■ Select Archive or exploded directory is on the server where Enterprise Manager is running and enter the location of the archive or click Browse to find the archive file.