Applying feature packs or fix packs on the App Visibility server silently

Where you are in the Applying-feature-packs-or-fix-packs process

To silently apply a feature pack or fix pack on the App Visibility server

On the computer where you want to apply the feature pack or fix pack to the App Visibility server component or components, extract the downloaded files to a temporary directory.
Open the downloaded options file in a text editor:
- (Windows) adop-silent-option-upgrade.txt
- (Linux) adop-silent-option-upgrade
(For App Visibility collector or proxy) If you apply the feature pack or fix pack to the App Visibility collector or proxy on a computer that does not have the App Visibility portal installation, you can update the App Visibility portal connection information.
For example, if you are upgrading to a high-availability environment from an environment that is not HA, use these values to enter the IP address and port number of the load balancing server for the App Visibility portal.
If you apply the feature pack or fix pack to the portal on the same computer as the collector, proxy, or both, the portal parameters are ignored for that process.
-J portal_ip=
-J portal_communication_port=
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
(For portal or collector, upgrade to high-availability)
- If you do not want to set up your environment for high availability, or if it is already set up for HA, skip to Step 6.
- To set up a high-availability environment, set ha_enabled to true and enter values for the current component and alternate component.
  The following example displays values for a collector in a high-availability environment.
  -J ha_enabled=true
  -J ha_current_node_fqdn=myCollectorA.bmc.com
  -J ha_current_node_port=8202
  -J ha_alternate_node_fqdn=myCollectorB.bmc.com
  -J ha_alternate_node_port=8202
  -J ha_alternate_node_db_port=8800
  Parameter descriptions for the portal or collector's alternate component
  The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
(For collector, upgrade to high-availability ) Enter values for the load balancer that manages access to the collector:
-J ha_lb_host=
-J ha_lb_port=
Parameter descriptions for the collector's load balancer
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
Save and close the options file.
To apply the feature pack or fix pack silently, enter the following command:
- Windows
  setup.exe -i silent -DOPTIONS_FILE=<fullFilePath>\adop-silent-option-upgrade.txt
- Linux
  ./setup.bin -i silent -DOPTIONS_FILE=<fullFilePath>/adop-silent-option-upgrade

Troubleshooting the feature pack or fix pack application

If the feature pack or fix pack is successful applied, an indication is displayed in the command window.
If the feature pack or fix pack application fails, you must uninstall what has been installed before rerunning the process. For more information about the uninstall process, see Uninstalling-the-App-Visibility-server.
You can examine the App Visibility server log files are located in the following directories:
- (Windows) %temp%\adopserver_install_log.txt
- (Linux) /tmp/adopserver_install_log.txt

To verify the App Visibility server after applying the feature pack or fix pack

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.txt file, which is located in the %temp% directory (Windows) or /tmp directory (Linux).
Check for warnings or errors. If no error messages are present, the installation was successful.
According to what you have upgraded, verify that the App Visibility server components are running.
- (Windows) Run services.msc and verify that services are running:
  - BMC App Visibility Collector
  - BMC App Visibility Portal
  - BMC App Visibility PostgreSQL
  - BMC App Visibility Proxy
- (Linux) Run the following commands to verify that the processes are running:
  ps -ea|grep adop_collectord
  ps -ea|grep adop_portald
  ps -ea|grep adop_apm_proxyd
  ps -ea|grep av_pgsqld
Check for errors reported in the App Visibility log files in the following locations:
- Windows
  - serverInstallationDirectory\collector\logs\collector.log
  - serverInstallationDirectory\portal\logs\portal.log
  - serverInstallationDirectory\apm-proxy\logs\apm-proxy.log
- Linux
  - serverInstallationDirectory/collector/logs/collector.log
  - serverInstallationDirectory/portal/logs/portal.log
  - serverInstallationDirectory/apm-proxy/logs/apm-proxy.log
Examine the portal status in the Components page of the TrueSight console.

Where to go from here

Step 4 Phase B Task 1 — Now that you have successfully installed the feature pack or fix pack on the App Visibility server, you must install it on the applicable App Visibility Agent.