|
|
|
|
|
|
|
|
|
|
- Overview
- How to?
- Creating a multisite setup
- To install the reference version
- Remarks
- Protocols used
- Download page
The two-level setup (or multisite setup) combines:- a reference network setup deployed on a local network.
- an HTTP setup used to update the reference setup on the local network.
The setup is performed in 3 steps: - Download (via an HTTP server) a reference setup on a local server. During a first setup, the end user starts the setup by Internet, via a specific page.
- Install this reference setup on a local server. The reference application is the program used to install the application on user workstations..
At the end of this setup, a scheduled task is created on the local server. This scheduled task is used to check and update (every 15 minutes) the version of the reference setup according to the version of the HTTP setup. - The final application is installed on each user computer by running the setup program found on the server. The updates will be automatically performed when the reference application changes on the server
When starting the application, an automatic update will be performed (according to the version of the application installed on the user computer) Creating a multisite setup To create a multisite setup: - Create the application executable (
 in the quick access icons). - Start creating the setup procedure:
- among the quick access icons.
- Select "Create the setup procedure of the executable".
- In the wizard, select "Setup".
- Choose "Setup with automatic update (Live Update)".
- Choose "Multisite setup".
- Choose whether to create a deployment package or deploy immediately to a PCS Cloud platform.
- Follow the different steps of the wizard.
To install the reference version 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. - Start the setup program that was created beforehand.
- Choose the destination server on which the reference setup will be installed:
- Current computer ("Deploy the setup on this computer" option). 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 to 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 reference application are installed in the specified directory.
- Hosting provider for a remote deployment ("Deploy the setup at a hosting provider" option).
In this case, an FTP connection must be used to send the elements to the server. - Enter the URL of your site with the hosting provider: this information corresponds to the address that users will need to enter to access the installation page for your application.. The setup of the reference application will be found at this URL.
- Enter the characteristics of the FTP server that will be used to install the reference application on the HTTP server.
- PC SOFT Cloud ("Deploy the setup in the PC SOFT Cloud" option).
In this case, you must:
- Type the parameters of your PC SOFT Cloud account.
- Select the platform on which the application should be deployed.
Remarks: - 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.
3. Validate the setup of the reference version. At the end of this setup, a scheduled task is created on the computer. This scheduled task is used to check and update (every 15 minutes) the version of the reference setup according to the version of the HTTP setup. The name of the created scheduled task is specified on the last setup plane. This name is in the form: MAJ_<NomApplication>_<identifiant>. Example: UPD_WDGoldLite_2169562193. 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. 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 is hosting the reference application. For more details, see FAQ #3102. Download page When the application is deployed, a htm page is automatically created with a link to the client application installation file (link to the Installe.exe file). You can take this page and customize it to suit your needs. This page can be moved. To do so, update the download link of the page. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|