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

7-26 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter 1. Start the WLST shell. For information on starting the WLST shell, see Section 1.13.3, Oracle WebLogic Scripting Tool WLST. 2. Connect to the Administration Server of your WebCenter installation: connectuser_name,password,host_id:7001 Where: ■ user_name is the user name to access the administration server for example, weblogic. ■ password is the password to access the administration server for example, weblogic. ■ host_id is the host ID of the administration server for example, myserver.example.com. You should see the following message: Successfully connected to Admin Server AdminServer that belongs to domain wc_domain. 3. Use the undeploy command to undeploy the application: undeployapp_name,[targets],[options] Where: ■ app_name is the deployment name for the deployed application. [targets] is a list of the target servers from which the application will be removed. Optional. If not specified, defaults to all current targets. ■ [options] is a comma-separated list of deployment options, specified as name-value pairs. Optional. See the deploy command for a complete list of options.

7.2.3 Removing an Applications Credential Map

When a WebCenter Portal application is undeployed, its application credentials are not removed. Consequently, you must manually remove the credential map used for the application after it is undeployed using Fusion Middleware Control. To remove an applications credentials map using Fusion Middleware Control: 1. Determine the credentials map name used by the application by inspecting the contents of the applications adf-config.xml and locating the value for adfAppUID. For example: adf:adf-properties-child xmlns=http:xmlns.oracle.comadfconfigproperties adf-property name=adfAppUID value=Veeva-7209 adf:adf-properties-child In this case, Veeva-7209 is the credential map name used by the application. 2. Log in to Fusion Middleware Control. For information on logging into Fusion Middleware Control, see Section 6, Starting Enterprise Manager Fusion Middleware Control.