This chapter provides instructions for uninstalling Sun JavaTM Enterprise System (Java ES) product component software or other Java ES-related utilities that have been installed during a Java ES installation.
This chapter includes the following sections:
This section contains the following subsections:
Java ES provides an uninstallation program for removing product components that were installed on your system using the Java ES installer. Like the Java ES installer, the uninstaller can be run in graphical, text-based, or silent mode.
During installation, the Java ES installer places the Java ES uninstaller at the following location:
Solaris OS: /var/sadm/prod/SUNWentsys5u1
Linux: /var/sadm/prod/sun-entsys5u1
You can use the optional -no parameter to run the uninstaller without uninstalling any software. This option is useful for familiarizing yourself with the uninstaller and for creating a state file for a subsequent silent uninstallation.
The uninstaller only removes product components that were installed by the Java ES installer. To remove product components that were not installed by the Java ES installer, follow instructions in the product component documentation.
The uninstaller does not remove Java ES shared components.
The uninstaller must be run separately on each host that contains Java ES product components. Remote uninstallation is not supported. For each host, you can select one or more product components for removal.
The uninstaller might remove configuration and user data files. The files vary for each component. After the uninstallation process is completed, you might need to remove some additional files and directories. For product-by-product information, refer to Reviewing Uninstallation Behavior for Java ES Product Components.
The uninstaller presents unconfigure pages for product components if needed for multi-session uninstallation.
The uninstaller does not unconfigure installations on third-party web containers.
The uninstaller does not unconfigure Access Manager SDK installations on any web container. You must reconfigure the web container manually (for example, restore the original classpath).
Do not use the uninstaller to remove Sun Cluster software unless Sun Cluster software was installed but never used to configure a cluster node. For more information, see Uninstalling Sun Cluster Software
The uninstaller might behave differently depending on which product components you installed and how they are interrelated.
The uninstaller recognizes dependencies among products that are installed on the same host. If you attempt to uninstall a product component that has dependent products installed on the local host, the uninstaller issues a warning.
For example, if you attempt to uninstall Access Manager from the host where Portal Server is also installed, the uninstaller warns you that Portal Server cannot function without Access Manager.
In most cases, you can uninstall a product component if no other product component depends on it.
For example, Portal Server depends on Access Manager but Access Manager does not depend on Portal Server. If you attempt to uninstall Portal Server, the uninstaller does not issue a warning because Access Manager can function without Portal Server.
When uninstalling a product component, you must identify which products are configured for that product component (some additional configuration might be required). Otherwise, you might have product components on your system that are configured to support products that are no longer present.
The uninstaller does not recognize the following interdependencies:
Dependencies from remote hosts
Dependencies resulting from configuration
Some product component dependencies can be satisfied with product components deployed on remote hosts. The uninstaller does not recognize these dependency relationships.
For example, if you uninstall Directory Server, the uninstaller does not warn you that Access Manager depends on Directory Server, even if both products are deployed on the same host. This is because another Directory Server instance on another host could support Access Manager.
The uninstaller does not recognize a product component dependency that is the result of postinstallation configuration.
For example, suppose you install both Portal Server and Calendar Server on the same host, and then configure Portal Server to use Calendar Server for the Portal Server calendar channel. After this configuration, Portal Server depends on Calendar Server. However, if you then uninstall Calendar Server, the uninstaller does not warn you that Portal Server depends on Calendar Server because the uninstaller does not know about the postinstallation configuration.
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 product component you are going to uninstall. |
Reviewing Uninstallation Behavior for Java ES Product Components |
2. Identify product component dependencies that result from configuration and take appropriate measures |
You might need to back up data, unconfigure the dependent product component from the supporting product component, or uninstall the product components in a particular order. |
3. Make a copy of the product registry file. The backup copy is helpful in recovering from a failed uninstallation. |
Solaris OS: /var/sadm/install/productregistry Linux: /var/opt/sun/install/productregistry |
4. Make a copy of the configuration or user data for product components you are uninstalling if you plan to reuse this data in subsequent installations. |
Reviewing Uninstallation Behavior for Java ES Product Components |
5. If necessary, gather administrator access information for Directory Server and Access Manager. | |
6. If uninstalling Access Manager, uninstall the schema. |
Use this LDIF file to remove the schema before uninstallation: Solaris OS: /etc/opt/SUNWam/config/ldif/ds_remote_schema_uninstall.ldif Linux: /etc/opt/sun/identity/config/ldif/ds_remote_schema_uninstall.ldif |
7. If uninstalling Sun Cluster software, Sun Cluster Geographic software must be uninstalled first. |
Uninstall Sun Geographic Edition software before Sun Cluster software. |
8. If uninstalling Access Manager or Portal Server without uninstalling the Web Container |
Ensure that the Web Container is up and running, For Application Server web container the domain should be started before uninstallation, For Web Server container, the administration instance should be started before uninstallation. If this is not the case Portal Server and Access Manager will not be undeployed from the Web Container during uninstallation. |
9. If uninstalling Access Manager |
Ensure that Directory Server and the Web Container is up and running. |
10. If uninstalling Web Server |
Ensure that administration instance is running. |
Before using the uninstaller, you should survey your installation and plan the steps you might have to take to prevent loss of data or loss of interdependency connections. It is important to understand how the various Java ES product components behave when they are uninstalled.
This section contains the following subsections:
Perform one of the following procedures to review the Java ES product component software that is already installed on each host.
As root, navigate to the directory where the uninstaller is located:
Solaris OS: /var/sadm/prod/SUNWentsys5u1
Linux: /var/sadm/prod/sun-entsys5u1
To survey the local host, run the uninstaller without uninstalling software.
For graphical mode:
./uninstall -no |
For text-based mode:
./uninstall -no -nodisplay |
To see the full syntax for the uninstall command, refer to uninstall Command.
Proceed through the uninstaller pages until you reach the list of installed products.
After viewing the list of installed product components, exit the uninstaller.
No software has been uninstalled.
Use the prodreg utility to view information about all packages installed on your system, including Java ES product components.
This information is useful when checking for product component dependencies. The prodreg utility also indicates packages that are incomplete and might need special handling. On the Solaris 10 and Solaris 9 operating systems, run the utility as follows:
prodreg
For more information, see the prodreg man page.
Review the relevant tables in this section to see what the uninstaller does with each Java ES product component. Plan the steps you might have to take to prevent loss of data or loss of interdependency connections.
In some cases, component files are left behind after uninstallation, which could cause a subsequent installation to fail. If this occurs, refer to Installation Fails Due to Files Left Behind During an Uninstallation for guidelines on resolution.
This section contains the following subsections:
Topic |
Details |
---|---|
Configuration Data |
No entries in Directory Server will be removed (including Access Manager specific data). |
Other Installations This Component Requires |
Directory Server Web container |
Products Requiring This Installation |
Portal Server must reside on the same host as Access Manager SDK. |
Pre-Uninstallation Tasks |
Remove the schema using this file: Solaris OS: /etc/opt/SUNWam/config/ldif/ds_remote_schema_uninstall.ldif Linux: /etc/opt/sun/identity/config/ldif/ds_remote_schema_uninstall.ldif |
Post-Uninstallation Tasks |
Uninstallation unconfigures Access Manager from the web container for full installations on Web Server or Application Server only. It does not unconfigure Access Manager from third-party web containers. Uninstallation also does not unconfigure SDK on any web container. Additionally, remove the following files located in the directory /var/sadm/install if they exist: .lockfile.pkg.lock. For information on additional post-uninstallation issues, refer to Access Manager Post-uninstallation Issues. |
Topic |
Details |
---|---|
Configuration Data and User Data (Solaris OS and Linux only) |
|
Other Installations This Component Requires |
Requires Message Queue on the same system. |
Products Requiring This Installation |
Components that are configured to use Application Server as web container. |
Pre-Uninstallation Tasks |
To preserve configuration data, make a copy of the administration domain directories. |
Post-Uninstallation |
To completely remove Application Server from your system, remove any remaining Application Server log files and directories. Default locations for Application Server directories are: Solaris OS: /var/opt/SUNWappserver /opt/SUNWappserver/appserver or ApplicationServer-base Linux : /var/opt/sun/appserver /opt/sun/appserver Refer to Message Queue Uninstallation Behavior for information on Message Queue post-uninstallation tasks. |
Topic |
Details |
---|---|
Configuration data |
Configuration data for the instance of Directory Proxy Server you are uninstalling is removed during uninstallation. Shared configuration data between several instances of Directory Proxy Server remains after uninstallation. Directory Proxy Server has no user data. |
Other Installations This Component Requires |
Directory Proxy Server has a logical dependency upon the local or remote Directory Server. |
Products Requiring This Installation |
None |
Pre-Uninstallation Tasks |
None |
Post-Uninstallation Tasks |
None |
Topic |
Details |
---|---|
Configuration Data and User Data |
If you are uninstalling the Directory Server instance hosting user data, the Directory Server LDAP database is removed during uninstallation. Caution: To avoid loss of data, make sure to back up Directory Server information before uninstalling. Directory Server has several tools and utilities to backup Directory Server and migrate configuration data. Refer to Directory Server documentation at http://docs.sun.com/coll/1224.1 for more information. |
Other Installations This Component Requires |
None |
Products Requiring This Installation |
|
Pre-Uninstallation Tasks |
|
Post-Uninstallation Tasks |
If you subsequently install Directory Server to the same location, the installation directory must not exist. You might need to manually remove the installation directory and any custom configuration files before reinstalling to the same location. |
Topic |
Details |
---|---|
Configuration Data and User Data |
Configuration and user data are not removed during uninstallation. By default, this data resides in the following locations:
|
Other Installations This Component Requires |
None |
Products Requiring This Installation |
Application Server when configured to use HADB for high availability session persistence. |
Pre-Uninstallation Tasks |
If you plan to upgrade HADB and reuse configuration data, refer to the chapter on High Availability Session Store in the Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX |
Post-Uninstallation Tasks |
Remove configuration and user data that is no longer needed. |
Topic |
Details |
---|---|
Configuration Data |
Instance-specific configuration data, user repository and access control file remains after uninstallation, and can be reused upon subsequent reinstallation. |
Other Installations This Component Requires |
Directory Server (optional) |
Products Requiring This Installation |
Application Server (must reside on same host as Message Queue). |
Pre-Uninstallation Tasks |
|
Post-Uninstallation Tasks |
If you are not planning to reinstall Message Queue, use the commands in the product component documentation to clean up your system. |
Topic |
Details |
---|---|
Configuration Data |
User data remains after uninstallation, however, this data is removed before any reinstallation. |
Other Installations This Component Requires |
None |
Other Products Requiring This Installation |
None |
Pre-Uninstallation Tasks |
None |
Post-Uninstallation Tasks |
To preserve data, copy the following to a persistent location, then copy back after reinstallation: For Solaris OS: /etc/opt/SUNWmfwk/config/mfwk.properties /etc/opt/SUNWmfwk/config/masteragent.properties /etc/opt/SUNWmfwk/config/nodelist /var/opt/SUNWmfwk/persistence/ /var/opt/SUNWmfwk/alarms/ For Linux : /etc/opt/sun/mfwk/config/mfwk.properties /etc/opt/sun/mfwk/config/masteragent.properties /etc/opt/sun/mfwk/config/nodelist /var/opt/sun/mfwk/persistence/ /var/opt/sun/mfwk/alarms/ |
Topic |
Details |
---|---|
Configuration Data and User Data |
|
Other Installations This Component Requires |
|
Products Requiring this Installation |
None |
Pre-Uninstallation Tasks |
Verify that Directory Server and the web container are running. If the web container is Web Server, Web Server admin server must be running. |
Post-Uninstallation Tasks |
|
Topic |
Details |
---|---|
Configuration Data |
The Registry configuration process installs the Registry database domain and server keystore in the following directory:
The directory is not removed when Service Registry is uninstalled. This allows you to preserve the database for use in a future installation or release if you want. |
Other Installations This Component Requires |
Application Server (Domain Administration Server and Command-Line Administration Tool) HADB Message Queue |
Products Requiring This Installation |
None |
Pre-Uninstallation Tasks |
1. Navigate to the ServiceRegistry–base/install directory. 2. Stop the Service Registry domain as follows: .../ant -f build-install.xml appserver.domain.stop 3. Delete the Service Registry domain as follows: .../ant —f build-install.xml appserver.domain.delete If you want to preserve the Registry database for future use, copy the /var/opt/SUNWsrvc-registry/3.0 directory (on Solaris OS) or /var/opt/sun/srvc-registry/3.0 (on Linux) directory to another location before you reinstall the Registry. |
Post-Uninstallation Tasks |
For information on some optional tasks, refer to Service Registry Post-uninstallation Tasks |
Topic |
Details |
---|---|
Configuration Data |
Do not use the Java Enterprise System uninstaller to remove Sun Cluster software, except to remove software that was installed but never used to configure a cluster node. For more information, refer to Uninstalling Sun Cluster Software. |
Other Installations This Component Requires |
Sun Cluster Geographic Edition software must be removed on every host that contains Sun Cluster Geographic Edition components. For more information, refer to Chapter 5, Uninstalling the Sun Cluster Geographic Edition Software, in Sun Cluster Geographic Edition Installation Guide Sun Cluster core and agents for Sun Cluster must be removed together. |
Products Requiring This Installation |
None |
Pre-Uninstallation Tasks |
Sun Cluster software should only be uninstalled using the utilities provided with your Sun Cluster installation. Note: Sun Cluster Geographic Edition software must be removed before Sun Cluster software is removed. |
Post-Uninstallation Tasks |
You might need to update the product registry after uninstalling Sun Cluster software. For more information, refer to Uninstalling Sun Cluster Software. |
Topic |
Details |
---|---|
Configuration Data |
Only the certificate database files in the alias directory under the installation location are preserved. All other files are removed. |
Dependencies |
Directory Server (optional) if external LDAP access control has been selected. |
Pre-Uninstallation Tasks |
Stop all instances of Web Proxy Server. |
Post-Uninstallation Tasks |
The certificate database is preserved under the WebProxyServer-base/alias directory. Before reinstalling, move the certificate database and delete the old installation directory. |
Topic |
Details |
---|---|
Configuration Data and User Data |
|
Other Installations This Component Requires |
None |
Products Requiring this Installation |
Components that can be configured to use Web Server as web container, such as Access Manager and Portal Server. Also Application Server Load Balancing Plugin (if Application Server uses Web Server as its web container). |
Pre-Uninstallation Tasks |
Make sure you can provide the administrator password for the web container. |
Post-Uninstallation Tasks |
To preserve configuration data, back up the Administrative Server and Web Server instance directories under the installation location. If you reinstall Web Server to the same location, the installation directory must not exist. You might need to manually remove the installation directory and any custom configuration files before reinstalling to the same location. For information on additional post-uninstallation issues, refer to Web Server Post-uninstallation Tasks (Web Server Not Uninstalled). |
Depending on the product components you choose to uninstall, you might need to grant the uninstaller administrator access to Access Manager and Directory Server.
Access Manager administrator access is required to undeploy the Access Manager web applications from the Application Server and to remove the Access Manager schema.
Directory Server administrator access is required to manage the configuration directory during uninstallation.
The following table describes the information that the uninstaller needs for granting administrator access. The left column of each table lists the graphical mode labels and state file parameters for the information you must provide. The right column provides additional information.
Table 8–15 Required Administration Information
Label and State File Parameter |
Description |
---|---|
Access Manager | |
Administrator User ID IS_IAS81_ADMIN |
User ID of the Application Server administrator. |
Administrator Password IS_IAS81_ADMINPASSWD |
Password of the Application Server administrator. |
Directory Manager DN IS_DIRMGRDN |
Distinguished Name (DN) of the user who has unrestricted access to Directory Server. Default value is cn=Directory Manager. |
Directory Manager Password IS_DIRMGRPASSWD |
Password of the Directory Manager. |
Directory Server | |
Administrator User ID CONFIG_DIR_ADM_USER |
User with administrator privileges for the configuration directory. This user can modify Directory Server configuration, including creating and removing suffixes. Access control restrictions apply. |
Administrator Password CONFIG_DIR_ADM_PASSWD |
Password for the Administrator. |
Portal Server | |
Administrator Password PS_DEPLOY_ADMIN_PASSWORD |
Password that Portal Server uses to access the web container as administrator. |
Access Manager Administrator Password PS_IS_ADMIN_PASSWORD | |
Directory Server Administrator Password PS_DS_DIRMGR_PASSWORD | |
Directory Server Administrator Domain PS_DS_DIRMGR_DN | |
Web Server |
|
Administrator User ID IS_WS_ADMIN_ID | |
Administrator Password IS_WS_ADMIN_PASSWORD |
After you have completed the relevant tasks in Verifying Prerequisites and planned for component uninstallation behavior, you are ready to run the uninstaller. This section contains information on the three ways in which the uninstaller can be used.
Information on syntax of the uninstall command can be found in Appendix B, Installation Commands.
This section provides instructions for using the interactive graphical interface to uninstall the Java ES product components.
(Optional) Provide access to your local display.
If you are logging in to a remote machine, make sure your DISPLAY environment variable is properly set to the local display. If the DISPLAY variable is not set properly, the installer runs in text-based mode.
Example for C Shell (machine name myhost):
setenv DISPLAY myhost:0.0 |
Example for Korn Shell (machine name myhost):
DISPLAY=myhost:0.0 |
You might need to grant display authorization to run the installer on your local display. For example, you can use the following command to grant display authority from myhost to the root user on serverhost:
myhost\> xauth extract - myhost:0.0|rsh -l root serverhost xauth merge - |
For full instructions on granting such authorization safely, refer to the “Manipulating Access to the Server” chapter in the Solaris X Window System Developer's Guide.
If you are not logged in as root, become superuser.
Navigate to the directory where the uninstaller is located:
Solaris OS: /var/sadm/prod/SUNWentsys5u1
Linux: /var/sadm/prod/sun-entsys5u1
Start the graphical uninstaller:
./uninstall |
The Welcome page is displayed.
Click Next to proceed.
The Select Components page is displayed.
Examine the product components and select those you want to uninstall.
Product components that are installed on your system are enabled and can be selected. Product components that are not installed on your system are disabled.
Some product components contain subcomponents. Expand the product components to view the subcomponents.
After you are satisfied with your selections, click Next.
Resolve configuration or dependency issues.
If the uninstaller detects any recognizable product component dependencies, or potential loss of configuration data among the products selected, warnings are displayed. Your choices are:
If unconfigure pages are displayed, enter the information requested for the product component.
Depending on the product components you selected for removal, the uninstaller prompts you for administrator IDs and passwords. For details on the information you must provide the uninstaller, refer to Granting Administrator Access for the Uninstaller.
In addition, the uninstaller might also prompt you for a port number or a host name.
Provide the required administrator information.
Click Next to proceed to the Ready To Uninstall page.
Before removing software from your system, the uninstaller lists the product components you have selected for removal and the total disk space that will be reclaimed.
Review the uninstallation selections you have made and make any changes needed as follows:
Click Next when you are satisfied with your selections.
The uninstaller begins removing software from your system and displays the following:
A progress bar that displays the overall completion percentage
The name of the package currently being removed
The Uninstallation Complete page displays after all product component software has been removed.
Click View Summary or View Log for information about the uninstallation.
Uninstallation summary. Shows the product components that were uninstalled and a list of configuration information for the product components.
Uninstallation log. Shows all messages that were generated by the uninstaller during uninstallation.
You can also review the uninstallation summary and log files:
Solaris OS: /var/sadm/install/logsLinux: /var/opt/sun/install/logs
Click Close to exit the uninstaller.
If you uninstalled Access Manager or Service Registry, go to Completing Post-uninstallation Tasks.
The text-based interface allows you to run the uninstaller directly from a terminal window by responding to prompts displayed in the window. For usage guidelines, refer to How to Use the Text-Based Interface.
If you have problems during uninstallation, refer to Chapter 9, Troubleshooting.
If you are not logged in as root, become superuser.
Navigate to the uninstaller directory:
Solaris OS: /var/sadm/prod/SUNWentsys5u1
Linux: /var/sadm/prod/sun-entsys5u1
Run the uninstaller:
./uninstall -nodisplay |
The Welcome message is displayed followed by a list of all possible Java ES product components on your system.
The uninstaller selects for removal any Java ES product components it finds on your system by listing the numbers corresponding to the installed product components. Product components that are not installed on your system are disabled and cannot be chosen. You can choose to uninstall all installed components, or select only some of the installed components for uninstallation.
Choose product components for uninstallation.
To uninstall all installed product components, press Return.
To choose specific product components, type a comma-separated list of the numbers corresponding to the product components you want to uninstall, and press Return.
Resolve configuration or dependency issues.
If the uninstaller detects product component dependencies among the products selected for removal, warnings about a potential loss of configuration data are displayed. Your choices are:
If unconfigure pages are displayed, enter the information requested for the product component.
If you selected a product component for which the uninstaller needs an administrative ID or password, the uninstaller prompts you for administrator IDs and passwords.
For details on the information you must provide the uninstaller, refer to Granting Administrator Access for the Uninstaller.
Depending on the product components you selected for removal, the uninstaller might also prompt you for a port number or a host name.
Before removing software from your system, the uninstaller displays a summary page, showing the product components selected for removal.
Review your selections.
When you are satisfied with your selections, type the number 1 and press Return.
The uninstaller begins removing software from your system. During uninstallation, the uninstaller displays a progress bar that displays the overall completion percentage.
After all product component software has been removed, you can view the uninstallation summary and log.
Type 1 or 2 and press Return to see information about the uninstallation.
Uninstallation summary. Type 1 to see the product components that were uninstalled and a list of configuration information for the product components.
Uninstallation log. Type 2 to list all messages that were generated by the uninstaller during uninstallation.
You can also view the uninstallation summary and log files:
Solaris OS: /var/sadm/install/logsLinux: /var/opt/sun/install/logs
Type the ! character to exit the uninstaller.
If you uninstalled Access Manager or Service Registry, go to Completing Post-uninstallation Tasks.
Silent uninstallation is useful for uninstalling Java ES product components on multiple hosts that share similar configurations. The procedure for uninstalling in silent mode is similar to the procedure for installing in silent mode as described in Chapter 5, Installing in Silent Mode.
To perform a silent uninstallation, you must first generate a state file by running an interactive uninstallation session in either graphical or text-based mode. For more information, refer to Generating the Initial State File.
If you are not logged in as root, become superuser.
Navigate to the uninstaller directory:
Solaris OS: /var/sadm/prod/SUNWentsys5u1
Linux: /var/sadm/prod/sun-entsys5u1
If you are using the graphical interface of the uninstaller, you might need to provide access to your local display. See Running the Uninstaller in Graphical Mode.
Run the silent uninstaller. For example:
Include the –no option if you do not want to uninstall software in this session.
Graphical mode:
./uninstall -saveState statefile_path |
Text-based mode, software not uninstalled:
./uninstall -no -nodisplay -saveState statefile_path |
To see the full syntax for the uninstall command, refer to uninstall Command.
Proceed through the uninstaller to completion.
As you respond to the prompts, the uninstaller records your answers in the specified state file. When you complete the uninstallation, the state file is available in the location that you specified. If you used the –no option, no software was uninstalled.
Make a copy of the state file for each host on which you are going to perform a silent uninstallation.
Edit each file providing information specific to the host where you will run that silent uninstallation.
For guidelines on editing state files, refer to Editing the State File. Editing the state file might also include generating a state file ID, as explained in Creating a Platform-Appropriate State File ID.
Verify that you have properly prepared and edited the state file for the host where you want to uninstall Java ES product components.
If you are not logged in as root, become superuser.
Navigate to the uninstaller directory:
Solaris OS: /var/sadm/prod/SUNWentsys5u1
Linux: /var/sadm/prod/sun-entsys5u1
Start the uninstaller. For example:
./uninstall -noconsole -state statefile_path |
To see the full syntax for the uninstall command, refer to uninstall Command.
In a terminal window, navigate to the log file directory:
Solaris OS: /var/sadm/install/logsLinux: /var/opt/sun/install/logs
Locate the log files for the current uninstallation. The log file of interest for monitoring purposes is:
Java_Enterprise_System_5_uninstall.Btimestamp |
The timestamp variable represents the time the log was created. The variable has the following format MMddhhmm, where:
Specifies the month
Specifies the date
Specifies the hour
Specifies the minute
Use the tail command to watch messages as they are written to the logs. For example:
tail -f logfile_name |
To exit the tail program, press Ctrl+C.
Java ES Reporter is not a component managed by the Java ES installer, therefore, you cannot use the uninstaller to remove Reporter.
Disable Java ES Reporter
Follow instructions contained in Java ES Reporter Postinstallation Configuration.
As root, delete the following files:
Solaris OS |
/opt/SUNWmfwk/lib/commons-codec-1.3.jar /opt/SUNWmfwk/lib/commons-httpclient-3.0.jar /opt/SUNWmfwk/lib/mfwk_reporter.jar /etc/opt/SUNWmfwk/config/reporter/config.properties /var/opt/SUNWmfwk/jobtool/reporter/job_measurement_reporter.xml /etc/cacao/instances/default/modules/com.sun.mjwk.reporter.xml /etc/opt/SUNWmfwk/config/reporter/config_state.properties |
Linux |
/opt/sun/mfwk/share/lib/commons-codec-1.3.jar /opt/sun/mfwk/share/lib/commons-httpclient-3.0.jar /opt/sun/mfwk/share/lib/mfwk_reporter.jar /etc/opt/sun/mfwk/config/reporter/config.properties /var/opt/sun/mfwk/jobtool/reporter/job_measurement_reporter.xml /etc/opt/sun/cacao/instances/default/modules/com.sun.mjwk.reporter.xml /etc/opt/sun/mfwk/config/reporter/config_state.properties |
Do not use the Java ES uninstaller to remove Sun Cluster software unless Sun Cluster software was installed but never used to configure a cluster node. Sun Cluster software should be uninstalled using the utilities provided with the Sun Cluster software. Sun Cluster Core and Sun Cluster Agents for Sun Java System must be removed together. Sun Cluster Geographic Edition software must be removed before removing Sun Cluster software. For more information on unconfiguring and uninstalling Sun Cluster software, refer to the Sun Cluster Software Installation Guide for Solaris OS.
After uninstalling Sun Cluster software manually, run the Java ES uninstaller to remove Sun Cluster components from the product registry.
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.
Access Manager Post-uninstallation Task (Application Server Not Uninstalled)
Web Server Post-uninstallation Tasks (Web Server Not Uninstalled)
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:/opt/sun/identity
or, if Access Manager was not installed in the default location:
AccessManager_base/identity
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: /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: /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: /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.
Please refer http://hostname.domainname:8800 or https://hostname.domainname:8989.
Click Apply Changes to restart the web container.