Complete the Upgrade

To complete the upgrade, complete the following procedures:
Re-Enable the Automatic Recovery of the Data Aggregator Process
Re-enable the automatic recovery of the data aggregator process. You disabled the automatic recovery before you upgraded the data aggregator. When enabled, if the database server runs out of memory, or if the data repository is unavailable for a time, the data aggregator shuts down automatically to help ensure that data consistency is maintained.
In a fault-tolerant environment, this procedure is unnecessary because Consul manages the start and stop state of the data aggregator.
For more information, see Fault Tolerance.
 
Follow these steps:
 
  1. Log in to the computer where the data aggregator is installed as the root user.
  2. Open a console and issue the following command:
    crontab -e
    A vi session opens.
  3. Uncomment out the following line by removing the pound symbol (#) from the beginning of the following line:
    # * * * * * /sbin/service dadaemon start > /dev/null
    For example:
    * * * * * /sbin/service dadaemon start > /dev/null
    The automatic recovery of the data aggregator process is re-enabled.
Perform Post-Upgrade Configuration
Do the following steps after you upgrade 
DX NetOps Performance Management
:
  • If you use the Java Cryptography Extension (JCE), upgrade the JCE to version 8.
    For the Java 8 version of the JCE, visit the Oracle site.
  • Upgrading the data aggregator backs up the
    /opt/IMDataAggregator/apache-karaf-<
    vers
    >
    directory to the
    /opt/IMDataAggregator/backup/apache-karaf
    directory. Customizations that are located in the
    /opt/IMDataAggregator/apache-karaf-<
    vers
    >/etc/
    directory, such as default logging levels or other configurations are backed up, but are not restored to the installation directory automatically. To avoid losing these customizations, restore the customizations manually after you have successfully upgraded.
  • Upgrading the data collector backs up the 
    /opt/IMDataCollector/apache-karaf-<
    vers
    >
    directory to the
    /opt/IMDataCollector/backup/apache-karaf
    directory. Customizations that are located in the
    /opt/IMDataCollector/apache-karaf-<
    vers
    >/etc/
    directory, such as default logging levels or other configurations are backed up, but are not restored to the installation directory automatically. To avoid losing these customizations, restore the customizations manually after you successfully upgraded.
Vendor Certification Priorities
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 is 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.
CA Business Intelligence
 Integrations
If you have an existing 
CA Business Intelligence
 (CABI) integration, this version of 
DX NetOps Performance Management
 supports CABI 6.4.2 and higher.
After you upgrade to a supported CABI version, you must re-install your CABI content.
For more information, see Install CA Business Intelligence Reports and Dashboards.
(Optional) Disable the ActiveMQ Admin Console for the Data Aggregator or Data Collector
Generally, the ActiveMQ admin console should not be available on the network. Therefore, you can disable it for the data aggregator or the data collector.
Follow these steps:
 
  1. Go to one of the following files:
    • The data aggregator
      DA_Install_Directory
      /broker/apache-activemq-
      version
      /conf/activemq.xml
    • The data collector
      DC_Install_Directory
      /broker/apache-activemq-
      version
      /conf/activemq.xml
  2. Comment out
    <import resource="jetty.xml"/>
    .
  3. Shut down the ActiveMQ broker on each data collector by issuing the following command:
    service activemq stop
  4. Shut down the ActiveMQ broker on the data aggregator by issuing the following command:
    service activemq stop
  5. Start the ActiveMQ broker on the data aggregator by issuing the following command:
    service activemq start
    If you do not, the data aggregator starts the broker automatically.
  6. The data collectors automatically restart the ActiveMQ brokers. Issue the following command to restart the brokers manually:
    service activemq start
(Optional) Update ActiveMQ Admin Console Access
Generally, the ActiveMQ admin console should not be available on the network. However, if certain users absolutely need the console, you can grant them access.
Follow these steps:
 
  1. Go to one of the following files:
    • The data aggregator
      DA_Install_Directory
      /broker/apache-activemq-
      version
      /conf/activemq.xml
       
    • The data collector
      DC_Install_Directory
      /broker/apache-activemq-
      version
      /conf/activemq.xml
       
  2. To update user access, edit the
    jetty-realm.properties
    file.
  3. To encrypt the user passwords, issue one of the following commands:
    • The data aggregator
      java -cp
      DA_Install_Directory
      /broker/apache-activemq-
      version
      /lib/web/jetty-all-9.2.22.v20170606.jar org.eclipse.jetty.util.security.Password
      password
      password
    • The data collector
      java -cp
      DC_Install_Directory
      /broker/apache-activemq-
      version
      /lib/web/jetty-all-9.2.22.v20170606.jar org.eclipse.jetty.util.security.Password
      password
      password
  4. Shut down the ActiveMQ broker on each data collector by issuing the following command:
    service activemq stop
  5. Shut down the ActiveMQ broker on the data aggregator by issuing the following command:
    service activemq stop
  6. Start the ActiveMQ broker on the data aggregator by issuing the following command:
    service activemq start
    If you do not, the data aggregator starts the broker automatically.
  7. The data collectors automatically restart the ActiveMQ brokers. Issue the following command to restart the brokers manually:
    service activemq start