|
|
|
|
|
|
|
|
|
|
- Overview
- Site configuration
- Immediate installation: installation on a remote WEBDEV Application Server
- Site security
- Generating site statistics
WEBDEV site deployment: Site parameters
Once the site installed, you can define the site connection options. If necessary, these settings can be modified: - via the deployment administrator located on the server.
- via the remote administrator, which can be used by the site manager.
The deployment parameters are as follows: - Publish site immediately after installation:
The site will be available immediately after installation: you can connect to it using the appropriate address.
If this option is not checked, the site can be published via the remote administrator. - Perform a backup of the site before the update:
For an update, allows you to save the existing site.
This backup copy should have a name and can be a full backup or contain only the deployed files.
This backup can be reactivated from the remote WEBDEV Administrator. - Schedule deployment for a later date:
In this case, the deployment will be performed at the specified date and time. For more details, see Immediate or delayed setup.
The site parameters are as follows: - AWP context duration (WEBDEV AWP site deployment only)
Validity period of AWP contexts for the site. If the specified time has elapsed and no new requests have been made, the context file is deleted. For more details on AWP contexts, see AWP: Managing contexts. - Maximum task duration:
Maximum duration for running the scheduled or deferred tasks. If the tasks used exceed this duration, they will be automatically stopped. For more details, see WEBDEV: Scheduled tasks and deferred tasks. - 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. - Maximum number of connections per user (dynamic WEBDEV site deployment only)
Corresponds to the maximum number of simultaneous connections to the site allowed for the same Web user.
If this parameter is set to zero, the 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 x simultaneous connections. - Maximum number of pre-launched sessions:
Number of pre-launched sessions for the site.
For more details, see Pre-launched sessions.
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 after.
Immediate installation: installation 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. For example: - installation of a large site: a deferred installation ensures that all files are installed (in immediate installation, the installation can be stopped according to the time out defined for the CGI.
- updating a site: deferred installation enables night-time installation, to limit the number of Internet users connected.
- update several sites sharing an analysis with automatic data modification: a deferred update can be scheduled to update all sites at the same time, to take into account the automatic modification of data files.
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. Warning: the date and time specified are those of the server. Make sure they are valid. Then, the wizard allows you to define the parameters for site security:
- IP change during browsing: If this option is disabled, the IP address associated with the session cannot change during browsing.. This prevents "session hijacking" attacks, which occur when an attacker impersonates a legitimate user connected to the server.
- Access to 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 prevents cross-site scripting (XSS) attacks.
By default, access to 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 WDStatistics 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. When deploying to multiple servers simultaneously, you can configure the statistics files for each profile. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|