Creating/Configuring a WEBDEV deployment account

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

Help / WEBDEV administrator / WEBDEV Application Server administrator / 11. IIS example

Overview
Using WEBDEV Account Manager
Configuring WEBDEV Account Manager
Creating a deployment account with WEBDEV Account Manager
Special case
Linux server
Apache server on Windows

WINDEV

WEBDEV

WINDEV Mobile

Others

Creating/Configuring a WEBDEV deployment account

Overview

We recommend that you use WEBDEV Account Manager to create and configure a WEBDEV account, especially in a configuration of the following type:

Windows Server 2008/2012/2022,
IIS Web server,
IIS FTP server.

This is recommended especially for shared hosting or for hosting that requires multiple WEBDEV accounts.

When the WEBDEV Application Server is installed, a Windows account is created or defined as administrator of the WEBDEV Application Server. This user has all the rights (administration, deployment, statistics).

To configure the different characteristics of this user or define a specific user to deploy your sites, use WEBDEV Account Manager

WEBDEV Account Manager automatically performs the following configuration tasks:

Creating a deployment account.
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).
Creation of an FTP alias (for an installation via FTP).

If you do not use IIS as a Web server, WEBDEV Account Manager will not perform all the necessary steps, you will need to define some settings manually.

Using WEBDEV Account Manager

Configuring WEBDEV Account Manager

First, you need to configure WEBDEV Account Manager. Here is a typical configuration example:

Directory configuration
In the "Hosting parameters" group, click "Directories":

The directory that will contain all elements deployed by the WEBDEV sites: "C:\WEBDEV hosting\". There will be one subdirectory per WEBDEV account and another subdirectory per site. Example: "C:\WEBDEV hosting\USER_WEBDEV\".
The name of subdirectory of dynamic sites (corresponds to fExeDir() when running a site): "sites". This directory will contain the libraries (.wdl) of the sites, the _WEB subdirectories, the .awl, .awp pages, ... There will be one subdirectory per site. Example: "C:\WEBDEV hosting\USER_WEBDEV\sites\FirstWEBDEVSite\".
The name of subdirectory of SOAP Webservices (corresponds to fExeDir() when running a SOAPWebservice): "SOAPWebservices". This directory will contain the SOAP Webservices (.awws). There will be one subdirectory per web service. Example: "C:\WEBDEV hosting\USER_WEBDEV\SOAPwebservice\FirstSOAPWebService\".
The name of subdirectory of REST Webservices (corresponds to fExeDir() when running a REST Webservice): "RESTWebservices". This directory will contain the REST web services (.WDL). There will be one subdirectory per web service. Example: "C:\WEBDEV hosting\USER_WEBDEV\RESTwebservice\FirstRESTWebService\".
The name of data subdirectory (corresponds to fExeDir() at runtime): "Data"
This directory will contain the HFSQL Classic data files(.fic) , .ini files, PDF, ... There will be one subdirectory per site and/or web service. Example: "C:\WEBDEV hosting\USER_WEBDEV\Data\FirstWEBDEVSite\".
The name of the subdirectory of static sites: "wwwroot"
This directory will be set as the root of the website, the root of the virtual website.

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

Click the "Apply" button to save the modifications.

OS accounts
In the "Hosting parameters" group, click "OS accounts".

Specify:
- The group of Windows accounts that will be used for administration purposes, and to perform the installations, including the FTP installation, if necessary
- The group of Windows accounts in which the sites will operate: (Guests)
Click the "Apply" button found at the bottom of window to save the modifications.

Account limits
You can set two limits on a user account:

the maximum number of connections assigned to the account. This number of connections must be distributed between the different WEBDEV sites of the account.
the number of sites associated with an account.

To set the limits:

In the "Hosting parameters" group, click "Limits":
Specify:
- The maximum number of connections that will be shared between sites (0 = unlimited),
- If the number of sites associated with an account must be limited, etc.

Click "Apply" at the bottom of the window to save the changes.

Creating a deployment account with WEBDEV Account Manager

To create a deployment account in WEBDEV Account Manager:

Open WEBDEV Account Manager from the Windows Start menu.
In the "Users" group, click "New user". The user creation wizard starts. Simply follow the different steps.
Remark: If necessary, WEBDEV Account Manager will prompt you to define an administration group. In this example, answer "Yes" to the question "Continue without this group?".
You can:
- Create a Windows account. This account will be used for deploying and configuring your sites.
- Use an existing Windows account.
If you are creating a Windows account, enter the username and password (you can also generate the password. In that case, don't forget to write it down).

Go to the next step of the wizard.
The wizard prompts you to select the specific WEBDEV options associated with the account:

The (optional) options are:
- This account is a WEBDEV administrator account: In this case, this account will be able to configure the other user accounts via the remote administrator.
- Leave account inactive when created: In this case, this account cannot be used to deploy or update sites. Likewise, this account won't allow you to use the remote administrator.
Go to the next step.
The wizard suggests a Windows account to run the applications. Go to the next step of the wizard.
Enter the user details. Go to the next step.
The directories of the user account are defined automatically according to the data specified in the server configuration.
Go to the next step.
Specify the maximum number of connections allowed for the account and, if necessary, the maximum number of sites that can be installed.
Select or specify the parameters of the HFSQL Client/Server server that must be associated with the user account.
The next step of the wizard includes virtual websites.
- If you choose to create a new virtual site, simply enter the DNS name that will point to this site (the DNS must also be configured).
- If you choose to use an existing virtual site, its configuration will be replaced.
  Remark: the root directory of the virtual site will change. 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).
Go to the next step.
In this step you can specify whether FTP access and deployment should be allowed for the user. This step is not necessary for HTTP deployments.
Go to the next step.
The wizard is finished. Check all choices. You can uncheck the operations you don't want the wizard to perform for you.
Finish the wizard. Your server is now ready to receive WEBDEV sites.

Special case

Linux server

When using a Linux server, it is necessary to:

Create a WEBDEV user account with the WEBDEV Account Manager.
Associate the WEBDEV user account with an existing system account of the same name via the Remote WEBDEV administrator.

Apache server on Windows

When using an Apache server on Windows, it is necessary to create a WEBDEV user account with WEBDEV Account Manager.