PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
New WEBDEV 24 feature!
  • Overview
  • Interface of WEBDEV administrator
  • Characteristics of current connections
  • Sites installed
  • Webservices installed
  • General configuration
  • Advanced options
  • Setups/Accounts
  • Logs
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
2. The WEBDEV administrator in practice
Previous pageTable of contentsNext page
Overview
The WEBDEV administrator is a module to manage dynamic WEBDEV sites (Session or AWP).
When developing a dynamic WEBDEV site, the administrator is mainly used to:
  • run the site test via the test page.
  • define the parameters for connecting to the site for tests: disconnection time, ...
  • delete the current test connections.
  • change the Web server used for tests.
  • perform a diagnostic if a problem occurs when starting a WEBDEV site.
  • ...
In deployment, two types of WEBDEV administrators are available:
  • the WEBDEV Deployment administrator that allows the hosting company to manage the dynamic WEBDEV sites installed on a Web server.
  • the remote WEBDEV administrator that allows the site manager to manage his dynamic WEBDEV sites remotely from any computer.
This chapter presents the WEBDEV Development administrator only.
For more details about the deployment tools, see their help.
Starting the WEBDEV administrator
To start the WEBDEV Development administrator:
  • from WEBDEV Development version: on the "Tools" pane, in the "Web utilities" group, click "WDAdmin".
  • select "Programs .. WEBDEV 24 .. WEBDEV administrator" from the "Start" menu.
The WEBDEV administrator is automatically started during the first test of the site.
Then, the administrator can be run in background task.
By default, the WEBDEV administrator allows ten simultaneous connections to the same dynamic WEBDEV site (GO icon).
Interface of WEBDEV administrator
The WEBDEV administrator includes a window containing several tabs:
  • "Connections" tab.
  • "Sites" tab and "Webservices" tab.
  • "Configuration" tab.
  • "Advanced" tab.
  • "Setups/Accounts" tab.
  • "Logs" tab.

Characteristics of current connections

The "Connections" tab gives various information about the current connections. This information can be consulted at any time on the server:
  • The number of current connections indicates the total number of connections to the dynamic WEBDEV sites managed by the administrator.
  • The table of current connections indicates for each connection:
    • the connection identifier,
    • the site affected by the connection,
    • the identity of connected client. At run time, the client is identified by its IP address or by its Internet address,
    • the current connection time,
    • the idle time of connection.
  • Automatic refresh: this option is used to automatically refresh the displayed data.
The "Connections" tab can also be used to:
  • Stop a current connection:
    Select one of the connections and click "Disconnect".
  • Stop all current connections and close the administrator: click "Disconnect all".

Sites installed

The "Sites" tab gives information about the dynamic WEBDEV sites installed on the computer.
The "Sites" tab returns the list of dynamic WEBDEV sites installed on the computer and managed by the WEBDEV administrator. For each site, the following information is displayed in a table:
  • the site name.
  • the full setup directory of site on the computer.
  • the name of corresponding "project" file.
  • the site status (locked or not). You have the ability to check the box in order to directly lock the access to the site during the update.
  • the number of scheduled tasks used by the site.
