We’re sorry. We could not find a match for your search.

We suggest you try the following to help find what you’re looking for:

  • Check the spelling of your keyword search.
  • Use synonyms for the keyword you typed, for example, try "application" instead of "software."
  • Start a new search.
Cloud Account Sign in to Cloud
Oracle Account

Advanced Management Console 2.5 Release Notes

The Advanced Management Console is a commercial product available for Java users who have license for Java Standard Edition (SE) Advanced or Java SE Suite. The Advanced Management Console is available to customers from My Oracle Support (MOS).

For an overview of the Advanced Management Console, see the Advanced Management Console product page.

What's New

This release adds the following features to Advanced Management Console 2.5:
  • Java Usage Tracker (JUT) collection in Advanced Management Console agents
  • Java Runtime Environment (JRE) Management on Mac OSX
  • Simplified Application Names
  • Displaying more information about Java applications
    • Includes Hostname/IP address
    • Includes JRE paths

Updated  Documentation

Known Issues

  • JAMC-4536: By default, all plugins are disabled in Safari. When you navigate to a page with a Java applet, you need to explicitly enable Java Plugin on that page. However, even after you enable the Java Plugin, the applet doesn't have access to certain features, such as the file system. If you can't select a file in JICTool, or don't see your Java applications tracked on Mac OS X in the Java Usage tab, then it may be caused by the Safari sandbox restrictions.

    Workaround: To grant the applet all permissions, you need to enable Java Plugin to run in an Unsafe mode.

  • JAMC-4325: The Desktop and Properties icon are disabled in the Desktop sub tab of the Status tab.

    Workaround: To switch from the table to the properties view, double click on a non-empty table row. To switch back, just reload the page.

  • JAMC-3865: When the AMCAgent.exe-remove command is executed, the agent doesn't automatically un-register itself from the server.
  • JAMC-3656: All the currently registered agents refuse to connect to the server if the server's SSL certificate changes.

    Workaround: Install a new version of the Advanced Management Console, which could result in a new KeyPair and shortens the time the generated KeyPair that is in use.

  • JAMC-3119: The Deploy API doesn't provide any API to get updated information if a particular JRE has been enabled or disabled in the Java Control Panel (JCP), or if run-time parameters were added or removed.

    Workaround: Restart the Advanced Management Console agent.

  • JAMC-2677: On startup, the Java Web Start (JWS) downloads all the application resources, for example jar files, and checks the signatures and certificates. If all the JICTool jars are signed, then their certificates should be validated. To perform validation, the JWS should have access to the Internet. If the proxy server is not correctly configured, then the time taken to connect to signer's servers is very long (and the connection fails in the end). It may slow down JICTool startup process significantly.

    Workaround: If a desktop where the Advanced Management Console UI and JICTool run doesn't have direct Internet connection, then ensure that the proxy settings in the JCP are correct.

  • JAMC-2031: The Advanced Management Console cannot use XA-enabled DataSource for Oracle Database.

    When a Data Source object is configured in the WebLogic Server, by default, an XA-enabled Oracle Database driver is used. The Advanced Management Console can't work with this type of driver and generates an error similar to the following:

    SEVERE: ORA-02089: COMMIT is not allowed in a subordinate session

    Workaround: When you configure the Data Source object in the WebLogic Server, make sure that you set the Database Driver to a driver that is not XA-enabled.

  • When you install a JRE, the JRE entry may not get updated in the Web Enabled JREs table. Similarly, the entry may not get removed from the table when the JRE is uninstalled.

    Workaround: Restart the Advanced Management Console Agent.

  • In the JCP, if JREs are manually added, deleted, or modified, then these changes may not get reflected in the Advanced Management Console.
  • JAMC-3570: In the Java Usage tab, when you set the Display type to Application, the Application column in the Application table shows the original application locations, and not application names. Therefore, after you have updated or changed the name for an application, you may not be able to view the new name of the application in the Application table.

    Workaround: To view the name of an application, select the application. Click Update Name to display the Update Application Name dialog box, which shows the application name.