PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
New WEBDEV 24 feature!
  • Library implementation
  • Remote deployment (by HTTP or FTP)
  • The steps
  • Creating the setup
  • Deployment by deployment package
  • The steps
  • Creating the setup
  • Install the site
  • Deployment by physical media
  • Creating the setup
  • Installing the site on a Web server (physical media)
  • On-lining the WEBDEV site
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
5. Deploying a dynamic site (Session or AWP) in practice
Previous pageTable of contentsNext page
When developing a dynamic site (in Session or AWP), one of the important phases consists of deploying this site on a Web server (at a hosting company or in Intranet)
Several deployment methods are available:
  • remote deployment (by HTTP): recommended method when the server is not directly accessible.
    Note: for backward compatibility, it is also possible to perform a remote deployment by FTP.
  • deployment by physical media: DVD, ...: recommended method when the server is easily accessible.
  • deployment by package: recommended method when the server is not directly accessible and when its characteristics are unknown.
Notes:
  • For each Web server that hosts WEBDEV sites, the hosting company must own a license for the WEBDEV application server.
  • To create the setup of a site, on the "Project" pane, in the "Generation" group, click "Deploy the site".
To deploy a static site, see Deploying a static site or a PHP site.
Library implementation
Before performing a setup, all the objects found in your dynamic site (in Session or AWP mode) must be included in a library.. A library is a file that groups all the elements created during the development (description of database and pages, compiled source codes, ...). The HTML pages and the images are not included in the library. The library is automatically implemented when creating the setup procedure.
Once the library is created, the wizard for setup creation starts. You can choose to perform:
  • a remote setup (by HTTP or FTP)
    In order to perform a remote setup, the hosting company must have:
    1. Created and configured your FTP account on the server (for setups by FTP).
    2. Created and configured your WEBDEV account on the server.
    The hosting company must provide you with your logins and passwords for these different accounts, as well as the name of the account that runs the sites associated with the WEBDEV account.
  • deployment in the PC SOFT Cloud:
    PC SOFT offers a hosting platform based on the Cloud Computing model: you deploy without worrying about hardware constraints and you are billed based on your applications' real usage.
    A PC SOFT Cloud account is required to perform this type of setup. The wizard proposes to create this account if necessary.
  • an installation by FTP via the test hosting service of PC SOFT :
    PC SOFT proposes to host your test sites. The setup is easily performed, directly from the environment. Once your site is developed, you have the ability to run its test directly.
    A PC SOFT developer account is required to perform this type of setup. The wizard proposes to create this account if necessary.
  • a deployment package:
    A deployment package is an executable containing all the elements required to deploy a WEBDEV site. This package can be run from any computer to install the Web site on the server by HTTP or FTP.
    To create this type of setup, there is no need to know the characteristics of FTP account and WEBDEV account found on the Web server.
  • a setup by physical media:
    The wizard allows you to create a setup program for your site. Then, this program will be supplied to the hosting company and it will be used to install your WEBDEV site on the Web server. To install your WEBDEV site, the hosting company must:
    1. Install the WEBDEV application server on the Web server (if not already done).
    2. Install your WEBDEV site by running the Install.exe executable of your setup.
Note: It is also possible to create a setup by stand-alone physical media, containing the setup of a WEBDEV application server limited to 10 connections. This solution is ideal for proof-of-concepts presented on a laptop.
Remote deployment (by HTTP or FTP)

The steps

The deployment steps are as follows:
  1. Installing the WEBDEV application server at the hosting company (optional step). See the documentation about the WEBDEV application server for more details.
  2. Creation of the following elements by the hosting company:
    • a WEBDEV account (in the administrator).
    • an FTP account (in the FTP server) only if the deployment is performed by FTP.
  3. The hosting company supplies the names and associated passwords as well as the name (IP address) of the server.
  4. Creating the remote setup from the editor: on the "Project" pane, in the "Generation" group, expand "Deploy the site" and select "Deploy the site remotely". The necessary files are copied into the transfer directory.
  5. On-lining the WEBDEV site.
Caution: By default, a WEBDEV site is deployed remotely by HTTP.

Creating the setup

