ONLINE HELP
 WINDEV, WEBDEV AND WINDEV MOBILE
Help / WEBDEV concepts / Part 7 - Deploying a website
  • Generating a library
  • Remote deployment (via HTTP or FTP)
  • Steps
  • Creating the setup program
  • Deployment using a package
  • Steps
  • Creating the setup program
  • Installing the site
  • Deployment using installation media
  • Creating the setup program
  • Installing the site on a web server (installation media)
  • Publishing the WEBDEV website
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
5. Deploying a dynamic Session or AWP site in practice
Previous pageTable of contentsNext page
When developing a dynamic Session or AWP site, one of the most important steps is to deploy the site on a web server (at a hosting provider or on an Intranet).
Several deployment methods are available:
  • deployment to PCSCloud: paid turnkey solution. For more details, see http://www.pcscloud.net.
  • remote deployment (via HTTP) on a WEBDEV Application Server or WEBDEV Cluster: recommended method when the server is not directly accessible.
    Note: For backward compatibility, it is also possible to perform a remote deployment via FTP.
  • deployment using a package: recommended method when the server is not directly accessible and you don't know the characteristics of the server.
  • deployment using installation media: recommended method when the server is easily accessible.
  • deployment via a Docker image.
Remarks:
  • For each web server hosting WEBDEV websites, the hosting provider must have a WEBDEV Application Server license.
  • To create the setup of a site, go to the "Project" tab, "Generation" group, expand "Deploy site" and select "Generate and deploy site".
To deploy a static site, see Deploying a static or PHP site.
Generating a library
Before creating the setup program, all the objects from your dynamic Session or AWP site must be included in a library. A library is a file containing all the objects created during the development process (database description, page description, compiled source code, etc.). HTML pages and images are not included in the library. The library is automatically generated when the setup program is created.
Once the library is created, the setup wizard opens. You can choose one of the following options:
  • deployment to PCSCloud:
    PC SOFT offers a hosting platform based on the Cloud Computing model. You can deploy without worrying about hardware constraints and pay only for the resources used by your applications.
    A PCSCloud account is required for this type of installation. The wizard prompts you to create this Cloud account if necessary.
  • remote deployment (via HTTP or FTP) on a WEBDEV Application Server or WEBDEV Cluster:
    Before performing a remote setup, the hosting provider must have configured the web server (and the WEBDEV Cluster if necessary) and sent the parameters needed to install the site.
  • remote deployment package:
    A deployment package is an executable file containing all the elements required to deploy a WEBDEV website. This package can then be executed from any computer to install the website on a remote WEBDEV Application Server or a WEBDEV Cluster (via HTTP or FTP).
    To create this type of setup, there is no need to know the characteristics of the WEBDEV account on the web server.
  • installation media:
    The wizard allows you to create a setup program for your site. This program can be provided to the hosting service and used to install your WEBDEV website on the web server. To install your WEBDEV website, the hosting provider must:
    1. Install the WEBDEV Application Server on the web server (if necessary).
    2. Install your WEBDEV website by running the Install.exe file of your setup.
    Note: It is also possible to create stand-alone installation media, containing the setup of a WEBDEV Application Server limited to 10 connections. This solution is ideal for a proof of concept presented on a laptop.
  • setup via a Docker image:
    This option allows you to create a Docker recipe including the site, the WEBDEV Application Server and the web server.
  • setup via PC SOFT's test hosting service:
    PC SOFT can host your test sites. The setup is very easy and can be started directly from the environment. Once the site is developed, you can test it directly.
    A PC SOFT developer account is required for this type of setup. The wizard prompts you to create this account if necessary.
Remote deployment (via HTTP or FTP)

Steps

The deployment steps are as follows:
  1. The WEBDEV Application Server is installed at the hosting provider (optional step). For more details, see the WEBDEV Application Server documentation.
  2. The hosting provider creates a deployment account.
    Note: If the installation is done via FTP (optional), an FTP account is created (in the FTP server).
  3. The hosting provider provides the names and associated passwords as well as the name (IP address) of the server.
  4. The setup is created remotly from the editor: on the "Project" tab, in the "Generation" group, expand "Deploy site" and select "Generate and deploy site". In the wizard that opens, in the "Select setup model" step, select "Deploy to a remote WEBDEV Application Server or to a WEBDEV Cluster". The necessary files are copied to the transfer directory.
  5. The WEBDEV website is published.
Caution: By default, a WEBDEV website is deployed remotely via HTTP.

Creating the setup program

