Chapter 7

There's more...
This recipe demonstrates in detail the steps to be followed in order to deploy ADP Manager
on the same host as OMS with a newly-created managed server. It is possible to deploy
ADP Manager on an already-created managed server on a domain by selecting Deploy on
an existing managed server under the Deploy ADP Engine section of the Application
Performance Management screen.

It is also possible to deploy ADP Manager on a separate host from OMS. This is referred to as
Remote Deployment.

Setting up JVM Diagnostics (JVMD) Manager

in Cloud Control
JVM Diagnostics (JVMD) is one of the most important functionalities in OEM 12c, and enables
the Middleware Administrators to diagnose performance issues in Java applications.

JVMD leads to effective management of applications and simplified identification of the

root cause of performance problems without having to reproduce the issues in a test or
development environment.

JVMD Manager is a key analytical engine of the JVMD monitoring system.

This recipe describes the installation of JVMD Manager on the same host as OMS having
Cloud Control Version 12.1.0.2.

Getting ready
The following prerequisites are required for finalizing Weblogic Domain for the JVMD Manager
installation:

ff Weblogic Server must be up and running to deploy the JVMD Manager application
ff JVMD Manager can only be deployed on those managed servers which are a part of
OEM 12c Weblogic Domain

Log in to the Cloud Control console URL to deploy JVMD Manager.

How to do it...
To deploy JVMD Manager on the same host as OMS, perform the following steps:

1. Log in to Enterprise Manager Cloud Control.

2. Select Application Performance Management from the Setup menu.

269

www.it-ebooks.info
Middleware Management using OEM 12c

3. Select JVM Diagnostics Engine from the + Add menu on the Application
Performance Management page.

4. On the Deploy JVM Diagnostics Engine page, select Create a managed server, and
enter the following details:
‰‰ Select an OMS Server from the Host list of all the servers discovered in the
EM Weblogic Domain.
‰‰ Enter the Managed Server Name, which should be unique.
‰‰ The managed server name EMGC_JVMDMANAGER1 is set in this example as
the default value. The default ports are kept unchanged for this example. It
is possible to change the different ports if required.

270

www.it-ebooks.info
 Chapter 7

Based on the OMS host selected, specify the Oracle Management Server Host
Credentials and Oracle WebLogic Domain Credentials section of the Application
Performance Management page.
Oracle Management Server Host Credentials are the credentials for the host
machine where the selected OMS server is running. The Named credential is selected
in this example, which is available on the domain for the OMS host credential.
Oracle WebLogic Domain Credentials are the credentials of Weblogic Domain in
Enterprise Manager Cloud Control. The Named credential, is selected in this example,
which is available for OMS Cloud Control Weblogic Domain.

271

www.it-ebooks.info
Middleware Management using OEM 12c

5. Click on Deploy after populating all of the sections on the Application Performance
Management screen.

6. Click on the JVMD job execution status link to view the status of the job execution of
the job status for setting up JVMD Manager.

To verify whether JVMD Manager has been accurately set up on the managed server of Cloud
Control Weblogic Domain, perform the following steps:

1. In Cloud Control, select Application Performance Management from the

Setup menu.

On the Application Performance Management page, all of the deployed Managed

servers are listed. Fields such as Host, Port, and so on, on the Application
Performance Management page helps monitor the status of JVMD Manager.

272

www.it-ebooks.info
 Chapter 7

How it works...
This recipe describes the steps to be followed to set up JVMD Manager on the host of OMS.

JVMD Diagnostics is integrated with Oracle Enterprise Manager Cloud Control. It enables the
Middleware Administrators to diagnose performance-related issues in the Java applications in
the production and test environments.

The Application Performance Management GUI tool as part of Enterprise Manager Cloud
Control, is used to install JVMD Manager in Cloud Control Weblogic Domain.

During the process of JVMD Manager deployment, a managed server is deployed in the OEM
12c Weblogic Domain, and the JVMD Manager application is deployed on the managed
server. It is advisable not to deploy any other application on this managed server.