You must define in the wizard:
  1. The information regarding the remote computer. This information must be supplied by the hosting company:
    • Server address (name of a computer accessible by network, IP address or Internet address).
    • Characteristics of the WEBDEV account (user name, password and account of the OS that runs the WEBDEV sites associated with the account).
    • Characteristics of the FTP account if necessary (user name and password).
    To easily identify the characteristics of the server for a forthcoming update, give a name to this server. This name will be displayed (followed by the server address) in the window for choosing the type of setup.
  2. The files to install. By default, the wizard selects the library, the data files, the images and the HTML pages.
  3. Configuring the setup: Chose the type of remote setup to perform:
    • Immediate update:
      The site files are compressed and immediately transferred onto the Web server (the Web server must be accessible from the setup computer). Then, the WEBDEV site is automatically installed on the Web server.
    • Delayed update:
      The site files are compressed and immediately transferred onto the Web server (the Web server must be accessible from the setup computer). The WEBDEV site will be installed on the server at the specified date and time. This allows you to update your site during the night (between midnight and 3 AM for example), when the number of Web users is reduced.
      Caution: the specified date and time are the ones of the server. Make sure that they are valid.
    • Activating the site immediately after setup:
      The site will be available once it has been installed: you will be able to connect to it either by using the proper address, or via a static page containing a link pointing to the site. If this option is not checked, the site can be activated via the remote administrator.
  4. Configuring the site. These options are used to configure the options for connecting to the site after its setup.
    These parameters can be modified if necessary:
    • by the deployment administrator found on the server.
    • by the remote administrator, that can be used by the site manager.
  5. If an analysis update was performed, select the automatic modification of data files during the setup.
    Note: if this option is selected, the update will be proposed during the setup.
    Special case: If the data files found on the server are in Hyper File 5.5 format, they must be migrated to HFSQL Classic format. This migration must be performed during the first site update.
  6. Specify whether your site is using the Native AS/400 Access.
    Reminder: if your site is using the Native AS/400 Access, the AS/400 DLLs must be installed on the Web server.
    If you are using a license for a limited number of computers, the number of current connections must be managed in the WEBDEV site (INI file or registry, ...).
Summary of elements installed as well as their location:
Site server
Data server
Directory of WEBDEV sites of user N
Data directory of user N
Directory defined by the hosting company.
In this directory, a sub-directory will be created for each site of user N.
Directory defined by the hosting company.
In this directory, a sub-directory will be created for the data files of each site of user N.
The following elements are installed in this site sub-directory: HTML pages, the library (".WDL"), the image directory.The following elements are installed in this data sub-directory: the ".FIC" files, the ".NDX" files, the ".MMO" files.
Example: The directory of sites for user N is "C:\UserN\WEBDEV sites".
The user N installs his site named "Boat". This site will be installed in the "C:\UserN\WEBDEV sites\Boat" directory.
Example : The data directory of user N is "D:\UserN\WEBDEV data".
The user N installs his site named "Boat". By default, the data files will be installed in the "D:\UserN\WEBDEV data\Boat" directory.
Deployment by deployment package

The steps

The deployment steps are as follows:
  1. Creating the deployment package from the editor: on the "Project" pane, in the "Generation" group, expand "Deploy the site" and select "Deploy the site remotely". In the wizard, select "Create a remote deployment package". A setup file is created.
  2. Transmitting the deployment package (by Internet, DVD, etc.) to the Web server administrator (hosting company for example)
  3. Installing the WEBDEV application server at the hosting company (optional step). See the documentation about the WEBDEV application server for more details.
  4. Creation by the hosting company of a WEBDEV account (in the administrator) and creation of an FTP account (in the FTP server) if necessary.
  5. Running the deployment package on a computer and installing the WEBDEV site.
  6. On-lining the WEBDEV site.

Creating the setup

You must define in the wizard:
  1. The files to install. By default, the wizard selects the library, the data files, the images and the HTML pages.
  2. If an analysis update was performed, select the automatic modification of data files during the setup.
    Note: if this option is selected, the update will be proposed during the setup.
    Special case: If the data files found on the server are in Hyper File 5.5 format, they must be migrated to HFSQL Classic format. This migration must be performed during the first site update.
  3. Configuring the site. These options are used to configure the options for connecting to the site after its setup.
    These parameters can be modified if necessary:
    • by the deployment administrator found on the server.
    • by the remote administrator, that can be used by the site manager.
  4. Specify whether your site is using the Native AS/400 Access.
    Reminder: if your site is using the Native AS/400 Access, the AS/400 DLLs must be installed on the Web server.
    If you are using a license for a limited number of computers, the number of current connections must be managed in the WEBDEV site (INI file or registry, ...).
  5. The default profile of the Web server to use. These parameters can be entered or modified by the person who installs the deployment package.
  6. Configuring the setup: Chose the type of remote setup to perform:
    • Delayed update:
      The site files are compressed and immediately transferred onto the Web server (the Web server must be accessible from the computer that installs the package). The WEBDEV site will be installed on the server at the specified date and time. This allows you to update your site during the night (between midnight and 3 AM for example), when the number of Web users is reduced.
      Caution: the specified date and time are the ones of the server. Make sure that they are valid.
    • Activating the site immediately after setup:
      The site will be available once it has been installed : you will be able to connect to it either by using the proper address, or via a static page containing a link pointing to the site. If this option is not checked, the site can be activated via the remote administrator.

