Documentation Center

Configuring .properties files

WorldServer reads many system settings from configuration (.properties) files that are installed on the WorldServer application server. For WorldServer to work properly, you must configure these settings correctly before starting the application server.

Prior to WorldServer 11.0, the configuration files were loaded from classpath:config. Starting with version 11.0, the system checks the WS_CONFIG folder first, looking for the subfolder with the application name (ws-legacy, ws-api, or ws). In case it does not find it there, it goes to classpath:config.

In the ui.properties file, located in the WS_CONFIG\ws folder, set the value of the ws.api.url property to the publicly available address of the application server.

The following properties must have the same values across all WorldServer components:
  • session_timeout
  • use_secure_urls
  • temp_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 on in the %WS_CONFIG% and ws-legacy folders
  • to off in the ws-api folder
When you set it to 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.