Installing an App Visibility agent using the wizard
Where you are in the Installation process
Step | Task |
---|---|
1 | Complete the planning activities |
2 | Prepare for TrueSight Operations Management installation |
3 | Install Remedy Single Sign-On |
4 | Install TrueSight Presentation Server |
5 | Install TrueSight Infrastructure Management (if licensed) |
6 | Install TrueSight App Visibility Manager — Phase A |
Install TrueSight App Visibility Manager — Phase B Task 1 (You are here) | |
Install TrueSight App Visibility Manager — Phase B Task 2 | |
7 | Install Real End User Experience Monitoring Software Edition (If licensed) |
8 | Install TrueSight IT Data Analytics (If licensed) |
9 | Complete the post-installation activities |
App Visiblity agents are available for Java and .NET environments. Based on your environment, you can install the applicable agent on the computer with the application server you want to monitor. After you install the agent, connect it to the App Server instance.
To install the App Visibility agent for Java
Log in to the computer with the user that runs the application server.
On Windows computers, you must run the installation with a user that has administrator privileges.- Copy and extract the files to a temporary directory on the target computer.
- (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
export DISPLAY=<IP address of the host computer>:0.0
- Launch the installation wizard:
- (Windows) Double-click setup.exe.
- (Unix) Double-click setup.bin.
- On the Welcome page, click Next.
- Read the license agreement, agree to the terms, and click Next.
Specify the installation directory or retain the default, and click Next.
The default directory is:(Windows) C:\Program Files (x86)\BMC Software\App Visibility\Agent for Java
(Linux, AIX, Solaris) /opt/bmc/App_Visibility/Agent_for_Java
- Type the Application Server Display Name, which is displayed in the TrueSight console, and click Next. The default name is the DNS host name.
- Type the values for the Portal Connection parameters.
- Enter the Portal connection details:
- Portal Server—Enter the IP address or host name on which the App Visibility portal is (or will be) installed.
If a load balancing server manages access to the portal, enter the host name or IP address of the load balancer.
- Portal Port—Enter the App Visibility portal port number.
If a load balancing server manages access to the portal, enter the port number of the load balancer.
- Portal Server—Enter the IP address or host name on which the App Visibility portal is (or will be) installed.
If your environment requires the agent to use a proxy server when communicating with the portal and collector, enter Proxy Server Details:
Note
Proxy server details are required only if you are using a reverse proxy server or load balancing server. This server is not the same server as the App Visibility proxy, which is used to collect end-user browser data.
- Proxy Server—Select one of the following:
- No Proxy
- HTTPS Proxy
- SOCKS Proxy
Default: No Proxy
- Proxy Host Name or IP Address—Enter the web proxy server host name or IP address.
If the App Visibility portal is behind a proxy server, enter the server host name or IP address.
Proxy Port—Enter the web proxy server port number for outbound connection. If you use a proxy server, this property cannot be blank.
- Proxy Server—Select one of the following:
- Click Next.
The installation utility tests the connection.- If the system successfully connects to the App Visibility portal, the Installation Preview page is displayed.
- If the system fails to connect to the App Visibility portal or the proxy server, a validation error is displayed. Do one of the following:
- Click Previous to verify the connection details and test the connection again.
- Continue with the installation, and change the connection details after installation.
- Enter the Portal connection details:
Review the details, and click Install.
- Click Done to end the installation process.
Configure the Java options for the agent.
Verify that the installation of the App Visibility agent for Java was successful, and that the agent was invoked, by reviewing the log files created during installation.
Configuring App Visibility agents for Java
After installing the App Visibility agent for Java, complete the following configuration tasks:
Update Java options according to the application server type
As part of the App Visibility agent for Java installation process, you must add the agent JVM options to the Java command line of your application server.
The procedure to update the JVM options is different for each application server type, and this topic provides examples for some of the leading types of application servers. If you have more than one JVM process using the same agent installation, you can assign meaningful names to distinguish each instance.
The App Visibility agent for Java runs in the same JVM memory space as the monitored applications, therefore BMC recommends increasing by 256 MB the maximum heap size specified through the -Xmx
Java option.
For full details about both the -javaagent
and -Xmx
options, refer to the Java options documentation for your application server type.
In the following procedures, replace the <AgentInstallationDirectory>
with the location where the agent is installed. The default folder is the one from which the installation script is run, for example:
- (Windows)
<AgentInstallationDirectory>
\ADOPsInstall\adops-agent.jar
Where<AgentInstallationDirectory>
is the C:\bmc\appvis_agent directory
- (Linux)
<AgentInstallationDirectory>
/ADOPsInstall/adops-agent.jar
Where<AgentInstallationDirectory>
is the /usr/bmc/appvis_agent directory
Grant Java 2 permissions to the App Visibility agents
The App Visibility agent requires permissions to the Java 2 system, such as write access to the application server computer (for log entries), and API access to various application interfaces to collect diagnostic information. On application servers that use Java 2 security, you must provide permissions to the App Visibility agent.
Granting the relevant permissions depends on the Java 2 security provider and application server type. This topic describes how to grant the relevant Java 2 permissions on different application server types.
To install the App Visibility agent for .NET
- Log in to the computer with the user that runs the application server.
On Windows computers, you must run the installation with a user that has administrator privileges. - Copy and extract the files to a temporary directory on the target computer.
- Launch the installation wizard by double-clicking setup.exe.
- On the Welcome page, click Next.
- Read the license agreement, agree to the terms, and click Next.
- Specify the installation directory or retain the default, and click Next.
The default directory is C:\Program Files (x86)\BMC Software\App Visibility\Agent for .NET.
- Type the Application Server Display Name, which is displayed in the TrueSight console, and click Next. The default name is the DNS host name.
- Type the values for the Portal Connection parameters..
- Enter the Portal connection details:
- Portal Server—Enter the IP address or host name on which the App Visibility portal is (or will be) installed.
If a load balancing server manages access to the portal, enter the host name or IP address of the load balancer.
- Portal Port—Enter the App Visibility portal port number.
If a load balancing server manages access to the portal, enter the port number of the load balancer.
- Portal Server—Enter the IP address or host name on which the App Visibility portal is (or will be) installed.
If your environment requires the agent to use a proxy server when communicating with the Portal and Collector, select Use Web Proxy Server and enter connection details:
Note
Proxy server details are required only if you are using a reverse proxy server or load balancing server. This server is not the same server as the App Visibility proxy, which is used to collect end-user browser data.
- Proxy Host Name or IP Address—Enter the web proxy server host name or IP address.
- Proxy Port—Enter the web proxy server port number.
- Click Next.
The installation utility tests the connection.- If the system successfully connects to the App Visibility portal, the Installation Preview page is displayed.
- If the system fails to connect to the App Visibility portal or the proxy server, a validation error is displayed. Click Previous to verify the connection details and test the connection again. If the connection fails again, continue with the installation and change the connection details after installation.
- Enter the Portal connection details:
Review the details, and click Install.
Click Done to end the installation process.
- When the installation process is complete, restart IIS.
Verify that the App Visibility agent for .NET installation was successful, and that the agent for .NET was invoked.
Apply the App VisibilityHotfix (11.3.01.000.001) to work with Presentation Server
If you are using TrueSight App Visibility Manager11.3.01 as a component in your Presentation Server environment, apply the App Visibility Hotfix 11.3.01.000.001 before you proceed. If you didn't apply this hotfix, the admin users may not be able to view all the Synthetic Metric Rules.
Troubleshooting installation issues
If you face issues during installation, see Troubleshooting the App Visibility Manager deployment
Next Step in the Installation process
Step 6 Phase B Task 2 — Now that you have successfully installed the App Visibility agent, you must install the Transaction Execution Adapter agent.
Comments
Log in or register to comment.