The "Sites" tab can also be used to:
  • Delete the site selected in the table.
    It is used to remove the site from the administrator: the WEBDEV site will still be found on disk.
  • Refresh the list of sites found in the table.
    This refresh operation is used to check the presence of a site in the administrator after its setup.
  • Add a site into the table.
  • Configure each site found on the computer.
    The configuration used by default is the one defined in the "Configuration" tab.
    You can also create a specific configuration for the selected site ("Parameters" button).
    This configuration affects the number of authorized connections, the authorized idle time and whether the site must be locked during an update. See the "Configuration" tab for more details.
    To validate the new setting immediately, click the "Apply" button.
    You can also manage scheduled tasks associated with the selected site (Scheduled tasks" button). This setting is available when the site is deployed.
  • Run the test of the sites installed on the computer (in development version only):
    Select the site and click on "Run the test".

Webservices installed

The "Webservices" tab gives information about the dynamic WEBDEV Webservices installed on the computer.
The "Webservices" tab lists the dynamic WEBDEV Webservices installed on the computer and managed by the WEBDEV administrator. For each Webservice, the following information is displayed in a table:
  • the name of the Webservice.
  • the complete Webservice installation directory on the workstation.
  • the name of corresponding "project" file.
  • the Webservice status (locked or not). You can check the box to lock the access to the Webservice during its update.
  • the number of scheduled tasks used by the Webservice.
The "Webservices" tab also allows you to:
  • Delete the selected Webservice from the table.
    The Webservice is deleted from the administrator: the WEBDEV Webservice will still be found on disk.
  • Refresh the display of the Webservices found in the table.
    This refresh operation is used to check the presence of a Webservice in the administrator after its setup.
  • Add a Webservice into the table.
  • Configure individually the Webservices on the computer.
    The configuration used by default is the one defined in the "Configuration" tab.
    You can also create a specific configuration for the selected Webservice ("Parameters" button).
    This configuration affects the number of authorized connections, the authorized idle time and whether the Webservice must be locked during an update. See the "Configuration" tab for more details.
    To validate the new setting immediately, click the "Apply" button.
    You can also manage scheduled tasks associated with the selected Webservice (Scheduled tasks" button). This setting is available when the Webservice is deployed.

General configuration

The general configuration corresponds to the default connection options for the WEBDEV sites found on the server and managed by the administrator.
The "Configuration" tab is used to:
  • Configure the connections.
  • Configure the sessions and the requests.
  • Manage the log file to get the traffic statistics.
  • Managing remote debugging.
    The connections can be configured via the following options:
    • 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 on 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 user connections on a site:
      Maximum number of simultaneous connections allowed for a given Web user to each site managed by the administrator.
      If this parameter is set to zero, a Web user trying 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.
    The sessions and requests can be configured via the following options:
    • 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.
    • Duration of Webservices contexts:
      Validity duration of contexts corresponding to Webservices.
    • 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.
    • Maximum task duration:
      Used to limit the runtime duration of a WEBDEV scheduled task or delayed task. The task will be automatically stopped when this duration is exceeded.
    • Allow the pre-launched sessions:
      Makes it possible to manage the pre-launched 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. See the online help for more details.
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):
    Allows you to generate a log file (".LOG" extension) used to see the traffic statistics of WEBDEV sites via WDStatistic. See the help about WDStatistic for more details.
  • 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".
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.

Advanced options

The "Advanced" tab is used to:
  • Choose one of the Web servers installed on the current computer to run the WEBDEV sites.
  • Perform a diagnostic regarding the configuration of current computer.
  • Specify the name or IP address of current computer.
  • Display in the browser a page used to start all WEBDEV sites installed on the current computer.
  • Manage the search for expired pages.
  • Manage the prints.
  • Manage the error messages.
  • Manage the emails in asynchronous mode.
  • Manage the server sockets.
  • Allow (or not) some specific functions.
  • Forbid the change of IP while navigating.
  • Forbid the access to AWP context identifiers from Javascript.
Server used
The "Server" button is used to choose one of the Web servers installed on the current computer to run the WEBDEV sites. Caution: This server will be used for all the dynamic WEBDEV sites installed on this computer.
If the server used is not found in this list, choose "Other". You will have to manually configure the Web server used. See the online help for more details.
Diagnostic
The "Diagnostic" button is used to check the configuration of current computer. This diagnostic is used to check:
  • whether the FTP/IP protocol is installed
  • whether a Web server (HTTP server) is started
  • whether the AWP protocol manager is configured properly
  • whether the necessary WEBDEV executables are found.
The dynamic WEBDEV sites will not operate if one of these conditions is not fulfilled.
See the online help for more details.
Name or IP address of the current computer
The WEBDEV administrator allows you to specify a name or an IP address to identify a specific computer. You also have the ability to specify the port number. For example: localhost:8080.
This computer will be used:
  • when clicking the "Diagnostic" button.
  • when clicking the "Test page" button.
  • when running the test of a site, page, report, ... from the WEBDEV editor ("GO" icon).
Test
The "Test page" button is used to display in the browser a page allowing you to start each one of the dynamic WEBDEV sites and dynamic WEBDEV Webservices installed on this computer.
For more details on testing a WEBDEV site, see 5. Test of a site in practice.
Searching for expired pages
This option is used to enable and configure the search for expired pages on the WEBDEV sites managed by WEBDEV application server.
Printer used by default (Intranet sites only)
The "Prints" button is used to select the default printer that will be used when printing on a local printer or on a network printer of Web server.
Error messages
The "Errors" button displays the different error messages that can be displayed in the browser of Web user. You have the ability to customize the error message and the HTML page where the error message is displayed.
Email spooler
If "Disable the email spooler" is unchecked, your sites will be able to send emails without locking the execution of other processes (asynchronous mode).
The asynchronous mode must be enabled when starting the email session (with EmailStartSMTPSession or EmailStartSession).
If the asynchronous mode is enabled, all outgoing emails will be redirected to a "Spooler". The emails are queued up before they are sent. The execution of Email functions do not lock the rest of your program anymore. EmailStatus is used to find out the email status.
Note: If the WEBDEV administrator is closed, the email spooler is cleared: the pending emails are not sent and they are removed form the spooler.
If "Disable the email spooler" is checked while emails are still found in the spooler, these emails will not be lost: the administrator keeps sending them but no new email is accepted by the spooler.
Caution: The asynchronous mode can only be used when starting a session on an SMTP server (EmailStartSMTPSession to send emails or EmailStartSession). This mode is ignored in the other cases.
Sockets
If "Allow the server sockets" is checked, your sites will be able to handle the server sockets (via the Socketxxx functions of WLanguage).
Forbid the change of IP while navigating
If this option is checked, 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).
Forbid the 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 the option "Forbid the access to the AWP context identifiers from JavaScript" is checked, 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.
Managing fCopyFileWebFolder and fDeleteFichierWebFolder
The option "Allow fCopyFileWebFolder and fDeleteFileWebFolder" must be checked if these functions are used in the Web site.
These functions are mainly used to include images found in the data directory in the directory of site images (images uploaded then made available to the Web users of the site for example).
Caution: The copy is taken into account by the WEBDEV administrator on the server (WD240ADMIN.EXE). The Windows account that runs it must have sufficient rights on the target location of copy.

Setups/Accounts

The "Setups/Accounts" tab is used to:
  • Configure the server for the site setups and updates.
  • Manage the log of setups.
  • Manage the WEBDEV accounts.
Setup/Update
These options are available in deployment version. They allow the hosting company to authorize and configure the site setups and updates remotely.
The option "Lock the server (for an update)" is used to easily update a site by blocking any connection from a new user. Whenever attempting to connect to one of the sites found on the server, the Web user receives a message signaling that the site is temporarily unavailable and asking him to retry later. The Web users who are already connected can continue to use the current WEBDEV site.

Logs

The "Logs" tab is used to see the details of logs over a specific period.
Caution: To use this feature, the logs must have been enabled for the site. The logs can be enabled:
  • in the "Configuration" tab to manage a general log,
  • in the "Sites" tab ("Parameters" button) and in the "Webservices" tab ("Parameters" button") to manage a specific log.
The log of errors is automatically created when the log of statistics is enabled.
Previous pageTable of contentsNext page
Minimum version required
  • Version 24
Comments
Click [Add] to post a comment