7 Advanced Management Console Agent Installation and Configuration
The Advanced Management Console agent runs as a native service with the operating systems (Windows as well as macOS) on a client desktop. The agent finds all the installed Java Runtime Environments (JREs), and then enables and automatically configures Java Usage Tracker. In an enterprise network, the agent enables the Java Usage Tracker on agent-managed desktops. At system startup, the agent reports the data on the Advanced Management Console client. The agent periodically reports data (operating system family, version, and installed JREs) to the Advanced Management Console server. The agent downloads and applies the Deployment Rule Set to the installed JREs. It automatically enables the Java Usage Tracker on installed JREs on Windows as well as macOS operating systems.
This topic contains the following sections that describe the Advanced Management Console agent, agent bundle, agent installation, and agent distribution:
About Advanced Management Console Agent
The Advanced Management Console agent is a background service.
The Advanced Management Console agent performs the following tasks:
-
Identifies all the installed JREs on the desktop and reports the resulting list to the Advanced Management Console server.
-
Enables Java Usage Tracker for each JRE in which Java Usage Tracker is available.
-
Downloads deployment rule sets from the Advanced Management Console server and installs them on each JRE.
Advanced Management Console supports Windows,
macOS, and Linux distributions (with systemd
or
upstart
service management framework). See Software Prerequisites and System Requirements for Advanced Management Console
Components for details. For platforms that are not supported, the Java Usage
Tracker can be configured manually.
The Advanced Management Console server and all its components use different protocols to communicate.
Advanced Management Console Agent Bundle
The Advanced Management Console agent is
bundled as a .zip
file.
The bundle file is configured with Application server URL and Application server certificate chain details. You can download the agent bundle from the Advanced Management Console server through the Advanced Management Console User Interface (UI). The bundle installs the agent on the desktop that must be managed by the Advanced Management Console server.
The Advanced Management Console agent bundle is configured to the Advanced Management Console server that it has been downloaded from.
Note:
If multiple agents from different servers are installed on the same machine, then the earlier configurations will be overwritten by the latest agent installation. The system is configured to communicate with the server from which the latest agent bundle was downloaded.Installing Advanced Management Console Agent
The Advanced Management Console agent installation requires administrator privileges and should be performed by a system administrator.
This topic contains the following sections:
Configuring the Agent Proxy and the Agent Intervals
The agent proxy server is included in the bundle. If the bundle is already downloaded and the proxy is changed later, the bundle will not contain the proxy settings.
Installing Advanced Management Console Agent on Windows
To install the agent on Windows:
Note:
The Advanced Management Console supports the agent on Windows 32-bit and 64-bit operating systems only. The agent-bundle-win32.zip
bundle works for both 32-bit and 64-bit Windows operating systems.
Installing Advanced Management Console Agent on Linux
You can use the bin/AMCAgent.sh
script file to install
and uninstall the Advanced Management Console agent on
the Linux operating system. The Advanced Management Console agent is a native service that you can start, stop, or restart from the
Linux terminal.
/usr/local/Oracle/Java_AMC
directory and starts the daemon. It
also registers the native service by placing the registration file in
/etc/systemd/system/
or /etc/init/
directories for systemd
or upstart
frameworks
respectively.
Installing Advanced Management Console Agent on macOS
You can use the bin/AMCAgent.sh
script file to install
and uninstall the Advanced Management Console agent on
the macOS operating system. The Advanced Management Console agent is a launched daemon that you can start, stop, or restart by using
the launchctl
command.
/Library/Application Support/Oracle/Java_AMC
directory, the .plist
file to /Library/LaunchDaemons/
, and starts the daemon.
Advanced Management Console Agent Logging
The Advanced Management Console agent utilizes the Java logger to log information about tasks performed by the agent as well as any errors that are encountered.
- Windows:
%PROGRAMDATA%\Oracle\Java_AMC
- macOS:
/Library/Application Support/Oracle/Java_AMC
- Linux:
/usr/local/Oracle/Java_AMC/
The logs are rotated according to a policy. Beginning with Advanced Management Console 2.7, the maximum size of the log files and the number of files are configurable through AMCAgent.properties. By default, the rotation uses three log files with a maximum size of 64K. This means that when the first log file grows to a size of 64K, logs are directed to the second log file. When the third log becomes full, the log rotates back to the first file, overwriting any existing contents there. See Configuring the Agent Proxy and the Agent Intervals for procedures you can use to edit logging parameters.
Unstalling Advanced Management Console Agent
Uninstalling the Advanced Management Console Agent on Windows
On Windows, you can run the remove
command to uninstall the
Advanced Management Console agents and remove all Java Usage Tracker Properties files on the
Advanced Management Console server.
Uninstalling the Advanced Management Console Agent on Linux
On Linux, you can run the remove
command to uninstall the
Advanced Management Console agents and remove all Java Usage Tracker Properties
files on the Advanced Management Console agent.
sudo bash ${AMC_DIR}/bin/AMCAgent.sh -remove
The agent attempts to unregister itself on the Advanced
Management Console server before uninstalling. After the agent is
unregistered on the server, all Java Usage Tracker configuration
files (usagetracker.properties
) on the desktop are
also removed.
If the Advanced Management Console
server is not reachable, this could cause the uninstallation to
stall or fail. In this case, you can use the sudo bash ${AMC_DIR}/bin/AMCAgent.sh -forceremove
command to force the agent to uninstall without unregistering first.
However, AMCAgent.exe -forceremove
does not perform
the cleanup of usagetracker.properties
files.
AMCAgent.sh -forceremove
command in the following
scenarios:
-
If using the
AMCAgent.sh -remove
command fails to uninstall the agent service, then run theAMCAgent.sh -forceremove
command to force uninstall the agent. -
If the agent was never successfully registered on the server, then you need to execute
AMCAgent.sh -forceremove
command to uninstall the agent. TheAMCAgent.sh -remove
command doesn’t work in such a scenario.
Note:
See Unregistering Desktops with the Advanced Management Console User Interface to unregister the agent from the User Interface.-
/etc/systemd/system/
-
/etc/init/
Uninstalling the Advanced Management Console Agent on macOS
On macOS, you can run the remove
command to uninstall the
Advanced Management Console agents and remove all Java Usage Tracker Properties
files on the Advanced Management Console server.
sudo ${AMC_DIR}/bin/AMCAgent.sh -remove
The agent attempts to unregister itself on the Advanced
Management Console server before uninstalling. After the agent is
unregistered on the server, all Java Usage Tracker configuration
files (usagetracker.properties
) on the desktop are
also removed.
If the Advanced Management Console
server is not reachable, this could cause the uninstallation to
stall or fail. In this case, you can use the ${AMC_DIR}/bin/AMCAgent.sh -forceremove
command to
force the agent to uninstall without unregistering first. However,
AMCAgent.exe -forceremove
does not perform
the cleanup of usagetracker.properties
files.
AMCAgent.sh -forceremove
command in the following
scenarios:
-
If using the
${AMC_DIR}/bin/AMCAgent.sh -remove
command fails to uninstall the agent service, then run the${AMC_DIR}/bin/AMCAgent.sh -forceremove
command to force uninstall the agent. -
If the agent was never successfully registered on the server, then you need to execute
AMCAgent.sh -forceremove
command to uninstall the agent. TheAMCAgent.sh -remove
command doesn’t work in such a scenario.
Note:
See Unregistering Desktops with the Advanced Management Console User Interface to unregister the agent from the User Interface..plist
file from the following directories:
-
/Library/LaunchDaemons/
-
/Library/Application Support/Oracle/Java_AMC
Unregistering Desktops with the Advanced Management Console User Interface
After running -remove
to uninstall the Advanced Management Console agents on Windows and macOS, you can use the Advanced Management Console to remove any desktops that cannot contact the Advanced Management Console server.
Distributing Advanced Management Console Agent
Distribution of the Advanced Management Console agent bundle is not handled by Advanced Management Console .
You can download the Advanced Management Console agent bundle from the Advanced Management Console web UI. A Software Management System, such as Microsoft SCCM, can be used to distribute the agent bundle to desktops in your enterprise.
The Software Management System that you use must provide customized options to support Advanced Management Console secure agent distribution. This system must handle the following operations using administrator privileges:
-
Extraction of the agent bundle as described in Installing Advanced Management Console Agent on Windows. Incorrect extraction may cause improper file permissions that prevents agent from starting.
-
Configuration of the bundle based on the desktop owner's user credentials.
-
Installation of the agent using the install command.
After the agent is distributed, each desktop that receives the agent is registered with the Advanced Management Console server using the user credentials that were configured for the desktop. The agent also automatically configures Java Usage Tracker and associates the Java Usage Tracker records with the user credentials that were configured for the desktop. The agent then periodically reports data, such as operating system family and version, and installed JREs to the Advanced Management Console server.
To view the desktops that are registered with the Advanced Management Console server, log in to the Advanced Management Console web UI and click the Desktops tab.