Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Install the App Visibility agent for Java on the computer with the application server you want to monitor. After you install the agent, connect it to the application server instance. You can perform a silent installation, as described in this topic, or use the interactive installation mode.

This topic contains the following sections:

Before you begin

Ensure that you have completed all tasks to prepare the environment for agent installation.

To install the agent for Java in silent mode using default values

  1. Configure the Java options according to the application server type.

To install the agent for Java in silent mode using customized configuration settings

You can customize the silent installation to suit your deployment by running the install command with specified parameter values.

  1. To verify the installation, view the parameters selected during installation in the bmc_ad_agent_install.log file, which is usually located in the same folder as the installation script and the agentInstaller.jar.

  2. Configure the Java options according to the application server type.

Installation command options

To run the silent installation, you must enter the -s (or -silent) option. The remaining options use the default values. The following table describes the options that you can customize and their default values.

OptionShort option

Description

-silent-sSets the silent mode, so that the installation utility does not wait for parameters. For any missing parameter, the installation utility uses the default value.

-destination

-d

Destination installation path

Default: Blank, which uses the working directory (that is, the directory from which the installation script is invoked)

Notes:

  • In Windows systems, do not install directly on the the C directory.
  • In Linux systems, do not install directly on the root directory.
-agentPortMin-pmin

Minimum value of the supportability port number range

Default: 50000

-agentPortMax-pmax

Maximum value of the supportability port number range

Default: 50100

-host

-n

Display name for the application server computer

The name must be no longer than 255 characters and can include only alphanumeric Latin characters, spaces, underscore characters (_), and hyphens (-).

Default: Blank, which takes the server host name

-portalHost

-ph

Portal IP address or host name

Default: localhost

-portalPort

-t

Portal port

Default: 8100 (for HTTP)

-proxyHttpsHost

-phttpsh

(For web proxy server) If the App Visibility portal is behind a web proxy server, enter the server host name or IP address. If blank, this proxy is not used.

Default: blank (no proxy)

Note: Proxy server details are required only if you are using a proxy server or load balancing server. This is not the same server as the App Visibility proxy, which is used to collect end-user browser data.

-proxyHttpsPort

-phttpsp

(For web proxy server) Proxy server port for outbound web proxy connection

Default: -1 (no proxy)

-proxySocksHost

-psocksh

(For SOCKS proxy server) If the App Visibility portal is behind a SOCKS proxy server, enter the server host name or IP address. If blank, this proxy is not used.

Default: blank (no proxy)

Note: Proxy server details are required only if you are using a proxy server or load balancing server. This is not the same server as the App Visibility proxy, which is used to collect end-user browser data.

-proxySocksPort

-psocksp

(For SOCKS proxy server) Proxy server port for outbound SOCKS proxy connection

Default: -1 (no proxy)

Examples of customized configuration settings

  • A customized silent installation on Windows. The agent is installed in c:\BMC\AD\Agent, and connects to the portal on goodhost.abcd.com

    adops-agent-install.bat -s -d c:\BMC\AD\Agent -host FrontEndMachine -portalHost goodhost.abcd.com
  • A customized silent installation on Linux. The agent is installed in /usr/BMC/AD/agent, and connects to the portal on goodhost.abcd.com

    adops-agent-install.sh -s -d /usr/BMC/AD/agent -host BackEndRHMachine -portalHost goodhost.abcd.com
  • A customized silent installation on Windows, using a proxy, with customized configuration of the proxy web host and port

    adops-agent-install.bat -s -phttpsh 10.64.180.2 -phttpsp 443
  • A customized silent installation on Linux, using a proxy, with customized configuration of the proxy SOCKS host and port

    adops-agent-install.sh -s -psocksh 10.64.180.2 -psocksp 3128

To configure Java options

After you install the agent, you need to add the agent to the Java command line. The javaagent option is required to connect the App Visibility agent to the JVM process. Enter the information that is relevant to your installation.

  1. Add the following agent JVM options to the Java command line of your application server.

    Replace <installationDirectory> with the destination directory in which the App Visibility agent was installed.

    The procedure to update Java options is different for each application server type.

    • Windows

      -javaagent:<installationDirectory>\ADOPsInstall\adops-agent.jar
      
    • Linux

      -javaagent:<installationDirectory>/ADOPsInstall/adops-agent.jar
      
  2. If you have a single App Visibility agent installation directory that is used by multiple JVM processes, you can assign meaningful names to distinguish each instance. For information, see To distinguish multiple JVM processes using the same agent installation.
  3. Restart the application server or JVM process.

Where to go from here

Verifying the installation of App Visibility agent for Java

Access the Operations Management Console.

Related topics

Installing an App Visibility agent for .NET

Changing settings of the App Visibility agent for Java