Upgrading the App Visibility server in the standalone mode using the wizard
Where you are in the Upgrade process
| Step | Task |
|---|---|
| 1 | Preparing to upgrade TrueSight Operations Management solution |
| 2 | Upgrade Remedy Single Sign-On |
| 3 | Upgrade TrueSight Presentation Server |
| 4 | Upgrade TrueSight Infrastructure Management |
| 5 | Upgrade App Visibility Manager — Phase A (You are here) |
| Upgrade App Visibility Manager — Phase B | |
| 6 | Upgrade Real End User Experience Monitoring Software Edition |
| 7 | Upgrade TrueSight IT Data Analytics |
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.
You must be a system administrator to perform the TrueSight App Visibility Manager server components upgrade. When you run the installation wizard to upgrade on a system with a previous version of the product, the wizard automatically switches to upgrade mode for the installed component or components. The App Visibility server includes the following components:
- One App Visibility portal, or in an HA environment (wizard-based or silently), one pair of App Visibility portal nodes
- One or more App Visibility collectors, or in an HA environment (wizard-based or silently), one or more pairs of App Visibility collector nodes
One or more App Visibility proxies
Note
The Proxy server can be used with multiple deployments (as a cluster) working together as a single entity.
Upgrade the portal before the other server components because:
- The collector and proxy reference the portal during upgrade.
- The App Visibility agents also reference the portal during upgrade.
The portal includes a small database for configuration and connection information. If you install a portal and a collector on the same computer, they share the same database.If TrueSight App Visibility Manager server components are installed on separate computers, the portal and collector upgrade processes include the option to enable high availability (HA). For more information about TrueSight App Visibility Manager Manager and HA, see App Visibility Manager high-availability deployment.You can have several collectors, depending on the volume of your transactions. Install each collector on a separate computer. Each collector includes a database for App Visibility data.
To upgrade the App Visibility portal
The procedure describes how to upgrade the App Visibility portal when it is the only App Visibility server component on the computer.
To upgrade an App Visibility collector
The procedure describes how to upgrade an App Visibility collector when it is the only App Visibility server component on the computer.
Login to the host computer on which you want to install the app Visibility collector, and delete all the files from the temporary directory:
- (Windows) %temp%
- (Linux) /tmp
- Extract the downloaded files to a temporary directory.
- (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 upgrade wizard:
(Windows) Right-click setup.exe and select Run as administrator.
- (Linux) Run setup.bin.
- Review the Welcome page, and click Next.
Read the license agreement, agree to the terms, and click Next.
If you do not agree to the terms of the license agreement, the upgrade process ends.
On the Features page, select the upgrade BMC App Visibility Collector 11.0.00 to 11.3.01 component and click Next.
On the upgrade prerequisites page, confirm that you have backed up your App Visibility collector database. If you haven't backed it up, see "Backing up the App Visibility database" in Preparing to upgrade the App Visibility Server and checking compatibility for details on how to do it.
If necessary, update the App Visibility portal connection information. After you update the information, click Test Connection to check communication with the portal, and then click Next.
Option
Description
Portal Host Name or IP
App Visibility portal host name or IP address
If a load balancing server manages access to the portal, enter the host name or IP address of that load balancing server.
The default value is the value from the original installation.
Portal Port
Listening port of the portal
If a load balancing server manages access to the portal, enter the port number of that load balancing server.
The default value is the value from the original installation.
After the upgrade process completes, click View Log to view the installation log files.
- Click Done to exit the wizard.
For large and extra large deployments (150,000–360,000 transactions per hour), increase the heap size on your App Visibility collector to 6 GB. For details, see Changing the heap size on App Visibility components.
To upgrade an App Visibility proxy
The procedure describes how to upgrade an App Visibility proxy when it is the only App Visibility server component on the computer.
Note
(For App Visibility proxy upgrade) The upgrade process includes several checks for connectivity to the App Visibility portal and to other App Visibility proxy servers and storage engines. The process cannot continue until the connectivity and storage engine cluster issues are resolved, unless you explicitly run the installation utility with a command to continue with such errors.
(Not recommended) If you want to upgrade the proxy without testing connectivity, run the utility from a command line with the -J continue_with_connectivity_error=true parameter. At your own risk, you will have to resolve connectivity and storage engine cluster issues after the upgrade process, and restart all the storage engine cluster nodes.
Login to the host computer on which you want to install the app Visibility proxy, and delete all the files from the temporary directory:
- (Windows) %temp%
- (Linux) /tmp
- Extract the downloaded files to a temporary directory.
- (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 upgrade wizard:
(Windows) Right-click setup.exe and select Run as administrator.
- (Linux) Run setup.bin.
- Review the Welcome page, and click Next.
Read the license agreement, agree to the terms, and click Next.
If you do not agree to the terms of the license agreement, the upgrade process ends.
On the Features page, select the upgrade BMC App Visibility Proxy 11.0.00 to 11.3.01 component and click Next.
On the Proxy Configuration page, provide port numbers for the storage component that is added with the upgrade, and then click Next.
Other port numbers are displayed but they are not editable during upgrade. For details about changing the settings after you complete the upgrade process, see Changing App Visibility proxy settings
Ensure that the port numbers are available.
Option
Description
Communication Port
Listening port of the proxy, communication from the portal and collector
The default port is 8300.
Supportability Port
Listening port of the proxy support console
A support console, which helps detect issues, is automatically activated with one-way SSL authentication.
The default port is 8301.
Beacon Receiver HTTP Port
Listening port of the beacon receiver, HTTP communication from the end users' browsers
The default port is 880.
Beacon Receiver HTTPS Port
Listening port of the beacon receiver, HTTPS communication from the end users' browsers
The default port is 8444.
Storage HTTP Port
Listening port of the App Visibility proxy database
The default port is 8302.
Storage Transport Port
Port for TCP communication between App Visibility proxy database nodes in a cluster
The default port is 8303.
Storage Transport IP Address Used for communication between the different nodes in the storage cluster
The IP address must be available from other App Visibility proxy nodes.
The default IP address is the first received by the system.
If necessary, update the App Visibility portal connection information. After you update the information, click Test Connection to check communication with the portal, and then click Next.
Option
Description
Portal Host Name or IP
App Visibility portal host name or IP address
If a load balancing server manages access to the portal, enter the host name or IP address of that load balancing server.
The default value is the value from the original installation.
Portal Port
Listening port of the portal
If a load balancing server manages access to the portal, enter the port number of that load balancing server.
The default value is the value from the original installation.
After the upgrade process completes, click View Log to view the installation log files.
Click Done to exit the wizard.
After you upgrade the App Visibility proxy, you must update the JavaScript stub for every application where you manually set up active end-user monitoring
: change the last line of the stub to aeuem.min.js, as shown in the following example:<script type="text/javascript" src="https://apm_proxy_host:apm_proxy_https_port/static-resources/aeuem.min.js"></script>
To upgrade one or more App Visibility server components
(For a very small environment or a test environment) The procedure describes how to upgrade one or more App Visibility server components on the same computer.
Note
(For App Visibility proxy upgrade) The upgrade process includes several checks for connectivity to the App Visibility portal and to other App Visibility proxy servers and storage engines. The process cannot continue until the connectivity and storage engine cluster issues are resolved, unless you explicitly run the installation utility with a command to continue with such errors.
(Not recommended) If you want to upgrade the proxy without testing connectivity, run the utility from a command line with the -J continue_with_connectivity_error=true parameter. At your own risk, you will have to resolve connectivity and storage engine cluster issues after the upgrade process, and restart all the storage engine cluster nodes.
Login to the host computer on which you want to install the app Visibility portal, and delete all the files from the temporary directory:
- (Windows) %temp%
- (Linux) /tmp
- Extract the downloaded files to a temporary directory.
- (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 upgrade wizard:
(Windows) Right-click setup.exe and select Run as administrator.
- (Linux) Run setup.bin.
- Review the Welcome page, and click Next.
Read the license agreement, agree to the terms, and click Next.
If you do not agree to the terms of the license agreement, the upgrade process ends.
If prompted, select the upgrade component:
- For all App Visibility server components installed on the computer, the components are selected on the Features page and you must upgrade them.
- If one or more server components are not installed, you can select to install another component on the Features page.
For instructions about installing the new component, see Installing. - If App Visibility server components are installed on separate computers, the portal and collector upgrade processes include the option to enable HA.
(For portal or collector) On the upgrade prerequisites page, confirm that you have backed up your App Visibility portal database. For information on backing up the App Visibility database, see Preparing to upgrade the App Visibility Server and checking compatibility.
(For App Visibility proxy upgrade)
On the Proxy Configuration page, provide port numbers for the storage component that is added with the upgrade, and then click Next.
Other port numbers are displayed but they are not editable during upgrade. For details about changing the settings after you complete the upgrade process, see Changing App Visibility proxy settings
Ensure that the port numbers are available.
Option
Description
Communication Port
Listening port of the proxy, communication from the portal and collector
The default port is 8300.
Supportability Port
Listening port of the proxy support console
A support console, which helps detect issues, is automatically activated with one-way SSL authentication.
The default port is 8301.
Beacon Receiver HTTP Port
Listening port of the beacon receiver, HTTP communication from the end users' browsers
The default port is 880.
Beacon Receiver HTTPS Port
Listening port of the beacon receiver, HTTPS communication from the end users' browsers
The default port is 8444.
Storage HTTP Port
Listening port of the App Visibility proxy database
The default port is 8302.
Storage Transport Port
Port for TCP communication between App Visibility proxy database nodes in a cluster
The default port is 8303.
Storage Transport IP Address Used for communication between the different nodes in the storage cluster
The IP address must be available from other App Visibility proxy nodes.
The default IP address is the first received by the system.
(For App Visibility collector or proxy upgrade)
If necessary, update the App Visibility portal connection information. After you update the information, click Test Connection to check communication with the portal, and then click Next.
Option
Description
Portal Host Name or IP
App Visibility portal host name or IP address
If a load balancing server manages access to the portal, enter the host name or IP address of that load balancing server.
The default value is the value from the original installation.
Portal Port
Listening port of the portal
If a load balancing server manages access to the portal, enter the port number of that load balancing server.
The default value is the value from the original installation.
After the upgrade process completes, click View Log to view the installation log files.
- Click Done to exit the wizard.
- For large and extra large deployments (150,000–360,000 transactions per hour), increase the heap size on your App Visibility collector to 6 GB. For details, see
Changing the heap size on App Visibility components.
After you upgrade the App Visibility proxy, you must update the JavaScript stub for every application where you manually set up active end-user monitoring
: change the last line of the stub to aeuem.min.js, as shown in the following example:<script type="text/javascript" src="https://apm_proxy_host:apm_proxy_https_port/static-resources/aeuem.min.js"></script>
To verify that the TrueSight App Visibility Manager server upgrade was successful
After the upgrade is complete, a successful upgrade is indicated in the wizard or on the command window. Use the following procedure to confirm or troubleshoot the upgrade of the server components.
Access the adopserver_install_log file:
- (Windows) %temp%
- (Linux) /tmp
- Check for warnings or errors.
If no error messages are present, the upgrade (installation) was successful. Based on the upgraded component, verify that the App Visibility server components are running:
- (Windows) Run services.msc and verify that the services are running:
For Collector and Portal- App Visibility Collector
- App Visibility Portal
- App Visibility PostgreSQL
- App Visibility Proxy
- App Visibility Elasticsearch
(Linux) Run the following commands to verify that the processes are running:
For Collector and Portal
ps -ea|grep adop_collectord
ps -ea|grep adop_portald
ps -ea|grep adop_apm_proxyd
For Proxy
ps -ea|grep av_pgsqld
ps -ea|grep apm_elasticsearch
- (Windows) Run services.msc and verify that the services are running:
Check for errors reported in the App Visibility log files in the following locations:
- (Windows)
- server_installationDirectory\collector\logs\collector.log
- server_installationDirectory\portal\logs\portal.log
- server_installationDirectory\apm-proxy\logs\apm-proxy.log
- (Linux)
- server_installationDirectory/collector/logs/collector.log
- server_installationDirectory/portal/logs/portal.log
- server_installationDirectory/apm-proxy/logs/apm-proxy.log
Note
If a network port is occupied, the App Visibility server component stops, as reflected in the component log, but the log message does not give the reason.
- (Windows)
- Add App Visibility to the TrueSight console, if you have not already done so.
- Examine the portal status in the
Components
page of the TrueSight console.
Troubleshooting upgrade issues
If the upgrade fails, you must uninstall what has been installed before rerunning the installation wizard. For more information about the uninstall process, see Uninstalling the App Visibility server.
You can examine the App Visibility server log files located in the following directories:
- (Windows) %temp%\adopserver_install_log.txt
- (Linux) /tmp/adopserver_install_log.txt
Next step in the Upgrading process
Step 5 Phase B Task 1 — Now that you have successfully installed the App Visibility server, you must upgrade the applicable App Visibility agents.
Comments
Log in or register to comment.