In the wizard, define the following elements:
  1. Information about the remote computer. This information must be provided by the hosting service:
    • Server address: Name of a computer accessible over the network, IP address or Internet address.
    • Account: Username, password and account of the OS that runs the WEBDEV websites associated with the account.
    • Characteristics of the FTP account if necessary: Username and password. To easily identify the characteristics of the server for future updates, assign a name to this server. This name will appear (followed by the server address) in the installation type selection window.
    • Site deployment settings: This includes the site deployment name, the domain associated with the site, and the location of the data files.
  2. Zero-downtime update: The update of a WEBDEV Session or AWP website does not affect active users. Active users stay on the old version. They will only have access to the new version of the site the next time they log in.
    This deployment mode allows session sites to be deployed with zero downtime.
  3. Files to install: By default, the wizard selects the library, data files, images and HTML pages.
  4. If the analysis was updated, select the automatic modification of data files.
    Note: If this option is selected, you will be asked to update the data files during installation.
    Special case: If the data files found on the server are in Hyper File 5.5 format, they must be migrated to HFSQL Classic. This migration should only be performed when the site is updated for the first time.
  5. Specify whether your site uses the Native AS/400 Connector.
    Reminder: If your site uses the Native AS/400 Connector, the AS/400 DLLs must be installed on the web server.
    If you are using a license for a limited number of computers, you will need to manage the number of concurrent connections in the WEBDEV website (INI file, registry, etc.).
  6. Site settings: Choose the deployment and site settings:
    • Deployment settings. You can choose between:
      • immediate update: The site files are compressed and immediately transferred to the web server (the server must be accessible from the setup computer). Then, the WEBDEV website is automatically installed on the web server.
      • deferred update ("Schedule deployment for a later date" option): The site files are compressed and immediately transferred to the web server (the server must be accessible from the setup computer). The WEBDEV website will be installed on the server at the specified date and time. This allows you to update the site at night (between midnight and 3 AM, for example), when the number of users is lower.
        Caution: The specified date and time are the ones of the server. Make sure they are valid.
    • Site settings. These options allow you to configure the site connection options after it is installed.
      If necessary, these settings can be modified:
      • via the deployment administrator located on the server.
      • via the remote administrator, which can be used by the site manager.
Summary of elements installed as well as their location:
Website server
Data server
Directory of WEBDEV websites of user N
Data directory of user N
Directory defined by the hosting provider.
A subdirectory will be created in this directory for each site of user N.
Directory defined by the hosting provider.
A subdirectory will be created in this directory for the data files of each site of user N.
The HTML pages, the library (".WDL") and the image directory are installed in this subdirectory.".FIC", ".NDX" and ".MMO" files are installed in this data subdirectory.
Example: The site directory of user N is "C:\UserN\WEBDEV websites".
User N installs their site named "Boat". This site will be installed in the "C:\UserN\WEBDEV websites\Boat" directory.
Example: The data directory of user N is "D:\UserN\WEBDEV data".
User N installs their site named "Boat". By default, the data files will be installed in the "D:\UserN\WEBDEV data\Boat" directory.
Deployment using a package

Steps

The deployment steps are as follows:
  1. The deployment package is created from the editor: on the "Project" tab, in the "Generation" group, expand "Deploy site" and select "Generate and deploy site". In the wizard, select "Create a remote deployment package". A setup file is created.
  2. The deployment package is sent (via the Internet) to the web server administrator (hosting provider, for example)
  3. The WEBDEV Application Server is installed at the hosting provider (optional step). For more details, see the WEBDEV Application Server documentation.
  4. The hosting provider creates a deployment account (via WEBDEV Account Manager) and an FTP account (in the FTP server) if necessary.
  5. The deployment package is run on a computer and the WEBDEV website is installed.
  6. The WEBDEV website is published.

Creating the setup program

In the wizard, define the following elements:
  1. Default web server profile to use: These parameters can be entered or modified by the person who installs the deployment package.
  2. Zero-downtime update: The update of a WEBDEV Session or AWP website does not affect active users. Active users stay on the old version. They will only have access to the new version of the site the next time they log in.
    This deployment mode allows session sites to be deployed with zero downtime.
  3. Files to install: By default, the wizard selects the library, data files, images and HTML pages.
  4. If the analysis was updated, select the automatic modification of data files.
    Note: If this option is selected, you will be asked to start the update during installation.
    Special case: If the data files found on the server are in Hyper File 5.5 format, they must be migrated to HFSQL Classic. This migration should only be performed when the site is updated for the first time.
  5. Deployment settings. Chose the type of remote installation:
    • Deferred update:
      The site files are compressed and immediately transferred to the web server (the web server must be accessible from the computer where the package is installed). The WEBDEV website will be installed on the server at the specified date and time. This allows you to update the site at night (between midnight and 3 AM, for example), when the number of users is lower.
      Caution: The specified date and time are the ones of the server. Make sure they are valid.
    • Publish site immediately after installation:
      The site will be available after its setup. You will be able to access the site by using its address, or via a static page containing a link pointing to the site. If this option is not checked, the site can be published via the remote administrator.

