This is a commercial product licensed as part of Java SE Advanced, SE Advanced Suite and Java SE Subscriptions. 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.
This release of the Advanced Management Console is primarily a bug fix release. See the What's New In Advanced Management Console page for descriptions of the additions to the Advanced Management Console features in all releases, so far.
AMC requires that you keep your instance of WebLogic Server up-to-date with security patches. We also recommend that you subscribe to receive notifications of Oracle’s Critical Patch Update Advisories and Security Alerts. Refer to https://www.oracle.com/technetwork/topics/security/securityemail-090378.html for instructions.
Java Plug-in support has been removed from Chrome, Firefox, and Safari in Windows and macOS platforms.
For additional information, see:
Java Web Start has been removed from Java SE 11 and later.
For additional information, see: Java Client Roadmap Update
Oracle WebLogic Server 12.1.x Extended Support ends in Dec 2019 . Accordingly, AMC updates released after Dec 2019 will require Oracle WebLogic Server 12.2.x. AMC users running on WebLogic Server 12.1.x should upgrade to 12.2.x as soon as possible.
The following table contains a list of known issues in the Advanced Management Console 2.14 release.
|1||JAMC-4933||Web Enabled JREs may not been reported correctly for initial scan when jre version is the same as AMC agent bundled|
|2||JAMC-6107||agent failed to uninstall jre9 on windows|
The following table contains a list of issues that were addressed in the Advanced Management Console 2.14 release.
|1||JAMC-7977||AMC RFE: Customization of AMC user password length|
|2||JAMC-8022||Associate Java Usage with agent id|
|3||JAMC-8037||App properties: Display "unknown" if jar file cannot be downloaded|
|4||JAMC-8072||Update error message when updating Exclude Paths|
|5||JAMC-8094||Agent cannot connect to the server: sun.security.validator.ValidatorException: Extended key usage does not permit use for TLS client authentication|
|6||JAMC-8102||Desktops tab shows JRE 11.0.1 below security baseline even though secure version for 11 is 0.1|
|7||JAMC-8106||Implement database approach to fix Sorting issue of "JRE Version"|
|8||JAMC-8118||Refactor the AgentReportsHandler code for Java version comparison|
|9||JAMC-8124||Owner name is exported as "null null" if no owner specified|
|10||JAMC-8125||Exported HTML file must specify its encoding|
|11||JAMC-8160||Jep223JavaVersion must ensure first component ≥ 9|
|12||JAMC-8167||Release string missing while saving JUT records in database|
|13||JAMC-8170||Refactor Java version parsing|
|14||JAMC-8174||JRE Security Baseline filterring code should be fixed based on new table columns added post JAMC-8106|
|15||JAMC-8175||Java version string "11.8.0_201" is accepted|
|16||JAMC-8178||Typos in AMC messages|
|17||JAMC-8179||Change "OS X" to "macOS"|
|18||JAMC-8180||Remove unused sanity messages in UI|
|19||JAMC-8192||JUT Record FirstUsage and LastUsage data is incorrect|
|20||JAMC-8195||Uncaught reference error in initilaization-page.js|
|21||JAMC-8199||Locale specific strings for messages added\updated|
|22||JAMC-8200||LegacyJavaVersion can't parse "1.4.0-beta"|
|23||JAMC-8205||Java Usage - Properties view is empty for all applications|
|24||JAMC-8214||JRE Security Baseline code interim, patch and update filter mismatch|
|25||JAMC-8216||Desktop tab -> JRE full version, JRE major version - Unable to sort based on hostcount|
|26||JAMC-8217||Populate newly added columns for Java Version while migrating agentjres data from pre AMC 2.4|
|27||JAMC-8242||[AMC 2.14] Agent fails to Uninstall JREs listed as 0, 1, 2|
|28||JAMC-8363||Create and update Third Party Readme for AMC 2.14|