AD4J Agent Deployment Automation Via EM Grid Control
(Doc ID 741896.1)
Last updated on FEBRUARY 13, 2024
Applies to:
Enterprise Manager Base Platform - Version 10.2.0.4 to 11.2.0.2 [Release 10.2 to 11.2]Information in this document applies to any platform.
Goal
AD4J Agent Deployment Automation via EM Grid Control
Note: AD4J has been renamed JVM (or Java) Diagnostics and is integrated with Grid Control for release 11. Where references are made to AD4J and AD4J agents, for version 11, these would be named JVM Diagnostics and JVM Diagnostics Agent for version 11.
AD4J agents need to be upgraded to latest AD4J release. The upgrade process requires undeploy and deploy of AD4J agents on monitored application servers manually.
Here you are providing steps to automate deploy/undeploy of AD4J agents on AS 10.1.3, 10.1.2 monitored instances. The orchestration provided is generic and can also be used to deploy AD4J agents on large scale through Enterprise Manager (EM) Grid Control irrespective of v3 upgrade process.
You must have Grid Control agents running on all hosts (where OC4J is running) where you need to deploy/undeploy AD4J agents.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| AD4J Agent Deployment Automation via EM Grid Control |
| Solution |
| References |