This chapter describes the procedure to set up and enable JVM Diagnostics as a Service. It covers the following:
JVM Diagnostics as a Service (JVMDaaS) enables IT organizations to provide JVM Diagnostics functionality in a self service manner and monitor JVMs within a Web based portal. The JVMs being monitored can either be monitored targets in Enterprise Manager or remote targets.
For example, a development organization may want to provide JVM Diagnostics functionality to its developers and QA personnel. The system administrator can provide this service through JVMDaaS. This helps reduce the organization cost by enabling developers and QA personnel to complete development tasks faster as JVM Diagnostics is easily accessible on any instance they are working on. Since the self service approach is used, there is no increase in the workload of the system administrator.
Oracle Enterprise Manager supports different classes of Oracle users, depending upon the environment you are managing and the context in which you are using Oracle Enterprise Manager. User privileges provide a basic level of security in Enterprise Manager. They are designed to control user access to data and to limit the kinds of SQL statements that users can execute. When creating a user, you grant privileges to enable the user to log in to Enterprise Manager, to view and monitor targets, view various reports, monitor JVMs, and so on.
A role is a collection of Enterprise Manager resource privileges, or target privileges, or both, which you can grant to administrators or to other users. Based on the role to a user or administrator, the user will be granted the appropriate privilege in the Enterprise Manager environment. These roles can be based upon geographic location (for example, a role for Canadian administrators to manage Canadian systems), line of business (for example, a role for administrators of the human resource systems or the sales systems), or any other model. By creating roles, an administrator needs only to assign the role that includes all the appropriate privileges to his team members instead of having to grant many individual privileges.
Before using JVMDaaS, the Super Administrator must create users for the following roles:
EM_SSA_ADMINISTRATOR
Users with this role can define quotas and constraints for the self service users and grant them access privileges. Users with this role also have provisioning and patching designer privileges that allow them to create and save deployment procedures, create and view patch plans, and support the plug-in lifecycle on the Management Agent. These privileges are required for initial setup and ongoing maintenance of the infrastructure.
EM_SSA_ADMINISTRATOR_BASE
Users with this role can set up the Self Service Portal. Users with this role can define quotas and constraints for self service users and grant them access privileges.
EM_SSA_USER
Users with this role can access the Cloud JVM Diagnostics Service and all service families and types available.
EM_SSA_USER_BASE
Users with this role can access the Self Service Portal without access to any service family and type available. This needs explicit grant of service family and type. This role is frequently used in production environments.
This section explains how to set up JVM Diagnostics as a Service. However, before you perform the setup tasks, you must ensure you have the necessary prerequisites. Users with the EM_SSA_ADMINISTRATOR and JVMDAAS role must have been created. See Creating Users and Roles.
To set up JVMDaaS, follow these steps:
Log in to Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
From the Enterprise menu, select Cloud, then select JVM Diagnostics Home.
Click the Quotas tab to allocate quota to one or more users with JDAAS role. See Defining and Allocating Quotas.
Click the Home tab to manage and monitor the JVM Diagnostics Agents. See Monitoring JVM Diagnostics Agents and Engines.
In JVMDaaS, quotas represent the maximum number of JVMs you can monitor using JVMDaaS. Users with the EM_SSA_ADMINISTRATOR role can define quotas for self service users.
The following prerequisites are required:
You must have created a user with the EM_SSA_ADMINISTRATOR role. This user must have the EM_SSA_ADMIN and JVM Diagnostics Administrator privileges.
You must have created one or more users with the JVMDAAS role.
To set up quotas, follow these steps:
Click the Quotas tab. This page shows the list of roles and the maximum number of JVMs allocated to each role.
Click Create. In the Create Quota window that appears, specify the following:
Role Name: Specify the EM_SSA_USER role to which the quota is to be allocated.
JVMs: Specify the maximum number of JVMs or the quota that will be available to the selected role.
JVMD Engine: Specify the URL of the engine where you want the JVMD agent to connect to.
Click OK to create the quota and return to the JVM Diagnostics Cloud Self Service Portal Setup page. The quota (JVM pool) with the specified number of JVMs is listed in the Quotas page.
You can edit or delete a quota by selecting the name of the role to which the quota has been assigned and clicking the Edit or Delete option as required.
Note:
If you modify a quota that contains active JVMs, the new quota will be applicable only to the new JVM connections. The existing JVMs will continue to use the old quota.As the JVMDaaS administrator, use the JVM Diagnostics page to check the status of the entire JVMDaaS environment. You can also use this page to perform administrative operations like adding, editing, and deleting quota.
Click on the Home tab to view the JVM Diagnostics Home page. It contains the following regions:
Overview: This region shows the total number of JVM Pools and JVMs for which quota has been allocated. It shows the number of active and deactivated JVMs.
JVM States: This region shows a chart with the various states of the JVM.
Activated JVMs: The region shows the number of the current active JVMs.
JVMs by Users: This region is a tree based structure where JVMs are grouped based on their owners. This section lists the JVM User statistics including: member status summary (up, down, unknown), JVMs, whether the JVM is activated, owner of the JVM, and creation date of the JVM.
JVMD Engines: This region lists the JVMD engines. Data includes the host on which the engine resides, port, SSL port, status, number of JVMs, and version of the engine.
Quota
Quota refers to the maximum number of JVMs a user (with a given Role) can monitor through JVMDaaS. If the user has been assigned more than one role, his quota will be the maximum quota from the roles assigned to him.
From this tab you can create quota by providing the number of JVMs and the JVMD engine. You can also edit and delete quota for a role.
Engine Usage
On this tab, you can view:
Engine Usage Graph: Graphical view of the various JVMD engines deployed along with the number of JVMs allocated to the engine through Quota.
JVMD Engines Usage: This region lists for each JVMD Engine and role, the quota, user count, and JVMs allocated to the engine.