WEBDEV administrator: General configuration

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

Overview
Details of "Configuration" tab
Configure the connections
Configure the sessions and requests
Manage the remote debugging

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

WEBDEV administrator: Overview

WEBDEV administrator: General configuration

Overview

The "Configuration" tab is used to define the default connection options for the WEBDEV sites found on the server and managed by the administrator.

Details of "Configuration" tab

The "Configuration" tab is used to:

Configure the connections.
Configure the sessions and requests.
Manage the remote debugging.

Configure the connections

The following options can be used to 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 on 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 user connections on a site:
Maximum number of simultaneous connections allowed for a given Web user to each site managed by the administrator.
- If this parameter is set to zero, the Web user who tries to connect simultaneously 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 validate the settings of connections, click the "Apply" button. The new settings are automatically taken into account.

To cancel the modifications, click the "Restore" button.

Configure the sessions and requests

The following options can be used to configure the connections:

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.
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.
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.
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.
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.
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 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 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 configure the site or the webservice in order to specify the number of necessary pre-launched sessions ("Sites" or "Webservices" tab, "Parameters" button).

To validate the settings of connections, click the "Apply" button. The new settings are automatically taken into account.

To cancel the modifications, click the "Restore" button.

Manage the remote debugging

The WEBDEV administrator can allow (or not) the remote debugging of dynamic WEBDEV sites.

If the remote debugging is allowed ("Allow remote debugging" is checked), the following parameters must be specified:

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

The "Default" button is used to restore the default values.