WebDev application

server
WebDev application server Version 18
WebDev application server - 18- 1 - 0513

Don’t forget to visit our site (www.windev.com) on a regular basis to find out whether upgraded ver-
sions are available.

Email address of our Free Technical Support: freetechnicalsupport@windev.com

This documentation is not contractually binding. Modifications may have been made to the software
since this guide was published. See the online help.

All product names or other trademarks mentioned in this publication are registered trademarks of their respective owners.
© PC SOFT 2013: This publication may not be reproduced in part or in whole in any form without the express permission of PC
SOFT.
 WebDev application server 3
Table of contents

TABLE OF CONTENTS

WEBDEV APPLICATION SERVER

1. OVERVIEW OF WEBDEV 18 9

2. WEB SERVER: FIRST DEPLOYMENT 11

2.1 Remote deployment (by FTP) .......................................................................................................................................11

2.1.1 Step 1: Check the configuration of the Web server ........ .... ........ .... .... .... ........ .... .... .... .....11
2.1.2 Step 2: Create an FTP account......... .... ........ .... .... .... ........ .... .... .... ........ .... .... .... ..... 12
2.1.3 Step 3: Create a WebDev account ........ ........ .... .... .... ........ .... .... .... ........ .... .... .... .....13
2.1.4 Step 4: Configure the access rights on the server.......... .... ........ .... .... .... ........ .... .... .... ..... 15
2.1.5 Step 5: Parameters to transmit ........ .... ........ .... .... .... ........ .... .... .... ........ .... .... .... .....19
2.2 Deployment via physical media (CD, …) ......................................................................................................................20
2.2.1 Step 1: Check the configuration of the Web server ........ .... ........ .... .... .... ........ .... .... .... .....20
2.2.2 Step 2: Installing a dynamic WebDev site by physical media (Windows server only).......... ........ .... ..... 20
2.2.3 Step 3: Configure the access rights on the server.......... .... ........ .... .... .... ........ .... .... .... ..... 22
2.2.4 Summary table about the necessary rights ............ ........ .... ........ .... .... .... ........ .... ........ .... .....23
2.3 A WebDev site with the same name is already installed on the server ...................................................................24
2.3.1 Setup by FTP ...... ........ .... ........ .... .... ........ .... .... .... ........ .... .... .... ........ .... .... .... ..... 24
2.3.2 Setup by physical media .......... ........ .... ........ .... .... .... ........ .... .... .... ............ ........ .... ..... 24
2.4 Where are the files of the WebDev site found after setup? ......................................................................................24
2.4.1 Case of a WebDev site (dynamic or AWP site)........ ........ .... ........ .... .... .... ........ .... .... .... .....24
2.4.2 Case of a Webservice ...... ........ .... .... ........ .... .... .... ........ .... .... .... ........ .... .... .... ..... 24
2.5 Migrating a WebDev 1.5 site or a site version 7 (and later) to WebDev 18 ............................................................25
2.6 Preparing the remote administrator ............................................................................................................................25

3. TROUBLESHOOTING 27

3.1 Web server: Common problems ...................................................................................................................................27

3.2 Identification and resolution of TCP/IP problems ......................................................................................................27
3.2.1 Checking the presence of the TCP/ IP layer and IP addresses .............. ........ .... ........ .... .... .... ..... 27
3.2.2 Checking the configuration of the TCP/ IP layer .............. .... ........ .... .... .... ........ .... .................. 27
3.3 Problems with the manager of the AWP protocol ......................................................................................................28
3.4 Problems linked to a setup by FTP ...............................................................................................................................28
3.4.1 Step 1: Entering the logins and the Server/ FTP passwords (site setup)....... .... ........ .... .... .... .....28
3.4.2 Step 2: Installing the site (setup or update)........... ........ .... ........ .... .... .... ........ .... .... ..... 29
3.4.3 Step 3: Updating a site.... ........ .... .... ........ .... .... .... ........ .... .... .... ........ .... .... .... .....32
3.5 Error messages that can be displayed in the browser ...............................................................................................32
4 WebDev application server
Table of contents

APPENDIX 1 - VOCABULARY OF WEBDEV 33

APPENDIX 2 - CONFIGURATION OF SERVERS 35

1 Overview .............................................................................................................................................................................35
2 Installing the WebDev application server .......................................................................................................................35
3 Configuring the Web servers for WebDev manually ......................................................................................................35
4 Configuring the "Apache 1.3.x" server for WebDev .......................................................................................................36
4.1 Configuring the server for the CGI protocol (AWP).............. .... ........ .... .... .... ........ .... ........ .... ..... 36
4.2 Configuring the server for the WebDev sites .... ........ .... .... ........ .... .... .... ........ .... .... .... .....36
5 Configuring the "Apache 2.x" server for WebDev ..........................................................................................................36
5.1 Configuring the server for the CGI protocol (AWP).............. .... ........ .... .... .... ........ .... ........ .... ..... 36
5.2 Configuring the server for the WebDev sites .... ........ .... .... ........ .... .... .... ........ .... .... .... .....36
6 Configuring the Web IIS server version 5, 6 or 7 for WebDev ......................................................................................37
6.1 Configuring the server for the CGI protocol (AWP).............. .... ........ .... .... .... ........ .... ........ .... ..... 37
6.2 Configuring the server for the WebDev sites .... ........ .... .... ........ .... .... .... ........ .... .... .... .....37
7 Printing from the server ....................................................................................................................................................37
7.1 Configuring the Web server for the local printers (IIS Web servers only).......... .... ........ .... .... .... 37
7.2 Configuring the Web server for the network printers ......... .... ........ .... .... .... ........ .... .... .... ..... 38

APPENDIX 3 - REGISTRY 39

1 Configuring the registry for the WebDev setup ..............................................................................................................39

2 Configuring the registry for installing a WebDev site or a Webservice .......................................................................41

APPENDIX 4 - MODULES SUPPLIED WITH WEBDEV 43

1 The WebDev administrator in practice ...........................................................................................................................43

1.1 Characteristics of current connections .... ........ .... .... .... ........ .... .... .... ........ .... .... .... .....45
1.2 Sites installed........ ........ .... ........ .... .... ........ .... .... .... ........ .... .... ............. .... .... .... .....45
1.3 General configuration .... .... ........ .... .... ........ .... .... .... ........ .... .... .... ............. .... .......... 46
3.3.1 Managing the server........ ........ .... .... ........ .... .... .... ........ .... .... .... ........ .... .... .... .....47
3.3.2 Advanced setting ........ .... ........ .... .... ........ .... .... .... ........ .... .... .... ........ ........ ........ .... .....48
1.4 Customizing the errors ................ .... .... ........ .... .... .... ........ .... .... .... ............. .... .... .....49
2 Tool for stress test .............................................................................................................................................................52
3 The remote WebDev administrator .................................................................................................................................52
4 WebDev Hosting Control Center ......................................................................................................................................53

APPENDIX 5 - SILENT SETUP 54

WebDev application server .................................................................................................................................................54

• HyperFileSQL Client/Server server ..................................................................................................................................55
 WebDev application server 5
Table of contents

EXAMPLES FOR IIS 57

1. INTRODUCTION 59

2. CHECKING/CONFIGURING THE SYSTEM 61

2.1 Prerequisites: WEB server and FTP server ..................................................................................................................61

2.1.1 IIS in Windows 2003 ....... ........ .... .... ........ .... .... .... ........ .... .... .... ........ .... .... .... .....61
2.1.2 IIS in Windows 2008 ....... ........ .... .... ........ .... .... .... ........ .... .... .... ........ .... .... .... .....62
2.2 Checking the IIS FTP server ..........................................................................................................................................63

3. CREATING A GROUP OF USERS 65

4. INSTALLING THE APPLICATION SERVER 67

5. RIGHTS ON THE REGISTRY 68

6. CREATING/CONFIGURING A WEBDEV ACCOUNT 70

6.1 Hosting Control Center ..................................................................................................................................................70

6.1.1 Configuring the Hosting Control Center ......... ........ .... .... ........ .... .... .... ........ .... .... .... ..... 70
6.1.2 Creating a WebDev account with CCHosting.......... ........ .... ........ .... .... .... ........ .... .... .... ..... 73
6.2 Manually (without the Hosting Control Center) ...........................................................................................................75
6.2.1 Creating the WebDev account .......... .... ........ .... .... .... ........ .... .... .... ........ .... .... .... ..... 75
6.2.2 Checking/ Granting rights ......... ........ .... ........ .... .... .... ........ .... .... .... ............ ........ .... ..... 77

7. CHECKING THE CONFIGURATION 79

7.1 With the WebDev administrator ...................................................................................................................................79

7.2 When deploying a new WebDev site ............................................................................................................................79

8. MOST COMMON PROBLEMS 82

8.1 The "Unable to add the programming" error occurs during the remote setup of a site (by FTP) ..........................82
8.2 "WDMetabase.dll: Meta_bInit failed" error or failure updating the meta base with IIS7 ......................................82
8.3 Checking the configuration ...........................................................................................................................................83
8.4 HTTP error 404 the diagnostic on AWP .......................................................................................................................84
8.5 Problem while displaying the images and the styles .................................................................................................85
8.6 The AWP pages do not operate ....................................................................................................................................85
8.7 The URL rewriting of the AWP pages does not operate .............................................................................................85
8.8 The short URLs of dynamic sites do not operate ........................................................................................................86
8.9 The access to the network data does not operate .....................................................................................................86
8.10 The URL with just the domain name does not start the WebDev site ...................................................................86
6 WebDev application server
Table of contents
 WebDev
Application
server
 WebDev application server 9
Overview of WebDev 18

1 . OVERVIEW OF WEB D EV 1 8
WebDev is a full development environment dedicated to Internet and Intranet. WebDev is the perfect tool for developing
Internet and Intranet sites that require (or not) an access to a database.
The dynamic sites created by WebDev operate with all browsers, regardless of their version and platform (PC, MAC, Unix,
…), …
The sites can be used by all the Linux servers and by all the Windows servers: Apache, IIS, …
WebDev includes:
• WebDev Development Version:
Installed on the development computer, this version is used to develop a WebDev site and to run its test locally.
• WebDev application server:
Installed on a server at the host, this version is used to deploy a dynamic WebDev site (site with database). The Web-
Dev site can be used by all the Web users.
Note: The WebDev application server is not required to deploy a static site (which means a site that uses no data).

Features of the WebDev application server

The WebDev application server must be installed on a server (at the host or on an Intranet server). Via the WebDev appli-
cation server:
• The Web users can use the dynamic WebDev sites.
• The server administrator can:
• Manage and configure the dynamic WebDev sites found on the server.
• Configure the WebDev accounts associated with each site manager.
• Install dynamic WebDev sites from a CD supplied by the site manager.
• Control the remote setup and update of the dynamic WebDev sites (via FTP).
• Monitor the servers where the dynamic WebDev sites are installed.
• The manager of the WebDev sites can:
• Perform the remote setup and update of his dynamic WebDev sites (via FTP).
• Modify the configuration of his dynamic WebDev sites.
• Perform stress tests on the deployment server.
• Check whether the Web server where the WebDev sites are installed operates properly.

Warning
Even though WebDev 18 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. This setting cannot be done by a novice.
You must have a minimum knowledge of this area or have knowledgeable help.
Our Assistance Directe© service is available to help you configure these non-PC SOFT elements.
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.
10 WebDev application server
Overview of WebDev 18
 WebDev application server 11
Web server: First deployment

2 . WEB SERVER: F IRST DEPLOYM ENT

The deployment of a dynamic WebDev site consists in installing the WebDev site on a Web server.
Two types of deployment can be done:
• Remote deployment (by FTP):
Two types of remote deployment are available:
1. Remote deployment from the development computer: the manager of the WebDev sites will be able to deploy his site
from the development computer. The necessary files will be transferred by FTP.
This type of deployment is required if the Web server is not directly accessible by the site manager.
2. The remote deployment from an administration computer: the developer does not have to know the characteristics
of the server when creating the setup program (called "Package" in this case). The server parameters are specified when
the package is run on an administration computer.
This type of deployment is recommended when the developer does not know the characteristics of the server when crea-
ting the setup program.
• Deployment by physical media (CD, …): the files required to install the site are transmitted to the server administrator
via a physical media: CD, ... The site must be installed from the physical media.
This type of deployment is possible when the Web server is directly accessible. This type of deployment is available for a
Windows server only.
Notes:
• A license of WebDev Application Server 18 is required for each Web server that hosts WebDev 18 sites.
• The WebDev 18 Application Server is supplied with the WebDev Hosting Control Center. This control center is used to
simplify the different steps for configuring a Web server. This control center can only be run on a computer that uses a
server operating system and a IIS server.

2 .1 Remote deployment (by FTP)

To allow the sites to be deployed by FTP, the server administrator must:
• Step 1: Check the configuration of the server.
• Step 2: Create an FTP account for the manager of WebDev sites.
• Step 3: Create a WebDev account for the manager of WebDev sites.
• Step 4: Configure the access rights to the server (server running Windows 2000 or NT)
• Step 5: Send the parameters of the FTP and WebDev accounts. These parameters must be sent:
- to the manager of the WebDev sites for a remote setup performed from the development computer. The manager of the
WebDev sites will be able to install his WebDev site from his development computer and to perform remote updates of
his sites on a regular basis.
- to the person who will install the package corresponding to the WebDev site for a remote setup from an administration
computer.

2 .1 .1 Step 1 : Check t he conf igurat ion of t he Web ser ver

To install a site developed in WebDev on an Internet server (installed at the hosting company for example), the following
elements must be installed on the server:
• a 32-bit or 64-bit operating system (Windows NT, 2000, XP and later versions) or LINUX.
• the TCP/ IP network protocol.
• a Web server, used to make the WebDev sites accessible.
• the WebDev 18 Application Server
• an FTP server (required to perform remote setups and updates by FTP).
To get fast response time, a powerful computer must be used for the Internet server.
12 WebDev application server
Web server: First deployment

To allow a setup via an authenticated access, the WD180INSTAWP program must be configured for an authenticated
access. The required operations are automatically performed when installing the WebDev application server.
For example, if you are using the IIS server, the following operations must be performed:
1. Open the Internet service manager.
2. Select the virtual directory WD180AWP.
3. Select "Properties" from the popup menu of WD180INSTAWP.
4. In the "File Security" tab, click the "Modify" button (in the "Anonymous access and authentication control" section).
5. Uncheck the "Anonymous access" box. Check the "Basic authentication" box. A warning message is displayed. Vali-
date ("Yes" button).
Important: The resources required per connected Web user:
For each connected Web user, you must plan for:
• about 400 KB of RAM per connection, in addition to the memory required by the server.
• about 1 MB of disk space (virtual memory) per connection, in addition to the space required by the site.
For example, for 20 parallel connections, you must plan for:
• RAM: 67.8 MB (7.8 MB for this site, 60 MB for the NT server).
• Virtual memory (also called disk space or swap disk): 84 MB (20 MB for the connections, 64 MB for the NT server).
To avoid a drop in the system performance, the total number of connections to all the dynamic WebDev sites or to one
dynamic WebDev site must be limited:
• by the developer of the site, in the WebDev site by programming.
• by the server administrator in the different management tools supplied with the WebDev application server.
• by the site manager, in the remote WebDev administrator.
To optimize your configuration, see Checking the configuration of the current computer (WebDev administrator of the
application server), page 52.

2 .1 .2 Step 2 : Create an FTP account