There's more...
This recipe demonstrates in detail the steps to be followed to deploy JVMD Manager on
the same host as OMS with a newly-created managed server. It is also possible to deploy
JVMD Manager on an already-created managed server on a domain by selecting Deploy
on an existing managed server under the Deploy JVM Diagnostics Engine section of the
Application Performance Management screen.

ff It is also possible to deploy JVMD Manager on a separate host from OMS, which
is referred to as Remote Deployment. There is an option available to deploy JVMD
Manager manually by downloading jvmd.zip from Middleware HOME>/
plugins/oracle.sysman.emas.oms.plugin_12.1.0.0.0/archives/jvmd,
followed by running the DeployAD4JManager.sh script in Linux.

273

www.it-ebooks.info
Middleware Management using OEM 12c

Discovering and managing Weblogic

Server Target
IT organizations are increasingly adopting Java EE, SOA, composite application, and Cloud
computing, which enable them to quickly connect their disparate applications and fulfill
ever-changing business needs.

Oracle Weblogic Server is the most commonly-used application server for deploying
enterprise-wide applications. It is very critical to manage and monitor multiple Weblogic
Domains running Weblogic Server instances centrally through Enterprise Manager Cloud
Control, rather than connecting to the individual Weblogic Domain console for managing
and monitoring.

The following recipe describes the steps to be followed to discover Weblogic Domain to Cloud
Control, followed by managing and monitoring Weblogic Servers from Cloud Control.

Getting ready
Weblogic Domain is already created on a target server. The assumption is that the target
server is already being monitored by Oracle Management Agent.

Log in to the Cloud Control console URL to discover Weblogic Domain, which is not yet
configured in Cloud Control to monitor.

How to do it...
To discover Weblogic Domain, perform the following steps:

1. Log in to Enterprise Manager Cloud Control.

2. Select Middleware from the Targets menu.
3. Select Oracle Fusion Middleware/Weblogic Domain from the +Add menu.

274

www.it-ebooks.info
 Chapter 7

4. Specify the Administration Server Host by selecting the appropriate target host,
Admin server Port, and the Weblogic Domain credentials such as the username
and password.

5. Click on Continue.

275

www.it-ebooks.info
Middleware Management using OEM 12c

6. Click on Close.

7. Click on Add Targets after reviewing the Add Fusion Middleware Farm: Assign
Agents screen page.

8. Click on Close.
The Managed servers, Admin server, and deployed application on the managed
servers have now been discovered by Cloud Control and can be managed and
monitored for the demo_domain domain for demonstration.

276

www.it-ebooks.info
 Chapter 7

9. Click on OK.

To manage and monitor Weblogic Domain, perform the following steps:

1. Log in to Enterprise Manager Cloud Control.

2. Select Middleware from the Targets menu.
You can identify all of the discovered Weblogic Domains managed by Cloud Control
on the Middleware screen. Expand the Weblogic Domain of interest to verify whether
all instances are up or not via a single point of view.
demo_domain is integrated as part of the demonstration of this recipe. Expand the
domain and verify if all the Weblogic instances of the domain are up or down.

The Admin server and two managed servers created as part of Weblogic Domain
demo_domain are up in this example.

3. Click on an individual domain of interest from the list of discovered Weblogic

Domains to get more details of the domain for managing and monitoring. demo_
domain is selected for demonstrating the example.
Active sessions, heap usage, CPU, number of requests, request processing times, and
so on can be monitored as per all the Weblogic Server instances, apart from checking
the status of application deployment in this screen.

277

www.it-ebooks.info
Middleware Management using OEM 12c

4. Click on the WebLogic Server Administration Console link to access the Weblogic
console directly to configure and manage Weblogic Domain.

5. Click on the appropriate options from the drop-down list under the Weblogic Domain
tab, which is available at the corner of the right-hand pane, in order to manage and
monitor Weblogic Domain from Cloud Control.

278

www.it-ebooks.info
 Chapter 7

6. Click on each Weblogic Server instance in the left-hand side pane to get more
monitoring details of the server instances, as per your requirements. In this example,
Managedserver_1 is selected in the left-hand side pane and the right-hand side
pane is populated with detailed information for the managed server, including the
applications deployed on the same server, which helps in providing a one-page view
of the Weblogic Server instance for monitoring and managing the instance.

