Skip to main content
Close announcements banner

Prerequisites to configuring execution servers

Information noteNote: Only users that have the Operation Manager role and rights can have read-write access to this page. Other users, depending on their roles, can have either read-only access or no access to this page.
  • Before you can launch any of the execution tasks you have scheduled, you need to configure the servers on which you will deploy them. Ensure that the script is running on the execution server to be able to deploy the task.

    Note that server rates are based on indicators, whose bounds (such as free disk space limits) and weight are defined in the file: monitoring_client.properties which is located in <ApplicationPath>\WEB-INF\lib\org.talend.monitoring.client-A.B.C_rYYYYY.jar. These constraints are used to calculate a usage value based on outbound values, and to determine which server to be used for load balancing (cluster mode).

    • 100: server availability is optimal, indicator values are within bounds,
    • < 100: one or several indicators' values are out of bound.

    For more information on how to edit the monitoring_client.properties and overwrite the default values, see Installing and configuring your Talend JobServer.

  • Make sure the execution server version is compatible with the Talend Administration Center and Talend Studio versions. For more information, see Compatible execution servers.
  • For users working in cluster mode via virtual servers, note that the ranking of servers to be used for load balancing is based on indicators, whose bounds (such as free disk space limits) and weight are defined in the monitoring_client.properties file which is located in <ApplicationPath>\WEB-INF\lib\org.talend.monitoring.client-A.B.C.jar. These values can be edited according to your needs. For more information, see Configuring the indicators which determine which server to be used for load balancing.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!