Preparing for upgrading the App Visibility agents

This topic provides information about preparing your environment to install the App Visibility agent for Java.

Upgrade warning

If you have the App Visibility Manager version 11.0.00.003 (Fix Pack 3) configured to work with the SAML authentication type, and want to upgrade your TrueSight Operations Management to version 11.3.01, you must also apply the Fix Pack version 11.3.02 for the SAML authentication type to work.

Before installing the agent, ensure that your environment satisfies the following requirements:

Requirement	Description
Upgrade the App Visibility server	Upgrade the App Visibility server components before installing the agent.
Disable or remove other agents	The JVM platform enables you to run multiple monitoring agents, and the App Visibility agent for Java generally runs as expected with other agents. Yet other agents might significantly alter the runtime environment and such changes, over which BMC has no control, might cause unexpected results or malfunction in the App Visibility agent for Java with your web application. Therefore, BMC strongly recommends that you disable or remove anynon-BMC application performance monitoring agent from the application server where you install the App Visibility agent for Java.
Download files	Download the following agent installation files from the Electronic Product Distribution site: Windows ad_java_agent_win_11.3.01.zip Unix ad_java_agent_unix_11.3.01.tar.gz The Unix file contains files for the following versions: Linux ad_java_agent_linux_11.3.01.tar.gz AIX ad_java_agent_aix_11.3.01.tar.gz Solaris ad_java_agent_solaris_11.3.01.tar.gz
Set access and permissions	Ensure that you have execute privileges on the upgrade scripts and write access to the upgrade location. Note: The Linux installation files and directories have executable permissions. You can modify the permissions after you complete the upgrade successfully. On Unix platforms, to ensure proper functioning of the agent, upgrade the agent with the user that runs the application server. On Windows platforms, perform the install or upgrade as administrator. Only the user that installed the agent will be able to uninstall or upgrade it. There are no restrictions on which user can run the application server with the agent.
Verify the JVM heap memory (If the Agent is running in the same JVM memory space as the monitored application)	Verify the memory requirements. The agent for Java requires up to 256 MB of JVM heap memory. If the agent is running in the same JVM memory space as the monitored application, BMC recommends adding 256 MB to the Max heapsize Java options flag -Xmx. Example set JAVA_OPTS=%JAVA_OPTS% -Xmx1024m For full details about both the `-javaagent` and `Xmx` options, refer to the Java options for each application server type. Watch videos on YouTube Watch Installing App Visibility Part 5 \| Agent for Java Startup and Tuning (starting at 1:20) to tune the agent by increasing the JVM heap memory in WebLogic.

To Prepare for upgrading the App Visibility agent for .NET

Upgrade the App Visibility server

Upgrade the App Visibility server components before installing the agent.

Download installation files

Download the agent for .NET installation files from the Electronic Product Distribution site.

Confirm access and permissions

When you perform an installation or upgrade, you must use an IIS Application Pool Identity that has read and execute access to the installation directory, subdirectories, and files for App Visibility agent for .NET. Specifically, you must have Traverse folder access to the agent installation directories. For example, if %ProgramFiles(x86)% is C:\Program Files (x86), you need Traverse folder access to the following directories:

C:\
C:\Program Files (x86)\
C:\Program Files (x86)\BMC Software\
C:\Program Files (x86)\BMC Software\App Visibility\

Remove SCOM APM

To use agent for .NET in a Microsoft System Center Operations Manager (SCOM) version 2012 environment, you must disable application performance monitoring for SCOM, because only one application can use the .NET CLR Profiler at a time. For more information, see the SCOM product documentation.

To remove SCOM APM

Uninstall the Operations Manager agent.
Reinstall the Operations Manager agent without .NET Application Performance Monitoring, as described in the SCOM product documentation . Ensure that you use the NOAPM=1 switch.

SCOM APM is not installed and will not interfere with agent for .NET.