How it works...
This recipe describes the steps to be followed in order to discover Weblogic Domain with Cloud
Control.

A Cloud Control agent uploads Weblogic instance monitoring stats to OMS, which
then provides a summarized view of the Weblogic Server instances in Cloud Control for
managing and monitoring.

There's more...
The Enterprise Cloud Control console also provides a direct link to access the Weblogic Server
domain console to perform the managing and monitoring of the Weblogic Server instances.

Deploying ADP agents on Weblogic

Target nodes
ADP Java Agent is used to collect data on the ADP Application Service Management (ASM)
system. It gets deployed to all of the managed application servers to perform a number
of tasks, including tracking, summarizing of data in real time, and identifying contextual
relationships, with minimal overhead.
279

www.it-ebooks.info
Middleware Management using OEM 12c

This recipe describes the steps to be followed to install an ADP agent on the managed node of
Weblogic Server.

Getting ready
Weblogic Domain is already created on a target server. The assumption is that the target
server is already being monitored by Oracle Management Agent.

The following prerequisites need to be checked before deploying an ADP agent:

ff Weblogic Server hosting ADP Manager should be up and running

ff Make sure that, in order to deploy an ADP agent, at least one ADP Manager is up and
running in the active state

How to do it...
To deploy an ADP agent to a Weblogic Server, perform the following steps:

1. Log in to Enterprise Manager Cloud Control.

2. Select Middleware from the Targets menu.
3. Click on the WebLogic Domain target of interest on the Middleware page.
demo_domain is selected for demonstrating this recipe.
4. Select Diagnostics from the WebLogic Domain menu.

280

www.it-ebooks.info
 Chapter 7

5. Click on the Setup Diagnostics Agents option to deploy agents.

ManagedServer_1 and ManagedServer_2 are selected in this example to deploy
an ADP agent.

6. Select the desired ADP Manager from the ADP Manager list under ADP Configuration
Properties.
The Update Remote Start configuration option is checked in this example for both of
the managed servers selected for the ADP agent installation.

7. In the Credentials section, provide the Oracle WebLogic Administration Server Host
Credentials and then scroll down.

281

www.it-ebooks.info
Middleware Management using OEM 12c

8. Provide Oracle WebLogic Domain Credentials and then scroll down in the
Credentials section.

9. Enter Oracle Enterprise Manager WebLogic Administration Server Host

Credentials, and the Oracle Enterprise Manager WebLogic Domain Credentials.

282

www.it-ebooks.info
 Chapter 7

10. Scroll up and click on Deploy to submit the job.

11. The status page appears with a link to the job status in the ADP Agent Deployment
<date> format. Click on the link to check the status of the job
that you have submitted.

283

www.it-ebooks.info
Middleware Management using OEM 12c

To verify the ADP agent installation, perform the following steps:

1. Select Middleware from the Targets menu.

2. Click on the Application Dependency and Performance option from the
Middleware features.
3. Expand the folder corresponding to the ADP Manager associated with the
deployed agents on the Monitoring tab.
4. In the navigation tree select the Status node, and click on the node without
expanding it. For the servers that you deployed, please verify the Agent
Information table.

How it works...
This recipe describes the steps to be followed to deploy an ADP agent on the Weblogic nodes.

Deploy ADP Manager to a managed server in the Cloud Control domain as demonstrated
earlier in this chapter. Then deploy the ADP agents on the production Weblogic Servers
wherever you need deeper visibility into the SOA, OSB, Portal, and ADF applications.

By default, Administration Server appears deselected during the selection of the managed
server to deploy an ADP agent. However, an ADP agent gets deployed to the Administration
Server in addition to the selected managed servers.

284

www.it-ebooks.info
 Chapter 7

There's more...
This recipe demonstrates in detail the steps to be followed to deploy an ADP agent on the
managed servers of Weblogic Domain hosted on a server other than OMS.

It is also possible to deploy the ADP agents on a Weblogic Domain that is being monitored by
Management Agent in Enterprise Manager Weblogic Domain. These are referred to as ADP
agents (Remote Deployment).

Deploying JVMD Agents on Weblogic

