What’s New in Java Management Service

Last June we announced a new cloud service running on Oracle Cloud Infrastructure (OCI) to help Java users manage, monitor and maintain their Java environments.  It enables the use of OCI to observe and manage Java in the enterprise – on OCI, on premises, or on other clouds.

Java Management Service (JMS) has come a long way since then.

Now deployed globally across all OCI regions, it available to any and all Java users for no additional charge on OCI, beyond the minimal cost of monitoring, logging and alarms. See the pricing information below for more on these minimal operations charges and options.

Several times each year, a new release of JMS is made available with new features and functionality. The latest release, 4.0, includes some interesting new capabilities, the most exciting of which are the ability to

Customers can:

• Use insights from JMS to optimize workloads across the enterprise (desktop, server, cloud)
• Protect your Java SE investments by identifying outdated Java installations, unauthorized applications, and Java runtime and application mismatches. For example, you expect your application to be using JDK 11, but via JMS you discover it is actually using JDK 8.

JMS helps systems administrators answer questions such as:

• Which vendors are providing the Java installations in my environment?
• Are my applications using their intended Java installations?
• Are unauthorized applications running?
• How many outdated Java installations do I have?

As the stewards of Java, Oracle can provide answers to these questions. Oracle is uniquely positioned to leverage its expertise to gain critical insights into Java application behavior, compliance, and performance.

How does it work?

Java Management Service relies on the Java Usage Tracker to report Java usage. The Java Usage Tracker tracks how Oracle Java Runtime Environments are being used in your systems and captures the JRE version, vendor, the application being run, and other details. Additionally, JMS also periodically performs a file scan to detect Java runtimes that are not captured by the Java Usage Tracker because they aren't being used, or they don't have the Java Usage Tracker capabilities.

For example, OpenJDK binaries will be detected by JMS through file scanning but won't be able to show you the usage associated with them, because OpenJDK binaries, in contrast to the more robust Oracle JDK, don't have Java Usage Tracker capabilities. Java Usage Tracker is available for all releases of Java 7* and later, and also for the following older Java releases:

• 6u25 and later updates
• 5.0u33 and later updates
• 1.4.2_35 and later updates

Pricing

For customers using Java SE Subscription for on-premises deployments and for anyone using Oracle Java SE on OCI (whether or not they are Java SE Subscribers), there is no additional fee for using JMS beyond the minimal cost of monitoring, logging and alarms as described above.

For those who use Java SE on other clouds, or who want to monitor JDKs from other vendors or open source providers, we recommend the purchase of a Java SE Subscription which allows for the full benefits of JMS and much more. This 1:12 minute video provides a snapshot of the benefits included with Java SE Subscription. 

Source: oracle.com