Other configurations

In addition to the mandatory configurations, there are other settings in the general.properties file that will improve your WorldServer experience, whether you installed WorldServer with the Windows installer or manually, through Apache Tomcat.

PropertyDescription
url_of_originFind this property and modify its value to include the URL to the root of the WorldServer application under the application server. For example: url_of_origin=http://worldserver.company.com:8080/ws-legacy

This URL is used in various places in WorldServer, such as email notifications or translation kits. The hostname in the URL should be a host that can be resolved and that WorldServer users can access.

Do not use localhost or an IP address as a hostname. If you do not configure the value of this property, users will have to set it manually in their client each time they want to upload a project back to the server from SDL Trados Studio.

zip_encodingWorldServer uses UTF-8 encoding to encode file names in .zip archives. However, some localized versions of Windows use different encodings to read .zip archives. If the encodings do not match, the extracted file names may be corrupt. To avoid this issue, configure WorldServer to use the same encoding as your localized system.

Search for the zip_encoding property and change it from the default (UTF-8) to the encoding of your local system. For example, Kanji or Katakana use MS932. The default Windows ZIP compression does not support UTF-8; therefore, you should not use it.

file_attribute_storageBy default, Attachment-type attributes are stored in the WorldServer temp folder. However, you might not want them stored in the temp folder, because that folder gets cleaned up periodically.

To configure WorldServer to store these attachments elsewhere, uncomment the file_attribute_storage property and specify a more suitable location. If you are using WorldServer in a clustered environment, all the machines in the cluster must have access to this location.

calculate_segment_length_in_bytesThis property determines whether WorldServer measures segment length in bytes or in characters. By default, the length is measured in characters.

To enable length calculation in bytes, uncomment the calculate_segment_length_in_bytes property and set its value to true. The property only applies to the maximum segment length limit functionality and it works in combination with the value of the maximum_target_length_penalty property, which you can set in the tm.properties file.

adhoc_asset_timeoutThis property schedules the removal of obsolete data from your database when you create translation projects from WorldServer Explorer. By default, this property is disabled (set at zero days).
workbench_generate_targetThis property manages the automatic generation of target files. By default, it is enabled. To disable it, uncomment the following line: #workbench_generate_target=false
security.password.encryption.algorithmBy default, WorldServer uses PBKDF2 (Password-Based Key Derivation Function 2) for password encryption. You can configure a different type of password encryption by changing the value of the security.password.encryption.algorithm property.
prefer_shallow_soap_objectsThis property was added in WorldServer 10.4.5. When you add it and set its value to true, it addresses an issue related to poor performance and high memory usage caused by web services deep copies for heavy duty resources. This property will use shallow copies (which do not expand embedded resources) for the following resources: WSGroup, WSClient, WSRole, WSLocale, WSWorkgroup, WSProject. It is recommended for systems that integrate with Tridion Sites and Tridion Docs.

By default, this property is disabled (=false), because some integrations may rely on web services deep copies. To enable it, you need to add it: prefer_shallow_soap_objects=true

Read the comments in the general.properties file to see the entire range of available properties.