PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
  • Creating a setup via an HTTP access
  • Installing the reference version on the HTTP server
  • Updating the application
  • Notes
  • Updating the end-user computer
  • Protocols used
  • How to transform a network application into a network application by HTTP
  • Download page
  • Managing a proxy server
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
Overview
The network setup via HTTP consists in installing and updating a WINDEV application via an HTTP server. This server can be a Windows server or a Linux server.
Only the reference version of the application is installed on the server. The reference application corresponds to the setup that will be run by the end users.
During a first setup, the end user installs his application via Internet, via a specific page.
Whenever the application is run, an HTTP request is automatically performed to check whether the application was updated on the server. If an update is available, the application will be automatically updated.
How to proceed?

Creating a setup via an HTTP access

To create a setup via an HTTP access:
  1. Create the executable of the application ("Workshop .. Executable .. Generate the Windows executable").Create the executable of the application: click among the quick access buttons.
  2. Start creating the setup procedure ("Workshop .. Create the setup procedure").Start creating the setup procedure: on the "Project" pane, in the "Generation" group, expand "Setup procedure" and select "Create the setup procedure".
  3. In the wizard, click "2 - Setup" and select "Access the setup options".
  4. Choose "Setup with automatic update (Live Update)".
  5. Select "Setup by HTTP".Select "Setup by HTTP or HTTPS".
  6. Versions 17 and later
    Specify the parameters for HTTP deployment. You can:
    • Use a secure connection or not. You can:
      • define the type of connection when installing the reference version.
      • use a secure connection only.
    • Use authentication parameters. You can:
      • define the authentication parameters when installing the reference version.
      • use a connection with authentication only. In this case, the end user will have to enter a login and password to connect to the HTTP server and to install his update.
    • Configure the external address. This option is interesting when deploying on a computer where the setup was already started.
      You have the ability to specify the address of the HTTP server. This address can be modified during the deployment on the server.
      This allows you to deploy the same setup on several HTTP servers.
    New in version 17
    Specify the parameters for HTTP deployment. You can:
    • Use a secure connection or not. You can:
      • define the type of connection when installing the reference version.
      • use a secure connection only.
    • Use authentication parameters. You can:
      • define the authentication parameters when installing the reference version.
      • use a connection with authentication only. In this case, the end user will have to enter a login and password to connect to the HTTP server and to install his update.
    • Configure the external address. This option is interesting when deploying on a computer where the setup was already started.
      You have the ability to specify the address of the HTTP server. This address can be modified during the deployment on the server.
      This allows you to deploy the same setup on several HTTP servers.
    Specify the parameters for HTTP deployment. You can:
    • Use a secure connection or not. You can:
      • define the type of connection when installing the reference version.
      • use a secure connection only.
    • Use authentication parameters. You can:
      • define the authentication parameters when installing the reference version.
      • use a connection with authentication only. In this case, the end user will have to enter a login and password to connect to the HTTP server and to install his update.
    • Configure the external address. This option is interesting when deploying on a computer where the setup was already started.
      You have the ability to specify the address of the HTTP server. This address can be modified during the deployment on the server.
      This allows you to deploy the same setup on several HTTP servers.
  7. Follow the different wizard steps and validate the creation of the setup program.