On most FTP servers, the following elements must specified when creating an FTP account:
• the user name (or "login")
• the associated password
• the base directory (also called "Home directory"). This home directory corresponds to the directory where the files requi-
red to install the site will be transferred. The setup is automatically performed once the files have been transferred.
This home directory must be accessible in read/ write.
Example: creating an FTP account on the FTP server of IIS 5:
To create an FTP account with IIS (version 5):
1. Create a new user on the computer. For example, to create a new user in Windows 2000, select "Start .. Control
panel .. Management tools .. Computer management".
2. Start the IIS service manager. For example, in Windows 2000, select "Start .. Control panel .. Management tools ..
Internet Service Manager".
3. Display the popup menu of the "default FTP site" and select "New .. Virtual directory".
4. In the wizard, specify:
• the alias of the FTP transfer directory for the user: this alias corresponds to the name of the FTP transfer directory.
You must necessarily enter the user name (defined when creating the user).
• the access path of the FTP transfer directory for the user: this directory corresponds to the physical directory where
the file transfers will be performed.
Caution: This access path to the FTP transfer directory must be supplied when defining a WebDev account in the
WebDev account manager.
• the access rights: the home directory must be accessible in read/ write.
5. Validate. The FTP account is created.
 WebDev application server 13
Web server: First deployment

Creating an FTP account in Linux

In most cases, an FTP account corresponds to a Linux user account.
The home directory of this system account corresponds to the FTP download directory. This home directory corresponds to
the directory where the files required to install the site will be transferred. The setup is automatically performed once the
files have been transferred.
The home directory must be accessible in read/ write to the relevant user and to the "webdev18" group (or at least to the
"apache" group). The user must belong to the "webdev18" group. This group is automatically created when installing the
WebDev application server.

Example:
/ usr/ sbin/ useradd -d / home/ client -g webdev18 client
cd / home
chown client:webdev18 client
chmod ug+rwx client

2 .1 .3 Step 3 : Create a WebDev account

The creation of a WebDev account can be performed:
• on a Windows server, via the account manager (WDCompte) started in interactive mode or in command line.
• on a Linux server, via the remote administrator. See “Preparing the remote administrator”, page 25 for more details.

Solution 1: To create a new WebDev account via the account manager:

1. Start the WebDev account manager (WDCompte):
• via the associated icon in the program group of WebDev Application Server 18.
• from the administrator of the WebDev application server ("Management" tab, "Accounts" button).
Note: The remote administrator of WebDev Deployment can also be used to manage the WebDev accounts remotely.
2. Click the "Create" button.
Note: A WebDev account is automatically created for the server administrator when the WebDev application server is
installed. This account (ADMINISTRATOR login) allows the server administrator to use the remote WebDev administra-
tor in order to supervise all the dynamic WebDev 18 sites installed on a Web server.
3. Specify the login of the site manager (his name), his password and confirmed password.
Note: For security reasons, we recommend that you use a password different from the one used for the FTP account.
4. Validate. The details of the WebDev account are displayed.
5. Specify:
• the user details: Last name, first name, address, …
• the sites assigned to the site manager (if necessary)
• the maximum number of authorized connections:
Maximum number of simultaneous connections allowed for all the dynamic WebDev sites of the account. The site
manager can distribute them among his WebDev sites via the remote WebDev administrator.
•the directories used by the WebDev sites:
- FTP transfer directory:
home directory defined for the FTP account. This directory must necessarily be the same as the one defined as
"home directory" for the FTP account used to deploy the sites (See “Step 2: Create an FTP account”, page 12).
Example:
FTP transfer directory: D:\ Customers\ Smith\ FTP
- home directory of the sites:
home directory where all the WebDev sites belonging to the site manager will be installed. Each site will be instal-
led in a sub-directory of this home directory. By default, the sub-directory and the site will have the same name.
Note: Several sites with the same name can be deployed by specifying the name of the sub-directory to use at the
time of deployment.
14 WebDev application server
Web server: First deployment

Example:
Home directory of the sites: D:\ Customers\ Smith\ Sites
The sites belonging to the site manager (HTML files, …) will be installed in a sub-directory. For example, the site
named "PhotoSite" will be installed in "D:\ Customers\ Smith\ Sites\ PhotoSite".
- home directory of Webservices:
home directory where all the WebDev of WinDev Webservices belonging to the site manager will be installed. Each
Webservice will be installed in a sub-directory of this home directory. By default, the sub-directory and the Webser-
vice will have the same name.
Note: Several Webservices with the same name can be deployed by specifying the name of the sub-directory to
use at the time of deployment.
Example:
Home directory of Webservices: D:\ Customers\ Smith\ Webservices
The Webservices of the site manager (AWWS files, …) will be installed in a sub-directory. For example, the
"WSPhoto" Webservice will be installed in the "D:\ Customers\ Smith\ Webservices\ WSPhoto" directory.
-
home directory where the HyperFileSQL data files used by the dynamic WebDev sites and by the Webservices
belonging to the site manager will be installed. For each site or Webservice, the data files will be installed in a sub-
directory of this home directory. By default, the sub-directory and the site or Webservice will have the same name.
Note: The data can be shared among several sites or Webservices by specifying the name of the data sub-direc-
tory at the time of deployment.
Example:
Home directory of the data files: D:\ Customers\ Smith\ Data
The data files of the site (.FIC, .NDXand .MMO files) will be installed in a sub-directory. For example, the data for
the site named "PhotoSite" will be installed in "D:\ Customers\ Smith\ Data\ PhotoSite".
6. Validate. The account is created.
 WebDev application server 15
Web server: First deployment

Solution 2: To create a new WebDev account from a command line and a parameter file, the fol-
lowing operations must be performed:
1. Create a file containing the parameters of the account to create. This file is a text file with any extension. This file
has the following structure:

[MAIN]
NOM=Smith
PRENOM=Alan
LOGIN=ASmith
PASSWORD=Secret
SOCIETE=MyCompany
CONNEXION=100 ; Number of connections to distribute among the sites/Webservices
EMAIL=asmith@mycompany.com
ADRESSE=
TELEPHONE=
DIVERS=
INTERDIT=0 ; 0 = Active user, 1 = Locked user
[DIR]
FTP=d:\Customers\Smith\FTP
APPLI=d:\Customers\Smith\Sites
WEBSERVICE=d:\Customers\Smith\Webservices
FICHIER=d:\Customers\Smith\Data
2. Start WDCompte from the following command line :
WDCompte.exe /CREATEUSER /PARAM=<Full path of parameter file>
Caution: This file is NOT destroyed at the end of account creation.

2 .1 .4 Step 4 : Configure t he access r ight s on t he server

In Windows 2000 or Windows NT, you must configure the access rights to the server:
• to perform a remote setup of a site.
• to use a WebDev site.
These access rights are used to grant specific authorizations: authorization to write into the file transfer directory, …
Depending on the type of access chosen for the setup (authenticated or anonymous access), the necessary rights may dif-
fer.
Note: This setting is required for the servers running Windows 2000, XP or NT, with disks in NTFS format. In Windows 95,
Windows 98 or Windows Me, no management of access rights is available. The access rights to the files cannot be restric-
ted.
Caution
Even though WebDev 18 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. This setting cannot be done by a novice.
You must have a minimum knowledge of this area or have knowledgeable help.
Our Assistance Directe© service is available to help you configure these non-PC SOFT elements.
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.
16 WebDev application server
Web server: First deployment

1. Rights required to perform a remote setup or update (by FTP)

Access rights for the FTP account
These rights are required regardless of the access type used for the setup or update by FTP (authenticated access or ano-
nymous access).
Reminder: The home directory of the FTP account must correspond to the home directory specified in the WebDev account
manager.
The FTP account must have read/ write rights in its home directory. This setting must be performed when creating the FTP
account.
Access rights for the HTTP server
Setup with an anonymous access URL
The access rights are configured according to the Windows account that runs the AWP manager. This Windows account
must be able to:
• Create a sub-directory in the directories of the sites and Webservices of the client.
• Create a sub-directory in the data directory of the client.
• Create a temporary directory.
• Read and write in the FTP directory of the client.
• Create registry keys in "HKEY_LOCAL_MACHINE\ Software\ PC SOFT\ WebDev\ 18.0\ Applications" and in
"HKEY_LOCAL_MACHINE\ Software\ PC SOFT\ WebDev\ 18.0\ Webservices" (use regedt32 to define these rights in Win-
dows NT and 2000, regedit in Windows XP and later).
• Read and run the programs found in the setup directory of WebDev and in its sub-directories.
• Modify the data files of the user accounts of WebDev (found by default in the "Accounts" sub-directory of the setup direc-
tory of the application server).
Setup with an authenticated access URL
The access rights are configured according to the Windows account that runs the WD180INSTAWP manager. This account
will be identical to the FTP account. This Windows account must be able to:
• Create a sub-directory in the site directory of the client
• Create a sub-directory in the data directory of the client
• Create a temporary directory
• Read and write in the FTP directory of the client
• Create registry keys in "HKEY_LOCAL_MACHINE\ Software\ PC SOFT\ WebDev\ 18.0" (use regedt32 to define these
rights).
• Read and run the programs found in the setup directory of WebDev and in its sub-directories.
• Modify the data files of the user accounts of WebDev (found by default in the Accounts sub-directory of the setup direc-
tory of the application server).
For a Linux server
The access rights are configured according to the "Linux" account that runs the AWP manager. This account will be identi-
cal to the FTP account. This account must be able to:
• Create a sub-directory in the directories of the sites and Webservices of the client.
• Create a sub-directory in the data directory of the client.
• Create a temporary directory.
• Read and write in the FTP directory of the client.
• Create the configuration files (.conf) in the / etc/ PC SOFT/ WEBDEV/ 18.0/ Applications/ directory and in the / etc/ PC
SOFT/ WEBDEV/ 18.0/ Webservices/ directory
• Read and run the programs found in the setup directory of WebDev and in its sub-directories.
• Modify the data files of the user accounts of WebDev (found by default in the Accounts sub-directory of the setup direc-
tory of the application server).
 WebDev application server 17
Web server: First deployment

Access rights for the administrator of WebDev Application Server

The access rights are configured according to the Windows account that runs the administrator of WebDev Application Ser-
ver. This account depends on the setup mode of the local WebDev administrator.
1. If the administrator of the WebDev application server is not run in service, it is the account that opened the Win-
dows session.
2. If the administrator of WebDev Application Server is run in service, it is the account defined in the control panel of
the service.
In Linux, it is the "root" account.
This Windows account must be able to:
• Modify the setting of the Web server (create virtual directories).
• Stop and restart the Web server.
For example, if the server is IIS 4 or 5, the Windows account must be able to:
- Create registry keys in "HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Services\ W3SVC\ Parameters" (use
regedt32 to define these rights).
- Stop and restart the Web server.
For example, if the server is Apache, the Windows account must be able to:
- Modify the srm.conf file (Apache 1.3.x) or httpd.conf (Apache 2.x) found in the CONF sub-directory of the setup directory of
the Apache server.
- Stop and restart the Web server.

2. Rights required to use a site or a Webservice deployed on a WebDev Application Server

Access rights for the HTTP server
The access rights are configured according to the Windows account that runs 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 WebDev dynamic site, .AWP file for an AWP site and .AWWS
file for a Webservice).
This account must be able to:
• Read the files in the directory of the site or Webservice.
• Read and write in the data directory of the site or of the Webservice.
3. How do I find out the Windows account that runs the AWP protocol?
In the IIS 5 and 6 server (Windows NT/2000/XP/2003 Server)
1. Start the Internet service manager ("Start .. Run .. inetmgr.exe").
2. Display the properties of the "WWW" service.
3. Click the "Directory Security" tab.
4. Display the authentication methods for the anonymous access ("Modify" button).
18 WebDev application server
Web server: First deployment

The Windows account corresponds to the user name that was used to open an anonymous session ("Modify" button)

In the IIS 7 server (Windows Vista and Windows Seven)

1. Start the Internet service manager ("Start Menu .. inetmgr")
2. On the home page of the server, double-click the "Authentication" feature
3. Select the "Anonymous authentication" method
4. In the "Actions" column or the popup menu, click "Modify"
5. The dialog box that is opened presents the user account

For the Apache server

1. Start the control panel of services.
2. Display the properties of the Apache service.
3. The corresponding Windows account is displayed:
• the system account
• another Windows account.

4. How do I find out the Linux account that runs AWP?

The name of the account that runs the AWP protocol is written in the configuration file of Apache, in the "User" and "Group"
entries.
 WebDev application server 19
Web server: First deployment

5. How do I configure the rights on the registry

To use the regedt32 program:
• Start regedt32 ("Start .. Run .. Regedt32" from the Windows desktop)
• Select "HKEY_LOCAL_MACHINE\ SOFTWARE\ PC SOFT\ WEBDEV\ 18.0"

• Select "Security .. Authorizations". Check whether the Windows account that runs the AWP protocol has sufficient rights
to create registry keys ("Full control").

2 .1 .5 Step 5 : Parameters to transmit

The parameters required to perform a remote setup (direct setup or setup by package) are as follows:
• Name of the Web server (Address of the server). You can specify:
• the name of a computer accessible via network (Intranet for example). Example: "TestServer"
• an IP address. Exemple: 123.3.250.12
• an Internet address. Example: www.success.eu
• Name and associated password for the FTP account (defined in the FTP server).
• Name and associated password for the WebDev account (defined in the WebDev account manager).
20 WebDev application server
Web server: First deployment

2 .2 Deployment via physical media (CD, …)

To deploy a WebDev site or a WebService by physical media, you must:
• Step 1: Check the configuration of the server.
• Step 2: Install the WebDev site on the server.
• Step 3: Configure the access rights on the server.

2 .2 .1 Step 1 : Check t he conf igurat ion of t he Web ser ver

To install a site developed in WebDev on an Internet server (installed at the hosting company 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 the setup program was created on the develop-
ment computer).
• the WebDev 18 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 the setup program was created on
the development computer).
To get fast response time, a powerful computer must be used for the Internet server.
Important: The resources required per connected Web user:
For each connected Web user, you must plan for:
• about 400 KB of RAM per connection, in addition to the memory required by the server.
• about 1 MB of disk space (virtual memory) per connection, in addition to the space required by the site.
For example, for 20 parallel connections, you must plan for:
• RAM: 67.8 MB (7.8 MB for this site, 60 MB for the NT server).
• Virtual memory (also called disk space or swap disk): 84 MB (20 MB for the connections, 64 MB for the NT server).

Note: the notion of "connection" only makes sense for the dynamic WebDev sites. With the AWP sites and the Webservices,
the server resources are only used during the time it takes to process a user request.

To avoid a drop in the system performance, the total number of connections to all the dynamic WebDev sites or to one
dynamic WebDev site must be limited:
• by the developer of the site, in the WebDev site by programming.
• by the server administrator in the different management tools (local or remote) supplied with the WebDev 18 application
server.
• by the site manager, in the remote WebDev administrator.

2 .2 .2 Step 2 : I nstalling a dynamic WebDev sit e 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 via the WebDev administrator (check "Lock the server" in the "Management" tab),
• disconnect all the Web users from the site.
2. Choose the setup language: a setup wizard starts. Click "Next" to continue.
Note: The language of the wizard 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 application server 21
Web server: First deployment

("WebDev Account" button).

