Verifying and troubleshooting the server rename

The verification and troubleshooting steps for server rename are listed. These steps are performed after the successful completion of sever rename.

There are two primary parts to server rename verification:

Running the server rename verification wizard.
Performing final verification for the Jazz® Team Server, IBM® Engineering Lifecycle Management applications, other common components and integrations.

Checklist for application verification:

Perform verification for each application. Refer to Completing the server rename verification process
Ensure that existing project areas and artifacts are accessible.
Run diagnostics tests for each Engineering Lifecycle Management application. Refer to Repository tools command to run diagnostics on the server. Run the following command for containers
```
cd /elm/server/
./repotools-jts.sh -executeDiagnostics zipOutputFile=/elm/server/conf/myServerDiagnostics.zip
```

The Deployment Events section in operator with the Engineering Lifecycle Management setup and the Engineering Lifecycle Management post setup conditions must be completed.
Application Events shows that all applications are ready.

If the pods are not in ready state after completing the Server-rename: Reset the pod by deleting it. Upon deletion a new pod is created which eventually goes into ready state if there are no problems. However, if the POD does not come into ready state; review the teamserver.properties for missed configurations.
JTS page shows server-rename has not started but the appServerStatus (e.g. https://staging.example.org/<application-name>/appServerRenameStatus) page of all applications says 100% complete then Restart the JTS pod and check if the teamserver.properties are correct.
If the LQE application route is not accessible after completing the server rename, to troubleshoot indexing issue refer to Cleaning the database and indexes for LQE