ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Help / WEBDEV administrator / WEBDEV Application Server administrator / 02. First deployment
  • Overview
  • Step 1: Check the server configuration
  • Step 2: Installation of a dynamic WEBDEV site by physical media (Windows server only)
  • Step 3: Configuring the server access rights
  • Overview
  • Access rights required to use a WEBDEV site or a SOAP/REST Webservice
  • Summary table about the necessary rights
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Deployment via physical media (DVD, etc.)
Overview
To deploy a WEBDEV site or a SOAP/REST Webservice via physical media, you must:
  • Step 1: Check the server configuration.
  • Step 2: Install the WEBDEV site on the server.
  • Step 3: Configure the access rights on the server.
Step 1: Check the server configuration
To install a site developed with WEBDEV on an Internet server (at a hosting provider for example), the following elements must be installed on the server:
  • a Windows 32-bit or 64-bit operating system (a Server version is recommended).
  • The TCP/IP network protocol.
  • a Web server, used to make the WEBDEV sites accessible. If no Web server is installed, the setup by physical media can automatically install the Apache server (if this one was included when creating the setup on the development computer).
  • the WEBDEV 2024 application server. If the application server is not found, the setup by physical media can automatically install an application server limited to 10 connections (if this one was included when creating the setup on the development computer).
To get fast response time, a powerful computer must be used for the Internet server.
To avoid a drop in the system performance, the total number of connections to all dynamic WEBDEV sites or to a dynamic WEBDEV site must be limited:
  • by the site developer, in the WEBDEV site through programming.
  • by the server administrator in the different local or remote administration tools provided with WEBDEV 2024 application server.
  • by the site manager, in the remote WEBDEV administrator.
Step 2: Installation of a dynamic WEBDEV site by physical media (Windows server only)
To install a dynamic WEBDEV site on a Web server:
  1. Run INSTALL.EXE (supplied with the site setup) on the Web server.
    Important: To update an existing site, you must:
    • lock the site with the WEBDEV administrator: check "WEBDEV site locked (for an update)" in the "Sites" tab or "Lock the server for an update" in the "Setups/Accounts" tab.
    • disconnect all Web users from the site.
    Special case: a WEBDEV site with the same name is already installed on the server
  2. Choose the setup language: a setup wizard starts. Click "Next" to continue.
    Remark: The wizard language only affects the setup wizard (it does not affect the installed site).
  3. Select the WEBDEV account that will be associated with the site. If no account is suitable, create a new account ("WEBDEV account" button).
  4. The setup automatically detects whether one or more of the following Internet servers are installed on the computer:
    • IIS Version 7 to 10 (Microsoft Internet Information Server): Microsoft server supplied with Windows and Windows Server.
    • Apache Version 2.x: free Web server supplied by Apache Software Foundation.
    Three cases may occur:
    • Case 1: your Web server is not displayed in this list: select "Other server". You will have to configure the server manually.
    • Case 2: your Web server is displayed in the list but it is grayed: it means that it was not detected (rare case). You will have to configure the server manually.
    • Case 3: your Web sever can be selected directly: select your server.
      You can ask to generate a configuration file in order to run the configuration later. The configuration file can be modified before it is run. Depending on the selected server, the extension of configuration file will be .reg, .conf or something else.
  5. Select the installation directory:
    • for the site files: HTML pages, ...
    • for the data files of the site
    The paths corresponding to the selected WEBDEV account are automatically proposed:
    • <site> corresponds to the installation directory of site files defined in the account.
    • <webservice> corresponds to the installation directory of SOAP Webservice files defined in the account.
    • <rest> corresponds to the installation directory of REST Webservice files defined in the account.
    • <data> corresponds to the installation directory of data files defined in the account.
    • <webroot> indicates the root directory of the computer's web server. Depending on the selected web server, the root directory is detected and displayed. If the root directory of the Web server does not appear, you can type it in the gray area or find it via the "…" button.
      Caution: if the area is filled, we advise you not to modify it.
  6. Choose to generate the statistical files. If this option is selected, the site manager or the Webservice manager will be able to directly see the traffic statistics regarding the site or the SOAP/REST Webservice. In this case, specify the directory for generating the statistical file. By default, the proposed directory corresponds to a subdirectory of file directory of site or Webservice.
    Remark: This option can be modified in the WEBDEV administrator or in the remote administrator.
  7. Update data files (optional step, for a site update only).
    To update the data files associated with the WEBDEV site or with the Webservice, choose to run the automatic modification of data files.
    Contact the site or Webservice provider if you don't know whether this update must be performed or not.
    Caution: no site or Webservice that uses these data files must be running. Use the WEBDEV administrator to check that no connection is in progress and to stop the sites: check "WEBDEV site locked" in the "Sites" tab (or "Webservice locked" in the "Webservices" tab) or check "Lock the server for an update" in the "Setups/Accounts" tab.
  8. For a site: specify the URL (Internet address) where the site is available in order to build the SiteMap file. This file is used by the search engines to better reference your site. The address to specify is the home address of your site.
    For example: if your site is available at "http://www.mysite.fr/index.awp", you must specify www.mysite.fr as referencing URL.
    For a web service: specify the URL (Internet address) where the Webservice file (.AWWS file) is accessible. This address will be used to build the Webservice import file (WDSL file) required to import your Webservice into a project in order to use it.
  9. If your site uses the "User Groupware" feature, you can specify the location of the data files used. For more details, see the WEBDEV documentation
  10. Install an ODBC driver for HFSQL if programs not developed with WEBDEV must access the HFSQL files of the site that will be installed (optional step).
  11. The setup summary is displayed:
    • Click "Previous" if you want to modify some options.
    • Click "Next" to start the setup.
  12. The setup is completed:
    • Click on the suggested address to test the WEBDEV site locally. This option can be used only if the Web server was automatically configured. The "Clipboard" option is used to retrieve this address.
    • Click "Finish" to exit the setup.
  13. Configuring the Web server: If the configuration of the Web server was not performed automatically, two cases may occur:
    • Case 1: your server was detected and a configuration file was generated: this file can be viewed, modified (if necessary) and run.
    • Case 2: your server was not detected: see configuration of Web servers.
  14. Unlock the sites that may be locked via the WEBDEV administrator.
  15. Run the test of WEBDEV site from the WEBDEV administrator with the "Test page" option ("Advanced" tab) or by using the link supplied at the end of setup.
    Remark: The WEBDEV administrator (WD290ADMIN.EXE) must be started and running in the background at all times. It can be installed as service. For more details about the local WEBDEV administration tool, see "WEBDEV administrator".
