The server administrator can define the server parameters via the remote management tool.These parameters are organized in different categories grouped on the "Configuration" tab of remote WEBDEV administrator.

Maximum number of connections

The following options can be used to configure the connections:

Maximum number of connections to the server: Maximum number of simultaneous connections allowed for all the dynamic WEBDEV sites managed by the management tool (one connection = one Web user).

Maximum number of connections to a site or Webservice: Maximum number of simultaneous connections to each site managed by the management tool. This parameter will be automatically proposed when configuring a specific site ("By default" option).

Maximum number of connections per Web user: Maximum number of simultaneous connections for the same Web user to each one of the sites managed by the management tool.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 parameter will be automatically proposed when configuring a specific site ("By default" option).

Managing sessions/requests

The following parameters are used to manage the sessions and the requests:

Disconnect the inactive Web users since: 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 parameter will be automatically proposed when configuring a specific site ("By default" option).

Maximum request duration: Maximum time-out allowed between the beginning of an action performed by the 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.

Duration of AWP contexts: The files storing the AWP contexts on disk are regularly 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 cached sessions: To speed up the initialization of dynamic WEBDEV sites, you have the ability to use cached sessions. These ones will be waiting until they are contacted by user requests. The number of cached sessions must be adjusted according to the memory available on your server. Each cached session will use 3 MB of memory to be initialized.

Log file

The WEBDEV Application Server can generate a global file for logging the accesses to the different sites and Webservices installed.

New in version 16by the statistical module of remote WEBDEV administrator.

by the statistical module of remote WEBDEV administrator.

Remote debugging

This section of configuration parameters is used to enable or disable the ability to debug a WEBDEV site remotely.

To debug a site remotely, you must own 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.

Note: This feature is not available if the application server is running Linux.

Various

The other features are:

Forbid the users to modify their password in the Remote Administrator: if this box is checked, only the person responsible for the server will be able to modify the passwords of the user, either by using the remote WEBDEV administrator, or via WDCompte or WEBDEV Hosting Control Center.

Disable the email spooler: if this box is checked, the emails sent by the WLanguage functions from a WEBDEV site (dynamic site or AWP site) will be directly sent to the SMTP server. If the box is not checked, the Application Server enables a spooler that sends the emails in background task in order not to penalize the interactivity of the site.Note: The email spooler is not available in Linux.

Allow the server sockets: For security reasons, the WEBDEV sites are not allowed to create sockets (by using SocketCreate). This feature can be re-enabled via this check box.

Note: In most cases, creating sockets in the server code of an application is not recommended. This feature is available only for the special cases that use it (authentication protocols that use some bidirectional socket openings for example).

Finding the expired pages

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