|
|
|
|
|
- Overview
- Maximum number of connections
- Managing sessions/requests
- Log file
- Remote debugging
- Miscellaneous
- Finding expired pages
Remote WEBDEV administrator: Server settings
The server administrator can define the server parameters via the remote administration tool. These parameters are organized in different categories in the "Configuration" tab of the remote WEBDEV administrator. Maximum number of connections You can configure connections by setting the following options: - Maximum number of connections on the server: Maximum number of simultaneous connections authorized for all WEBDEV dynamic sites managed by the administration tool (one connection = one user).
- Maximum number of connections to a site / Webservice: Maximum number of simultaneous connections authorized to each site managed by the administration tool. This parameter will be automatically proposed when configuring a specific site ("By default" option).
- Maximum number of connections for a single user Maximum number of simultaneous connections by a single user to each of the sites managed by the administration tool.
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. This parameter will be automatically proposed when configuring a specific site ("By default" option).
Managing sessions/requests The following parameters are used to manage sessions and requests: - Disconnect inactive users from: Maximum connection time allowed without user action. When this time is exceeded, the user is automatically disconnected and an error message is displayed. This parameter will be automatically proposed when configuring a specific site ("By default" option).
- Maximum duration of a request: Maximum waiting time allowed between the triggering of an action by the surfer (via a button or link) and the display of the response.. If this time is exceeded, an error page is displayed, but the user is not disconnected.
- AWP contexts duration: files storing AWP contexts on disk are periodically deleted by the Application Server.. This setting is used to define the maximum lifespan of an AWP context. An AWP context consumes little disk space (unlike a session of a dynamic site that remains in memory), therefore the lifespan of the AWP contexts can be very long without creating problems if there is enough disk space.
- Number of pre-launched sessions: To speed up the initialization of dynamic WEBDEV sites, it is possible to pre-launch sessions.. These ones will be waiting until they are contacted by user requests. The number of pre-lauched sessions must be adjusted according to the memory available on your server. Each pre-lauched session will use 3 MB of memory to be initialized.
The WEBDEV Application Server can generate a global file for logging the accesses to the different sites and web services installed. This file is intended to be exploited: - via WDStatistics.
- by the statistical module of the remote WEBDEV administrator.
This section of configuration parameters is used to enable or disable the ability to debug a WEBDEV website remotely. To debug a site remotely, you must have the project corresponding to the site. However, for security reasons, we do not advise you to enable the remote debugging on a production server, except if a debugging session is required. The other features are: - Prohibit users from changing their passwords in the remote WEBDEV administrator: if this box is checked, only the server manager will be able to change user passwords, either using the remote WEBDEV administrator, or using WEBDEV Account Manager.
- Disable mail spooler: if this box is checked, emails sent using WLanguage functions from a WEBDEV site (dynamic site or AWP) are sent directly to the SMTP server.. If the box is not checked, the Application Server activates a spooler that sends emails in the background so as not to slow down the site.
Remark: The email spooler is not available in Linux. - Allow server sockets: For security and stability reasons, WEBDEV sites are not allowed to create sockets by default (using the SocketCreate function).. This feature can be re-enabled via this check box.
Remark: The creation of sockets in the server code of an application is generally not recommended.. This feature is available only for the special cases that use it (authentication protocols that use some bidirectional socket openings for example). The parameters found in the "Searching for the expired pages" section are used to configure: - the frequency with which the Application Server will search for the expired pages in the deployed sites
- the SMTP server that will be used to notify the site managers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|