4.1.3.1 Verification of Configuration Data

This procedure checks the configuration data of the system and servers to ensure a successful upgrade.

4.1.3.1 Active NOAM VIP: Verify Application Version

  1. Navigate to Administration, then Software Management, then Upgrade.
  2. Verify if the upgrade path to the target release is supported as documented in Supported Upgrade Paths to 8.6.0.7.0.
  3. Select the NOAM Server Group and verify the Application Version.

4.1.3.1 Active NOAM CLI: Check if the setup has customer supplied Apache certificate installed and protected with a passphrase

  1. Use the SSH command (on UNIX systems – or putty if running on windows) to log into the active NOAM ssh admusr@<NOAM_VIP> password: <enter password> Answer yes if you are asked to confirm the identity of the server.
  2. cd to /etc/httpd/conf.d and open the file named ssl.conf.
  3. Locate the line beginning with the phrase SSLCertificateFile.
  4. The path that follows SSLCertificateFile is the location of the Apache certificate. If the path is /usr/TKLC/appworks/etc/ssl/server.crt, then the certificate is supplied by Oracle and no further action is required. Continue with the next step.
  5. If the path is anything other than /usr/TKLC/appworks/etc/ssl/server.crt, then a customer-supplied Apache certificate is likely to be installed. Rename the certificate, but note the original certificate pathname for use in Verify NOAM Post Upgrade Status.

    Note:

    The following data collection procedures collect similar data. However, the collection method varies depending on the source release. Only Data Collection for Source Release 8.0 and Later procedure is to be executed for the pre-upgrade data collection.