Verifying the upgrade

After you upgrade your deployment of your Content Cortex environment, you must verify that your upgraded applications work with the rest of your container environment.

To verify your upgraded containers

• Complete and verify the Content Platform Engine services:
  1. Location your deployments access routes / ingress, for more information see topic Accessing your deployment .
  2. Check the Content Platform Engine Startup Context (Ping Page).
     Browse to https://hostname/FileNet/Engine, where hostname represents the route to the Content Platform Engine deployment.
  3. Check the automatic upgrade status for Content Platform Engine data.
     Enter the URL for the automatic upgrade status page into your browser https://hostname/FileNet/AutomaticUpgradeStatus. Review the status for the Content Cortex domain and object stores.
• Complete and verify the Content Search Services upgrade:
  1. Re-enable text indexing for the object stores. For more information, see the following topic: Starting the IBM Content Search Services index dispatcher .
  2. Verify your Content Search Services upgrade by using the following instructions: Verifying the IBM Content Search Services upgrade .
• Complete and verify the IBM Navigator upgrade.
• Location your deployments access routes / ingress, for more information see topic Accessing your deployment .
• Verify that you can access IBM Content Navigator at the following URL: https://hostname/navigator.
• Verify that the Content Platform Engine server information is correct:
  1. Log in to the Navigator admin desktop: https://hostname/navigator/?desktop=admin
  2. Navigate to Repositories.
  3. Select the repository, and click Test Connection to verify the communication with the Content Platform Engine services are functional.
  4. If the test fails, click Edit and change the Server URL value to update to the new cpe service value, typically myproject-cpe-svc, for the upgraded deployment.
• If your configuration includes External Share, re-load and re-configure the External Share plug-in.
• Use of operator-shared-pv during the upgrade.

  During the upgrade process, the Content operator continues to use the JDBC driver files provided during for the down-level deployment using the operator-shared-pv. Any other optional files provided using the operator-shared-pv are also retained. As a new Content operator feature, the operator requires a URL to an accessible web server to download the necessary files from. You should perform an update to the deployment to incorporate this feature as soon as possible to avoid future issues. For information, see topic Preparing customized versions of ICCSAP libraries.