Getting Started with Java Management Service
This chapter includes the following topics:
About Java Management Service
Java Management Service (JMS) is a reporting and management infrastructure integrated with Oracle Cloud Infrastructure Platform services to observe and manage your use of Java SE (on-premise or in the Cloud).
- Use insights from JMS to optimize your workloads across your enterprise (desktop, server, cloud); and
- Protect your Java SE investments by identifying outdated Java installations, unauthorized applications, and Java runtime and application mismatches. For example, your application is using JDK 11, but you learn it's using JDK 8.
- 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?
JMS is a region specific service and regions are independent. See Regions and Domain Availability.
System Requirements
Operating System | Version - all 64 bit |
---|---|
Windows | 2019, 2016, 2012 R2, 10
Note
The OCA plugin isn’t available for Windows at this time. |
Oracle Linux | 6, 7, 8 |
Red Hat Enterprise Linux | 6, 7, 8 |
CentOS | 6, 7 |
SUSE Linux Enterprise Server | 12, 15 |
Ubuntu | 20.04.3 LTS |
-
6u25 and later updates
-
5.0u33 and later updates
-
1.4.2_35 and later updates
To install a management agent on a host, you must meet the prerequisites described in Install Management Agents. In particular, your host must meet the Generic Prerequisites for Deploying Management Agents, including the requirement for JDK 8 (update 281, JDK 1.8.0_281, or higher). The management agent is not compatible with any other versions of the JDK. For more information, see Configuring a Management Agent for Java Management Service.
To update the Java Runtime used by the Management Agents, you should follow the instructions in the Using Java with Management Agent section to ensure the Management Agents continue working.
Key Concepts and Terminology
The following concepts and terminology will help you get started with Java Management Service. The Oracle Cloud Infrastructure documentation provides related terminology.
Application
An application refers to a Java program.
The name of an application is derived from the fully-qualified name of its main class. An application can run on multiple Java Runtimes.
Compartment
A compartment enables you to organize and control access to your cloud resources, such as a Fleet or a Management Agent. A compartment should be thought of as a logical group and not as a physical container.
For more details, see OCI Key Concepts and Terminology.
Compute Instance
A Compute Instance is a host that is provisioned and managed by Oracle Cloud Infrastructure. For more information, see Overview of the Compute Service.
Fleet
A fleet is the primary collection with which you interact when using JMS. It contains Managed Instances that share rules and policies.
Installation
An installation refers to an installation of a Java Runtime on one or more hosts.
- File system path, such as
/usr/lib/jvm/jdk13.0.1/
- Vendor, such as Oracle Corporation
- Operating System version, such as Linux 5.4.17-2011.7.4.el7uek.x86_64
- Architecture, such as x64
Java Runtime
A Java Runtime Environment (JRE, or Java Runtime) is a Java Virtual Machine (JVM), Java platform core classes, and supporting Java platform libraries. It's released as a certain version of a distribution or included with a vendor's product release. A Java Runtime can be installed to run a single Application or to be used by many applications.
- Vendor, such as Oracle Corporation
- Name of distribution to which it belongs, such as OpenJDK Runtime Environment
- Version, such as 1.8.0_282
When displayed by JMS, a Java Runtime from Oracle indicates if it requires an update.
Log Configuration
JMS uses the OCI Logging service to store inventory and operation logs. Inventory logs are Custom Logs that store the Java Runtime inventory and usage related information reported from the hosts by the Management Agent. Operation logs are Custom Logs for storing the logs related to operations carried out through JMS. Each fleet has its own unique inventory and operation log. Logs are placed under a Log Group. By relying on logs and JMS reports, you can do additional analytics using Logging Analytics.
Managed Instance
A Management Agent that has been installed on a host is known as a Managed Instance. A host can be any computer running in your enterprise. In most cases, the host is a computer on your premises, but it can be on OCI or on any other cloud platform. A managed instance has a unique identity that's used by JMS to distinguish it from other managed instances.
A managed instance must be contained by only one Fleet.
Management Agent
A Management Agent is installed on a host. A management agent can be installed directly on a host (for example, a host on your premises or on a third-party cloud platform) or indirectly as a plug-in for an oracle cloud agent (in the case of a Compute Instance). A management agent's plug-ins monitor and collect data from its host, which they then report to the Management Agent Cloud Service.
- The presence of a Java Runtime installation
- The start of a Java application
- The start of a Java Runtime
- Data provided by Java Usage Tracker
A management agent may have one or more Tags.
See also, Managed Instance.
The management agent cloud service is an OCI service that manages management agents and their life cycle. For more details, see Management Agent Concepts.
Oracle Cloud Agent
An Oracle Cloud Agent is a lightweight process that manages plug-ins running on a compute instance. Its plug-ins collect performance metrics, install OS updates, and perform other instance management tasks. An example plug-in is a Management Agent.
For more information, see Managing Plugins with Oracle Cloud Agent.
Tag
A tag is a key-value pair that you use to add metadata to your OCI resources.
JMS uses a tag in the namespace jms with the key fleet_ocid to identify the contents of a fleet. The managed instances contained in a fleet are identified by the tag value corresponding to the OCID of the fleet. (For more information, see Creating a Fleet.)
For a more detailed description of tags, see Tagging Overview.
Tenancy
When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for you or your enterprise. This is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.
Work Request
- If an operation fails, a Work Request can help you determine which step of the process had an error.
- Some operations affect multiple resources. For example, a delete Java Runtime operation could affect multiple Java Runtimes, Java Runtime installation paths and Managed Instances. A work request provides a list of the resources that an operation affects.
Checking Required OCI Resources
To enable you to swiftly get going with JMS, the Onboarding Wizard creates and checks required policies, tags, and other configurations, while the Log Configuration Wizard covers missing log configurations. This section describes how to use the Onboarding Wizard and Log Configuration Wizard.
The Onboarding Wizard creates the OCI resources similar to those described in Setting Up Oracle Cloud Infrastructure for Java Management Service.
- You've signed up for an account with Oracle Cloud Infrastructure and have received your sign-in credentials.
- You've logged in to the Oracle Cloud Infrastructure Console and selected Java Management from the navigation menu.
Using the Onboarding Wizard
- Click Inspect Prerequisites.
- Click Allow to automate the creation of prerequisite OCI resources, such as permissions and polices.
You'll be presented with an error message if JMS isn't successful and JMS will roll back any changes.
- Optional steps:
- Click Details to view the OCI resources that JMS will create on your behalf.
- Expand Policy Details to view a detailed description of the OCI resources that JMS will attempt to create on your behalf.
- Click Set up JMS to automate the creation of the OCI resources described.
You'll be presented with a list of errors and their causes if JMS doesn't successfully create the policies on your behalf. JMS will roll back any changes.
Using the Log Configuration Wizard
- The Log Configuration wizard is presented by JMS if at least one fleet in a compartment has missing log configurations. Click Enable log configuration to automate log configuration for all fleets with missing log configurations.
You'll be presented with an error message if JMS isn't successful and JMS will roll back any changes.
- Optional steps:
- Click View Details to view the fleets that have missing log configuration.
- Use the checkbox to define the scope of the operation.
- Click Enable log configuration to automate the creation of log configuration for all selected fleets. You'll be presented with a list of errors and their causes if JMS isn't successful. JMS will roll back any changes.
Setting Up Oracle Cloud Infrastructure for Java Management Service
Before you can use Java Management Service, you must ensure that your Oracle Cloud Infrastructure environment is set up correctly to allow the communication flow between all required components and cloud services.
This section describes the manual steps to set up Oracle Cloud Infrastructure for Java Management Service. You can skip this section if you've used the Onboarding Wizard. (The Onboarding Wizard automates these steps. For more information, see Checking Required OCI Resources.)
Review the prerequisites and the overview of the steps.
- You've signed up for an account with Oracle Cloud Infrastructure and have received your sign-in credentials.
- You've read Set Up Oracle Cloud Infrastructure for Management Agents.
Overview
- Sign in to Oracle Cloud Infrastructure.
- Create a compartment for your JMS resources.
- Create a new tag namespace.
- Create a new tag key.
- Create a user group for your JMS users.
- Create one or more user accounts for your JMS users.
- Create policies for your user group to access and manage JMS fleets, management agents, and management agent install keys, metrics, and tag namespaces.
- Create a dynamic group of all management agents.
- Create policies that enable the management agents to interact with JMS, allow JMS to store monitoring data in your tenancy, and use tag namespaces..
- Create policies for log configuration.
- (Optional) Create policies to perform Java Runtime Lifecycle Management operations.
Steps
Getting Help
Follow the guidance below if you encounter an error or issue with Oracle Cloud Infrastructure or need help with Java Management Service.
Review the Troubleshooting chapter.
Review Getting Help and Contacting Support in the OCI documentation.
If you're unable to resolve your issue, open a support service request using the Help menu () in the OCI console.