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.

1. Enter https://server:port/amcwebui in the browser and log in to the AMC UI by using administrator credentials to initialize the AMC. See Initializing Advanced Management Console.
2. Configure the agent proxy server host and port.

   Note:

   Step 2 must be completed before the agent bundle is downloaded. If a proxy server is required to access the AMC Server, then the agent would not be able to reach the server to register without this information.

   1. In the Advanced Management Console UI, click the Configuration tab.
   2. Click Agents Download.
   3. Click Edit to display the Configure AMC Agent Proxy Settings dialog.
   4. Enter the following details for the agent to connect to the Advanced Management Console server:

      • Agent Proxy Host Name: Specify a proxy server host name.

      • Agent Proxy Port: Specify a proxy server port number.

   5. Click Save.
3. Configure the agent intervals.

   Note:

   If you increase the agent intervals, then the system load is reduced. When the agent intervals are increased, the communication of the agent with the Advanced Management Console server automatically decreases, which reduces the system load.
   1. Click the Configuration tab.
   2. Click Agent Settings.
   3. Click Edit to make the fields editable.
   4. Edit any of the following values. You can either edit all of them or just the ones that you want to:

      JUT Processing Interval

      Interval for the agents to report Java Usage Tracker records to the server

      Check Command Interval

      Interval to check if the server has any commands for the agent

      Standard JRE Scan Interval

      Interval to scan Java Runtime Environment (JRE) in the standard location (For example, on Windows it is C:\Program Files\Java) and report to server

      Application JRE Scan Interval

      Interval to scan JRE under the application location (For example, on Windows it is C:\Program Files) and report to server

      LocalStorage JRE Scan Interval

      Interval to scan JREs in the entire local storage system (not targeting any particular directory) and report to server

      Agent Auto Update

      Enable or disable the agent auto update

      Agent Log File Max Size (Kb)

      Maximum agent log file size in Kb

      Number of Agent Log Files

      Maximum agent log file number during agent log rotation

      Randomize Interval

      Enable or disable randomize interval

   5. Click Save.

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.

1. Configure the agent proxy and the agent intervals. See Configuring the Agent Proxy and the Agent Intervals.
   The agent proxy server is included in the bundle. If you change proxy server settings, you will need to download agent bundle again and distribute the updated bundle.
2. On the Advanced Management Console UI, click the Configuration tab and select Agents Download.
3. Click the link agent-bundle-linux64.zip and save the bundle to a desired location.
4. Start a Linux terminal. Goto the folder where the zip file was downloaded. Extract the zip. In the following steps, ${AMC_DIR} represents the AMC_Agent directory where the Java Advance Management Agent files are extracted.
5. Starting with Advanced Management Console 2.2, this is an optional step. Rename ${AMC_DIR}/conf/AMCUser.properties.template to ${AMC_DIR}/conf/AMCUser.properties and configure the three information values with the user's actual credentials.
6. Excute the AMCAgent.sh script from the terminal using the command:

   sudo bash ${AMC_DIR}/bin/AMCAgent.sh -install 

7. Log in to Advanced Management Console web UI again. Go to the Desktops page and check that the desktop is now registered with the Advanced Management Console server. If the user's credentials were configured in step 5, then the desktop owner now appears as Owner in the Advanced Management Console UI.

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.

1. Configure the agent proxy and the agent intervals. See Configuring the Agent Proxy and the Agent Intervals.
   The agent proxy server is included in the bundle. If you change proxy server settings, you will need to download agent bundle again and distribute the updated bundle.
2. On the Advanced Management Console UI, click the Configuration tab and select Agents Download.

   Note:

   When you select Agents Download, you might need to wait for the SHA256 values to finish computing. If the bundle isn't already generated, it takes a short time to build it. Once it's shown, the bundle is ready to download.

3. Click the link agent-bundle-macosx.zip and save the bundle.
4. Open the Finder, select the .zip file, right click to select Open With and then click Archive Utility to unzip all the files. You can also double click the .zip file to open the Archive Utility to unzip the files into the current folder.
   The script file doesn’t have permissions to execute. Use the chmod command to manually set the execute permissions.
5. The files get extracted to AMC_Agent directory within the current folder. In the following steps, ${AMC_DIR} represents the AMC_Agent directory where the Java Advance Management Agent files are extracted.
6. Starting with Advanced Management Console 2.2, this is an optional step. Rename ${AMC_DIR}/conf/AMCUser.properties.template to ${AMC_DIR}/conf/AMCUser.properties and configure the three information values with the user's actual credentials.
7. Execute the AMCAgent.sh script from the terminal using the command:

   sudo ${AMC_DIR}/bin/AMCAgent.sh -install

8. A dialog appears stating that the AMCAgent app is downloaded. Click Open.
9. Log in to Advanced Management Console web UI again. Go to the Desktops page and check that the desktop is now registered with the Advanced Management Console server. If the user's credentials were configured in step 6, then the desktop owner now appears as Owner in the Advanced Management Console UI.

On Linux, you can run the remove command to uninstall the Advanced Management Console agent and remove all Java Usage Tracker Properties files from the desktop.

sudo bash ${AMC_DIR}/bin/AMCAgent.sh -remove

On macOS, you can run the remove command to uninstall the Advanced Management Console agent and remove all Java Usage Tracker Properties files from the desktop.

sudo ${AMC_DIR}/bin/AMCAgent.sh -remove

You can use the Advanced Management Console to remove any desktops that cannot contact the Advanced Management Console server.

1. In the Advanced Management Console UI, click the Desktop tab.
2. Ensure that the Desktop is selected in the Display drop-down list.
   The Other Actions button is available only with the Desktop display option.
3. Ensure that the Table icon is selected.
4. (Optional) Set the filter criteria to show only the desktops that you want to unregister.
   1. Click Add Criteria.
   2. Select the filters and set the values for each filter that you select.
5. In the Desktop table, select the check boxes adjacent to the desktops that you want to unregister.
6. Click Other Actions and then select Unregister Desktop(s) to display the Unregister Desktop(s) dialog.
7. Select the target desktops by selecting either of the following options:
   • Selected Desktops: Shows the number of desktops selected.
   • All Filtered Desktops: Shows the number of filtered desktops included.
8. Click Confirm.
   The selected desktops or all filtered desktops are unregistered.