Mandatory configurations
The installer does not update the configuration property files, so you need to configure them manually:
- Update the general.properties file by uncommenting and configuring the
navigation.panel.urlproperty (for example, http://worldserver.mycompany.com/ws) - 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)
- Other considerations
-
The following properties must have the same values across all WorldServer components:
session_timeoutuse_secure_urlstemp_file_path
Also, if you installed WorldServer through Tomcat, you should set the
session_client_check property in the general.properties file as follows:
- to
onin the %WS_CONFIG% and ws-legacy folders - to
offin the ws-api folder
on, the session_client_check property ensures that a session can only be used by the same browser that created it. If the same URL is used from another browser, the session is considered invalid and the user has to log in again. This applies to the legacy and TransPort components of WorldServer. As a security measure, in WorldServer 11.x, users always have to log in again if they copy the same valid URL into another browser. To enable the session_client_check property, your browser must accept cookies.