Resolution for Root Cause 1:Run all the database upgrade scripts to upgrade the WorldServer database to the installed version.
Resolution for Root Cause 2:There are two possible causes for this scenario.
1- Per the
WorldServer documentation in the section titled
Installing and configuring WorldServer, the
ws.api.url and
ws.legacy.url values must be configured in the
ui.properties file located in the
WS_CONFIG folder.
The installer does not update the configuration property files so they need to be manually configured.
Update the
ui.properties file by uncommenting and configuring the following properties:
ws.legacy.url
(for example, http://worldserver.mycompany.com/ws-legacy)ws.api.url
(for example, http:// worldserver.mycompany.com/ws-api) ws.api.version
(for example, v1)
In this scenario the
ui.properties file was placed in the
WS_CONFIG location and both the
ws.legacy.url and
ws.api.url were included in the file.
Once the
ui.properties file is corrected, restart the Idiom service and the error message will not display. The user will be able to successfully login to
WorldServer.
Resolution for Root Cause 3:Another possible cause of this error is a
mismatch of the database entries between different property files.
In one case the database entry in
general.properties under
WS_CONFIG was different than the database entry in
general.properties under
WS_CONFIG\ws-api.
For example:
WS_CONFIG\general.properties:
database=jdbc:idiom:oracle://OracleSrv1:1521;SID=MyDB01;AlternateServers=(OracleSrv2:1521)
WS_CONFIG\ws-api\general.properties:
database=jdbc:idiom:oracle://OracleSrv1:1521;SID=MyDB01
This causes a failure where the client fingerprint cookie doesn't match up. For more information on the client fingerprint, check the Oracle documentation.
Resolution for Root Cause 4:Refer to this article for resolution steps:
Error 'WorldServer API not available' in New UI and 'Unable to find valid certification path to requested target' in WorldServer logs.Resolution for Root Cause 5:For this case the mandatory settings that are found in theregistry must be also deployed in ws-Confi/ws-api. These settings are all four settings related to the Database and the two settings related to the the temp folder.
Note: This defect has been addressed as of WorldServer 11.5