Installing the site

To install a site, you must:
  1. Run the deployment package.
  2. Specify the characteristics of the web server on which the WEBDEV website must be installed (characteristics of the server deployment account and FTP account, if necessary).
  3. Validate the setup of the site.
Deployment using installation media
This deployment is performed in three steps:
  1. The installation version is created from the editor: on the "Project" tab, in the "Generation" group, expand "Deploy site" and select "Generate and deploy site". In the wizard, select "Create installation media".
  2. WEBDEV Application Server is installed on the web server if necessary. For more details, see the WEBDEV Application Server documentation.
  3. The site is installed at the hosting provider.

Creating the setup program

In the wizard, define the following elements:
  1. Website files.
    Note: Library, HTML, Java, JavaScript and image files are selected by default.
  2. Type of deployment. You can choose to deploy with or without downtime.
  3. Deployment settings:
    • Publish site immediately after installation:
      The site will be available after its setup. You will be able to access the site by using its address, or via a static page containing a link pointing to the site. If this option is not checked, the site can be published via the remote administrator.
    • Deferred update:
      The WEBDEV website will be installed on the server at the specified date and time. This allows you to update the site at night (between midnight and 3 AM, for example), when the number of users is lower.
      Caution: The specified date and time are the ones of the server. Make sure they are valid.
  4. Site settings. These options allow you to configure the site connection options after it is installed.
    If necessary, these settings can be modified:
    • via the deployment administrator located on the server.
    • via the remote administrator, which can be used by the site manager.
  5. If the analysis was updated, select the automatic modification of data files.
    Note: If this option is selected, you will be asked to start the update during installation.
  6. If programs not created with WEBDEV need to access the HFSQL data files of your website, choose to install an ODBC driver.
    Note: If this option is selected, you will be asked to install the driver during installation.
  7. Specify whether your site uses the Native AS/400 Connector.
    Reminder: If your site uses the Native AS/400 Connector, the AS/400 DLLs must be installed on the web server.
    If you are using a license for a limited number of computers, you will need to manage the number of concurrent connections in the WEBDEV website (INI file, registry, etc.).
  8. Indicate if the web server should be included in the setup. In this case, you must select the web server to install.
  9. Specify the setup customization options:
    • If the setup should be customized.
    • Default installation directory (site and data).
    • Setup languages.
    • Setup title. This title can be written in any of the languages selected during setup.
    • License (txt file). This license will be displayed at the beginning of the setup process.
      Note: Setup will be canceled if the license is not validated by the person trying to complete the setup process.
    • Readme file: this file can be in different formats (txt, htm, doc, hlp, pdf, etc.). Regardless of the selected format, the user must have the necessary software to view the file.
  10. Change the setup generation directory if necessary.
    By default, the setup is generated in the "INSTALL" subdirectory of your project.
  11. Generate the setup.
    An information window indicates if there are files with long names. If the setup is performed on a network drive, make sure that:
    • the network drive supports long names,
    • the network drive does not change the case of file names.
  12. Once the setup has been created, WEBDEV prompts you to:
    • test the setup.
    • open Windows File Explorer to the setup generation directory.
  13. Back up your website.
    It is recommended to create a backup copy of the new installed version of your website.

Installing the site on a web server (installation media)

If you install your site via a hosting provider, they offer you two options:
  • Install your site on a "shared" server. This server manages sites for several customers. This server is configured when WEBDEV Application Server is installed. You can individually configure each WEBDEV website installed on this server in the WEBDEV administrator (WD300ADMIN.EXE).
    Caution: All server resources are shared with other websites.
  • Install your site on a "dedicated" server (recommended solution). This option gives you full access to the server without going through a hosting provider.
    In this case you must:
    • configure the web server,
    • manage the resources of your website.