4. The setup automatically detects whether one or more of the following Internet servers are installed on the compu-
ter:
• IIS Version 2 to 8 (Microsoft Internet Information Server): Microsoft server supplied with FrontPage and with Win-
dows NT, 2000, XP, 2003 Server, Vista, 2008 Server and 7, 2012 Server and 8.
• Apache Version 1.3.x to 2.x: free Web server supplied by the Apache Software Foundation.
Three cases may occur:
- Case 1: your Web server does not appear in this list: select "Other server". You will have to configure the server
manually.
- Case 2: your Web server appears in the list but it is grayed: it means that it was not detected. You will have to con-
figure the server manually.
- Case 3: your Web server can be selected directly: select your server.
If no server is installed and if Apache was included in the setup by physical media, you will have the ability to
request its setup.
5. Select the setup directory:
• for the files of the site: HTML pages, …
• for the data files of the site
The paths corresponding to the selected WebDev account are automatically proposed:
• <site> corresponds to the setup directory of the site files defined in the account.
• <webservice> corresponds to the setup directory of the Webservice files defined in the account.
• <data> corresponds to the setup directory of the data files defined in the account.
• <webroot> specifies the root directory of the Web server of the computer. Depending on the selected Web server, the
root directory is detected and displayed. If the root directory of the Web server is not displayed, it can be entered in
the gray area or it can be found via the "…" button.
• Caution: if the area is already filled, avoid modifying it.
6. Choose to generate the statistics file. If this option is selected, the site/ Webservice manager will be able to directly
view the traffic statistics about the site/ webservice. In this case, specify the directory for generating the statistics file.
By default, the directory proposed corresponds to a sub-directory of the directory of data files for the site/ Webservice.
Note: This option can also be modified in the WebDev administrator or in the remote administrator.
7. Updating the data files.
To update the data files associated with the WebDev site or the Webservice, choose to run the automatic modification
of the data files.
Contact the provider of the site/ webservice if you don’t know whether you must perform this update or not.
Caution: no site/ Webservice that uses these data files must be currently run. Use the WebDev administrator to check
that there is no current connection and to stop the sites (check "Lock Server" in the "Configuration" tab or "Locked site"
in the "Sites" tab, or "Locked Webservices" in the "Webservices" 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.com/ index.awp, you need to specify
www.mysite.com as reference URL.
In the case of a webservice: specify the URL (Internet address) where the Webservice (.AWWS file) is accessible. This
address will be used to build the import file for the Webservice (WDSL file) needed 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. See the WebDev
documentation for more details.
10. The setup is completed:
• Click the address proposed to run the test of the WebDev site locally. This option can be used only if the Web server
was configured automatically. The "Clipboard" option is used to retrieve this address.
• Click "Done" to exit from the setup.
22 WebDev application server
Web server: First deployment

11.Configuring the Web server: If the Web server was not configured automatically, the setup wizard will provide the
information required for a manual setup. See “Appendix 2 - Configuration of servers”, page 35 for more details.
12. Unlock the sites that may be locked via the WebDev administrator.
13. Run the test of the WebDev site from the WebDev administrator with the "Test page" option ("Configuration" tab) or
by using the link supplied at the end of setup.
Note: The WebDev administrator (WD180ADMIN.EXE) must be started and run in background task. It can be installed
as a service.

2 .2 .3 Step 3 : Conf igure t he access r ight s on t he server

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 file transfer directory, …
Caution
Even though WebDev 18 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. This setting cannot be done by a novice.
You must have a minimum knowledge of this area or have knowledgeable help.
Our Assistance Directe© service is available to help you configure these non-PC SOFT elements.
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.

1. Access rights for using a WebDev site or a Webservice

The access rights are configured according to the Windows account that runs 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 WebDev dynamic site, .AWP file for an AWP site and .AWWS
file for a Webservice).
This account must be able to :
• Read the files in the directory of the site or Webservice.
• Read and write in the data directory of the site or of the Webservice.
2. How do I find out the Windows account that runs the AWP protocol ?
See “2. Rights required to use a site or a Webservice deployed on a WebDev Application Server”, page 17.
 WebDev application server 23
Web server: First deployment

2 .2 .4 Summar y table about the necessar y r ights

The following user groups are used in this table :
• WWUSR: Group of WebDev users (It is the set of Windows/ Linux accounts used for FTP)
• IUSR: Group of anonymous Internet users (it is the set of accounts running the AWP protocol on each virtual server of
the machine). For example: on a Windows machine using IIS with only one virtual server, it is the IUSR_ComputerName
account.
• LOGIN: a member of the WWUSR group.
NTFS rights
Directory User Necessary rights
WebDev directory WWUSR and IUSR Read + Run
Sub-directory of the account files WWUSR Read + Write
IUSR Read
AWP sub-directory WWUSR and IUSR Read + Run
FTP directory of the LOGIN user LOGIN Full control
Directory of the sites and webservices of the LOGIN user LOGIN Full control
IUSR Read + List
Data directory of the LOGIN user LOGIN Full control
IUSR Read + Write + List
Temporary directory of the system WWUSR and IUSR Read + Write + List +
Modification
File of the metabase (c:\ winnt\ system32\ inetserv\ meta- WWUSR Read + Write
base.bin) IUSR Read
Directory of SaaS data IUSR Read + Write
Rights on the registry (Windows only): automatically configured during the setup
HKEY_LOCAL_MACHINE\ Software\ PC SOFT\ WEBDEV\ 18. WWUSR and IUSR Read
0
HKEY_LOCAL_MACHINE\ Software\ PC SOFT\ WEBDEV\ 18. WWUSR Read + Write
0\ Applications IUSR Read
HKEY_LOCAL_MACHINE\ Software\ PC SOFT\ WEBDEV\ 18. WWUSR Read + Write
0\ Webservices IUSR Read
Rights on the configuration files (Linux only)
/ etc/ PC SOFT/ WebDev/ 18.0 WWUSR and IUSR Read
/ etc/ PC SOFT/ WebDev/ 18.0/ Applications WWUSR Read + Write
IUSR Read
/ etc/ PC SOFT/ WebDev/ 18.0/ Webservices WWUSR Read + Write
IUSR Read
Rights in IIS (Windows and IIS only)
WD180AWP.EXE Execution in anonymous mode by using the
IUSR guest
WD180INSTAWP.EXE Execution in authenticated mode only by using
the basic authentication.
24 WebDev application server
Web server: First deployment

2 .3 A WebDev site with the same name is already installed on the ser-
ver
2 .3 .1 Setup by FTP
During a setup by FTP, two sites with the same name can be installed on the same Web server, even if these sites belong to
different site managers. You can choose a deployment name that is different from the project name in the setup wizard.

2 .3 .2 Setup by physical media

During a setup by physical media, two cases may occur if the site to install and an existing site have the same name:
• Case 1: the new site is an upgraded version of the existing site:
Its setup will replace the files of the existing site. Important: first lock the site using the WebDev administrator.
• Case 2: the new site has no relation to the site already installed:
If this site is installed, the existing site will no longer be referenced in the WebDev administrator and it will no longer be
available for use (the site is still found on disk but there is a single entry per site name in the registry).

2 .4 Where are the files of the WebDev site found after setup?
2 .4 .1 Case of a WebDev sit e (dynamic or AWP sit e)
After setup, the various elements of a site are found in the following directories:
• Site directory: sub-directory of the directory for the sites of the WebDev account used for deployment. This directory
bears the name chosen during the site’s deployment (name of the project by default).
This directory contains all the elements found in the "Exe" directory on the development machine except for the HyperFi-
leSQL Classic data files. The most common files are: the site libraries (WDL and AWL files).
• _WEB directory: sub-directory of the site directory. This directory bears the name of the project (in uppercase) followed by
_WEB. This directory is declared as an alias in the Web server. Its content is directly accessible from Internet.
This directory contains all the elements found in the directory of same name on the development computer. The most
common files are: the HTML pages (HTM files), the AWP dynamic pages (AWP files), the images, the CSS style sheets and
the JavaScript files.
• Directory of data: sub-directory of the data directory for the WebDev account used for deployment. This directory has the
name chosen when deploying the site (by default, this name corresponds to the deployment name of the site).
This directory contains the HyperFileSQL Classic data files. These files have the following extensions: FIC, NDX, MMO,
FTX.

2 .4 .2 Case of a Webservice
After setup, the different elements of a Webservice are found in the following directories:
• Site directory: sub-directory of the directory for the sites of the WebDev account used for deployment. This directory
bears the name chosen during the site’s deployment (name of the project by default).
This directory contains some of the elements found in the "Exe" directory on the development computer. The most com-
mon files are: the Webservice description file (WSDL file).
• _WEB directory: sub-directory of the site directory. This directory bears the name of the project (in uppercase) followed by
_WEB. This directory is declared as an alias in the Web server. Its content is directly accessible from Internet.
This directory contains some of the elements found in the "Exe" directory on the development computer. The most com-
mon files are: the Webservice file (AWWS file) and the HTML test pages.
• Directory of data: sub-directory of the data directory for the WebDev account used for deployment. This directory has the
name chosen when deploying the site (by default, this name corresponds to the deployment name of the site).
This directory contains the HyperFileSQL Classic data files.
 WebDev application server 25
Web server: First deployment

2 .5 M igrating a WebDev 1 .5 site or a site version 7 (and later)

to WebDev 1 8
If you owned WebDev 1.5 deployment version, WebDev 7 deployment version or the WebDev application server (version 9
to 16), some site managers may want to migrate their sites from WebDev 1.5, WebDev 7, WebDev 9 (and later) to WebDev
18.
Some operations must be performed on the server.
The following steps are used to migrate an existing WebDev site to WebDev 18:
1. Install (if necessary) the WebDev 18 application server on the server.
Note: WebDev 1.5, WebDev 7 deployment version or the WebDev application server version 9 to 16 can be installed on
the same server.
2. Create a WebDev 18 account associated with the site manager:
• via the WebDev administrator ("Configuration" tab, "WebDev account" button).
• via WDCompte.EXE found in the setup directory of WebDev 18. This tool can also be used to retrieve all the characte-
ristics of the accounts created with an earlier version.
3. Supply (if necessary) the details regarding the WebDev account to the site manager.
Notes:
• The same FTP account can be used to install the WebDev 1.5 sites, the WebDev sites version 7 to 17 or WebDev 18.
• If several versions of the same site must be installed on the same server (versions 1.5 to 17), these sites must have dif-
ferent names. Indeed, the alias created in the server corresponds to the name of the site. If the site is not renamed, the
WebDev site with an earlier version may not operate properly.
• If the site in version 18 replaces the previous version of the site, you have the ability to physically delete the site corres-
ponding to the previous version.

2 .6 Preparing the remote administrator

The remote WebDev administrator is an optional tool supplied with the WebDev 18 application server. The remote WebDev
administrator is a WebDev site, installed on the deployment Web server. This site allows:
• the site manager to directly manage his WebDev sites installed on the Web server.
• the server administrator to remotely manage the WebDev accounts and the WebDev sites installed on the Web server.
Regardless of the type of deployment performed, the Web server must be configured to allow the use of the remote Web-
Dev administrator:

Initial deployment Initial deployment

by FTP by physical media

Using the remote WebDev admi- Operation to perform: Specify the Operation to perform: Specify the star-
nistrator startup address tup address

Note: For optimal security, we recommend you use the remote administrator in the following context:
• SSL access (with a purchased or auto-signed certificate)
• Isolated on a virtual site different from the rest of the sites or Webservices and where the AWP protocol is executed by a
user account created only for this purpose.

Address for starting the remote WebDev administrator

To use the remote WebDev administrator, the site manager must know the address for starting the remote WebDev admi-
nistrator.
This address must be transmitted to the site manager.
26 WebDev application server
Web server: First deployment

On a Windows server, this address has the following format:

http:/ / Server/ WD180AWP/ WD180AWP.EXE/ CONNECT/ WDAdminWeb180
where Server corresponds to the name of the Web server where the WebDev application server is installed. This name can
be:
- an IP address (192.178.1.130 for example)
- the name of the computer (DocComputer for example)

On a Linux server, this address has the following format:

http:/ / Server/ WD180AWP/ WD180AWP/ CONNECT/ WDAdminWeb180
or
http:/ / Server/ WD180AWP/ WD180Awp.exe/ CONNECT/ WDAdminWeb180
where Server corresponds to the name of the Web server where the WebDev application server is installed. This name can
be:
- an IP address (192.168.1.130 for example)
- the name of the computer (DocComputer for example)
The case sensitivity must be complied with.

Note: Secured access to the remote administrator

If the remote WebDev administrator was secured during its setup (and if an SSL key was installed to secure the remote
WebDev administrator), the remote WebDev administrator will be automatically started in secured mode.
In Windows, a registry key allows you to specify whether the WebDev remote administrator must be started in secured
mode or in normal mode:
Registry key: HKEY_LOCAL_MACHINE/ SOFTWARE/ PC SOFT/ WebDev/ 18.0
Name of the value: SSLADMIN (REG_SZ)
In Linux, all you have to do is add the following line into the / etc/ PC SOFT/ WEBDEV/ 18.0/ WebDev.conf file:
SSLADMIN = 1
The value 1 is used to automatically enable the secured mode.
 WebDev application server 27
Troubleshooting

3 . TROUBLESHOOTING
This chapter presents the main problems (and their solutions) that may occur when using the WebDev application server.

3 .1 Web server: Common problems

The most common problems are as follows:
• No Web server is installed on your computer. In this case, install a Web server and reinstall WebDev.
To check whether a Web server is installed, click the "Server" button in the WebDev administrator ("Configuration" tab). If
the selected option is "Other", then no Web server is installed on your computer or your Web server is not recognized by
WebDev.
Note: The WebDev application server is provided with a copy of the free Apache Web server.
• A Web server is installed but this server is not started. In this case, start the Web server used (see the documentation of
the Web server for more details).
• A Web server is installed but it does not work in the current environment. In this case, install a Web server that is com-
patible with your environment and reinstall WebDev.
For example, the FrontPage and OmniHTTPd servers do not operate in Windows NT and 2000.
• Several Web servers are installed on your computer and these servers are started at the same time. In this case,
choose the Web server that must be used with WebDev and stop the additional Web server.
Note: In the WebDev administrator, check whether the Web server configured in the "Server" option ("Configuration" tab)
corresponds to the selected server.

3 .2 Identification and resolution of TCP/IP problems

3 .2 .1 Checking t he presence of the TCP/IP layer and IP addresses
To check whether the TCP/ IP layer is installed, run the IPCONFIG command from a DOS prompt.
A response of this type should be displayed:
IP configuration of Windows
IP Address: 192.168.1.50
Sub-network mask: 255.255.255.0
Default Gateway: 192.158.1.220
Where 192.168.1.50 represents an example of a valid IP address.
If an error message is displayed or if the IP address is 0.0.0.0, then no TCP/ IP layer is installed on the computer.
Install the network layer (in the configuration panel of Windows, double-click "Network" and "Add/ Protocol").

3 .2 .2 Checking t he conf igurat ion of t he TCP/IP layer

To check whether the TCP/ IP layer is installed and configured properly, you must perform a ’ping’ on the loop address
(127.0.0.1).
To do so, run the PING 127.0.0.1 command from a DOS prompt.
28 WebDev application server
Troubleshooting

A response of this type should be displayed:

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
If an error message is displayed, then the TCP/ IP layer was not installed properly on this computer.
Install the network layer (in the configuration panel of Windows, double-click "Network" and "Add/ Protocol").

3 .3 Problems with the manager of the AWP protocol

Several problems can occur:
• The AWP protocol manager is not configured properly on the Web server. See “Appendix 2 - Configuration of servers”,
page 35.
• The AWP protocol manager (WD180AWP.EXE) is not found in the AWP sub-directory of WebDev. In this case, reinstall
WebDev.

3 .4 Problems linked to a setup by FTP

The list below presents the error messages that are displayed in the wizard for remote setup (at the site manager). Some of
these messages require specific actions for configuring the deployment Web server.
Several solutions are proposed for each error.
Error messages can be displayed at different steps of the remote setup.

3 .4 .1 Step 1 : Entering t he logins and the Server /FTP passwords (site set up)
The setup wizard checks the validity of the logins and passwords. The list of errors that can occur is as follows.

Failure checking the user password: no information was returned by the server.
The possible problems are as follows:
• The Web server does not operate
Solution: Restart the Web server on the server.
• The FTP server does not operate.
Solution: Restart the FTP server on the server.
• The FTP server is not configured properly: wrong user name, …
Solution: Check the configuration of the FTP server for the user.
Caution: If you are using the IIS FTP server, check whether:
- the user is defined at Windows level
- the alias of the FTP transfer directory corresponds to the Windows user name.
• The WebDev application server is not installed properly.
Solution: Reinstall the WebDev application server.
 WebDev application server 29
Troubleshooting

Wrong FTP password or the FTP server cannot be accessed.

The possible problems are as follows:
• The FTP password specified by the site manager is incorrect.
Solution: Check the FTP password and give this password to the site manager.
• The FTP server does not operate.
Solution: Restart the FTP server.
• The number of authorized connections on the FTP server has been exceeded.
Solution: The site manager must wait for a connection to the FTP server to be freed.
• The address of the Web server is incorrect.
Solution: Indicate to the site manager the exact address of the Web server where the site must be installed by FTP.

Failure checking the user password: the user is unknown. Check the address of the server and
the user name.
The possible problems are as follows:
• The WebDev account manager does not recognize the site manager.
Solution: Check whether a WebDev account was created in the account manager for this site manager and give the cor-
responding "login" to the site manager.

Failure checking the user password: no information was returned by the server.
The possible problems are as follows:
• The password entered during the remote setup does not correspond to the password defined in the account manager.
Solution: Check the password associated with the site manager in the WebDev account manager and give this password
to the site manager.

3 .4 .2 Step 2 : Installing t he sit e (setup or update)

The setup wizard is used to install or update the site. The list of errors that can occur is as follows.