Install 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 site must be installed (characteristics of the server FTP account if necessary and characteristics of the server WEBDEV account).
  3. Validate the site setup.
Deployment by physical media
This deployment is performed in three steps:
  1. Creating the setup version from the editor: on the "Project" pane, in the "Generation" group, expand "Deploy the site" and select "Create a setup by physical media".
  2. Installing (if necessary) the WEBDEV application server on the Web server. See the documentation about the WEBDEV application server for more details.
  3. Installing the site at the hosting company.

Creating the setup

You must define in the wizard:
  1. A title and a version caption for your setup. A title can be typed in each language that can be selected during the setup.
  2. A default directory.
  3. A layout for the setup window. The layout can be customized with the "Customize" button.
  4. The files of your site.
    Note: the library, HTML, Java, JavaScript and image files are selected by default.
  5. The appendix files:
    • The license (file in txt format) will be displayed when starting the setup.
      Note: the setup will be canceled if the license is not validated by the person in charge of setup.
    • The "Read me" file: this file can correspond to different formats (txt, htm, doc, hlp, pdf,  …). Regardless of the selected format, the user must have a software allowing him to view this file.
    • An executable that must be run at the end of the setup.
      Caution: Don't forget to include the files linked to this executable (DLLs, parameter files, other executables, etc.).
      Note: a license file and a "Readme" file can be selected for each setup language.
  6. If an analysis update was performed, select the automatic modification of data files during the setup.
    Note: if this option is selected, the update will be proposed during the setup.
  7. If programs not developed with WEBDEV must access the HFSQL files of your site, choose to install an ODBC driver.
    Note: if this option is selected, installing the driver will be proposed during the setup.
  8. Specify whether your site is using the Native AS/400 Access.
    Reminder : if your site is using the Native AS/400 Access, the AS/400 DLLs must be installed on the Web server.
    If you are using a license for a limited number of computers, the number of current connections must be managed in the WEBDEV site (INI file or registry, ...).
  9. Print the deployment documentation:
    The deployment documentation indicates the WEBDEV license as well as all the modules installed during the deployment. It also specifies the registry keys generated for the WEBDEV site. When the site is installed on the server, these keys can be updated in the registry or saved in a file for further examination.
    The deployment documentation must be supplied to the person in charge of installing your WEBDEV site (hosting company or Intranet manager).
  10. Modify (if necessary) the directory for generating the setup.
    By default, the setup is generated in the "INST" sub-directory of your project.
  11. Generate the setup.
    An information window flags the possible presence of files with long names. If the setup is performed on a network drive, make sure that:
    • the network drive supports the long names,
    • the network drive does not modify the case (uppercase/lowercase characters) in the names of files.
  12. When the setup is created, WEBDEV proposes to:
    • run the test of created setup.
    • open the Windows explorer in the directory for setup generation.
  13. Perform a backup of your site.
    We advise you to keep a backup of source code corresponding to an installed version of your site.

Installing the site on a Web server (physical media)

If you are installing your site via a hosting company, this one can propose two possibilities:
  • Install your site on a "shared" server. This server manages the sites for several customers. This server is configured when installing the WEBDEV application server. The WEBDEV administrator (WD240ADMIN.EXE) is used to individually configure each WEBDEV site installed on this server.
    Caution: The memory resources of server are shared by all sites.
  • Install your site on a "shared" server (recommended solution). You own this server.
    In this case you must:
    • configure the Web server,
    • manage the memory resources for your site.
