Configuring WorldServer
To be able to log in to WorldServer and to make WorldServer available to your users, you must configure settings for areas such as security, single sign-on, or database connections in various .properties files. After you finish configuring these settings, make sure that you stop WorldServer and start it again, so that your changes take effect.
- Configuration overview
Starting with version 11.0.1, WorldServer consists of three components: the WorldServer 11 interface (ws), the new REST API (ws-api) and the legacy application (ws-legacy). In previous (10.x) versions, you could specify a certain configuration value only in one place (i.e. classpath). However, starting with version 11.0.1, you can customize configuration files in different locations. This is the best way of managing settings in WorldServer 11.x. - Mandatory configurations
A list of settings that you must configure for WorldServer to work properly. Almost all of these settings are in the general.properties file. - Security settings and connections
WorldServer addresses security concerns in several ways. - Configuring general login and session settings
These settings have to do with aspects such as the session timeout or the way in which users can recover forgotten passwords. - Session synchronization in WorldServer
There are two types of user sessions in WorldServer: a back-end session (the WorldServer legacy session) and a UI session (managed by Spring). The two sessions are synchronized through calls to the REST API and thesession.synchronization.rateproperty in the ui.properties file determines when those calls are made. - Implementing single sign-on
Starting with version 11.4, WorldServer contains a layer that you can use to integrate your company's single sign-on (SSO) solution with WorldServer. In a typical single sign-on authentication scenario, users select Internal Sign In on the WorldServer login page. WorldServer directs users to your company's identity provider (IDP), users authenticate with their company credentials, and then the identity provider takes users directly to the WorldServer page configured in the authenticator. - Enabling entity history and stats engine logging
Starting with WorldServer 11.1.1, two new logging categories have been added for user assignments—a history category and a stats engine category. If you enable them, you can view information about their corresponding actions either in the default WorldServer log file or in separate log files. - Enabling the new Workflow Editor
Enabling the new Workflow Editor involves adding a new property in the general.properties and ui.properties files. By doing so, you are replacing the previous applet-based editor with a modern, plugin-free version that you can open on all supported browsers. - Configuring human action servlets on the WorldServer 11 interface
Configuring human action servlets to work on the WorldServer 11 interface involves uploading them into WorldServer, using them in a workflow, and creating projects that use that workflow. - TCP/IP configurations with SSL/TLS for database connections
WorldServer ensures an additional layer of security to your information by offering support for encoded client-server communication. The specific WorldServer, File Type Support (FTS) Server, and JasperReports Server configurations are different depending on the type of relational database management system you use (Microsoft SQL Server or Oracle). - Connection string configurations for Azure SQL Database
A series of configurations required to run WorldServer, JasperReports Server, and the File Type Support (FTS) Server on Azure SQL Database, which is supported starting with WorldServer 11.7.2. - Configurations for clustered environments
Clustered WorldServer application machines share a common database. The settings in the general.properties file on each system tell WorldServer how to handle clustered activities. - Configuring notification delivery
To make sure that automatic email notifications are sent successfully, you need to perform several steps both within WorldServer (e.g. configure notification delivery settings) and in the general.properties file (e.g. turn on the notification engine). - Configuring Live TM mode
As of WorldServer 9.0, you can choose how you want users to update translation memories: either dynamically, as they translate (Live TM mode) or statically, when they select a button (Non-Live mode). By default, WorldServer runs in Live TM mode, because this enables users to share the same translation memory in real time or near-real time. - Logging and terminating abandoned connections
In WorldServer, you can log and identify which connections have been idle or abandoned by using the general.properties file. The general.properties file also contains values that you need to change to have WorldServer monitor and log events according to your needs. - Configurations for importing and exporting translation kits
The exchange.properties file is a Java properties file through which you can configure the behavior of the import and export features in WorldServer. - Specifying names for WorldServer connection pools
Starting with WorldServer 11.5, you can name the main connection pool of each application (ws, ws-legacy, and ws-api) differently through a property calledconnection_pool_name. By doing so, you can also configure each application to have a different maximum number of connections. - Increasing the Java heap size allocated to WorldServer
When you upgrade to WorldServer 11.8 or later by using the new installer, the default Java heap size allocated to WorldServer is of 4 GB, but you can increase this value according to the requirements and capabilities of your environment. - 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.