Unable to create a temporary directory on the server. Contact the server administrator.
The possible problems are as follows:
• The Windows account that runs the WD180AWP protocol manager has insufficient rights to write into the registry.
Solution: Grant the necessary rights to the Windows account.
Note: to find out which account is running WD180AWP.EXE, start the Internet service manager (for IIS, "Start .. Run ..
Inetmgr.exe" from the Windows desktop) and display the properties of the "WWW" service. The Windows account corres-
ponds to the user name used to start an anonymous session. See “Summary table about the necessary rights”, page 23
for more details.

The client name is unknown. Check the client name and the associated password.
The possible problems are as follows:
• The WebDev account manager does not recognize the site manager.
Solution: Check whether a WebDev account was created in the account manager for this site manager and give the cor-
responding "login" to the site manager.

The files required for setup have not been transmitted properly. Check whether the user name
and the FTP password are correct and correspond to the owner account of the site.
The possible problems are as follows:
• An error occurred during the FTP transfer and the file installed on the server cannot be read.
Solution: The site manager must restart his setup.
Caution: If it is a first setup, the site manager must delete the server description from the "Remote update" list.
30 WebDev application server
Troubleshooting

The setup file is invalid. The file was not transmitted properly or the transmitted file was dama-
ged.
The possible problems are as follows:
• An error occurred during the FTP transfer and the file installed on the server cannot be read.
Solution: The site manager must restart his setup.
Caution: If it is a first setup, the site manager must delete the server description from the "Remote update" list.

Error while decrypting the setup information. Check the password used.
The possible problems are as follows:
• The password entered during the remote setup does not correspond to the password defined in the account manager.
Solution: Check the password associated with the site manager in the WebDev account manager and give this password
to the site manager.

Unable to add programming due to the following error: XXX

When programming a delayed setup, one of the following problems occurred:
• Insufficient memory
Solution: Free memory space on the Web server and retry the delayed setup.
• Unable to find the local WebDev administrator, check whether the WebDev application server is installed properly
The local WebDev administrator does not respond to the programming request.
Error while starting the local WebDev administrator: check whether the WebDev application server is installed properly.

A site with the same name is already installed on this server. The same server cannot host two
sites with the same name. Rename your site or uninstall the existing one. If it is the same site,
you must perform a site update (instead of a site setup).
During a setup by FTP, two sites with the same name cannot be installed on the same Web server, even if these sites
belong to different site managers.
For a first setup of the site on the server, the manager of the WebDev sites must rename his site (rename his project).
Note: To perform a setup by FTP, the site manager must select "Remote update" when installing his site by FTP (instead of
"Remote setup").
 WebDev application server 31
Troubleshooting

Unable to create the directory of the site. Contact the server administrator.
The possible problems are as follows:
• The home directory of the sites does not exist
Solution: Check the home directory of the sites specified in the account manager. Check the existence of this directory.
• Insufficient access rights to the home directory of the sites
Solution: grant the necessary rights to the Windows account that runs WD180AWP.EXE.
Note: to find out which account is running WD180AWP.EXE, start the Internet service manager (for IIS, "Start .. Run ..
Inetmgr.exe" from the Windows desktop) and display the properties of the "WWW" service. The Windows account corres-
ponds to the user name used to start an anonymous session. See “Summary table about the necessary rights”, page 23
for more details.

Unable to create the directory of the data files. Contact the server administrator.
The possible problems are as follows:
• The home directory of the data does not exist
Solution: Check the home directory of the data specified in the account manager. Check the existence of this directory.
• The access rights to the home directory of data are not sufficient
Solution: grant the necessary rights to the Windows account that runs WD180AWP.EXE.
Note: to find out which account is running WD180AWP.EXE, start the Internet service manager (for IIS, "Start .. Run ..
Inetmgr.exe" from the Windows desktop) and display the properties of the "WWW" service. The Windows account corres-
ponds to the user name used to start an anonymous session. See “Summary table about the necessary rights”, page 23
for more details.

Write error in the registry. Contact the server administrator.

The possible problems are as follows:
• The Windows account that runs the WD180AWP protocol manager has insufficient rights to write into the registry.
Solution: Grant the necessary rights to the Windows account. Use Regedt32.exe to grant the rights to write into the regis-
try ("Security .. Permissions" in Regedt32).
Note: to find out which account is running WD180AWP.EXE, start the Internet service manager (for IIS, "Start .. Run ..
Inetmgr.exe" from the Windows desktop) and display the properties of the "WWW" service. The Windows account corres-
ponds to the user name used to start an anonymous session.

Unable to open the file containing the custom error messages.

The possible problems are as follows:
• The message file was not supplied in the setup
Solution: Restart the setup and check whether the files required to customize the error messages are found (.REG file).

Error while writing into the registry when creating the custom error messages.
The possible problems are as follows:
• The message file is invalid.
Solution: Check whether the configuration file of the error messages supplied in the setup corresponds to the site to ins-
tall.
32 WebDev application server
Troubleshooting

3 .4 .3 Step 3 : Updating a sit e

When updating the site, the setup wizard checks whether the site is installed and configured properly. The list of errors that
can occur is as follows.
Unknown site name
The possible problems are as follows:
• The site is not installed on the server
Solution: Perform a full remote setup.
• The site is no longer referenced in the WebDev administrator
Solution: Reference the WebDev site in the WebDev administrator ("Sites" tab, "Add" button).

The name of the client does not correspond to the name of the site owner
The possible problems are as follows:
• This site was installed by another site manager.
Solution: In the WebDev account manager, assign the site to the corresponding WebDev account. Check whether the
home directories (for the data, the site and the FTP transfer) are correct.

Failure during the encryption

The possible problems are as follows:
• The encryption of the update failed.
Solution: Free memory space and/ or disk space on the computer that performs the update (computer of the site mana-
ger for instance).

Error while copying the information file. Check the information of the WebDev account and retry.
The possible problems are as follows:
• Unable to copy the temporary file that describes the status of the site. The user does not have the necessary rights in
the FTP directory
Solution: Grant write rights in the FTP directory.
• Unable to copy the temporary file that describes the status of the site. Insufficient disk space
Solution: Free disk space on the server.

3 .5 Error messages that can be displayed in the browser

A site developed in WebDev can display error messages on the browser of the client computers.
These error messages are presented in the online help for the WebDev application server.
 WebDev application server 33
Appendix 1 - Vocabulary of WebDev

A PPENDIX 1 - VOCABULARY OF WEB D EV

This page presents the main terms specific to WebDev used in the documentation of the WebDev application server.
Unless otherwise stated, all text referring to sites can be applied to Webservices.
Server administrator
Person responsible for installing software, sites, …on one or more servers at the host. For a shared server, the server
administrator is responsible for distributing the connections per site manager, in charge of the physical location of the sites
on the server, …
Remote WebDev administrator
Site installed on the Web server, allowing:
• the site manager to remotely check and/ or modify the configuration of his WebDev sites installed on a server.
• the server administrator to remotely check and/ or modify the configuration of all the WebDev sites installed on the ser-
ver. The server administrator can also manage the WebDev accounts.
WebDev administrator
Windows application installed on the server allowing the server administrator to configure the dynamic WebDev sites ins-
talled on the current server.
The WebDev administrator can also be used to create WebDev accounts.
WebDev account
Account associated with a site manager.
This account allows the server administrator to:
• group the sites that belong to a site manager.
• configure the number of authorized connections for a site manager.
• configure the setup directories of the sites
• configure the directory for file transfer (for a setup or an update by FTP)
This account allows the site manager to:
• use the remote administrator.
• perform remote setups and remote updates of the sites.
This account is created on a Web server by the server administrator via:
• the local administrator.
• the remote administrator.
Site developer
Person who creates and modifies WebDev sites with WebDev Development Version.
WebDev account manager (WDCompte)
Windows application used to create the WebDev accounts. This application is started by the server administrator on a Web
server. This application can only be used to create accounts for the current computer.
Note: The server administrator can also manage the WebDev accounts remotely via the remote management tool.
Hosting company
Company proposing to host Internet sites on their Web servers.
Web user
User of Internet sites.
Site manager
Person responsible for deploying and maintaining one or more WebDev sites. This person is in direct contact with the ser-
34 WebDev application server
Appendix 1 - Vocabulary of WebDev

ver administrator.
 WebDev application server 35
Appendix 2 - Configuration of servers

A PPENDIX 2 - CONFIGURATION OF SERVERS

1 Overview
To use the WebDev application server, a Web server must be found on the computer where the WebDev application server,
the WebDev sites and the Webservices are installed. This server enables you to runt the test of the developed sites and
Webservices.
Several Web servers are available for Windows: IIS, Apache, …
The configuration mode of these servers depends on:
• the publisher
• the version of the server,
• the current operating system,
• and other parameters.
The use of a Web server to run the test of the dynamic WebDev sites with the WebDev application server requires a specific
configuration for the CGI protocol.
This configuration is performed when installing the WebDev application server.

2 Installing the WebDev application server

When installing WebDev, the configuration of the Web server for the CGI protocol is automatically performed for the fol-
lowing Web servers:
• Apache 1.3.x and 2.x.
• IIS version 2 to 6: Microsoft Windows server.
If the Apache server is detected on the setup computer, it is automatically configured. In some cases, specific information
may be requested to manage the manual settings of Apache (Easy php, Wamp, …).
If the Apache server is not installed, IIS is automatically configured on the systems later than Windows Vista.
On the systems that use IIS 5 or 6 or without Web server, you have the ability to install an Apache server and to configure it
automatically.

3 Configuring the Web servers for WebDev manually

The method is as follows:
1. Create an alias on the AWP directory of WebDev.
2. This alias must have the following characteristics:
• Name: WD180AWP
• Associated directory: directory of the WebDev application server ("Programs\ AWP" sub-directory of the setup direc-
tory of WebDev).
• Associated rights: Read, Execute
36 WebDev application server
Appendix 2 - Configuration of servers

4 Configuring the " Apache 1 .3 .x" server for WebDev

4 .1 Configuring the server for the CGI protocol (AWP)
1. Edit the "srm.conf" file in a text editor. This file is found in the "/ Conf" sub-directory of the setup directory of the Apa-
che server.
2. Add the definition of the alias for the CGI protocol (WD180AWP.EXE) to the "srm.conf" file via the following line :
AliasScript / <Alias>/ "Directory of the application server".
For example, if the application server is found in "C:\ WEBDEV18\ Programs\ AWP" and if the name of the alias is
WD180AWP:
AliasScript / WD180AWP/ "C:/ WEBDEV18/ Programs/ AWP/ "
Note:
• the \ characters are changed into / .
• don’t forget the final / in the path.

4 .2 Configuring the server for the WebDev sites

To configure the Web server:
1. Edit the "srm.conf" file in a text editor. This file is found in the "/ Conf" sub-directory of the setup directory of the Apa-
che server.
2. Add the definition of the alias of images for each WebDev site to the "srm.conf" file:
Alias / <Name of Image Alias>/ "Directory of the site images".
Example for the WEBDEMO site:
Alias / WEBDEMO_WEB/ "C:/ WEBDEMO/ WEBDEMO_WEB/ "
Caution:
• With the Apache Web server, the alias name is "case sensitive". You need to respect the case defined for the alias in the
HTML pages referring to the images’ directory.
• An alias of images must be defined for each WebDev site.

5 Configuring the " Apache 2 .x" server for WebDev

5 .1 Configuring the server for the CGI protocol (AWP)
1. Edit the "http.conf" file in a text editor. This file is found in the "/ Conf" sub-directory of the setup directory of the Apa-
che server.
2. Add the definition of the alias for the CGI protocol (WD180AWP.EXE) to the "http.conf" file via the following line:
AliasScript / <Alias>/ "Directory of the application server"
For example, if the application server is found in "C:\ WEBDEV18\ Programs\ AWP" and if the name of the alias is
WD180AWP :
AliasScript / WD180AWP/ "C:/ WEBDEV18/ Programs/ AWP/ "
Note:
• the \ characters are changed into / .
• don’t forget the final / in the path.

5 .2 Configuring the server for the WebDev sites

To configure the Web server:
1. Edit the "http.conf" file in a text editor. This file is found in the "/ Conf" sub-directory of the setup directory of the Apa-
che server.
2. Add the definition of the alias of images for each WebDev site to the "http.conf" file:
Alias / <Name of Image Alias>/ "Directory of the site images".
Example for the WEBDEMO site:
Alias / WEBDEMO_WEB/ "C:/ WEBDEMO/ WEBDEMO_WEB/ "
 WebDev application server 37
Appendix 2 - Configuration of servers

Caution:
• With the Apache Web server, the alias name is "case sensitive". You need to respect the case defined for the alias in the
HTML pages referring to the images’ directory.
• An alias of images must be defined for each WebDev site.

6 Configuring the Web IIS server version 5 , 6 or 7 for WebDev

6 .1 Configuring the server for the CGI protocol (AWP)
1. Open the Microsoft Internet service manager (""Start .. Run .. Inetmgr.exe" from the Windows desktop).
2. Select the Web server into which the alias must be added.
3. Select "Action .. New .. Virtual directory".
4. In the wizard, specify the AWP protocol’s alias: WD180AWP. Click Next.
5. Select the directory of the AWP protocol ("Programs\ AWP" sub-directory of the setup directory of WebDev). Click
Next.
6. Grant the following rights: Read - Execute
7. Validate.

6 .2 Configuring the server for the WebDev sites

1. Open the Microsoft Internet service manager (""Start .. Run .. Inetmgr.exe" from the Windows desktop).
2. Select the Web server into which the alias must be added.
3. Select "Action .. New .. Virtual directory".
4. In the wizard, specify the alias of the directory containing the images of your project: <MyProject>_WEB. For exam-
ple: MARKET_WEB.
5. Select the directory containing your project’s images: <Project Name>_WEB. For example: C:\ WWProject\ MAR-
KET\ MARKET_WEB.
6. Grant the following rights: Read - Scripts
7. Validate.

7 Printing from the server

WebDev enables you to print from a WebDev site to a printer connected to the Web server. This option is useful for Intranet
sites installed on a Windows server.
To print a report on one of the printers connected to the Web server, the Web server must be configured. This configuration
depends on the type of printers used (local or network).

7 .1 Conf iguring t he Web server f or t he local print er s (IIS Web servers only)
1. In IIS, use a local account (IUSR) for the anonymous connections. This IUSR account corresponds to the "Internet
guest" account and it belongs to the "Guest" group.
To find out the IUSR account of the current Web server, see "How do I find out the account that runs the AWP protocol"
(page 17).
2. Check whether the printers used by this IUSR account are allowed to print ("Security" tab of the printer properties).
Note: No specific configuration is required for the other types of Web servers.
38 WebDev application server
Appendix 2 - Configuration of servers

7 .2 Conf iguring t he Web server f or t he net work print er s

1. Depending on the type of Web server used :
• In IIS, use a domain account for the anonymous connections. This account must belong to the "Domain guest" group.
• To find out the account of the domain of the current Web server, see "How do I find out the account that runs the AWP
protocol" (page 17)).
• For Apache, use an account of the domain.
• To find out the account of the domain of the current Web server, see "How do I find out the account that runs the AWP
protocol" (page 17)).
2. Check whether the domain account is allowed to write into the registry (Regedt32) :
• Start regedt32 ("Start .. Run .. Regedt32" from the Windows desktop).
• Select "HKEY_LOCAL_MACHINE\ SOFTWARE\ PC SOFT\ WEBDEV\ ’18.0".
• Select "Security .. Authorizations". Check that the domain account is allowed to create registry keys ("Total control").
3. Check whether the printers can be accessed by the Web server.
4. Check whether the printers used by the domain account are allowed to print ("Security" tab of the printer proper-
ties).
 WebDev application server 39
Appendix 3 - Registry

A PPENDIX 3 - R EGISTRY
1 Configuring the registry for the WebDev setup
When initializing the WebDev application server on a Windows server, the information about WebDev (application server
and protocol manager) and about the WebDev administrator are automatically saved in the registry, at the following entry:
HKEY_LOCAL_MACHINE/ SOFTWARE/ PC SOFT/ WebDev/ 18.0
When installing a WebDev application server on a Linux server, the information about WebDev (application server and pro-
tocol manager) and the WebDev administrator are automatically saved in the following configuration file:
/ etc/ PC SOFT/ WEBDEV/ 18.0/ WEBDEV.conf
This information is automatically updated when the parameters of the WebDev administrator are modified.
Note: the different registry entries are given for information only and they allow you to check whether the WebDev applica-
tion server is installed properly. All the entries are in "character string" type (REG_SZ) even if they contain a numeric value.
The following entries are created in the registry and in the configuration file:
ADMINLOG:
Path of the log file for the setups by FTP. This parameter is defined in the WebDev administrator.
ALLOW_REMOTEINSTALL:
Allow to perform remote site setups (by FTP). This parameter is defined in the WebDev administrator .
ALLOW_REMOTEUPDATE:
Allow to perform remote site updates (by FTP). This parameter is defined in the WebDev administrator.
AWPPATH:
Path of the WD180AWP.EXE program
BINPATH:
Path of the WD180SESSION.EXE program
ACOUNTPATH:
Path of the data files for the WebDev accounts.
DEBUGPORT:
Listening port of the remote debugger.
DEBUGPORTMIN:
Lower bound of auxiliary ports for remote debugging.
DEBUGPORTMAX:
Upper bound of auxiliary ports for remote debugging.
DEBUGREMOTE:
Allow the remote debugging of WebDev sites.
ERRORFILE:
Full name of the HTML file that will be used to display the error messages
LAUNCHER:
Name of the AWP engine
MAXCONNECT:
Maximum number of authorized connections (which means maximum number of engines started simultaneously). This
parameter is defined in the WebDev administrator.
MAXCONNECTAPP:
Maximum number of connections to the same site (defined in the WebDev administrator)
40 WebDev application server
Appendix 3 - Registry

MAXRECONNECTAPP:
Maximum number of simultaneous accesses to the same site by the same user (defined in the WebDev administrator)
NOMODIFPASS:
Authorization to modify the user passwords through the remote administrator.
NOREMOTEPARAM:
Authorization to modify the site parameters through the remote administrator.
SSLADMIN:
Key used to start the remote WebDev administrator in secure mode (1 to automatically enable the secure mode).
Caution: An SSL key must be installed and all the requirements specific to the SSL protocol must be complied with.
TIMEOUT_NORQ:
Time-out before the user is disconnected if no new request is received (defined in the WebDev administrator)
TIMEOUT_NORQ_AWP:
Time-out before terminating an AWP session.
TIMEOUT_RQ:
Maximum time-out for the launcher (defined in the WebDev administrator).
VDIR:
Name of the virtual directory declared in the HTTP server that contains WD180AWP.EXE
WEBSERVER:
Specifies the Web server to automatically configure.
WEBSERVER_BIN:
(Linux only) Specifies the path for the Web sever binary.
WEBSERVERCONF:
(Linux only) Indicates the configuration file of the Web server to configure automatically.
WEBSERVERRESTART:
Specifies the command line to use to reload the Web server configuration after a modification.
If the error messages have been customized for all sites installed on the computer, a new entry is created for each error
message.
 WebDev application server 41
Appendix 3 - Registry

2 Configuring the registry for installing a WebDev site or a Webservice

When installing a WebDev site on a Windows server, the information regarding the site is automatically inserted into the
registry, at the following entry:
HKEY_LOCAL_MACHINE/ SOFTWARE/ PC SOFT/ WebDev/ 18.0/ Application/ <SiteName>
Where <SiteName> is the name of the site installed.

When a WebDev site is installed on a Linux server, the information regarding the site is automatically saved to the fol-
lowing configuration file :
/ etc/ PC SOFT/ WEBDEV/ 18.0/ Applications/ <SiteName>.conf
Where <SiteName> is the name of the site installed. This name respects the case used for the name of the project.

When installing a Webservice on a Windows server, the details regarding the Webservice are automatically added into the
registry, in the following entry:
HKEY_LOCAL_MACHINE/ SOFTWARE/ PC SOFT/ WebDev/ 18.0/ Webservices/ <WebserviceName>
Where <WebserviceName> is the name of the installed Webservice.

When installing a Webservice on a Linux server, the information regarding the Webservice is automatically saved in the fol-
lowing configuration file:
/ etc/ PC SOFT/ WEBDEV/ 18.0/ Webservices/ <WebserviceName>.conf
Where <WebserviceName> is the name of the installed Webservice. This name respects the case used for the name of the
project.

Notes:
• The different entries in the registry and in the configuration file are given for information only and they allow you to check
whether a WebDev site is installed properly.
• These entries are automatically configured when a WebDev site or a Webservice is installed.
• Caution: The name of the site/ Webservice is case sensitive. This parameter must not be modified.
The following entries are created:
ERRORFILE:
Full name of the HTML file that will be used to display the error messages
GPUHISTOCNX:
Specify whether the user groupware must save the connection history.
GPUPATH:
Localization of the common data files (HyperFileSQL Classic) of the User groupware (full path).
GPUPATH_R:
Localization of the rights data files (HyperFileSQL Classic) of the User groupware for the site/ Webservice (full path).
LOGDIR:
Localization of the access statistics files of the WebDev site/ Webservice (full path).
LOCKFORUPDATE:
Indicates whether the connection to the site/ Webservice is locked for update.
HFPATH:
Location of the data files (HyperFileSQL Classic) of the site/ Webservice (full path)
MAXCONNECTAPP:
Maximum number of connections to the site/ Webservice (defined in the WebDev administrator)
42 WebDev application server
Appendix 3 - Registry

MAXRECONNECTAPP:
Maximum number of simultaneous accesses to the same site by the same Web user (defined in the WebDev adminis-
trator)
PROJECTPATH:
Path of the site files/ Webservice.
PROJECTNAME:
Name of the site/ Webservice (it is the project name if the site was deployed under a different name).
TIMEOUT_NORQ:
Time-out before the Web user is disconnected if no new request is received (defined in the WebDev administrator).
VERSION:
Version of the site
VIMAGEDIR:
Virtual directory of the site images
VIRTUALHOST:
Name of the host header of the virtual site where a site/ Webservice is deployed
 WebDev application server 43
Appendix 4 - Modules supplied with WebDev

A PPENDIX 4 - M ODULES SUPPLIED WITH WEB -

DEV
The different modules supplied with the WebDev application server are displayed in the table below.
Modules required by the WebDev sites to operate
Name Functions Started by ….
AWP (Active Web • Decodes the information coming from the Started by the Web server whenever a
Pages) manager WebDev site. request is made by a Web user in a dynamic
• Transmits the decoded information to the WebDev site.
WebDev application server.
WebDev application • Runs the information transmitted by the Started by WD180AWP whenever a Web user
server: AWP protocol. connects to a dynamic WebDev site.
• Builds the dynamic HTML page displayed by
the Web server on the browser of the Web
user.
WebDev administrator: Allows the administrator of the server to: Started when starting the computer where
• configure and manage the sites developed the Web server is installed.
in WebDev and installed on the server. This tool can only be used by the server admi-
• create the WebDev accounts nistrator.
• check the configuration of the server,…
This tool is required for the dynamic WebDev
sites to work.

Optional modules

Name Functions Started by ….

Remote WebDev Allows the managers of WebDev sites to Started by:

administrator: directly manage their different WebDev • the site manager from his browser.
(optional module) sites installed on the server. • the server administrator from a computer
Allows the server administrator to remotely other than the server, from his browser
configure the different WebDev sites instal- directly.
led on the server, the WebDev accounts, …

WebDev Hosting Con- Allows the hosting companies to configure Started by the hosting company on the
trol Center: the Web server that hosts the dynamic Web server.
(optional module) WebDev applications.

Stress test: Used to create a test script on the server Started by the site manager on the Web
(optional module) directly. Then, this script can be run from server directly to create a script for stress
different computers. test.

1 The WebDev administrator in practice

The WebDev administrator is a module used to manage the dynamic WebDev sites. This module is required to implement
the dynamic WebDev sites installed on the server.
In deployment, two types of WebDev administrators are available:
44 WebDev application server
Appendix 4 - Modules supplied with WebDev

• the WebDev administrator allowing the host to manage the dynamic WebDev sites installed on a Web server.
• the remote WebDev administrator allowing the site manager to manage his dynamic WebDev sites remotely from any
computer.
To start the WebDev administrator, select "Programs .. WebDev 18 application server .. WebDev administrator" from the
"Start" menu.
You can:
• automate the startup of the administrator by creating a shortcut in the start group of Windows.
• install the administrator as service on a computer running Windows NT or 2000 when the WebDev application server is
installed.
When the WebDev administrator is installed as a service, only its interface can be started by specifying the INTER-
FONLYparameter in the command line. The command lines becomes:
C:\ WEBDEV18\ Programs\ WD180ADMIN.EXE / INTERFONLY
Caution: The WebDev administrator must be run in background task.
The WebDev administrator includes a window containing three tabs:
• "Connections" tab to configure the characteristics of the current connections.
• "Sites" tab to list the WebDev sites installed on the current computer.
• "Configuration" tab to configure the WebDev sites installed on the current computer.
• "Management" tab to manage the WebDev server on the current computer.
• "Advanced" tab used to configure the specific features.

Use on a Linux server:

On a Linux server, the remote administrator should be used to manage the dynamic WebDev sites.
However, a WebDev administrator is also available. To view the interface of this administrator, you must:
• have the X11 server installed to view the graphic interface of the administrator
• start the administrator by using the following command line: wd180admin / INTERFONLY (case sensitive). This file is
found in the setup directory of the WebDev application server.

Note: In Linux, some features of the WebDev administrator are not available, especially:
• the management of the mail spooler
• the management of the error messages. This option is available in the remote administrator.
• the management of the prints
 WebDev application server 45
Appendix 4 - Modules supplied with WebDev

1 .1 Characteristics of cur rent connections

The "Connections" tab provides information about the current connections. This information can be consulted at any time
on the server.
The information displayed in "Connections" tab is as follows:
• 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 identifier of the connection,
- the site affected by the connection,
- the identity of the connected client. At run time, the client is identified by its IP address or by its Internet address,
- the current time of the connection,
- the idle time of the connection.
• the refresh rate: this parameter corresponds to the rate at which the table that displays the current connections is
refreshed.

The "Connections" tab can also be used to:

• Stop a current connection:
Select one of the connections and click "Disconnect".
• Stop all the current connections and close the administrator: click "Disconnect all".

1 .2 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 adminis-
trator. For each site, the following information is displayed in a table:
• the name of the site,
• the full setup directory of the site on the computer,
• the name of the corresponding "project" file.
The "Sites" tab can also be used to:
• Delete the site selected from the table.
The site is deleted from the administrator: the WebDev site is still found on the 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.
• Lock a site during an update.
• Configure each site found on the computer.
The configuration used by default is the one defined in the "Configuration" tab.
You also have the ability to create a specific configuration for the selected site. This configuration affects the number of
authorized connections, the authorized idle time and whether the site must be locked during an update

To validate the new setting immediately, click the "Apply" button.

46 WebDev application server
Appendix 4 - Modules supplied with WebDev

1 .3 General conf iguration

The "Configuration" tab is used to define the default connection options for the WebDev sites found on the server and
managed by the administrator.

Configuring the connections

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 WebDev administrator (one con-
nection = one Web user)
• Maximum number of connections on a site:
Maximum number of simultaneous connections allowed for each site managed by the WebDev administrator. This num-
ber can be modified for each site in the "Sites" tab.
• Maximum number of connections of a user on a site:
Maximum number of simultaneous connections allowed for a given Web user to each site managed by the WebDev
administrator.
• If this parameter is set to zero (recommended), any Web user who tries to establish simultaneous connections 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 con-
nections.
To validate the setting of the connections, click the "Apply" button. The new setting is automatically taken into account.
To cancel the modifications, click the "Restore" button.

Configuring the sessions and the requests

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 excee-
ded, 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 the AWP contexts. As soon as the specified duration is over and if no new request was performed, the
context file is deleted.
• Maximum duration of a request:
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.
• Number of cached sessions:
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: the connection to the site is faster.
- a new session is automatically cached.
To validate the setting of the 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.
• Generating a log file to manage the traffic statistics (.log):
 WebDev application server 47
Appendix 4 - Modules supplied with WebDev

This option enables you to generate a log file (".LOG" extension) used to view the traffic statistics of the WebDev sites via
WDStatistics. 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 the application and in the log file of the server. Indeed, if
the log file is defined both at server level and at application level ("Sites" tab), some information may be "lost". The table
below presents the different possible cases: l

Log of the application Log of the server "Save in the global file and in the file Result
of each application" checked
No No Any No log
No Yes Any Backup in the server log
Yes No Any Backup in the application log
Yes Yes No Backup in the application log
Yes Yes Yes Backup in the server log and in
the application log

Managing the remote debugging

The WebDev administrator is used to specify whether the remote debugging of the dynamic WebDev sites is allowed or not.
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.

3 .3 .1 M anaging t he ser ver

The "Management" tab is used to configure the features for managing the WebDev server.

Setup/Update
These options allow the server administrator to authorize and configure the remote setups and updates.
• Lock the server (for an update)
Used to simplify the update of a site by preventing any new connection from any new Web user. For each new connection
to one of the WebDev sites found on the server, the Web user receives a message informing him that the site is momen-
tarily unavailable. This message asks him to retry later. The Web users who are already connected can continue to use
the WebDev site.
Note: When performing an update via FTP, the WebDev site that is updated is automatically locked.
• Allow the remote update:
Allows the server administrator to authorize the sites installed on the server to be updated by FTP.
• Allow the remote setup of the sites:
Allow the server administrator to authorize the dynamic WebDev sites to be installed on the server by FTP.
• Allow the connection parameters to be updated:
Allows the server administrator to authorize the connection parameters to be customized when installing a site by FTP. If
this option is checked, the connection options defined by the creator of the site will be taken into account. If this option
is unchecked, only the connection options defined in this tab by the server administrator will be taken into account. The
custom options will be ignored.
Caution: The remote setup and update of WebDev sites are performed by FTP. See “Remote deployment (by FTP)”,
page 11 for more details.
48 WebDev application server
Appendix 4 - Modules supplied with WebDev

Error message
The "Errors" button displays the different error messages that can be displayed in the browser of the Web user. You have
the ability to customize the error message and the HTML page where the error message is displayed. See “Customizing the
errors”, page 49 for more details.

WebDev accounts
The "Accounts" button is used to configure the different sites managed by the WebDev administrator. See “Step 3: Create a
WebDev account”, page 13 for more details.

3 .3 .2 A dvanced setting
The "Advanced" tab enables you to configure the advanced features at server level.

Server used
The "Server" button enables you 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 WebDev sites installed on this computer.
If the server used is not found in this list, choose "Other". In this case, the Web server must be configured manually.
Note: The "Virtual servers" button is displayed if the IIS server is selected. This button is used to select the virtual servers
on which the alias required by WebDev (WD180AWP) will be created.

Diagnostic
The "Diagnostic" button enables you to check the configuration of the current computer or the configuration of the speci-
fied computer. This diagnostic is used to check:
• whether the FTP/ IP protocol is installed
• whether a Web server (HTTP server) is started
• whether the manager of the AWP protocol 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.

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.
Test page
The "Test page" button is used to display in the browser a page allowing you to start each one of the dynamic WebDev sites
installed on the current computer or on the specified computer.

Email spooler
If "Disable the email spooler" is unchecked, your sites will be able to send emails without locking the execution of the other
processes.
The asynchronous mode must also be enabled when starting the email session in the site (by EmailStartSMTPSession).
If the asynchronous mode is enabled, all the outgoing emails will be redirected to a "Spooler". The emails are queued up
before they are sent.
 WebDev application server 49
Appendix 4 - Modules supplied with WebDev

Note: If the WebDev administrator is closed, the email spooler is cleared: the pending emails are not sent and they are
removed from the spooler.
If "Disable the email spooler" is checked while some emails are still found in the spooler, these emails will not be lost: the
administrator continues to send them but no new email will be accepted by the spooler.

Server sockets
If "Allow the server sockets" is checked, the WebDev sites will be able to handle the server sockets via the Socketxxx func-
tions of WLanguage.

Printer used by default (Intranet sites only)

The "Configure the printouts" button enables you to select the printer used by default when printing to a local or network
printer of the Web server.
Note: If a network printer is selected, you need to define the print rights for this printer.
See “Printing from the server”, page 37 for more details.

1 .4 Customizing the er rors

The WebDev administrator enables you to customize the error messages displayed in a dynamic WebDev 18 site. All you
have to do is click the "Errors" button in the "Management" tab.
You can customize:
• the error messages for all the sites.
• the error messages for a specific site.

Customizing the error messages for all the sites

To customize the error messages for all the WebDev sites installed on the current computer, choose "All the sites" in the
"Site" combo box.

This customization applies to:

• the text of the error messages
• the page displaying the error message

Customizing the error messages for a specific site

To customize the error messages for a site installed on the current computer, select the name of the site in the "Site"
combo box.
This customization applies to:
• the text of the error messages
• the page displaying the error message

Priority order for the customization

The priority order for the customization is:
1. customizing all the messages for all the sites installed on the server.
2. customizing the messages for a specific site.
Caution: Customizing the error messages for all the sites is not recommended when using a shared server. Indeed, this
modification will be applied to all the WebDev sites installed on the server.
50 WebDev application server
Appendix 4 - Modules supplied with WebDev

How do I customize the error messages?

To customize the error messages:
1. Select the site that must be customized (specific site or all the sites).
2. To customize the page used for all the errors:
By default, the errors are displayed in a specific page. To customize this page:
• Choose "Custom"

• Select an HTML page accessible from your computer.

This HTML page must be a static HTML page that may contain images, ...
Two controls are optional in this page: the [%MSG%] and [%SYS%] tags. These controls will be respectively replaced
by the WebDev error message and the corresponding system error message.
This HTML page should be found in the "<ProjectName>_WEB" directory of the project.
3. To customize the error message and/or the error page:
• Choose the identifier of the error: the default caption is displayed.
• See the online help (keyword: "Error") for more details.

• Select "Custom caption" and enter the new caption associated with the option.
Note: The specific characters used in the messages:
- the {CONNECT}tag means that the Web user will be automatically reconnected once the error message is displayed.
- the %x characters will be automatically replaced when the error message is displayed.
• Select "HTML page" and select a specific HTML page to display this error.
This HTML page must be a static HTML page that may contain images, ...
Two controls are optional in this page: the [%MSG%] and [%SYS%] tags. These controls will be respectively replaced
by the WebDev error message and the corresponding system error message.
This HTML page should be found in the "<ProjectName>_WEB" directory of the project.
4. To apply the changes:
• Click the "Apply" button to immediately apply the changes to the current computer.
• Click the "Save" button to save the changes in a ".REG" file.
• If the selected site is a specific site, the configuration file is saved in the project directory.
• If the selected site is "All the sites", the configuration file is saved in the WebDev directory.
 WebDev application server 51
Appendix 4 - Modules supplied with WebDev

5. To install the modified files:

• If the customization applies to a specific site, the remote setup will automatically select the configuration file and will
run it on the server. If the HTML file for customizing the error page is found in the directory of project images
(<Project_Name>_Web), it will be automatically installed.
• If the customization affects all the sites found on the server, you must:
- Optional step: copy (if necessary) the HTML files of the error pages and the associated images onto the Web ser-
ver.
These files must be found in a server directory for which an alias was defined.
- copy and run the ERR_MSG_WebDev.REG file on the WEB server.
Caution: This customization is an advanced modification, requiring a good knowledge in the management of Web
servers.
52 WebDev application server
Appendix 4 - Modules supplied with WebDev

2 Tool for stress test

WDTestSite is used to run several tests on a WebDev site.
The various tests
Stress test:
The stress test consists in simulating the connection of several Web users to a WebDev site. Each one of these Web users
runs a set of operations (scenario) simultaneously.
Non-regression test:
The regression test consists in checking the operating mode of a WebDev site between two updates. The regression test
consists in checking whether a scenario performed with an earlier version of the site still operates properly once the site
was updated.
Running the test of a site in multi-user mode:
The test of a site in multi-user mode is used to check whether concurrent accesses to the data files are managed properly.
This test consists in simulating the simultaneous connection of several Web users to a WebDev site. Each Web user runs a
set of operations (scenario) simultaneously.
Comparing different servers:
WDTestSite is used to compare the speed of different servers. To do so, run the same scenario on different servers and
compare the execution time of this scenario.
Optimizing the processes created in WLanguage:
WDTestSite is used to compare the execution time of a scenario before and after the WLanguage code was optimized.

Main principle of WDTestSite

WDTestSite is used to:
• create a scenario for a WebDev site. This scenario contains a set of actions that must be performed on a WebDev site.
This scenario should be created on the Web server where the WebDev site is deployed.
• run the test of a scenario directly.
• start successively several executions of the same scenario from the same computer or from different computers.
• start the same scenario (simultaneous Web users) from the same computer or from different computers.
See the online help about WDTestSite for more details.

3 The remote WebDev administrator

The remote WebDev administrator is a WebDev site, installed on the deployment Web server. This site allows:
• the site manager to directly manage his WebDev sites installed on the Web server.
• the server administrator to directly manage the WebDev accounts and the WebDev sites installed on the Web server.
On a Linux server, the remote administrator should be used to manage the server as well as the dynamic WebDev sites
installed on the server.

Whether the WebDev site is installed remotely or via physical media, the manager of WebDev sites has the ability to use
the remote administrator (if it is installed on the server).
See the online help about the remote WebDev administrator for more details.
 WebDev application server 53
Appendix 4 - Modules supplied with WebDev

4 WebDev Hosting Control Center

Mainly intended for the hosts and for the Webmasters, the Hosting Control Center helps you easily host the WebDev 18
sites. The center manages the WebDev accounts as well as the account for the "IIS Web server" (versions 5.xx and 6.xx)
and the rights for the Windows operating system.
A default choice allows you to easily install a server, with no particular knowledge.
The creation of Client accounts can be automated. The following elements are centralized:
• Windows accounts,
• Groups of FTP users,
• Groups of WebDev clients,
• Home directory,
• FTP alias,
• WebDev accounts,
• Data directories,
• Virtual Web sites, …
54 WebDev application server
Appendix 5 - Silent setup

A PPENDIX 5 - S ILENT SETUP

WebDev application server

The WebDev application server includes a silent setup mode. In this mode, the wizard screens do not have to be validated
manually.

The following procedure is used to perform this silent setup:

1. Install a Web server on the server (IIS or Apache). These servers must be installed by following the specific features
mentioned in the documentation.

2. Create a file for emulating the setup. This file is a .INI file with the following structure:

[PILOTE_WebDep]
REPINST= ;Setup directory, for example "C:\WebDev 18"
NUMSERIE= ;Serial number
CLEACT= ;Activation key
SER_WEB= ;Web server. Must correspond to IIS or APACHE
3. Start the setup program of the WebDev application server (found in the EN32 or EN64 directory of the DVD). Use
the following command line:

/Silent=<Path of .INI File> /LOG=<Path of Log File>

where:
<Path of .INI File> corresponds to the path and full name of the file emulating the setup.
<Path of Log File> corresponds to the path and full name of the file in which the result of the setup will be saved. This
file will contain "OK" if the setup was successfully performed or an error message if the setup failed.

4. The setup progresses as follows:

• The setup progress bar is displayed. The windows that appear are automatically validated.
• If several versions of IIS or Apache are detected, the most recent version of the Web server is used.
• The setup performed is a full setup that uses the default options:
- the management sites (WDAdminWeb,WDAdminHF and WDAdminSaaS) are installed.
- the secured hosting mode for remote management is not enabled.
- the hosting is enabled for the sites in earlier version.
• At the end of the setup, the log file is filled with the status report of setup.

Notes:
• If a version 15 (or earlier) already exists, you must specify a setup directory different from the existing version.
• The user accounts will have to be migrated (via the Hosting Control Center).
 WebDev application server 55
Appendix 5 - Silent setup

HyperFileSQL Client/Server server

The HyperFileSQL CLient/ Server server includes a mode for silent setup. In this mode, the wizard screens do not have to
be validated manually.

The following procedure is used to perform this silent setup:

1. Create a file for emulating the setup. This file is a .INI file with the following structure:

[PILOTAGE]
Plateforme=1
MAJ=2
CCHF=0

[SERVEUR]
Serveur=LG2
Port=4912
Repertoire=c:\HF2 server

[MACHINE]
Nom=TRW1B

The parameters of this emulation file are as follows:

• Plateforme: 1: Windows / 2: Remote setup for Windows, 3: Linux, only 1 and 2 operate with this pack
• MAJ: 1: Update, 2 : Install, 3 : Uninstall
• CCHF : 1: Install or update the HyperFileSQL Control Center, 0: no HyperFileSQL Control Center
• Serveur: Name of the HyperFileSQL server
• Port: port number (not required when uninstalling)
• Repertoire: Path of the server directory (not needed for uninstalling)

2. To modify the configuration parameters, you must add a [CONFIGURATION] section containing the same keywords
as the server .CONF. For example:

[CONFIGURATION]
; indicates that the following parameters are taken into account (0 otherwise)
ModifConfig=1

;parameters with their default values :

DBRootPATH=%%COMMONAPPDATA%%\PC SOFT\HyperFileSQLServer_<name of the server specified in
the SERVER section>\BDD
NdxCacheSize=25
JNLRootPATH=%%COMMONAPPDATA%%\PC SOFT\HyperFileSQLServer_<name of the server specified in
the SERVER section>\BDD\_JNL
JNLBackupRootPATH=%%COMMONAPPDATA%%\PC SOFT\HyperFileSQLServer_<name of the server speci-
fied in the SERVER section>\BDD\_JNLBackup
MoreThan2Go=1
ServerLogPath=%%COMMONAPPDATA%%\PC SOFT\HyperFileSQLServer_<name of the server specified
in the SERVER section>\Logs
ServerLogLevel1=0
ServerLogLevel2=0
LogConnection=0
ServerLogMaxFileSize=100
ServerLogMaxFiles=3
PerformacePath=%%COMMONAPPDATA%%\PC SOFT\HyperFileSQLServer_<name of the server specified
56 WebDev application server
Appendix 5 - Silent setup

in the SERVER section>\Perf

PerformanceMaxFileSize=100
PerformancePeriod=0

Note: To put everything in the server directory, you must replace %%COMMONAPPDATA%%\ PC
SOFT\ HyperFileSQLServer_<name of the server specified in the SERVER section> by %%EXE%%.

3. To use this configuration file, start the HyperFileSQL Client/ Server pack and specify the following command

line: /Silent=<Path of .INI File> /LOG=<Path of Log File>

Note: You can also pass / DEBUG=<Path of .txt> to get the execution traces

4. In exit, an <Install.log> is created in the server directory. This file contains "OK" if everything is successful or error
messages otherwise.
Examples
for IIS
 WebDev application server 59
Introduction

1 .I NTRODUCTION
This document is a tutorial intended to remind you of the different steps required to configure a new Windows computer for
a WebDev Application Server. This document is not exhaustive, additional information is available in the first section of this
book.

Configuration of this example:

• Operating system of the server: Windows Server 2003/ 2008
• Web server: IIS
• FTP server (for the remote setups): IIS

Hosting and maintaining a Web server are not easy things to do, it is a tough job, requiring specific skills regarding:
• the operating system of the server
• the Web server used
• the FTP server used
• the management of rights
• the WebDev application server
If you do not possess these skills, we recommend that you have your site hosted by a professional company. You can find
some of these companies specialized in hosting WebDev sites on the PC SOFT site at: http:/ / www.windev.com/ webdev/
hosts.htm
If you want to host your WebDev site, choose a server according to your own skills.

What will be required for t he set up

The following elements are required:
• The setup CD/ DVD for the WebDev Application Sever (with the serial number and the setup key)
• A Windows administrator account of the computer (with the rights to create a Windows user account and a group of Win-
dows users).
• A Web server (IIS for this example).
• An FTP server for the remote setups (IIS for this example).
• A HyperFileSQL Client/ Server server (optional).

Version of the WebDev application server : 3 2 bit s or 6 4 bits

If the operating system of the server is in 32 bits: only the 32-bit WebDev Application Server can be installed.
If the operating system of the server is in 64 bits, you can install either the 32-bit WebDev Application Server or the 64-bit
WebDev Application Server. To choose, you must know that:
• more features are currently available in 32 bits than in 64 bits
• most of the native accesses are available in 32 bits only
• a site compiled WITHOUT the 64-bit option will not operate on a 64-bit server
• a site compiled WITH the 64-bit option will operate on a 32-bit server
Therefore, we advise you to install a 32-bit version.
If you decide to install the 64-bit version, make sure that all the necessary features (especially the access to the databa-
ses) are available.
60 WebDev application server
Introduction

Questions/Answers about the 64-bit mode:

1. What is the benefit of a 64-bit server?

It is very interesting to use a 64-bit operating system. The server can use more than 4 GB of RAM for all the applica-
tions and services. A 64-bit operating system can manage more volume.

2. A 32-bit application server installed on a 64-bit Windows will be slower?

Installing a 32-bit version or a 64-bit version is not a guarantee of fast speed. It is interesting to install a 64-bit applica-
tion server if some sites are likely to consume a lot of memory (very large queries, large generated images, etc.), which
is extremely rare.
In 32-bit mode, each session of each Web user can consume up to 2 GB of RAM, which is very important for an Inter-
net site.

3. Do I have to install the HyperFileSQL server in 32 bits or in 64 bits?

For the HyperFileSQL server, we advise you to install the 64-bit version. Indeed, if an important number of connections
is performed and if each one of these connections performs an important number of operations, the limit of 2 GB defi-
ned for the 32-bit mode can be reached very soon.
Furthermore, the same features are available regardless of the version of the HyperFileSQL server (32 bits or 64 bits).
It is entirely transparent for the connected WEBDEV sites and for the connected WINDEV applications: they can be run
in 32-bit mode or in 64-bit mode, they can even operate in Linux, Mac, Windows Mobile…
 WebDev application server 61
Checking/Configuring the system

2 .CHECKING/CONFIGURING THE SYSTEM

2 .1 Prerequisites: WEB server and FTP server

The WebDev Application Server requires a Web server. In Windows, the Web server installed by default is "Internet Informa-
tion Server", called IIS. This server is managed automatically, this is why this server was chosen it in this document. The
Apache Web Server can also be used but its configuration will not be presented here.
To be able to perform remote setups and updates, an FTP server is required. IIS includes an FTP server, this is the one that
will be used in this document.
In order for the WebDev Application Server to manage IIS automatically, IIS must be installed with some specific options
(especially in Windows 2008).

2 .1 .1 I IS in Windows 2 0 0 3
To check the IIS options in Windows 2003:
1. In the configuration panel, select "Add or Remove Programs" and "Add/ Remove Windows components".
2. In the list of Windows components, makes sure that "Application server" is checked. Keep this option selected and
click the "Details" button.
3. Check whether "Internet Information Service" is checked. Keep this option selected and click the "Details" button.
4. Check whether the following options are checked:
• "Internet Information Services Manager", "File Transfer Protocol Service" (to be able to perform remote setups and
updates)
• "World Wide Web Service".
62 WebDev application server
Checking/Configuring the system

2 .1 .2 I IS in Windows 2 0 0 8
To check the IIS options in Windows 2008:
1. In the "Start" menu of Windows, right-click "Computer" and select "Manage".
2. Select "Roles" and "Web server (IIS)".
The following options must be installed in the role services:
• Web server, common HTTP features, Static content; default document, HTTP error, CGI, Console for IIS management,
Compatibility with the IIS 6 data metabase, HTTP log, database authentication
• For the remote setups and updates: FTP server, console for FTP management.
You will find more details in the online help of WebDev.
 WebDev application server 63
Checking/Configuring the system

2 .2 Checking the IIS FTP server

By default, we advise you to remove the anonymous FTP access.
To perform this operation:
1. Start the console for IIS management via "Start .. Run" of Windows and type inetmgr.
2. In the IIS console, right-click the FTP site and select "Properties" from the popup menu. In the "Security accounts"
tab, uncheck "Allow anonymous connections"

To propose anonymous FTP downloads in your site, we advise you to create a specific Windows account and an alias in the
FTP site.
64 WebDev application server
Checking/Configuring the system

In Windows 2008 R2, start the console for IIS management via "Start .. Run" of Windows and type inetmgr. In the IIS con-
sole, select the computer in the tree structure on the left ; then, in the "FTP" section on the right, select "FTP authentica-
tion" and disable the anonymous connections.
65 WebDev application server
Creating a group of users

3 .CREATING A GROUP OF USERS

To be able to globally manage the rights of the Windows accounts that will perform the setups of the WebDev sites, we
advise you to create a group.

To create a new group of users:

1. Right-click "Computer" and select "Manage".
2. Expand the treeview on the left to see the "Computer management", "Users and local groups" and "Groups" folders.
3. Right-click "Groups" and select "New group…".
4. Create a "WEBDEV_FTP" group.
66 WebDev application server
Creating a group of users

In Windows 2008 R2:

You can also create a second group for the Windows accounts that will make the Internet sites operate. You also have the
ability to use an exis ting group such as the "Guests" group (Windows 2003) or the "IUSR_WPG" group (Windows 2008).
 WebDev application server 67
Installing the application server

4 .I NSTALLING THE APPLICATION SERVER

Caution: The setup must be performed as administrator of the computer once the prerequisites have been checked. The
serial number and the setup key are required.
In this example, we are going to perform a full setup in the following directory: "C:\ WebDev18\ " with the option for hosting
the earlier versions of the sites.
Don’t forget to check the option allowing the administrator to be installed as service. Otherwise, you will not be able to con-
nect to the WebDev sites if no session is opened on the server.

The setup program automatically detects and configures the Web server (IIS in this example). If necessary, the information
regarding to the manual configuration of the Web server can be found in the online help of WebDev.
Once the WebDev Application Server is installed, you can identify the Web server for which it is configured as well as the
virtual sites in which it is configured.
To do so, you must:
1. Start the interface of the WebDev administrator.
2. Select the "Advanced" tab and click the "Server" button.
3. Choose the server in the list.
4. Click the "Virtual servers" button.
In the table, all you have to do is check the virtual servers in which you want the WebDev application server to be con-
figured:

You will be able to operate one or more dynamic WebDev sites (classic sites or sites with AWP pages) in each virtual server
in which the application server is configured.
Important for security:
As soon as the WebDev Application Server is installed, don’t forget to change the password of the WebDev account (ADMIN
account). To do so:
1. Start the WebDev administrator.
2. In the "Management" tab, click the "Accounts" button.
3. Double-click the "ADMIN" line.
4. In the "General" tab, click the "Password" button.
5. Modify the password and validate.
68 WebDev application server
Rights on the registry

5 .R IGHTS ON THE REGISTRY

In order for the setups of the WebDev sites to be able to create or modify the setting of the sites, the Windows account
used must have some modification rights in the registry, in the branch for configuring the WebDev sites.

To configure these rights:

1. Start the registry editor via "Start .. Run" of Windows, type "Regedit" and validate ("OK" button).
2. In the registry editor, in the treeview on the left, expand the branch:
• in 32 bits: "HKEY_LOCAL_MACHINE", then "SOFTWARE", then "PC SOFT", then "WEBDEV", then "18.0" and " Applica-
tions".
• in 64 bits: "HKEY_LOCAL_MACHINE", then "SOFTWARE", then "Wow6432Node", then "PC SOFT", then "WEBDEV",
then "18.0" and "Applications".
3. Right-click the "Applications" branch and select "Authorizations".
4. In the authorization window, click the "Add" button.
5. In the new window that is opened, clicks the "Location" button and choose the local computer (at the top of the tree-
view). In the edit control named "Enter the names of objects…", type WEBDEV_FTP (the name of the group that was
created beforehand) and click the "Check the names" button.
If no error was made, the name typed in the edit control is underlined and it is prefixed by the name of the computer.
Otherwise, it means that an error occurred during the input.
6. Click the "OK" button to validate the window.
7. Back to the window of authorizations of the WEBDEVregistry branch, select the group in the list (if not already done)
and check the requested authorizations: "Total control".
 WebDev application server 69
Rights on the registry

8. Perform the same operations on the branch:

• in 32 bits: "HKEY_LOCAL_MACHINE", then "SOFTWARE", then "PC SOFT", then "WEBDEV", then "18.0" and " Webser-
vices".
• in 64 bits: "HKEY_LOCAL_MACHINE", then "SOFTWARE", then "Wow6432Node", then "PC SOFT", then "WEBDEV",
then "18.0" and "WWebservices".
70 WebDev application server
Creating/Configuring a WebDev account

6 .CREATING/CONFIGURING A WEB DEV ACCOUNT

6 .1 Hosting Control Center

We recommend that you use the Hosting Control Center to create and configure a WebDev account, especially in a configu-
ration of the following type:
• Windows 2003/ 2008 server,
• IIS Web server,
• IIS FTP server.
This recommendation is mainly intended for the shared hosting or for the hosting that require several accounts
WebDev.

Indeed, to deploy a WebDev site on a WebDev Application Server, a WebDev account must be created and configured befo-
rehand. The Hosting Control Center of WebDev is used to automatically perform all the steps required for the new WebDev
account to operate properly:
• Creating the WebDev account, so that it is recognized by the WebDev administrator.
• Creating a specific Windows account, in order to grant the necessary rights.
• Creating the different directories (folders) used to host the deployed elements.
• Assigning the necessary rights to the created account on the created directories.
• Creating a new specific virtual Web server (optional).
• Creating an FTP alias.

The only point that is not automatically configured is the assignment of rights at registry level. This is the reason why it was
configured beforehand via a group of users (WEBDEV_FTP).

If you are not using IIS as Web server or as FTP server, the Hosting Control Center will not perform all the necessary steps,
some settings will have to be done manually.

6 .1 .1 Configur ing the Hosting Control Center

In a first time, the Hosting Control Center of WebDev must be configured. Let’s see an example of configuration:

• In the "Hosting Parameters" tab, in the "Directories" sub-tab:

• The directory that will contain all the elements deployed by the WebDev sites: "C:\ WEBDEV hosting\ ". There will be one
sub-directory per WebDev account and another sub-directory per site. Example: "C:\ WEBDEV Hos-
ting\ USER_WEBDEV\ ".
• The name of the sub-directory of the dynamic sites (corresponds to fExeDir() when running a site): "sites".
This directory will contain the libraries (.wdl) of the sites, the _WEB sub-directories, the .awl, .awp pages, …There will be
one sub-directory per site. Example: "C:\ WEBDEV Hosting\ USER_WEBDEV\ sites\ FirstWebDevSite\ ".
• The name of the sub-directory of the web services (corresponds to fExeDir() when running a service): "webservice".
This directory will contain the Web services (.awws). There will be one sub-directory per site. Example: "C:\ WEBDEV
Hosting\ USER_WEBDEV\ webservice\ FirstWebService\ ".
• The name of the data sub-directory (corresponds to fExeDir() at run time): "data"
This directory will contain the HyperFileSQL Classic data files(.fic) , .ini files, PDF... There will be one sub-directory per
site and/ or web service. Example: "C:\ WEBDEV Hosting\ USER_WEBDEV\ datas\ FirstWebDevSite\ "
• The name of the sub-directory of the static sites: "wwwroot"
 WebDev application server 71
Creating/Configuring a WebDev account

This directory will be defined as being the root of the Web site, the root of the virtual Web site.

With the above-mentioned parameters, all the elements of a WEBDEV user "USER_WEBDEV" with a base folder "C:\ WEB-
DEV Hosting\ " will be deployed in a tree structure such as:

• In the "Hosting Parameters" tab, in the "OS Accounts" sub-tab

• The group of Windows accounts that will be used to perform the setups (WEBDEV_FTP)
72 WebDev application server
Creating/Configuring a WebDev account

• The group of Windows accounts in which the sites will operate: (Guests)

• In the "Hosting Parameters" tab, in the "WebDev Accounts" sub-tab:

You can specify the maximum number of connections that the WebDev user will be able to distribute among his sites.
You can also specify a limit regarding the number of different sites that can be associated with the WebDev user.

When all the parameters are entered, click the "Apply" button to save.
 WebDev application server 73
Creating/Configuring a WebDev account

6 .1 .2 Creating a WebDev account with CCHosting

To create a new WebDev user (with all the associated elements including the Windows account) :
1. Select the "User accounts" tab in the Hosting Control Center of WebDev.
2. Click the "New user" button.
3. Specify the name of the user to create as well as his password.

4. In the "Associated Widows account" plane, you have the ability to create a Windows user with the same name and
password for the setups as well as a second Internet guest Windows user. In this plane, the "Generate" button found
beside the password is used to generate a random password: this type of password increases the security.
These users will be created in the groups previously configured in the Hosting Control Center. Click the "Next" button.
5. In the "Administrative contact" plane, you have the ability to enter some information regarding the physical person
for whom the WebDev account is created.
6. In the "Directories" plane, you will find the default directories specified in the setting of the hosting control center.
Important reminder: The root directory of the Web server will be modified to indicate the sub-directory of the static
sites specified here. In this example: "C:\ WEBDEV Hosting\ WEBDEV_USER_1\ wwwroot\ ".
74 WebDev application server
Creating/Configuring a WebDev account

7. In the "Virtual site" plane, you have the ability to specify an existing virtual site or a new virtual site.
A virtual Web site is used to redirect the HTTP requests according to the domain of the request. A virtual Web site
allows you to host several Internet domains on the same computer while each domain is displaying a different site.
The Hosting Control Center can automatically create a new virtual site in IIS. To do so, select "Create a new virtual Web
site" ; then, in the "Name of host header" column, specify the domain names of this virtual site (one per line):

When using a virtual site that already exists, the root directory of the virtual site will be modified. If sites (developed in
WebDev or not) are already operating on this same virtual Web server, they may be impacted. You may have to restore
the initial root directory (c:\ inetpub\ wwwroot\ by default).
 WebDev application server 75
Creating/Configuring a WebDev account

The WebDev hosting center creates all the necessary elements:

• The WebDev account
• The two Windows accounts
• The directories with the necessary rights
• A virtual Web server (optional)
• The WebDev setting for the selected virtual Web server
• An FTP alias

6 .2 M anually (without the Hosting Control Center)

This choice is not recommended if you want to use several WebDev accounts and several Windows accounts (for shared
hosting for instance) because its implementation is more complex.

6 .2 .1 Creat ing the WebDev account

The creation of the WebDev account is done from the WebDev administrator, "Setups/ Accounts" tab.
1. Start the WebDev administrator.
2. In the "Setups/ Accounts" tab, click the "Accounts" button.
3. In the window for account management, select "Users .. New".
4. Specify the name of the WebDev account and the requested password.
5. In the account information, in the "General" tab, specify the maximum number of connections for this account and
the different directories that will be used:
• Directory of FTP connection: You must specify the FTP root directory of the FTP account that will be used to perform
the remote deployments, by default with IIS: C:\ inetpub\ ftproot\ ’
• Other directories: These directories can be freely chosen but we recommend that you use a common home directory,
such as: C:\ WEBDVEV Hosting\
Caution: This folder must not be a sub-folder of the root of a virtual directory. It must absolutely not be found in a sub-folder
of "C:\ inetpub\ wwwroot\ ".
76 WebDev application server
Creating/Configuring a WebDev account

The different folders correspond to:

• The folder that will contain the elements of the dynamic sites (wdl, awl, awp, _WEB sub-directory, or fExeDir() for the
sites): C:\ WEBDEV Hosting\ sites\
• The folder that will contain the web services (.awws, fExeDir() for the web services): C:\ WEBDEV Hosting\ webservice\
• The folder that will contain the data (HyperFileSQL Classic files, .ini, Generations of PDF, or fDataDir()): C:\ WEBDEV Hos-
ting\ data\ ’
 WebDev application server 77
Creating/Configuring a WebDev account

6 .2 .2 Checking/Granting rights

For the remote setup and update

For the group (WEBDEV_FTP) or the user that will perform the remote setup, the necessary rights are:

• Full control in:

• Directories of data: C:\ WEBDEV Hosting\ data in this example
• Directories of dynamic sites: C:\ WEBDEV Hosting\ sites in this example
• Directories of Web services: C:\ WEBDEV Hosting\ webservice in this example
Note: If you have respected the same tree structure as the one recommended above, you can directly grant the rights
at parent folder level: "C:\ WEBDEV Hosting\ ". The 3 above-mentioned directories will inherit these rights
• Directory of accounts: C:\ WebDev18\ Account in this example\
• FTP directories: C:\ inetpub\ ftproot\ by default with IIS, but it is possible to create an alias with the same name as the
Windows account to define a different root.
• WebDev registry:
In 32 bits: HKEY_LOCAL_MACHINE\ SOFTWARE\ PC SOFT\ WEBDEV\ 18.0\ Applications and
HKEY_LOCAL_MACHINE\ SOFTWARE\ PC SOFT\ WEBDEV\ 18.0\ WebServices
In 64 bits: HKEY_LOCAL_MACHINE\ SOFTWARE\ PC SOFT\ WEBDEV\ 18.0\ Applications and
HKEY_LOCAL_MACHINE\ SOFTWARE\ Wow6432Node\ PC SOFT\ WEBDEV\ 18.0\ WebServices
• Read and run in (default case in most cases) : Setup directory of the WebDev engine C:\ WebDev18\

For the execution of WebDev sites.

By default, the Web sites operate with a user who belongs to the "Guests"or "Internet guests" group. By default, this user
is called "IUSR" or "IUSR_COMPUTERNAME". This user has restricted rights.

• Read/Write (see "total control" depending on the operations performed by the site) in:
• Directories of data: C:\ WEBDEV Hosting\ data in this example

• Read (default case in most cases) in:

• Directories of dynamic sites: C:\ WEBDEV Hosting\ sites in this example
• Directories of Web services: C:\ WEBDEV Hosting\ webservice in this example
• Directories of static sites: C:\ WEBDEV Hosting\ sites in this example
Note: If you have respected the same tree structure as the one recommended above, you can directly grant the rights
at parent folder level: "C:\ WEBDEV Hosting\ ". The 3 above-mentioned directories will inherit these rights.
• Directory of accounts: C:\ WebDev18\ Account in this example
• WebDev registry

Example of rights granted on a directory

Let’s see an example of rights granted to a group on a directory: the write rights to the Windows group named
"WEBDEV_FTP" in the "C:\ WEBDEV18\ Account\ " directory :
1. Use the file explorer of Windows and display the content of the directory that contains the directory for which the
rights must be modified: C:\ WEBDEV18\ for the C:\ WEBDEV18\ Account directory
2. Right-click the directory and choose "Properties".
3. In the window that is displayed, choose the "Security" tab, then the "Add" button.
4. In the new window that is opened, clicks the "Location" button and choose the local computer (at the top of the tree-
view).
In the edit control named "Enter the names of object…", type WEBDEV_FTP (the name of the group that was previously
created) and click the "Check the names" button. If no error was made, the name typed in the edit control is underlined
78 WebDev application server
Creating/Configuring a WebDev account

and it is prefixed with the name of the computer. Otherwise, an error occurred while typing. Click the "OK" button to
validate the window.
5. Back to the window of directory properties on the "Security" tab with the group selected in the list, check the reques-
ted authorizations: "Full control".
Note: for the directory of accounts, only the modify and write rights are required (and the associated sub-rights).
 WebDev application server 79
Checking the configuration

7 .CHECKING THE CONFIGURATION

7 .1 With the WebDev administrator

To start the check:
1. Start the WebDev administrator.
2.In the "Advanced" tab, specify the name or IP address of the site to check.
Caution: if several virtual servers are installed on the computer, you must specify the name of the domain that corres-
ponds to the requested site, otherwise leave localhost (if necessary, add the correspondence between the IP address
and the name of the domain in the "hosts" file of the computer, this file is found by default in C:\ Win-
dows\ System32\ drivers\ etc\ ).
3. Click the "Diagnostic" button.

7 .2 When deploying a new WebDev site

If you own WebDev Development Version, deploy a new small site in order to confirm your setup and your setting.
If you do not own WebDev Development Version, ask for a deployment package to a developer who wants to install a site.

7 .2 .1 With WebDev Development

To perform a remote setup by FTP from the WebDev environment, you must:
1. Open the project to deploy.
2. On the "Project" tab, in the "Generation" group, click on "Deploy the site".
3. Once the site library is created, select "Deploy the WebDev site on a remote WebDev Application Server".
4. Specify your parameters in the "Parameters of the application server" plane:
• In the edit controls regarding the address of the application server, specify the name or the IP address of the domain
corresponding to your Web server.
80 WebDev application server
Checking the configuration

If you are using a virtual Web server other than the default server, you must specify the address corresponding to the
virtual server in which you want to deploy your site. The same domain name that you may have specified in the "host
headers" when creating the virtual site with the hosting control center. If the DNS servers are not updated with your
domain name, add an entry into the "hosts" file of your computer (C:\ Windows\ System32\ drivers\ etc\ hosts)
• Then, specify the name of the WebDev account and the name of the Windows account for the setups as well as their
passwords.
• Click the "Check the parameters" buttons to check your input.

5. Validate the next steps, steps in which the different deployed elements will be reminded to you.
6. At the end of the deployment procedure, a wizard indicates the deployment progress and proposes a link to start
the site.

For a standard dynamic site, the URL used to start the site has the following format:
http:/ / www.domain.com/ WD180AWP/ WD180Awp.exe/ CONNECT/ SITE_NAME

For a dynamic site with AWP pages, the URL used to start the site has the following format:
http:/ / www.domain.com/ NAME_OF_WEB_SITE/ index.awp

From WebDev 15, with IIS 7 in Windows 2008, there is also a short URL used to start the dynamic sites:
http:/ / www.domain.com/ SITE_NAME
(Feature also available with Apache 1.3, Apache 2.2, but not available with IIS 5 or 6 therefore not available in Win-
dows 2000 or Windows 2003).
 WebDev application server 81
Checking the configuration

7 .2 .2 With a deployment package

A WebDev site can be deployed remotely with WDDeploy without owning WebDev development. WDDeploy is installed with
the WebDev application server, in the same directory as the WebDev administrator.
To install a deployment package (a .zip) created with WebDev development:
1. Start WDDeploy.
2. Select the deployment package.
3. Specify the name of the name of the Windows account to use and its password.
4. Specify the name of the WEBDEV account to use and its password.
5. Specify the address of the site toward which the deployment will be done.
Like with WebDev development, if the server uses a virtual Web server other than the default server, you must specify
the address that corresponds to the virtual server on which you want to deploy your site. The domain name that you
may have specified in the "host headers" when creating the virtual site with the hosting control center. If the DNS ser-
vers are not updated with your domain name, add an entry into the "hosts" file of your computer (C:\ Win-
dows\ System32\ drivers\ etc\ hosts).
82 WebDev application server
Most common problems

8 .M OST COM M ON PROBLEM S

8 .1 The " Unable to add the programming" error occurs during

the remote setup of a site (by FTP)
The following error may occur during the remote setup of a site on a Windows 2008 server on which the UAC mechanism of
Windows is enabled:
Unable to add the programming because of the following error:
The ’C:\WebDev18\WD180Admin.exe /DELAYEDUPD /DATE=201101260949 /CMD="/INSTALL/ADDALIAS/SITENAME/
domain.com/"’ executable cannot be run for the following reason:
The requested operation requires an elevation.

When this error occurs, the setup of the site is performed at 95% on the server: only the setting of the Web server (IIS) was
not performed. If the WebDev administrator is manually started on the server, the name of your site will be displayed in the
list of sites.
To correct this configuration problem, the setting of the Web server must be "manually" forced for your site. To do so, see
“Checking the configuration”, page 83. The diagnostic of your site will detect this configuration error of the Web server and
will propose to repair it automatically.

Reminder about the UAC mechanism (User Account Control) :

With the UAC mechanism of Windows, each executable is run with the rights granted to its parent without possibility to
increase these rights. Furthermore, the shell (iexplore) is started with a "filtered token" (for the administrators), which
means that it has the rights but not the privileges.
Therefore, an application started in an administrator session will not have the administrator privileges and it will not be
able to write into the registry of the "HKEY_LOCAL_MACHINE" branch. If the startup of the application requires an elevation
of rights (like the WEBDEV administrator), Windows displays a confirmation dialog box (mandatory), with eventually the
input of a login and administrator password if the current account is not administrator. When the startup is performed by
another application, no dialog box is displayed but the startup fails: this is what happens here.

To avoid this error, the UAC must be disabled. To disable the UAC, a simple method consists in running MSCONFIG.EXE
(Start .. Run, then type MSConfig.exe). In the window of MSConfig, choose the "Tools" tab and select "Disable the User
Account Control" (caution, the computer must be restarted).

8 .2 " WDM etabase.dll: M eta_bInit failed" error or failure upda-

ting the meta base with IIS7
This error occurs when the compatibility of the metabase IIS 6 is missing from the IIS configuration.
To correct this error, see:
• the online help.
• “IIS in Windows 2008”, page 62.
 WebDev application server 83
Most common problems

8 .3 Checking the configuration

For any problem, check the configuration from the interface of the WebDev administrator in the "Advanced" tab.
1. In the "Host name/ IP " controls, specify the domain name of your site. The next operations will be performed on this
address, make sure that it is the address of the virtual server to check. If there is a single virtual server, leave "local-
host" in the control in order for the test to use the default site.
2. Click the "Diagnostic" button.
3. Click the first "Check" button to check the configuration of the application server in the virtual site.
To check the configuration of a specific site, select the name of the site to check in the combo box and click the
second "Check" button.
4. The WebDev administrator detects the problems and proposes to correct them automatically.
84 WebDev application server
Most common problems

8 .4 HTTP error 4 0 4 the diagnostic on AWP

If the HTTP 404 error occurs on the AWP protocol (or on the HTTP:/ / Server/ WD180AWP/ WD180Awp,exe/ VERSION URL),
you must check whether the WebDev CGIs are allowed.

8 .4 .1 I n Windows 2 0 0 8
In the IIS console (started by "Inetmgr" from the Start menu of Windows ), select:
• the computer in the treeview (on the left),
• the "Restriction of requests" icon (on the right).
Make sure that the CGIs of the WebDev application server are found in the list. These elements must be "Authorized". Othe-
rwise, these elements must be added.

On the virtual site, check in the "Handler mappings" section whether the CGI executables are allowed. Otherwise, add
these elements (during the addition, check "Execution" in the "Request Restrictions", "Access" tab):
 WebDev application server 85
Most common problems

8 .4 .2 I n Windows 2 0 0 3
In the IIS console (started by "Inetmgr" from the Start menu of Windows ), select "Web service Extensions". Make sure that
the CGI of the WebDev application server are found in the list. These elements must be "Authorized". Otherwise, these ele-
ments must be added.

8 .5 Problem while displaying the images and the styles

Problem: The site is started but the images are not displayed. The styles are not correct: Javascript errors occur on the
pages. Some actions do not operate.
Solution: The alias (virtual directory) of the site is not defined or it is incorrect. Use the site diagnostic from the WebDev
administrator. You can also:
• start the IIS console ("Inetmgr" from the Start menu of Windows)
• check whether the alias with the name of the _WEB site is found and whether it is not in error.

8 .6 The AWP pages do not operate

Problem: The association between the AWP extension and the WebDev application server is not defined.
Solution: Use the diagnostic of the application server from the WebDev administrator.

8 .7 The URL rewriting of the AWP pages does not operate

Problem: The association between the AWP extension and the WebDev application server is not defined properly.
Solution: Use the diagnostic of the application server from the WebDev administrator.
Caution:
• The site must have been deployed at least one by a setup (physical media or FTP) in order for the WebDev application
server to have been configured (no simple manual copy).
• The directory corresponding to the path of the rewritten URL, a ".WDConfig.awp" file (that contains information about the
name of the site, such as: SITEID * <SiteName>) must be found.
• If the URL contains characters (such as +), some Web servers may consider that it is a double escape and trigger an
HTTP 404 error (or an HTTP 404.11 error). In this case, the Web server must be configured to allow the double escape.
Example for IIS7 (2008): On the Web site, go to "Filter the requests", then to the link on the right "Modify the function
parameters…" and check "Allow the double escape".
86 WebDev application server
Most common problems

8 .8 The short URLs of dynamic sites do not operate

Problem: IIS 6 is not supported in Windows 2000 or 2003. The association between the AWP extension and the WebDev
application server is not defined properly.
Solution: Use the diagnostic of the application server from the WebDev administrator.

8 .9 The access to the network data does not operate

Problem: The site cannot access the data found on another computer.
The Windows account that runs the site is a local guest account, therefore without any possibility to access the network
shares.
Solution: To access the network resources, you must change the Windows account associated with the virtual Web site and
implement a domain account.

8 .1 0 The URL with just the domain name does not start the WebDev
site
Once the WebDev site is deployed, the URL with the domain name must directly redirect to the WebDev site.

With IIS 7 in Windows 2008, you have the ability to specify a redirection rule, for example the address for starting the
requested dynamic WebDev site:

Special cases: IIS 6 (Windows 2003) or displaying static or AWP pages with only the domain in root:
1.Modify the home directory of the virtual site (wwwroot). This home directory must point to the _WEB sub-directory of
the requested WebDev site. If the site only support a single language, you have the ability to point to the sub-directory
of the language.
 WebDev application server 87
Most common problems

With IIS 6 in Windows 2003:

88 WebDev application server
Most common problems

With IIS 7 in Windows 2008:

2. Specify the default page (Default.html or index.htm). Use:

• a page that redirects to the URL of the dynamic site
• your static home page if you have one (the name given by WebDev is correct by default).
Note: If your first page is an AWP page, make sure that its name corresponds to the name of a document of the Web
site.

Let’s see some possibilities for creating a startup/redirection page toward a dynamic WebDev site:
• In the static home page of the WebDev site, enter the following code in the onload code of the page
DynamicSiteDisplay("MYSITE")
• Example of HTML code for a static "index.htm" page with FrameSet. With this type of page, the url displayed by the brow-
ser will remain unchanged (only the domain name) even when navigating in the site. This example is not suitable for a
site with .awp pages or for which a lot of referencing is required:
<html>
<head>
<title>My site</title>
<meta name="url" content="/WD180AWP/WD180AWP.EXE/CONNECT/MYSITE">
<meta name="robots" content="all">
</head>
<frameset rows="100%,0" frameborder=no border=0>
<frame name="SITE" src="/WD180AWP/WD180AWP.EXE/CONNECT/MYSITE">
<frame name="NONE" src="" scrolling="no" noresize>
<noframes>
<body><a href="/WD180AWP/WD180AWP.EXE/CONNECT/MYSITE">
Your browser does not support the frames, click here to start the site</a>
 WebDev application server 89
Most common problems

</body>
</noframes>
</frameset>
</html>
• Example of HTML code for a static "index.htm" page for redirection by meta tag:
<html>
<head>
<title>My site</title>
<meta name="url" content="/WD180AWP/WD180AWP.EXE/CONNECT/MYSITE">
<meta http-equiv="refresh" content="0;URL=/WD180AWP/WD180AWP.EXE/CONNECT/
MYSITE">
<meta name="robots" content="all">
</head>
<body><a href="/WD180AWP/WD180AWP.EXE/CONNECT/MYSITE">
The site is currently loading, click here to force a reload</a>
</body>
</html>