Configure the connections

• Maximum number of connections on the server:
  Maximum number of simultaneous connections allowed for all the sites managed by the administrator (a connection = a Web user).
• Maximum number of connections to a site:
  Maximum number of simultaneous connections allowed for each site managed by the administrator. This number can be modified for each site in the "Sites" tab.
• Maximum number of connections of a user to a site:
  Maximum number of simultaneous connections allowed for a given Web user to each site managed by the administrator.
  If this parameter is equal to zero, the Web user who tries to simultaneously connect to the same site will be automatically disconnected then reconnected.
  If this parameter is greater than zero, an error message will be automatically displayed after the x simultaneous connections.
  This number can be modified for each site ("Sites" tab).
  The option "A single connection automatically recycled" is used to limit the connection of a user to a single connection. The same connection will be re-used. To allow multiple connections from the same IP address (users through a router or proxy), select "Limit the number of connections to" and specify the number of connections allowed for the same IP address.

Configure the sessions and requests

• Disconnect the idle users since:
  This is the maximum connection time allowed without any action performed by the Web user. When this time is exceeded, the Web user is automatically disconnected and an error message is displayed.
  This number can be modified for each site in the "Sites" tab.
• Duration of AWP contexts:
  Validity period of AWP contexts. As soon as the specified duration is over and if no new request was performed, the context file is deleted. See AWP: Managing contexts for more details.
• Versions 16 and later
  Duration of webservice contexts:
  Validity period of webservice contexts. As soon as the specified duration is over and if no new request was performed, the context file is deleted. See Generating a webservice for more details.
  New in version 16
  Duration of webservice contexts:
  Validity period of webservice contexts. As soon as the specified duration is over and if no new request was performed, the context file is deleted. See Generating a webservice for more details.
  Duration of webservice contexts:
  Validity period of webservice contexts. As soon as the specified duration is over and if no new request was performed, the context file is deleted. See Generating a webservice for more details.
• Maximum request duration:
  Maximum time-out allowed between the beginning of an action performed by the Web user (via a button or a link) and the display of a response. When this time is exceeded, an error page is displayed but the Web user is not disconnected.
• Versions 18 and later
  Maximum task duration:
  Used to limit the runtime duration of a WEBDEV scheduled or delayed task. The task will be automatically stopped when this duration is exceeded.
  See WEBDEV: Scheduled tasks and delayed tasks for more details.
  New in version 18
  Maximum task duration:
  Used to limit the runtime duration of a WEBDEV scheduled or delayed task. The task will be automatically stopped when this duration is exceeded.
  See WEBDEV: Scheduled tasks and delayed tasks for more details.
  Maximum task duration:
  Used to limit the runtime duration of a WEBDEV scheduled or delayed task. The task will be automatically stopped when this duration is exceeded.
  See WEBDEV: Scheduled tasks and delayed tasks for more details.
• Number of pre-launched sessions (available for the WEBDEV application server only):
  Used to optimized the connection time to the WEBDEV sites managed by the server. Whenever a Web user connects to a site, a session is started on the server. Starting the session may take a few seconds.
  If a number of pre-launched sessions is defined, when a Web user connects to a site:
  - one of the pre-launched sessions is automatically used: therefore, the connection to the site is faster.
  - a new session is automatically pre-launched.
  Versions 20 and later
  Allow the pre-launched sessions: This option is used to manage the cached sessions on the WEBDEV application server. This option is used to optimize the connection time to the WEBDEV sites and Webservices found on the server. If this option is checked, you must:

  • modify the project to manage the pre-launched sessions properly. See The cached sessions for more details.
  • configure the site or the webservice in order to specify the number of necessary pre-launched sessions ("Sites" or "Webservices" tab, "Parameters" button).
  New in version 20
  Allow the pre-launched sessions: This option is used to manage the cached sessions on the WEBDEV application server. This option is used to optimize the connection time to the WEBDEV sites and Webservices found on the server. If this option is checked, you must:

  • modify the project to manage the pre-launched sessions properly. See The cached sessions for more details.
  • configure the site or the webservice in order to specify the number of necessary pre-launched sessions ("Sites" or "Webservices" tab, "Parameters" button).
  Allow the pre-launched sessions: This option is used to manage the cached sessions on the WEBDEV application server. This option is used to optimize the connection time to the WEBDEV sites and Webservices found on the server. If this option is checked, you must:
  • modify the project to manage the pre-launched sessions properly. See The cached sessions for more details.
  • configure the site or the webservice in order to specify the number of necessary pre-launched sessions ("Sites" or "Webservices" tab, "Parameters" button).

Manage the remote debugging

• Main port (27 271 by default).
• Range of ports for sessions (between 27 282 and 27 289 by default).