Step 5: Site parameters

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

Help

Editors

Installing applications and sites

WEBDEV site

Wizard steps

Step 5: Site parameters

Overview

Configuring the site

Site security

Generating site statistics

See also

Step 5: Site parameters

Overview

The site parameters are used to configure the options for connecting to the site as soon as it is installed. These parameters can be modified if necessary:

by the deployment administrator found on the server.
by the remote administrator, that can be used by the site manager.

Configuring the site

The deployment parameters are as follows:

Activate the site at the end of setup:
The site will be available once it has been installed: you will be able to connect by using the proper address.
If this option is not checked, the site can be activated via the remote administrator.
Perform a backup of the site before the update:
For an update, allows you to save the existing site. You have the ability to "delete the backup after a successful update".
Schedule deployment for a later date:
In this case, the deployment will be performed at the specified date and time. See Immediate or delayed setup for more details.

The site parameters are as follows:

Disconnect the idle users since: (when deploying a dynamic WEBDEV site only)
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.
Versions 17 and later
Duration of AWP contexts: (when deploying an AWP WEBDEV site only)
Validity period of AWP contexts for the site. As soon as the specified duration is over and if no new request was performed, the context file is deleted. See AWP: Managing the contexts for more details.
New in version 17
Duration of AWP contexts: (when deploying an AWP WEBDEV site only)
Validity period of AWP contexts for the site. As soon as the specified duration is over and if no new request was performed, the context file is deleted. See AWP: Managing the contexts for more details.
Duration of AWP contexts: (when deploying an AWP WEBDEV site only)
Validity period of AWP contexts for the site. As soon as the specified duration is over and if no new request was performed, the context file is deleted. See AWP: Managing the contexts for more details.
Versions 20 and later
Maximum task duration:
Maximum duration for running the scheduled or delayed tasks. If the tasks used exceed this duration, they will be automatically stopped. See WEBDEV: Scheduled tasks and delayed tasks for more details.
New in version 20
Maximum task duration:
Maximum duration for running the scheduled or delayed tasks. If the tasks used exceed this duration, they will be automatically stopped. See WEBDEV: Scheduled tasks and delayed tasks for more details.
Maximum task duration:
Maximum duration for running the scheduled or delayed tasks. If the tasks used exceed this duration, they will be automatically stopped. See WEBDEV: Scheduled tasks and delayed tasks for more details.
Maximum number of simultaneous connections to the site:
Corresponds to the maximum number of simultaneous connections allowed for this site. For example, if this number is set to 250, 250 Web users will be able to connect to this site at the same time.
Versions 20 and later
Maximum number of cached sessions for the site:
Number of cached sessions for the site.
See Pre-launched sessions for more details.
New in version 20
Maximum number of cached sessions for the site:
Number of cached sessions for the site.
See Pre-launched sessions for more details.
Maximum number of cached sessions for the site:
Number of cached sessions for the site.
See Pre-launched sessions for more details.
Maximum number of connections per user: (when deploying a dynamic WEBDEV site only)
Corresponds to the maximum number of simultaneous connections to the site allowed for the same Web user.
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.

Versions 16 and later
During a deployment on several servers simultaneously, you have the ability to configure the site parameters for each profile. The following elements are taken into account:

Maximum number of simultaneous connections to the site.
Maximum number of connections per user.
Disconnect the idle users since.

New in version 16
During a deployment on several servers simultaneously, you have the ability to configure the site parameters for each profile. The following elements are taken into account:

Maximum number of simultaneous connections to the site.
Maximum number of connections per user.
Disconnect the idle users since.

During a deployment on several servers simultaneously, you have the ability to configure the site parameters for each profile. The following elements are taken into account:

Maximum number of simultaneous connections to the site.
Maximum number of connections per user.
Disconnect the idle users since.

Immediate setup: case of a setup on a remote WEBDEV application server

By default, WEBDEV proposes an immediate setup of the site. In this case, the files are immediately transfered by FTP to the server and installed in the directory defined on the server.

In some case, a delayed setup may be useful. Some examples:

installing a large site: a delayed setup allows you to check whether all the files are installed (in immediate setup, the setup can be stopped according to the time-out defined for the CGI.
updating a site: a delayed setup allows you to perform your setup at night, in order to reduce the number of connected Web users.
updating several sites that share an analysis with automatic data modification: a delayed update allows you to update all the sites at the same time in order to take the automatic modification of data files into account.

During a delayed setup, the files are immediately transmitted by FTP but they are actually installed only when the specified date and time are reached on the server.

Caution: the specified date and time are the ones of the server. Make sure that they are valid.

Versions 21 and later

Site security

Then, the wizard allows you to define the parameters for site security:

Changing IP while navigating: If this option is not allowed, the IP address associated with the session cannot change while navigating. This is used to protect against "session hijack" attacks (attack that consists in pretending to be a legitimate user connected to the server).
Access to the AWP context identifiers from JavaScript: In an AWP site, the site context is stored on the server. The identifier of this context is sent and stored in the browser via a cookie. If this option is not allowed, the cookies used will be "HTTPOnly" cookies, that cannot be read from Javascript code. This mode protects against XSS attacks (Cross-Site scripting).
By default, the access to the AWP context identifiers is not allowed from JavaScript.

New in version 21

Site security

Then, the wizard allows you to define the parameters for site security:

Changing IP while navigating: If this option is not allowed, the IP address associated with the session cannot change while navigating. This is used to protect against "session hijack" attacks (attack that consists in pretending to be a legitimate user connected to the server).
Access to the AWP context identifiers from JavaScript: In an AWP site, the site context is stored on the server. The identifier of this context is sent and stored in the browser via a cookie. If this option is not allowed, the cookies used will be "HTTPOnly" cookies, that cannot be read from Javascript code. This mode protects against XSS attacks (Cross-Site scripting).
By default, the access to the AWP context identifiers is not allowed from JavaScript.

Site security

Then, the wizard allows you to define the parameters for site security:

Changing IP while navigating: If this option is not allowed, the IP address associated with the session cannot change while navigating. This is used to protect against "session hijack" attacks (attack that consists in pretending to be a legitimate user connected to the server).
Access to the AWP context identifiers from JavaScript: In an AWP site, the site context is stored on the server. The identifier of this context is sent and stored in the browser via a cookie. If this option is not allowed, the cookies used will be "HTTPOnly" cookies, that cannot be read from Javascript code. This mode protects against XSS attacks (Cross-Site scripting).
By default, the access to the AWP context identifiers is not allowed from JavaScript.

Generating site statistics

Then, the wizard allows you to implement the statistical files of the site. These files are exploited by WDStatistic to find out the site traffic or the most visited pages for example.

You can modify the directory of the statistical file or you can choose not to generate these files by unchecking "Generate the statistical files for this site". The directory of the statistical files is always relative in relation to the data directory.

See WDStatistic for more details.

Versions 16 and later
During a deployment on several servers simultaneously, you have the ability to configure the statistical files for each profile.

New in version 16
During a deployment on several servers simultaneously, you have the ability to configure the statistical files for each profile.

During a deployment on several servers simultaneously, you have the ability to configure the statistical files for each profile.