- Default PC SOFT update server
- Custom update server
In french: HGèreMiseAJourServeur
Allows you to manage the automatic update of HFSQL Client/Server servers by specifying the check frequency regarding the availability of updates. If an update is available, the HFSQL server is automatically updated.
Remark: Two rights are required to use this function:
- The rights to manage the server.
- The rights to stop the server.
These rights correspond respectively to the hRightsManageServer
constants used in HInfoServerRights
MyConnection is Connection
MyScheduling is hScheduling
// Enables the server update according to a specific scheduling
(<Former Scheduling>, <Former URL>) = HManageServerUpdate(<Connection> [, <Scheduling> [, <URL>]])
<Former Scheduling>: hScheduling variable
hScheduling variable containing the characteristics of the previous scheduling.
<Former URL>: Character string
Former URL for downloading the server update.
<Connection>: Character string or Connection variable
Connection to a database. This connection corresponds to:
<Scheduling>: Optional hScheduling variable
Name of the hScheduling variable corresponding to the options for scheduling the server update.
<URL>: Optional character string
- URL to the custom update server. For more details, see Custom update server.
- Empty string (default value) to use the official update server of PC SOFT.
Default PC SOFT update server
Fore each update, PC SOFT proposes packs allowing you to automatically update the HFSQL server in production (for the version currently used).
These packs have been thoroughly checked by our services.
Custom update server
You can use a custom update server for the HFSQL server. This allows you to control the HFSQL server updates of the users. You can for example validate the use of a new version before releasing it.
To create a custom update server for HFSQL servers, you must:
- Install a Web server (IIS or Apache) on the selected computer.
- Create the following MIME types on the Web server if they do not exist:
- .json -> application/json
- .sign -> application/byte-stream
- .zip -> application/x-compress
- Create a directory at the root of the Web server. This directory will contain the update packs. Example: C:\inetpub\wwwroot\hfsql_packs
This directory must contain:
These packs and their signatures are available from the following address: http://package.windev.com/hfsql/.
- A json file containing the names of the packs to be used according to the versions (see below). The name of this file must be "hfsql_updateinfo.json".
- The packs corresponding to the updates (packs in zip format with ".zip" extension).
- The signature files corresponding to the packs (".sign" extension).
- Web server for updates: srvupd
- UNC directory containing the updates: \\srvupd\hfsql_packs\
- URL for updates: http://srvupd/hfsql_packs/
Example of Json file:
"language" : "F",
"version" : "220099",
"min_version" : "220036",
"data" : "srv_hfsql_win32_90F220099z"
"data" : "srv_hfsql_win64_90F220099z"
"data" : "srv_hfsql_linux32_90F220099z"
"data" : "srv_hfsql_linux64_90F220099z"
- major_version: corresponds to the major version of the pack (22, 23, ...). Only the HFSQL servers corresponding to this version will be updated.
- language: corresponds to the server language (F for French, A for English, ...).
- version: corresponds to the version of the HFSQL server found in the pack.
- min_version: corresponds to the minimum version from which the pack can be applied.
- pack: used to give the characteristics of the packs.
- platform: platform corresponding to the pack:
- win32: 32-bit Windows
- win64: 64-bit Windows
- linux32: 32-bit Linux
- linux64: 64-bit Linux
- data: corresponds to the name of the pack (without extension).
Remark: A single pack may be referenced according to the platform used by the HFSQL servers.
This page is also available for…