PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Details of "Configuration" tab
  • Configure the connections
  • Configure the sessions and requests
  • Managing the log file
  • Managing the remote debugging
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
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

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 to 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 connections of a user to a site:
    Maximum number of simultaneous connections allowed for a given Web user to each site managed by the administrator.
    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.
    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 setting of connections, click the "Apply" button. The new setting is automatically taken into account.
To cancel the modifications, click the "Restore" button.

Configure the sessions and requests

The following options are used to configure the sessions and requests:
  • 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. See AWP: Managing contexts for more details.
  • 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. See Generating a webservice for more details.
    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. See Generating a webservice for more details.
    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. See Generating a webservice for more details.
  • 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.
  • Number of cached sessions (available for the WEBDEV application server only):
    Used to optimized the connection time to the WEBDEV sites managed by the server. Whenever a Web user connects to a site, a session is started on the server. Starting the session may take a few seconds.
    If a number of cached sessions is defined, when a Web user connects to a site:
    - one of the cached sessions is automatically used: therefore, the connection to the site is faster.
    - a new session is automatically pre-launched.
    Versions 20 and later
    Allow the cached 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:
    • modify the project to manage the cached sessions properly. See The cached sessions for more details.
    • configure the site or the webservice in order to specify the number of necessary cached sessions ("Sites" or "Webservices" tab, "Parameters" button).
    New in version 20
    Allow the cached 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:
    • modify the project to manage the cached sessions properly. See The cached sessions for more details.
    • configure the site or the webservice in order to specify the number of necessary cached sessions ("Sites" or "Webservices" tab, "Parameters" button).
    Allow the cached 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:
    • modify the project to manage the cached sessions properly. See The cached sessions for more details.
    • configure the site or the webservice in order to specify the number of necessary cached sessions ("Sites" or "Webservices" tab, "Parameters" button).
To validate the setting of connections, click the "Apply" button. The new setting is automatically taken into account.
To cancel the modifications, click the "Restore" button.

Managing the log file

The WEBDEV administrator is used to manage a specific log file allowing you to follow the traffic statistics.
  • Generate a log file to manage the traffic statistics (.log):
    This option allows you to generate a log file (".LOG" extension) used to view the traffic statistics of WEBDEV sites via WDStatistic. See the help about WDStatistic for more details.
    The location of the log file can be specified in the "Directory" control.
    This option can be modified for each site in the "Sites" tab.
  • Save in the global file and in the file of each application:
    This option is used to save the statistics both in the log file of application and in the log file of server. Indeed, if the log file is defined both at server level and at application level ("Sites" tab), information may be "lost". The table below presents the different possible cases:
    Application log
    Server log
    "Save in the global file and in the file of each application" option checked
    Result
    NoNoAnyNo log
    NoYesAnyBackup in the server log
    YesNoAnyBackup in the application log
    YesYesNoBackup in the application log
    YesYesYesBackup in the server log and in the application log
Versions 20 and later
Note: If the log file is enabled, the log of errors can be viewed in the "Logs" tab of administrator.
New in version 20
Note: If the log file is enabled, the log of errors can be viewed in the "Logs" tab of administrator.
Note: If the log file is enabled, the log of errors can be viewed in the "Logs" tab of administrator.

Managing the remote debugging

The WEBDEV administrator can allow (or not) the remote debugging of dynamic WEBDEV sites.
If the remote debugging is allowed, 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.
Minimum required version
  • Version 10
Comments
Click [Add] to post a comment