Step 3: Configuring the server access rights

Overview

If you are using a NTFS file system, you must configure the access rights to the server in order to use a WEBDEV site or a Webservice. These access rights are used to grant specific authorizations: authorization to write into the directory for file transfer, ...
Reminder: Access rights are automatically configured via the Hosting Control Center.
Caution: Even though WEBDEV 2024 assists you the best it can, the remote setup requires an "expert" level for configuring the server. This area is NOT directly related to WEBDEV. These settings cannot be defined by a novice.
You must have a minimum knowledge of this area or have knowledgeable help.
If you want to use these advanced features, plan to spend the required time for installing them and for configuring them. This setting depends on several parameters not related to PC SOFT and to WEBDEV.

Access rights required to use a WEBDEV site or a SOAP/REST Webservice

The access rights are configured in relation to the Windows account that is running the AWP manager.
In Windows, it is in most cases the "Internet guest" account named IUSR_ComputerName.
In Linux, it is the account that owns the library (.WDL file for a dynamic WEBDEV site or for a REST Webservice, .AWP file for an AWP site and .AWWS file for a SOAP Webservice).
This account must be able to:
  • Read files from the site or web service directory (SOAP or REST).
  • Read and write to the site or web service data directory (SOAP or REST).
To identify the Windows account that runs the AWP protocol, see Identifying the account that runs the AWP protocol.

Summary table about the necessary rights

The following user groups are used in this table:
  • WWUSR: Group of WEBDEV users (set of Windows/Linux accounts used for FTP)
  • IUSR: Group of anonymous Internet users (set of accounts running the AWP protocol on each virtual server of the computer). For example: on a Windows computer that uses IIS with a single virtual server, it is the account named IUSR_ComputerName.
  • LOGIN: A member of the WWUSR group.
NTFS rights
DirectoryUser Necessary rights
WEBDEV directory WWUSR and IUSR Read + Execution
Subdirectory of account filesWWUSR Read + Write
IUSR Read
AWP subdirectoryWWUSR and IUSRRead + Execution
FTP directory of LOGIN userLOGIN Full control
Directory of sites and webservices of LOGIN userLOGINFull control
IUSR Read + List
Data directory of LOGIN userLOGINFull control
IUSRRead + Write + List
Temporary directory of systemWWUSR and IUSRRead + Write + List + Modification
File of the metabase (c:\winnt\system32\inetserv\metabase.bin)WWUSR Read + Write
IUSR Read
Directory of SaaS dataIUSR Read + Write

Rights on the registry (Windows only): automatically configured at setup
Directory User Necessary rights
HKEY_LOCAL_MACHINE\Software\PCSOFT\WEBDEV\29.0WWUSR and IUSRRead
HKEY_LOCAL_MACHINE\Software\PCSOFT\WEBDEV\29.0\ApplicationsWWUSRRead + Write
IUSRRead
HKEY_LOCAL_MACHINE\Software\PCSOFT\WEBDEV\29.0\WebservicesWWUSRRead + Write
IUSRRead
HKEY_LOCAL_MACHINE\Software\PCSOFT\WEBDEV\29.0\RESTWebservicesWWUSRRead + Write
IUSRRead

Rights on the configuration files (Linux only)
Directory User Necessary rights
/etc/PCSOFT/WEBDEV/29.0WWUSR and IUSRRead
/etc/PCSOFT/WEBDEV/29.0/ApplicationsWWUSR Read + Write
IUSR Read
/etc/PCSOFT/WEBDEV/29.0/WebservicesWWUSR Read + Write
IUSR Read
/etc/PCSOFT/WEBDEV/29.0/RESTWebservicesWWUSR Read + Write
IUSR Read

Rights in IIS (Windows and IIS only)
WD290AWP.EXEExecution in anonymous mode by using the IUSR guest
WD290INSTAWP.EXEExecution in authenticated mode only by using the basic authentication.
Minimum version required
  • Version 9
Comments
Click [Add] to post a comment

Last update: 09/07/2023

Send a report | Local help