According to information on the Java site the Java Console "provides information about the Java version, user home directory, and any error message that occurs while running an applet or application".
Two different Java Console extensions were installed on our test system: Java Console 6. The enable and disable buttons were active but the uninstall buttons grayed out so that the extensions could not be uninstalled the usual way. This is usually an indicator that the add-on was not installed by the user but installed elsewhere. Options include installation by a third-party software that got installed on the device, or by a system administrator who pushed the add-on to the user system. Changing the setting from Hide Console to Do not start console did however have no effect on the two extensions that were installed in Firefox.
A post at the Firefox Extension's Guru blog revealed the solution. Windows users who run Firefox as an administrator will have the uninstall buttons enabled making it possible to remove the Java Console extensions from the web browser.
A right-click on the Firefox executable and the selection of "run as administrator" will start Firefox with administrative privileges. The removal of the add-on will also remove the Java Console link in the Tools menu in Firefox. It is likely that an update or new installation of the JRE will add a new Java Console extension to the web browser.
If you know of a way to prevent that let us know in the comments. We would also like to hear from users who have encountered similar extensions that they did not install directly, and how they handled those.
While you can block Firefox from re-enabling plugins , there does not seem to be an option to do the same for third-party extensions. Which version of fx are you using?
I have the nightly 3. Indeed I do, jre6u The two plugins it installs java deployment toolkit and java platform I always disable as I never seem to need them. But I;ve never seen this java extension. Because there is no reason to have it there if you are not using it? Besides it is also a security risk. I had three consecutive versions of the Java console extension in my FF.
All for no reason, unless you want to run java applets. You have to do it manually. This advice is out of date and no longer applies. For example, using the csh:. The uninstall wizard performs administrative functions to undeploy the RFID Management Console from the application server. All Rights Reserved. Corresponding Web Application. Web services for ALE and device access. 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.
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.
Make a copy of the product registry file. The backup copy is helpful in recovering from a failed uninstallation. 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. If necessary, gather administrator access information for Directory Server and Access Manager. 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. Perform one of the following procedures to review the Java ES product component software that is already installed on each host. To see the full syntax for the uninstall command, refer to uninstall Command. 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:. 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. 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. For information on additional post-uninstallation issues, refer to Access Manager Post-uninstallation Issues.
User-created domains, including all administrative server and Application Server instances, are not removed during uninstallation. All Administration Server and Application Server instances are stopped prior to the completion of 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:.
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. 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. 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.
Configuration and user data are not removed during uninstallation. By default, this data resides in the following locations:. Instance-specific configuration data, user repository and access control file remains after uninstallation, and can be reused upon subsequent reinstallation. Stop any running brokers. You will be prompted for user name admin and password: imqcmd shutdown bkr [ -b hostName:port ]. If you are not planning to reinstall Message Queue and therefore want to delete dynamic data, the flat-file user repository, and the access control file associated with each broker instance, remove this data using the following command.
If you upgrade Message Queue using the Message Queue upgrade script, make a note of your process. The upgrade script does not write install information to the Java ES registry. If you are not planning to reinstall Message Queue, use the commands in the product component documentation to clean up your system. User data remains after uninstallation, however, this data is removed before any reinstallation.
To preserve data, copy the following to a persistent location, then copy back after reinstallation:. Configuration data is removed during uninstallation.
Unconfiguring includes removing services created in Access Manager by Portal Server. Providers for user channels are not removed during installation and can be reused upon subsequent installation.
Customized configuration data display profiles, property files, resources strings, and other customizations is not removed by the uninstaller. It can be reused upon subsequent installation only if Portal Server is reinstalled to the same host with the same configuration. Verify that Directory Server and the web container are running.
If the web container is Web Server, Web Server admin server must be running. For more information, refer to Access Manager Post-uninstallation Issues. All configuration data for the Portal Server Secure Remote Access Core product component is removed during uninstallation.
Gateway, Netlet Proxy, and Rewriter Proxy cannot be in the same directory. You can remove any Portal Server Secure Remote Access product component without removing any dependent product component. 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. For information on some optional tasks, refer to Service Registry Post-uninstallation Tasks. 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.
Sun Cluster software should only be uninstalled using the utilities provided with your Sun Cluster installation. You might need to update the product registry after uninstalling Sun Cluster software. Only the certificate database files in the alias directory under the installation location are preserved. All other files are removed. Before reinstalling, move the certificate database and delete the old installation directory. The Web Server administrative server instance and configured Web Server instance directories are removed.
The initially-configured document root directory is not removed. Web Server administrative server and Web Server instances are stopped before completion of uninstallation. 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. 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. User with administrator privileges for the configuration directory. This user can modify Directory Server configuration, including creating and removing suffixes. Access control restrictions apply.
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. 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 :. 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. 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:. 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. 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. The uninstaller remembers previously-specified values. You can modify any value you previously specified.
0コメント