Verifying the upgrade

There are certain verification points that you can use to determine if the upgrade is successful.

About this task

Your self-signed certificate might not work after you upgrade because of the possible cypher changes in the newer version. If you can't login to the server after the upgrade and encounter the error ssl_error_no_cypher_overlap, regenerate your self-signed keystore by using the newer JDK that is bundled with the newer version.

Run diagnostics on each server and verify that the diagnostics completed successfully by following these steps.

Procedure

  1. Open a browser and log on to the admin page.
    https://host.example.com:port/jts/admin
  2. Click Diagnostics.
    Note: Lifecycle Query Engine and Report Builder have no Diagnostics section.
    Tip:

    Verify the server performance by running the database statistics after the upgrade.

Troubleshooting repair task for defect 139850

Problem: After upgrading Engineering Lifecycle Management applications, if the background data repair task for defect 139850 is running and is progressing slowly, it might result in performance issues.
Note: With Engineering Lifecycle Management 7.2, after upgrading applications, the background data repair task for defect 139850 doesn't run automatically and doesn't cause performance issues. This background repair task needs to be run on any Engineering Lifecycle Management application with the data dating back to 3.0.2 or earlier.

Solution:

  1. In the Admin > Advanced Properties page, find these two properties:

    • Defect 139850 repairer work period: This property value determines how long the task runs. The more value in seconds, the longer time it runs.

    • Defect 139850 repairer fixed delay: This property value determines how often it runs. If you increase this property value, it delays the run in effect.

  2. Ensure that the Defect 139850 repairer fixed delay property value is -1, which by default stops the repair task from running in background.