Upgrade the Data Aggregator Installation

Upgrading › How to Upgrade CA Performance Management Data Aggregator - Command Line › Upgrade the Data Aggregator Installation - Command Line

Upgrade the Data Aggregator Installation - Command Line

Upgrading your existing installation of Data Aggregator lets you retain your custom profiles and configuration settings for the following features:

Vendor certifications
Vendor certification priorities
Note: New vendor certifications are placed at the bottom of the Vendor Certification Priorities list for the corresponding metric family. To take advantage of the new vendor certifications, manually change the vendor certification priorities. For example, F5 CPU vendor certifications are modeled as normal CPUs but do not get discovered because F5 also supports Host Resources. After an upgrade, the Host Resources CPU priority entry will be higher than the F5 entries appended to the end of the priority list. To discover F5 CPU devices and components, update the vendor certification priority for the CPU metric family. A fresh installation does not have this issue.
Monitoring profiles
Polling control configuration settings, as follows:
- Compiled MIBs
- Interface filter settings
- Any monitored devices and components that you discovered
- Any polled data that you gathered
- SNMP profiles
- Discovery profiles

The installation upgrade is installed without uninstalling the existing software. The installer detects whether there is an existing installation and confirms that you want to continue.

Important! Back up the Data Repository database before upgrading the Data Aggregator installation. Also, upgrade CA Performance Center before upgrading the Data Aggregator installation.

Follow these steps:

Log in to the computer where you plan to install Data Aggregator either as the root user or the sudo user.
Copy the installDA.bin file to a local directory. For the sake of installation instructions, we assume that the installer is placed in the /tmp directory, however, this location is not required.
Change permissions for the installation file by typing the following command:
```
chmod a+x installDA.bin
```
Type the following command to access the /tmp folder:
```
cd /tmp
```
To run the console installation, do one of the following steps:
- To run the installation as the root user, type the following command:
```
./installDA.bin -i console
```
- To run the installation as the sudo user, type the following command
```
sudo ./installDA.bin -i console
```
The License Agreement opens.
Read the license agreement, accept the agreement, and click Next.
When the installer prompts you, enter a user. This user will both own the installation and will be the user that Data Aggregator will run as.
Enter an installation directory when prompted.
The installer automatically calculates your maximum memory usage allocation for the Data Aggregator process and ActiveMQ broker. You can modify these values during or after the installation.
If prompted, enter the following parameters for Data Repository:

Data Repository server hostname/IP

Defines either a name or an IP address for the Data Repository server host.

Note: If you installed Data Repository in a cluster, specify the name or the IP address of any one of the three hosts that are participating in the cluster. The installer automatically determines the name and IP address of the remaining nodes.

Data Repository server port

Defines the port number for the Data Repository server.

Default: 5433

Database name

Defines the database name of Data Repository.

Data Repository username

Specifies the username that Data Aggregator uses to connect to the database. When installing Data Aggregator for the first time, you can specify a username and any password as long as the password does not match the username. This username and password combination is added to the database during installation.

Example: dauser

Data Repository admin username

Specify the Linux user account that was used to install Data Repository. This username is needed for administration, such as backing up and restoring Data Repository, or updating the database schema if it becomes out of synchronization. The example password that was used was dradmin.

Data Repository admin password

Defines the password for the Data Repository admin username.

Note: This database user account password was specified when you created the database after the Data Repository installation. The example password that was used was dbpassword.
When asked if you want the installer to recreate the schema, accept the default option. This question only applies to the case when your Data Repository has been used by a previous Data Aggregator installation.
The following table describes the Data Repository users that you created:

New User Example	Password Example	Operating System User Account?	Vertica Database User Account?
dauser	dapass	No	Yes
dradmin (This user was created during the Data Repository installation)	dbpassword Note: The password that is specified for this database will be the password for the database administrator.	No	Yes

New User Example

Password Example

Operating System User Account?

Vertica Database User Account?

dauser

dapass

Yes

dradmin (This user was created during the Data Repository installation)

dbpassword

Note: The password that is specified for this database will be the password for the database administrator.

Yes

The following results can occur:

If wrong information is entered, or if Data Repository is not accessible the console installer displays a message asking the user to either correct the wrong information or choose to exit.
If the database schema does not exist, the installer automatically creates the schema and the installation continues.
If the database schema is out of synchronization, the installer either cancels the installation or the installer recreates the schema. The installation continues, based on the options that you selected previously.
If the database schema is correct from an earlier Data Aggregator installation, the current installation continues.

When prompted, enter the HTTP port number for Data Aggregator. This number is the port number for accessing Data Aggregator using Data Aggregator REST web services and for downloading the Data Collector installer.
Default: 8581
When prompted, enter the SSH port for logging in to the Data Aggregator Apache Karaf shell for debugging purposes.
Default: 8501

Data Aggregator is installed.
Verify that Data Aggregator is installed:
- To verify that the installation was successful, review the information in the CA_Infrastructure_Management_Data_Aggregator_Install_timestamp.log file. This log file is located in the Logs subdirectory of the directory where you installed Data Aggregator.
- Verify that the Data Aggregator service is started and running. Open your web browser on a computer where you have HTTP access to Data Aggregator. Navigate to the following address:
```
	http://data_aggregator:port/rest
```
data_aggregator:port

Specifies the Data Aggregator host name and the required port number.

The return is a list of hyperlinks for available web services. When you click a link, such as Monitoring Profiles, the XML content describing the selection displays.
- Open a command prompt and type the following command to verify that the ActiveMQ broker is running:
```
/etc/init.d/activemq status
```
(New installations) Register Data Aggregator as a data source with CA Performance Center.
Note: For more information about registering a data source, see the CA Performance Center Administrator Guide.
Wait a few minutes for Data Aggregator to synchronize automatically with CA Performance Center. Alternatively, you can manually synchronize CA Performance Center and Data Aggregator if you do not want to wait for the automatic synchronization to occur.
Note: The installer restarts Data Aggregator automatically when the installation is complete.

More information:

How to Upgrade CA Performance Management Data Aggregator - Command Line