To install the WEBDEV site on a Web server (at a hosting company or in Intranet):
  1. Install (if necessary) the WEBDEV application server on the Web server.
    Caution: if the WEBDEV application server is not installed on the Web server, the dynamic WEBDEV site will not operate properly.
    Note: For each Web server that is hosting WEBDEV sites, the hosting company must own a license for the WEBDEV application server.
  2. To install the WEBDEV site, INSTALL.EXE (supplied with the setup of WEBDEV site) must be run on the Web server.
    Important: To update an existing site, you must lock the access to the site via the WEBDEV administrator (check "WEBDEV site locked" in the "Sites" tab).
  3. Choose the setup language: a setup wizard starts. Go to the next plane.
  4. The setup automatically detects whether one or more of the following Internet servers are installed on the computer:
    • IIS Version 2 to 7 (Microsoft Internet Information Server): Microsoft server.
    • Apache Version 1.3.x and 2.x: free Web server supplied by the Apache Group.
    Three cases may occur:
    • Case 1 : your Web server is not displayed in this list: select "Other server". See the online help for more details about the server configuration.
    • Case 2: your Web server is displayed in the list but it is grayed: your Web server was not detected. To select it, all you have to do is check "Display all the servers".
      Then, you must ask to generate a configuration file in order to run the configuration later (to install your server later for example).
    • Case 3: your Web sever can be selected directly: select your server.
      You can ask to generate a configuration file in order to run the configuration later.
      The configuration file can be modified before it is run.
      Depending on the selected server, the extension of configuration file will be ".reg", ".conf" or something else.
  5. Select the setup directory:
    <webroot> indicates the root directory the computer's Web server. Depending on the selected Web server, the root directory is detected and displayed. If the root directory of Web server is not displayed, it can be typed in the gray area or it can be found via the "…" button.
    Caution: if the area is filled, we advise you not to modify it.
  6. Updating the data files (optional step, only for a site update).
    To update the data files associated with the WEBDEV site, choose to run the automatic modification of the data files.
    Contact the provider of the site if you don't know whether you must perform this update or not.
    Caution: The data files must not be currently used. Use the WEBDEV administrator to check that no current connection is in progress and to stop the sites (check "Site locked" in the "Sites" tab).
  7. Install an ODBC driver for HFSQL if programs not developed with WEBDEV must access the HFSQL files of the site that will be installed (optional step).
  8. The setup summary is displayed. Confirm your choices.
  9. The setup is completed:
    • Click the proposed address to run the test of your site locally. This option can be used only if the Web server was automatically configured.
    • Click "Copy" to retrieve the proposed address. See "On-lining the dynamic site", page 220 for more details.
    • Click "Done" to end the setup.
  10. Configuring the Web server:
    If the configuration of the Web server was not performed automatically, two cases may occur:
    • Case 1: your server was detected and a configuration file was generated: this file can be viewed, modified (if necessary) and run.
    • Case 2: your server was not detected: see the online help for more details.
  11. Via the WEBDEV administrator, unlock the sites that may be locked and configure the parameters of your dynamic site.
    These parameters correspond to:
    • the total number of authorized connections to the site,
    • the number of authorized connections for a user,
    • the authorized idle time.
Run the test of the WEBDEV site from the administrator via the [test page] option ("Advanced" tab).
Notes:
  • The WEBDEV administrator (WD240ADMIN.EXE) must be started and run in background task. It can be installed as service in Windows NT.
  • See The WEBDEV administrator in practice for more details about the WEBDEV administrator.
On-lining the WEBDEV site
To allow the Web users to access your site installed at a hosting company, create a link in your home page allowing your WEBDEV site to be started.
If the setup was perform by physical media, the address to use was supplied at the end of setup. Replace <localhost> by the address of your site.
Example used to start a "OURAPP" site from the PC SOFT site:
http://www.windev.com/WD240AWP/WD240AWP.EXE/ CONNECT/OURAPP
To start the site by using its address (prettyeyes.com 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 toward the WEBDEV site, which means toward the following address for example:
    "http://205.51.231.57/WD240AWP/WD240AWP.EXE/CONNECT/prettyeyes"
Example of META tag that must be included in the <HEAD> section of an HTML page:
<meta http-equiv="refresh"
content="0;URL=http://205.51.231.57/WD240AWP/WD240AWP.EXE.EXE/CONNECT/prettyeyes">
Special case: If a home page was defined in your dynamic site, the address for starting this home page is as follows:
http://<ServerAddress>/
<ProjectName>_WEB/
Previous pageTable of contentsNext page
Minimum version required
  • Version 24
Comments
Click [Add] to post a comment