We are excited to announce that Java Management Service (JMS) now supports Java Runtime Lifecycle management operations. Users can now use the Install Java Runtime and Delete Java Runtime operations available in Java Management Service - Fleet Management, to manage the lifecycle of Oracle JDK runtimes in their enterprise. Using JMS, you can group compute instances (Desktops, Servers, or Cloud deployments) that require centralized management into fleets. Each fleet would contain compute instances that share common sets of rules and policies. Lifecycle management operations are first of the advanced features being introduced to JMS in addition to the existing basic features - the Java discovery and usage tracking capabilities available through Java Usage Tracker and file scanning.
Users can install Oracle Java runtimes across compute instances in a fleet using the new Install Java Runtime operation. As shown in the image below, users can install Oracle Java Runtime versions, including non-Long Term Support (LTS) versions that are EOSL (End Of Support Life), that were released in the last two years and are widely available to all Oracle customers in My Oracle Support.
The Oracle Java runtimes downloaded using the JMS advanced features are downloaded under your Java SE subscription terms when running on systems covered by an Oracle Java SE Subscription, Java SE Desktop Subscription. When running on an Oracle Cloud Infrastructure service that permits access to the underlying operation system, the Oracle Java runtimes are downloaded under the terms of your Oracle Cloud Infrastructure Cloud Service agreement.
Users can remove Oracle Java runtimes reported across compute instances in a fleet using the new Delete Java Runtime operation. As shown in the image below, users can choose Oracle Java Runtime versions and use the Delete button in the Java runtimes table to delete these runtimes.
You will be able to review the Java runtime usage - the installation paths within compute instances and applications invoking the runtime, to understand the impact of removing the Java runtime in the fleet before carrying out the Delete Java Runtime operation.
JMS has also simplified the installation of OCI agents by introducing Operating system specific installation scripts that allow you to setup OCI agent on your host and configure it for JMS usage by executing a single command. Previously separate steps for configuring OCI agent for JMS usage - installation of OCI agent, deploying of JMS service plug-ins, and configuration of Java Usage Tracker; can now be achieved by executing these new installation scripts in a single command.
Fleet Management in JMS allows Java users to group Java Virtual Machines running in Desktops, Servers, or Cloud deployments into fleets, obtain insights into their Java usage, and manage their Java workloads. Fleet Management provides reporting and management capabilities through Oracle Cloud Infrastructure platform services to monitor and observe Java usage (on-premises or in the cloud), as well as potentially identify issues that may be present in their usage. Fleet Management reduces the challenges of inventory, stability, performance, security baseline and compliance, tuning, troubleshooting, and cost optimization for stakeholders involved in the end-to-end life-cycle of Java applications, starting with design and development all the way to production and maintenance.
Sanju Nair is a Product Manager in the Java Platform Group at Oracle. He has worked in the IT industry for 10 years starting as a Java developer in Wipro Technologies and Oracle before moving into Product Management roles at NTT-Netmagic and Oracle. Sanju currently manages Java Management Service, JDK Mission Control and Java Advanced Management Console at Oracle.