To create a setup via an HTTP access:
  1. Create the executable of the application: click among the quick access buttons.
  2. Start creating the setup procedure: on the "Project" pane, in the "Generation" group, expand "Setup procedure" and select "Create the setup procedure".
  3. In the wizard, click "2 - Setup" and select "Access the setup options".
  4. Choose "Setup with automatic update (Live Update)" and select "Setup by HTTP (on owner server or in the CLOUD)".
  5. The different types of deployment are presented:
    • Create a deployment package. This option is used to perform a setup on a HTTP(S) server or in the CLOUD of PC SOFT applications.
    • Deploy in the CLOUD immediately. This option is used to deploy the application in the CLOUD for PC SOFT applications and it requires the identifiers of the CLOUD platform created beforehand.
  6. Select "Create a deployment package".
  7. Specify the parameters for HTTP deployment. You can:
    • Use a secure connection or not. You can:
      • define the type of connection when installing the reference version on the server.
      • use a secure connection only.
    • Use authentication parameters. You can:
      • define the authentication parameters when installing the reference version on the server.
      • use a connection with authentication only. In this case, the end user will have to enter a login and password to connect to the HTTP server and to install his update.
    • Configure the external address. This option is interesting when deploying on a computer where the setup was already started.
      You have the ability to specify the address of the HTTP server. This address can be modified during the deployment on the server.
      This allows you to deploy the same setup on several HTTP servers.
  8. Follow the different wizard steps and validate the creation of the setup program. See Setup wizard: The steps for creating the setup of a WINDEV application for more details.

Installing the reference version on the HTTP server

Once the setup procedure is created, you have the ability to run the setup program. This program can also be run directly via the INSTALL.EXE file.
When running the setup program, the wizard proposes to:
  • deploy the application locally, on the current computer.
  • deploy the application remotely, on the HTTP server (at the hosting company).
  • Versions 17 and later
    deploy the setup in the PC SOFT cloud.
    New in version 17
    deploy the setup in the PC SOFT cloud.
    deploy the setup in the PC SOFT cloud.
Case #1: Deploying the application locally, on the current computer.
This setup mode is not available during the setup on a Linux server.
  • If an HTTP server is installed on the current computer, this server is configured and the files of the reference application are copied into the specified directory.
  • If no HTTP server is installed on the current computer, a default server is installed (WDADMINEXE) and automatically configured. The files of the reference application are installed in the specified directory.

    Versions 17 and later
    In the setup options, if you have specified that:
    • the type of connection is defined during the setup, a combo box allows you to specify the protocol used.
    • the authentication choice is performed during the setup, you have the ability to specify that an authentication is required.
    • a specific external address must be used, this address is selected in the "Access IP address" control.
    New in version 17
    In the setup options, if you have specified that:
    • the type of connection is defined during the setup, a combo box allows you to specify the protocol used.
    • the authentication choice is performed during the setup, you have the ability to specify that an authentication is required.
    • a specific external address must be used, this address is selected in the "Access IP address" control.
    In the setup options, if you have specified that:
    • the type of connection is defined during the setup, a combo box allows you to specify the protocol used.
    • the authentication choice is performed during the setup, you have the ability to specify that an authentication is required.
    • a specific external address must be used, this address is selected in the "Access IP address" control.
Click "Next".
Case #2: Deploying the application remotely, on the HTTP server (at the hosting company). In this case, an FTP connection must be used to send the elements to the server.
  • Enter the URL of your site at the hosting company: this information corresponds to the address that will be entered by the users to access the setup page of your application. The setup of the reference application will be found at this URL.
    Versions 17 and later
    In the setup options, if you have specified that:
    • the type of connection is defined during the setup, a combo box allows you to specify the type of the address (http or https).
    • the authentication choice is performed during the setup, you have the ability to specify that an authentication is required.
    New in version 17
    In the setup options, if you have specified that:
    • the type of connection is defined during the setup, a combo box allows you to specify the type of the address (http or https).
    • the authentication choice is performed during the setup, you have the ability to specify that an authentication is required.
    In the setup options, if you have specified that:
    • the type of connection is defined during the setup, a combo box allows you to specify the type of the address (http or https).
    • the authentication choice is performed during the setup, you have the ability to specify that an authentication is required.
    Click "Next".
  • Enter the characteristics of the FTP server that will be used to install the reference application on the HTTP server.
Versions 17 and later
Case #3: Deploy the setup in the PC SOFT Cloud.
In this case, you must:
  • Enter the parameters of your PC SOFT Cloud account.
  • Select the platform on which the application will be deployed.
  • Click "Next".
