Completing and verifying the IBM FileNet Content Manager upgrade

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

To verify your upgraded containers

• Check the status of the Content Platform Engine services:
  1. In the OpenShift or Kubernetes console information for Networking, locate the Content Platform Engine route or Ingress instance, for example, myproject-cpe-route.
  2. Click Launch HTTPS to open the URL that displays the hostname that represents the service.
  3. 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.
  4. 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 FileNet P8 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 External Share upgrade:
  • For user management with an Identity Provider:

    UMS

    Verify your registrations.

    1. Go to https://<your_ums_url>/oidc/endpoint/ums/registration.
    2. Log in with your UMS admin credentials, specified when you created your secret.
    3. Verify that Content Platform Engine, Navigator, and External Share are all registered with UMS.
       The new Ingress routes must contain:

       • New Ingress URL
       • Open Shift Cloud Platform route URL
       • Service URL
    4. Verify that the "client_id" matches the ID in the new oidc.xml and idp-oidc.xml that was generated by the operator.
       You can use the following commands to check:

       oc get pods -n <namespace>
        

       oc exec -it <pod name> bash -n <namespace>

       cd /opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides
       

       cat oidc.xml

       cat idp-oidc.xml

    Identity Provider

    Edit the redirect URL in your chosen Identity Provider. For example, update the URL in your Google application to add the new Ingress URL.

    Ingress

    Optionally delete the ingress.yml file that was created in the previous version:

    kubectl delete -f ingress.yaml

    This command removes the routes.

  • For user management with 2 LDAP realms:
    1. In the configDropins/overrides folder for Content Platform Engine, Business Automation Navigator, and External Share, delete the following files:

       zcustom-ssl.xml
       custom p12

    2. Delete the ingress.yml file that was created in the previous version:

       kubectl delete -f ingress.yaml

       This command removes the routes.

  • For all External Share configurations, update the External Share settings in the Administration Console for Content Platform Engine to use the new Ingress URL:
    1. In the Administration Console for Content Platform Engine, navigate to Object Store > Search > New Object Store Search.
    2. In the Class drop down menu, choose Share configuration, and click Run.
    3. Click the Share Configuration ID, and on the Properties screen, in the Share Configuration Details field, change the value for the shareURL to the new Ingress URL.