Worldsoft Documentation Search

Configuring – ESMJobRunner.exe.config

The ESMJobRunner.exe.config file stores several configurable values that are used by the ESM.net Job Runner service.  The default values are shown below:

<connectionStrings>
<add name=”ESMJobRunner.Properties.Settings.esm_conn” connectionString=”Server=LOCALHOST\MSSQL2012; Database=es_manager_xxx; User ID=esm_sql_server_user; Password=esm_sql_server_password;” />
</connectionStrings>
<userSettings>
<ESMJobRunner.Properties.Settings>
<setting name=”polling_frequency” serializeAs=”String”>
<value>5</value>
</setting>
<setting name=”error_connect_sleep” serializeAs=”String”>
<value>60</value>
</setting>
<setting name=”procedure_timeout_hours” serializeAs=”String”>
<value>3</value>
</setting>
</ESMJobRunner.Properties.Settings>
</userSettings>

Note: The dark orange text represents values that are configurable:

  • Server: Represents the server name, IP address, or SQL Server instance name.  Please note that if non-standard ports are used (other than 1433), please specify the port like so: Server=YourServerName,1234
  • Database: The database to connect to. Note: All ESM.net databases will have a short suffix after es_manager representing the organization.  Ex: es_manager_abc
  • User ID: The SQL Server ID which has access to the es_manager_xxx database.  It must have the db_esm_server_role to function properly
  • Password: The SQL Server password for the above user.
  • polling_frequency: Frequency that the ESM.net Job Runner checks the database for new jobs (in seconds).  5 second interval is recommended.  This check only fires if there are no jobs currently processing
  • error_connect_sleep: If the database goes down or any other type of unexpected error happens, the service will go to sleep for the number of seconds specified before attempting to re-connect to the database.  The default value is 60 seconds
  • procedure_timeout_hours: When a procedure is called from .NET, there is a default timeout applied to it.  Generally the timeout would be small, but the Job Runner was built to run long-running jobs behind the scenes.  A few of our jobs are very large on systems with very large databases, so sometimes this timeout will need to be increased.  The default is 3 hours and unless WSI configures it otherwise it should stay at this value.