This section provides instructions for tasks that you might need to perform after uninstalling Java ES product components from your system. The actual tasks required depend on which product components you chose to uninstall.
If you uninstall Access Manager but not its web container (Application Server or Web Server), you need to apply configuration changes to the instance where Access Manager was deployed.
In some cases the uninstaller might not be able to remove some or all of the Access Manager files. In this case, do a final cleanup by removing the following default directories and their contents:
For Solaris OS: /opt/SUNWam
For Linux and HP-UX: /opt/sun/identity
or, if Access Manager was not installed in the default location:
If you uninstall Access Manager but not the Application Server in which it is deployed, you must complete the following procedure.
If necessary, start the Application Server admin instance. For example, on a Solaris host:
cd /opt/SUNWappserver/appserver/bin ./asadmin start-domain --user admin_user --passwordfile path_to_admin-password_file domainname
In a browser window, go to the Application Server administration console. The default URL is https://hostname:4849 .
In the left pane, click the key to the left of Application Server Instances.
Select the server or the name of the Application Server instance on which Access Manager was deployed.
Click Apply Changes.
In some cases, the uninstaller might not be able to remove some or all of your installation files. To do a final cleanup, remove the ServiceRegistry-base directory and its contents at the following location:
Solaris OS: /opt/SUNWsrvc-registry
Linux and HP-UX: /opt/sun/srvc-registry
The directory that contains the Service Registry database, domain, and keystores is not removed when you uninstall the Registry:
Solaris OS: /var/opt/SUNWsrcv-registry
Linux and HP-UX: /var/opt/sun/srvc-registsry
You can remove it manually if you want. However, to preserve the database for use in a future installation or release, copy the following directory to another location before you reinstall the Registry, then copy it back after you reinstall:
Solaris OS: /var/opt/SUNWsrvc-registry/3.0
Linux and HP-UX: /var/opt/sun/srvc-registry/3.0
For reinstallation, if you made a copy of the Registry database before you installed Service Registry, copy it back after you reinstall. After restoring the database and keystore files (stored in the 3.0 directories), run the following command using platform-specific variants:
.../ant —f build-install.xml appserver.domain.stop export.registryOperatorCert install.cacerts \ appserver.domain.start
This enables existing users to have continued use of the Service Registry Web Console.
If you uninstall Access Manager but not the Web Server in which it is deployed, you must complete the following procedure.
If necessary, start the Web Server admin instance. Refer to To Start Web Server .
Access the Web Server administration console. For example:
/var/opt/SUNWwbsvr7 instance-config-root /admin-server/bin/startserv
Click Apply Changes to restart the web container.