Fleets
JMS allows you to create fleets within a compartment, deploy JMS plug-ins, manage your fleets, and monitor Java workloads. See JMS Fleets Quick Start Guide for steps to get started with fleet management.
- Basic features, which includes the Java discovery and usage tracking capabilities available through Java Usage Tracker and file scanning. Basic features allow you to:
- View the versions and vendor information of Java runtimes running in your systems
- Identify which Oracle Java versions are being used
- Identify how many Oracle Java installations are not up to date
- View the applications running on Oracle Java runtimes
- Identify which systems run Oracle Java runtimes
- Export your usage data to object storage locations in csv format
- Advanced features allow you to:
- Scan for Java Libraries used by your applications to identify and report potential vulnerabilities (CVE) associated with 3rd party Java libraries
- Optimize Java workload performance with JVM tuning recommendations leveraging Performance Analysis
- Evaluate the feasibility and effort required for migrating Java applications to newer JDK versions with Java Migration Analysis
- Help you keep your applications secure by identifying weak cryptographic usages that will stop working with upcoming updates in Oracle JRE and JDK Cryptographic Roadmap using Crypto Event Analysis
- Understand which services and applications are running on each Java application server by scanning for Java servers
- Run JDK Flight Recorder to remotely gather application insights
- Download, install, and configure Java Runtimes
- Remove reported Oracle Java versions
- Distribute Deployment Rule Set
Advanced features are to be enabled only on desktops, servers, or cloud deployments covered by an Oracle Java SE Universal Subscription, a legacy Oracle Java SE Subscription, a legacy Java SE Desktop Subscription, or when running on an Oracle Cloud Infrastructure service that permits access to the underlying operating system. Basic features are available to all Java users, whether or not they have an Oracle Java SE Universal Subscription or a legacy Oracle Java SE Subscription.
Java Management Service will track and report Java usage in your fleet by using:
- Java Usage Tracker: JMS relies on Java Usage Tracker to report Java usage. Using the Java Usage Tracker, you can monitor Oracle Java Runtime Environment usage and capture information such as the JRE version, vendor, applications running, and other details.
Note
- Java Usage Tracker detects application invocations and doesn't provide information about the duration for which an application was run. Consequently, JMS reports application invocation information in its resource records.
- Java Usage tracker properties file is truncated once the usage reports are successfully sent to JMS.
Java Usage Tracker is available for all releases of Oracle Java 7 and later versions, as well as the following older Java versions:
-
6u25 and later updates of Oracle Java 6
-
5.0u33 and later updates of Oracle Java 5
-
1.4.2_35 and later updates of Oracle Java 1.4
JMS generates the usage tracker in the central file system location during agent installation. If an older Oracle Java release earlier than 1.8.0_60, which doesn't support a central usage tracker, is detected, agents generate a local usage tracker properties file for the discovered older Java runtimes.
- Attach API: JMS uses Attach API during the execution of advanced features. OpenJDK usage may be reported by JMS during the execution of Scan for Java Libraries in the fleet.
Note
To exclude applications from being attached to, include the command line options:-XX:+DisableAttachMechanismand-XX:-UsePerfData. - File scanning: JMS periodically performs file scanning to detect Java runtimes that aren't captured by Java usage tracker or Attach API. File scanning will detect
- OpenJDK releases
- Oracle JDK releases that are unused and, consequently, not captured by the Java Usage Tracker
This chapter includes the following topics: