In a distributed deployment, each Harvester is installed on a separate server. To upgrade a Harvester on a dedicated Windows server or virtual machine, complete the steps in this topic. These steps apply to a two-tier or three-tier distributed deployment.
Before You Begin: Verify that the server is upgrade-ready as described in Verify Preparation of the Windows Servers.
Follow these steps to prepare the NFA console server for the Harvester upgrade:
The Console tool prepares the system for the upgrade.
java -jar consoletool-exe.jar
To launch the Console tool by double-clicking the file, Windows Explorer must have the correct association for .jar files.
The ConsoleInfoToPollerTool<yyyy-mm--dd>.log file opens when the Console tool completes--whether the tool completes successfully or fails. The log is saved in the <install_path>\Reporter\Logs\ directory.
The Console tool cannot complete successfully if the system has undeployed interface aggregations or unscheduled merge or delete interface tasks. If the tool does not complete successfully, note the error messages in the log file and contact CA Support.
The service stops.
Follow these steps to upgrade the Harvester:
A check verifies that the server has a supported version of the Java Runtime Engine (JRE) installed. If the check fails, an error message opens. You cannot launch the installation or upgrade program until this problem is corrected.
If the server passes the Java prerequisite check, the program starts and the language selection screen opens.
A check verifies whether the installed version of CA Network Flow Analysis is supported for upgrade. If a supported version is found, the Prior Installation Detected message opens.
The Welcome screen opens.
A check verifies that the Console tool completed successfully on the NFA console server. If the tool did not run successfully, an error message opens and the upgrade stops.
If the server passes the check, the CA NFA Harvester License Agreement screen opens.
Prerequisite tests are run to identify problems on the server. If a problem is found, an error message opens. A critical problem causes the upgrade program to exit. If the problem is not critical, the Pre-requisite Check Warning message or other warning message opens, which gives you the option to make corrections now or after the upgrade is complete.
Once the server passes the required checks and you close any noncritical messages that appear, the Choose Install Folder screen opens. This screen displays the original root installation path as the default setting.
Once the server passes the required checks successfully and you dismiss any warnings that appear, the Choose Install Folder screen opens. This screen displays the original root installation path as the default setting.
Important: If you do not use the original installation path, the upgraded software will not run properly.
If the program does not find certain expected directories in the installation path, an error message opens and the upgrade stops. This problem does not occur when the previous software installation is fully functional.
The Pre-Installation Summary screen opens.
The Installing Harvester screen opens, which shows the upgrade progress. When the upgrade is complete, the Install Complete screen opens and reports any errors that occurred.
The upgrade program closes after a moment. If you selected the option to restart now, the system restarts and the upgrade is finalized.
Next:
Copyright © 2013 CA.
All rights reserved.
|
|