Advanced Management Console (AMC) 2.0 Release Notes

Advanced Management Console (AMC) is a commercial product available for Java users who license Java SE Advanced or Java SE Suite.

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

What's New

  • The following important new features are applicable to Advanced Management Console in this release:
    • Advanced Management Console server now uses WebLogic Server
    • Advanced Management Console uses MySQL database
    • Advanced Management Console user interface can use any HTML browser
    • Advanced Management Console agent is available for desktops that run Microsoft Windows
  • Advanced Management Console 2.0 gives enterprise administrators increased visibility into, and control over, how Java is used in their enterprise. This version provides the following enhanced functions:
    • Collection of information about Java applications that are run in the enterprise
    • Automated discovery of installed versions of Java
    • Web-based analytics for collected data
    • Management and distribution of deployment rule sets
    • Configuration of the MSI file for installing JREs
  • New and Updated Documentation:

Known Issues

  • Agent: AMC Agent does not function on certain localized Windows systems:

    This issue affects the following locales: Finnish, French, Hungarian, Portuguese (Brazil), Portuguese (Portugal), Russian, Spanish and Swedish.

    On such systems, the AMC Agent fails to properly initialize and will be reported as "Running" by the Windows Service Manager although it is in a zombie state.

    See JAMC-2183

  • Client UI: Java AMC DRSTool displays an error dialog after login screen with the message "Already Connected":

    The Deployment Rule Set Tool might display an error dialog after the login screen, with the message "Already Connected". This is usually due to the WebLogic Server using an HTTPS certificate that is not trusted by the client side JRE (for example, a self-signed certificate).

    Workaround: Add your self-signed certificate to the cacerts file of the Java distribution used by your browser.

    See JAMC-1903.

  • Web UI: Compatibility View in Internet Explorer:

    If you are using Internet Explorer as your browser, then make sure that 'Display Intranet Sites in Compatibility View' is not selected in Compatibility View Settings.

    See JAMC-1686.

  • Web UI: Cannot start DRSTool with Chrome:

    DRSTool and JICTool are not supported to be launched from Chrome browser. Use other supported browsers such as Internet Explorer, Firefox, or Safari.

    See JAMC-1839.

  • Web UI: Cannot load UI on Internet Explorer 9(IE9):

    AMC 2.0 has limited support for IE9 browser. If possible, use a different browser such as IE10, IE11, Firefox, Chrome. The following issues are may be encountered when using the WebUI with IE9:

    • In Desktops tab, when selecting some filters the page will be redirected to home tab
    • In Installers tab, the page will redirect to another page when clicking the 'Export to File' button
    • Uploading desktop groups file to the server does not work
    • IE compatibility view mode is not supported
    • Other cosmetic layout problems

    See JAMC-1811.

  • Client UI: JIC not able to customize a .msi file with Chinese characters in the file path:

    JICTool will fail to customize a .msi file if there are Chinese characters in the file path.

    Workaround: Use the file path without Chinese characters.

    See JAMC-1815.

  • Client UI: DRSTool file chooser issue on OS X 10.9 and later:

    Starting with OS X 10.9, Safari runs Java in a sandbox as part of it's security setup. This means that by default Java cannot access the local filesystem. The DRSTool needs access to the filesystem in order to perform some of it's functions. This permission can be enabled in the Safari security preferences panel.

    Workaround: Adjust the browser settings to allow DRSTool work correctly on Safari:

    • Go to Safari -> Preferences -> Security
    • Select the Checkbox to enable 'Internet plug-ins'.
    • Press the 'Website Setting' button.
    • In the Listbox on the left, select Java.
    • In the table on the right, select the correct AMC Server.
    • In the Choicebox on the right, select 'Unsafe mode' and 'Allow Always'.
    • Press the Done button.
    • Close the Preferences panel.
    • Exit Safari and restart it.

    See JAMC-852.

  • Web UI: Can not navigate to properties of desktop that is not on 1st page of Desktops tab:

    On the Desktops tab, when trying to see properties of a selected desktop listed on page #2 or further, properties of an unrelated desktop are shown. This issue will be fixed in a future release.

    See JAMC-1636.

  • Web UI (Java Usage): Application with space in directory path:

    If the directory path to a Java application contains a space, the corresponding JUT record could get truncated and only the path before "space" is displayed in the 'Java Advanced Management Console Java Usage' tab. This problem will be addressed in a future release.

    See JAMC-2019.

  • Server: Long JUT records may be truncated:

    The AMC server may not always be able to process all the Java Usage Tracking records sent by the desktops. This shows up in the AMC Console, under the Status tab, where a counter of Java Usage Rejected Records is provided. Java Usage Records can be rejected due to one of the following reasons:

    • Application access was denied (for instance, blocked by a DRS rule). In such a case, the AMC server simply discards the corresponding JUT record.
    • Application name was empty in the JUT record.
    • JUT record separators are not the default ones, and do not match those defined in the Configuration Settings from the AMC Console.
    • JUT record was truncated. This may be due to a Windows configuration on the desktop limiting the size of the JUT records sent to AMC server. On Windows, this limit can be increased with the 'DefaultSendWindow' registry key.
    • Application uses a local URL.

    See JAMC-2002.