The following table lists the tasks that you should perform before uninstallation. Some of the tasks might not apply to your particular situation.
The left column lists the order in which you should perform the tasks and the right column contains other useful information and the location of instructions.
Table 8–1 Pre-uninstallation Checklist
Task Description |
Instructions or Helpful Information |
---|---|
1. Review the needs and behaviors of each component you are going to uninstall. | |
2. Identify component dependencies that result from configuration and take appropriate measures, such as backing up data, unconfiguring the dependent component from the supporting component, or uninstalling the components in the proper order. | |
3. Make a copy of the product registry file. The backup copy is helpful in recovering from a failed uninstallation. |
On Solaris OS: /var/sadm/install/productregistry On Linux: /var/opt/sun/install/productregistry |
4. Back up or archive configuration or user data for components you are uninstalling if you plan to reuse this data in subsequent installations. | |
5. Make sure the Directory Server instance that hosts the configuration directory is running. Note: In most cases, the web container and Directory Server should be running, while the other servers should be shut down before uninstalling. |
This Directory Server instance must be running so the uninstaller can unconfigure the components you are uninstalling. |
6. If necessary, gather administrator access information for Administration Server, Directory Server, and Access Manager. | |
7. If uninstalling Access Manager, remove the schema before uninstallation. |
Use the following LDIF file to remove the schema: /etc/opt/SUNWam/config/ds_remote_schema_uninstall.ldif |
8. Before uninstalling Messaging Server that has been installed on its own system, unconfigure Administration Server. |
To unconfigure Administration Server: cd /usr/sbin/mpsadmserver unconfigure |