Validate your upgrade to make sure that your new WorldServer instance works as expected.
Procedure
Make sure that the WS_HOME environment variable points to your WorldServer installation.
Note: If you set WS_HOME to a location that has spaces in the name, you cannot use quotes around your path when you define it. Use a path such as WS_HOME=C:\Program Files\Idiom\WorldServer\Tomcat\webapps\ws-legacy. Do not surround the path with quotes.
For Tomcat deployments, make sure your TOMCAT_HOME and CATALINA_HOME environment variables are set as well.
For Windows:
set WS_HOME=<TOMCAT_HOME>\webapps\ws-legacy
set CATALINA_HOME=<TOMCAT_HOME>
If applicable, set execute permissions on the wsupgrade scripts:
cd <upgrade directory>
chmod 777 testschema.sh
Run the testschema script to validate the new version of WorldServer with the upgraded database.
For Windows: upgrade\1132\testschema.bat > testschema.log
For Linux: upgrade/1132/testschema.sh > testschema.log
You can find the testschema script in the upgrade folder of the version to which you are upgrading. For example, if you are upgrading to WorldServer 11.3.2, you can find it in the upgrade\1132 folder of the WorldServer distribution kit. The testschema script verifies all the steps of the incremental upgrade process. It also verifies that the entire schema complies with the latest version of WorldServer.
The output is redirected to a log file. Check it to see whether the schema test succeeded.
What to do next
Start WorldServer, verify if it works as expected, and inform your users that WorldServer is working again.