• How to deploy?
• Required configuration.

	Estimated time: 30 mn

	Note	This section presents the deployment on a Windows server. If you are using a Linux server, see the documentation about WEBDEV Application Server for Linux.

• Remote deployment from the development computer (via HTTP or FTP).
• Deployment to PCSCloud (PC SOFT's Cloud service).
• Remote deployment from a management computer (via HTTP or FTP) using a "deployment package".
• Deployment via PC SOFT test hosting service.
• Deployment via physical media (CD, etc.). This deployment can be stand-alone: in this case, a web server and a limited WEBDEV Application Server are also installed by the setup.
• Deployment via a Docker image of the site.

• A web server,
• A WEBDEV Application Server (a 10-connection version is provided with WEBDEV).

• Install "WEBDEV Application Server - 10 connections" on a Windows computer. This application server must be installed on a computer other than the development computer. WEBDEV must not be installed on the same computer.
• Deploy the site remotely (via HTTP).

	Note	If you already have the parameters to access the server to which your site will be deployed, there is no need to install "WEBDEV Application Server - 10 connections". You can start the installation directly on the server via HTTP.

Installing "WEBDEV Application Server - 10 connections"

The installation steps are as follows:

1. Select the installation language of WEBDEV Application Server and confirm.
2. Accept the license agreement. Go to the next step of the wizard.
3. Select "Install limited version (10 connections)". Go to the next step.
   

1. Select the installation path of the Application Server ("C:\WEBDEV 28" by default).
   
2. The next step allows you to specify the root directory for deploying sites and web services. Keep the default path and go to the next step.
3. In the next step, you can define the advanced settings of WEBDEV Application Server. Keep the "Use default parameters" option.
   
4. If it is the first time you install WEBDEV Application Server, specify the parameters of the Windows account that will be used as WEBDEV administrator. This account will also be called "Hosting account".
   You can create a new Windows account or use an existing Windows account.
   Select an option and go to the next step.
5. If a previous version of WEBDEV Application Server has already been installed on the computer, the wizard allows you to:
   • manage the sites and web services from earlier versions. Keep the "Keep sites in their current versions" option and go to the next step.
   • import WEBDEV accounts. Keep the option "Don't import existing accounts" and go to the next step. Enter the login credentials of the Windows account that will be used as WEBDEV administrator. This account will also be called "Hosting account".
     You can create a new Windows account or use an existing Windows account.
     Select an option and go to the next step.
6. The next step allows you to manage the hosting of SaaS sites. The SaaS activation automatically installs a site and a web service to manage your SaaS sites. For more details, see SaaS. Validate this step.
7. In the next step, you can specify that a secure connection is required to access all remote administration sites.
8. The next step allows you to select the language of the application server that will be installed. The Application Server is available in 3 languages: english, spanish, french.
9. Validate the different setup steps.
10. If the computer contains several virtual servers, select the web servers on which the WEBDEV Application Server must be installed. You can keep the default website. Validate.
11. The wizard presents different options: select the desired options and keep "Start the WEBDEV administrator". Validate.
    

    	Note	The "View the user guide" option automatically displays the WEBDEV Application Server help at the end of the installation process. This help may help you solve configuration problems linked to access rights on the server.
12. "WEBDEV Application Server - 10 connections" is automatically configured. WEBDEV sites can be deployed immediately.
13. The WEBDEV administrator and the Hosting Control Center are automatically started.

Configuration via the Hosting Control Center

• WEBDEV Application Server,
• Web server (IIS),
• FTP server (IIS). The FTP server must be configured only for an installation via FTP.

• If necessary, open the Hosting Control Center from the Windows Start menu.

• To view the different parameters:
  1. Click "Directories" in the "Hosting parameters" group to configure the directories used by your server.
     Remark: The different options of this group allow you to define the parameters that will be used by default for your hosting server.
  2. Indicate where the sites will be installed. Choose the root directory where the subdirectories of the WEBDEV accounts will be created.
     

     	Note	Use a local directory. If you use a network directory, you need to specify a UNC path. Guest users must be able to access this path without the need for authentication.

     
     You can choose the names of the subdirectories that will contain the sites, web services and data.
     
  3. Click "Windows groups" and define the groups to which the Windows users created for the deployment will be assigned.
     For the deployment, you can create a group or use the standard "Power Users" group.
     A good practice for running sites consists in using the "IIS_IUSRS" group (on Windows versions where it is available).
     
     Click "Apply" to validate.
  4. Click "Limits" to specify the resource limitations to be applied to WEBDEV accounts:
     
     • Maximum number of connections shared between the sites (0 corresponds to an unlimited number),
     • Limitation of the number of sites to associate with an account, etc.
  5. Click "HFSQL Client/Server database" to configure a new HFSQL database each time a user is created.
     
  6. Once the hosting is configured, click "Apply" then the "Refresh" button (if this button is proposed).

Creating a deployment account

1. Click the "New user" button. The user creation wizard starts. Simply follow the different steps.
   Remark: If necessary, the Hosting Control Center will prompt you to define an administration group. In this example, answer "Yes" to the question "Continue without this group?".
2. You can:
   • Create a Windows account. This account will be used for deploying and configuring your sites.
   • Use an existing Windows account.
   In this example we will create 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.
3. The wizard presents the WEBDEV options associated with the account:
   
   Keep the default options and go to the next step.
4. The wizard suggests a Windows account to run the applications. Keep the default options and go to the next step of the wizard.
5. Enter the user information. Go to the next step.
6. The directories of the user account are automatically filled according to the specified data.
   
7. Continue with the wizard until you reach the "Virtual website" step.
   • 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.
8. Go to the next step.
9. In this step you can specify whether FTP access and deployment should be allowed for the user. In our case, this option is not necessary because we will perform an HTTP deployment. Go to the next step.
10. The wizard is finished. Check all choices. You can uncheck the operations you don't want the wizard to perform for you.
11. Validate the wizard. Your server is now ready to host WEBDEV sites. We will use the user we created to test the deployment of a site via HTTP.

• Remote deployment from the development computer (via HTTP or FTP). We will deploy our site using this method via HTTP.
  Remark: deployment via FTP requires an FTP server.
• Deployment in PCSCloud.
• Remote deployment from a management computer (via HTTP or FTP) using a "deployment package". This deployment mode is similar to the direct remote deployment. Main difference: the deployment is not performed from the WEBDEV development environment. In this mode:
  • the developer generates a deployment package.
  • the site administrator (who can be a person other than the developer) deploys the package on the remote server via WDDeploy. WDDeploy is a redistributable tool provided with WEBDEV.
• Deployment via physical media (CD, etc.). Deployment via physical media creates a setup support (like an application) that must be run directly on the server. This deployment mode is available in Windows only.
• Deployment via PC SOFT test hosting service.
• Deployment via a Docker image of the site.

Detailed example: deployment via HTTP

• Open the project you worked on in the previous lesson.
  1. Go to the WEBDEV home page (Ctrl + <).
  2. On the home page, click "Tutorial", then in "Parts 3 to 6", double-click "Full WEBDEV Site - Exercise".
  3. A dialogue box prompts you to open the project you worked on in the previous lesson. You can open the local copy or the original project. Select "Open the local copy".

	Answers	A completed project is available. You can use this project to complete the different exercises of this lesson. To open the completed project, go to the home page and click "Tutorial", then in "Parts 3 to 6", double-click "Full WEBDEV Site - Answers".

• We are going to use this wizard:
  1. In the ribbon, on the "Project" tab, in the "Generation" group, expand "Deploy site" and select "Generate and deploy site".
     
  2. The wizard starts. Before starting the installation, you need to include all the elements of your site in a library. A library is a file that contains all the elements created during the development steps (database description, pages, reports, queries, etc.). HTML pages and images are not included in the library.
     
     Go to the next step.
  3. You can include multiple languages in the library. In our example, we will keep the default options. Go to the next step.
  4. In "Library version details", you can define the information that will appear in the file properties in the Windows explorer. Go to the next step.
  5. Don't make a backup copy of the project and confirm.

• The setup wizard will now ask you some questions to define how your site will be deployed. In our case, we are going to perform a remote installation via HTTP:
  1. Select "Deploy to a remote WEBDEV Application Server".
     
     Go to the next step.
  2. To define the server parameters, you will need to get the information below from your hosting provider. We will enter the information corresponding to the previous setup:
     • Server address (in our example, name of the computer where "WEBDEV Application Server - 10 connections" was installed). The name can be:
       • a computer name accessible over the network (for example: "TestServer"),
       • an IP address (for example: 192.168.15.99),
       • an Internet address (for example: www.myserver.com).
         
     • User account that runs the setup. We created it in the previous step: the name of the account is "Mark".
     • Password associated with the account (in our example, also "mark").
       

       	Note	Caution: the username can be preceded by the domain name to avoid confusions. For example: "mycomputer\test" or "mydomain\test"
  3. Once you have entered your account details, go to the next step.
  4. Enter the site deployment parameters. Keep the default options.
     
     Go to the next step.
  5. The wizard prompts you to select the deployment mode:
     • Deploy without disconnecting users. This option allows you to update the site without disconnecting the users.
     • Deploy by disconnecting users. If this option is selected, the users will be automatically disconnected to update the site.
     Select "Deploy by disconnecting users" and go to the next step.
  6. WEBDEV establishes the connection and lists the operations to be executed (number of files to update, number of files to delete, etc.). To get the details of the operations and modify them if necessary, click "Edit list of files".
     
  7. Go to the next step.
  8. The wizard presents an option to include the automatic data file modification in the setup. You can also configure the elements required to use an HFSQL Client/Server database.
     
     Keep the default options and go to the next step.
  9. Specify the parameters of the site:
     
     You can change:
     • The maximum number of connections to the site: if this value is set to "5" for example, only 5 users will be able to connect to your site at the same time.
     • The maximum number of connections per user: if you set this value to "5" for example, the same user will be able to access the site up to 5 times.
     • The amount of idle time before user disconnection: this option frees all the resources used by the user's session if the user has been inactive for a given amount of time.
  10. By default, your site is activated immediately after setup. Users will not be able to access your site if "Activate site immediately after setup" is unchecked.
  11. The wizard allows you to perform:
      • an immediate setup: the files will be transferred to the server and the site will be installed immediately.
      • a deferred setup: the files will be immediately transferred to the server but the site will be installed at the specified date and time ("Schedule deployment for a later date").
  12. Go to the next step.
  13. The wizard allows you to define the site security parameters: Change of IP, etc.. Go to the next step.
  14. The wizard presents an option to automatically generate statistics files for the installed site. These statistics include actions performed on the website, user location, etc.
      Keep the default options and go to the next step.
  15. Confirm the setup ("Finish"). The setup wizard transfers the files.

• <site>, <data> and <web service> are the directories defined when creating the hosting account (see above).
• <site name> is the name of the site.