To install the WEBDEV website on a web server (at a hosting provider or on an Intranet):
  1. Install WEBDEV Application Server on the web server if necessary.
    Caution: If the WEBDEV Application Server is not installed on the web server, the dynamic WEBDEV website will not work properly.
    Note: For each web server hosting WEBDEV websites, the hosting provider must have a WEBDEV Application Server license.
  2. To install the WEBDEV website, INSTALL.EXE (provided with the setup of the WEBDEV website) must be run on the Web server.
    Important: To update an existing website, you must first prevent user access. To do so, go to the WEBDEV administrator and uncheck "Enabled" in the "Sites" tab.
  3. Choose the setup language: a setup wizard starts. Go to the next step.
  4. The setup automatically detects whether one or more of the following Internet servers are installed on the computer:
    • IIS 7 and later: server provided by Microsoft.
    • Apache 2.2 and 2.4: free web server provided by the Apache Group.
    Three cases may occur:
    • Case 1: Your web server does not appear in this list. In this case, select "Other server". For more details, see the online help about the server configuration.
    • Case 2: Your web server appears in the list but it is grayed out. This means your server has not been detected. To select it, simply check "Show all servers".
      You must then request the generation of a configuration file so that you can run the configuration later (if you want to install your server at a later date, for example).
    • Case 3: Your web server can be selected directly. In this case, select your server.
      You can request the generation of a configuration file so that you can run the configuration later.
      The configuration file can be modified before it is run.
      Depending on the chosen server, the configuration file may have a ".reg", ".conf" or other extension.
  5. Select the installation directory:
    <webroot> represents the root directory of the computer's web server. Depending on the selected web server, the root directory is detected and displayed. If the root directory of the web server does not appear, you can type it in the gray area or find it via the "…" button.
    Caution: If the area is already filled, don't make any changes.
  6. Update the data files (optional step, only for a site update).
    To update the data files associated with the WEBDEV website, choose to run the automatic modification of the data files.
    If you are not sure whether this update is necessary, contact the site provider.
    Caution: The data files must not be in use. Check that there are no active connections in the WEBDEV administrator. Then, go to the "Sites" tab and uncheck "Enabled".
  7. Install an ODBC driver for HFSQL if programs not developed with WEBDEV must access the HFSQL data files of the site that will be installed (optional step).
  8. The setup summary is displayed. Confirm your choices.
  9. The setup is completed:
    • Click the address that appears to test your site locally. This option can be used only if the web server was automatically configured.
    • Click "Copy" to get the address. For more details, see "Publishing the site".
    • Click "Finish" to end the setup.
  10. Web server configuration:
    If the web server was not configured automatically, two cases may occur:
    • Case 1: Your server has been detected and a configuration file has been generated. You can view, edit and run this file.
    • Case 2: Your server has not been detected. For more details, see the online help.
  11. Via the WEBDEV administrator, unlock the sites that may be locked and define the settings of your dynamic site.
    These settings correspond to:
    • the total number of authorized connections to the site,
    • the number of authorized connections for a user,
    • the authorized idle time.
Test the WEBDEV website from the administrator via the [test page] option ("Advanced" tab).
Remarks:
  • The WEBDEV administrator (WD300ADMIN.EXE) must be started and running in the background at all times. It can be installed as service.
  • For more details about the WEBDEV administrator, see WEBDEV administrator in practice.
Publishing the WEBDEV website
To give users access to a website installed with a hosting provider, create a link in the home page to launch the WEBDEV website.
If you used installation media, the address to be used was provided at the end of the setup. Replace <localhost> with the address of your site.
Example: Starting a site named "APP" from PC SOFT's website:
http://www.windev.com/WD300AWP/WD300AWP.EXE/ CONNECT/APP
To start the site directly using its address (mywebdevsite, for example), you must:
  1. Create an "Index.html" home page.
  2. In the header of this page, use the html commands (META REFRESH) to perform a redirection towards the WEBDEV website, i.e., towards the following address, for example:
    "http://205.51.231.57/WD300AWP/WD300AWP.EXE/CONNECT/mywebdevsite"
Example of the META tag that will be included in the <HEAD> section of an HTML page:
<meta http-equiv="refresh"
content="0;URL=http://205.51.231.57/WD300AWP/WD300AWP.EXE.EXE/CONNECT/mywebdevsite">
Special case: If a home page has been defined in your dynamic website, the address of this page should have the following format:
http://<ServerAddress>/<SiteName>_WEB/
Previous pageTable of contentsNext page
Comments
Click [Add] to post a comment

Last update: 12/10/2024

Send a report | Local help