Target nodes
JVMD Agents act as data collectors of the target JVM. JVMD Agents collect JVM monitoring
data related to the JVM CPU usage, heap, threads, and stacks in real time, with minimal
impact on the source system.

The following recipe describes the steps to be followed to install a JVMD Agent on a managed
node of Weblogic Server.

Getting ready
A Weblogic domain is already created on a target server. The assumption is that the target
server is already being monitored by Oracle Management Agent.

The following prerequisites need to be checked before deploying JVMD Agents:

ff The Weblogic Server hosting the JVMD Agent should be up and running
ff At least one JVMD Manager should be in the active state to deploy JVMD Agent

How to do it...
The following sequences help to deploy JVMD Agent on a managed server hosted on a
different physical server to that of the OMS host:

ff Downloading the jamagent.war file

ff Deploying JVMD Agent

285

www.it-ebooks.info
Middleware Management using OEM 12c

To download the jamagent.war file using Cloud Control, perform the following steps:

1. Log in to Enterprise Manager Cloud Control.

2. Select the Application Performance Management option from the Setup menu.
3. Select the JVM Diagnostics Engine (1) option on the Application Performance
Management Engines page.

4. Click on Configure.
5. Click on the JVMs and Pools tab on the JVM Diagnostics Setup page.

6. Click on the Downloads button on the JVM Diagnostic Setup page.

7. Select JVMD Agent as JVMD Component.

286

www.it-ebooks.info
 Chapter 7

8. Click on OK.
9. Select one of the ports from the listed JVMD engines.
‰‰ For connecting to JVMD Manager, select the non-SSL port (3800)
‰‰ For securely connecting to JVMD Manager, select the SSL port (3801)

Note that if you do not want to select an existing manager, then

you can select Other from the Available Engines menu and
then specify the port and hostname for the agent to connect to.
This is especially useful when multiple JVMD Managers are load
balanced.

10. Click on Download.

The downloaded jamagent.war file can be used to deploy JVMD Agent either from the
Weblogic Administration console or via a non-Weblogic Server.

287

www.it-ebooks.info
Middleware Management using OEM 12c

To deploy jamagent.war on a Weblogic Server instance, perform the following steps:

1. Log in to the Weblogic console where you want to deploy JVMD Agent.
2. Deploy the jamagent.war file to the Admin server and all managed nodes of the
domain that are designated for the JVMD Agent installation.
3. Activate the application.

To verify the JVMD Agent installation, perform the following steps:

1. Select Middleware from the Targets menu.

2. On the Middleware page, select the domain where JVMD Agent was deployed.

You will notice that a Java Virtual Machine named <domain name>_jvmpool
appears. In this example, demo_domain_jvmpool is created as the Java Virtual
Machine pool. This consists of three JVMD Agents hosted on AdminServer,
Managed_Server1, and Managed_Server 2. The status of the Java Virtual Machine
is up, which suggests that JVMD Agents are up and running on these Weblogic
instances.

288

www.it-ebooks.info
 Chapter 7

How it works...
This recipe describes the steps to be followed to deploy JVMD Agent on a Weblogic node being
monitored by Oracle Management Agent other than Cloud Control Agent.

JVMD Manager runs as an Enterprise JavaBeans (EJB) technology on a Weblogic Server. JVMD
Agent is deployed to the managed application servers in order to collect the JVM monitoring
data related to the JVM threads, sacks, heap, and CPU usage in real time. The connection
between JVMD Manager and JVMD can be a secure or non-secure connection.

Note that JVMD Agent cannot be deployed on the Weblogic

managed node server on which the ADP Manager application
is running. It can be deployed on the OMS server, Admin
server, or JVMD managed server in the Enterprise Manager
domain or any other Weblogic domain.

There's more...
This recipe demonstrates the steps for downloading the jamagent.war file from the Enterprise
Manager Cloud Control console, followed by deploying the JVMD Agent application war file on
the Weblogic nodes being monitored by Oracle Management Agent on a different host.

The other option available for deploying JVMD Agent is using Enterprise Manager Cloud
Control. In this case, JVMD Agent is deployed on a Weblogic domain that is being monitored by
Management Agent in the Enterprise Manager Weblogic domain.

289

www.it-ebooks.info