New in version 17
Case #3: Deploy the setup in the PC SOFT Cloud.
In this case, you must:
  • Enter the parameters of your PC SOFT Cloud account.
  • Select the platform on which the application will be deployed.
  • Click "Next".
Case #3: Deploy the setup in the PC SOFT Cloud.
In this case, you must:
  • Enter the parameters of your PC SOFT Cloud account.
  • Select the platform on which the application will be deployed.
  • Click "Next".
Notes:
  • In some cases, you may have to configure the HTTP server. You can for example create a virtual directory (alias) on the Web site that points to the directory where the FTP deployment was performed.
  • In any case, an HTML page allowing the end user to download the application setup is available. This page can be included in your site.

Updating the application

To update your application:
  1. Create the executable of the application ("Workshop .. Executable .. Generate the Windows executable").Create the executable of the application: click among the quick access buttons.
  2. Start creating the setup procedure ("Workshop .. Create the setup procedure").Start creating the setup procedure: on the "Project" pane, in the "Generation" group, expand "Setup procedure" and select "Create the setup procedure".
  3. In the wizard, click "2 - Setup" and select "Access the setup options".
  4. Choose "Setup with automatic update (Live Update)".
  5. Select "Setup by HTTP".Select "Setup by HTTP or HTTPS".
  6. Validate the creation of the setup program.
  7. Install the reference version on the server.
When the reference version is updated on the server, the applications of the end users will be updated during their next start.Once the reference version is updated on the server, the applications of the end users will be updated according to the specified update options (during their next startup by default).
To update your application:
  1. Create the executable of the application: click among the quick access buttons.
  2. Start creating the setup procedure: on the "Project" pane, in the "Generation" group, expand "Setup procedure" and select "Create the setup procedure".
  3. In the wizard, click "2 - Setup" and select "Access the setup options".
  4. Choose "Setup with automatic update (Live Update)" and select "Setup by HTTP (on owner server or in the CLOUD)".
  5. Validate the creation of the setup program.
  6. Install the reference version on the server.
Once the reference version is updated on the server, the applications of the end users will be updated according to the specified update options (during their next startup by default).
Notes

Updating the end-user computer

Whenever the application is run, an HTTP request is sent to the server to check whether the reference application was modified since the last update. In case of modification, the application update is automatically proposed to the end user.According to the options for update management (whenever the application is started by default), an HTTP request is sent to the server to check whether the reference application was modified since the last update. In case of modification, the application update is automatically proposed to the end user.

Protocols used

The setup and the updates of the reference application on the server are performed by the FTP protocol.
The setup and the updates of the application on the end-user computers from the reference application are performed:
  • by the HTTP protocol.
  • Versions 17 and later
    by the HTTPS protocol.
    New in version 17
    by the HTTPS protocol.
    by the HTTPS protocol.
The HTTP requests download the files (".tmp", ".net" and ".zip" extensions) from the server. Therefore, these extensions must be accepted by the Web server that hosts the reference application. See https://faq.pcsoft.fr/faqread.awp?idfaq=3102&lang=us for more details.

How to transform a network application into a network application by HTTP

The application must be re-installed on the end-user computer.

Download page

When deploying the application, a htm page is automatically created with a link to the setup file of the client application (link to Install.exe).
This page can be modified and customized according to your own needs.
This page can be moved. To do so, update the download link of the page.

Managing a proxy server

The network setup via IP does not operate if the client computer is found behind a Proxy server.
Versions 17 and later
You have the ability to deploy an HTTP setup on a network that uses a proxy.
The setup and updates of the application on the client computers will automatically use the proxy without having to perform any additional configuration.
New in version 17
You have the ability to deploy an HTTP setup on a network that uses a proxy.
The setup and updates of the application on the client computers will automatically use the proxy without having to perform any additional configuration.
You have the ability to deploy an HTTP setup on a network that uses a proxy.
The setup and updates of the application on the client computers will automatically use the proxy without having to perform any additional configuration.
Minimum required version
  • Version 9
Comments
Click [Add] to post a comment