1 Introduction

Advanced Management Console (AMC) and Java Management Service (JMS) empower system administrators with secure, remote access to manage Java-based services and applications, and allow for centralized control of the Java environment. These tools can monitor Oracle Java runtimes like Java Development Kit (JDK), Java Runtime Environment (JRE), and GraalVM.

AMC, developed for on-premise deployments, provides effective Java application management for system administrators. However, AMC requires dedicated hardware and expertise for maintenance of the database and WebLogic server, making it suitable for enterprises with dedicated IT departments. JMS is integrated with Oracle Cloud Infrastructure (OCI), and can track Java usage across diverse environments; spanning OCI instances, on-premise desktops, laptops, servers, and third-party cloud services. JMS, therefore, allows for more rapid evolution and frees system administrators from the complexities of having to manage dedicated infrastructure. This makes JMS the preferred solution for enterprises to manage Java workloads within distributed environments.

This guide provides the information for AMC customers looking to upgrade to the more modern JMS. It not only covers the similarities between these tools but also highlights the additional capabilities that JMS offers to system administrators. The guide will equip you with insights for setting up and using JMS seamlessly, enabling you access to features designed for modern, distributed environments.

Note:

With the advancement of Java Management Service (JMS), and its enhanced capabilities and simplified model, Oracle is announcing users of the Advanced Management Console (AMC) feature should migrate to JMS by the end of 2024. Read more in our blog post at The Future of Java Management: Migrating from Advanced Management Console to Java Management Service.