PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
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
Adding a SaaS site is used to declare a SaaS site deployed on a WEBDEV Application Server to a SaaS Webservice in order to allow it to be used.
This operation must be performed after the deployment of the site.
Note: This operation is equivalent to the call to SaaSAdminAddSite.
Note: From version 19, HFSQL is the new name of HyperFileSQL.
How to proceed?
To add a SaaS site, from the SaaS Administrator's main menu, select the "Sites .. Add a site" option.
Reminder: The SaaS administrator is found on the Application Server hosting the SaaS Webservice that controls the site.
The following elements are requested:
ElementRole
Name of the siteThis is the deployment name of the WEBDEV site.
This name was given during the procedure for deploying the site in the setup wizard.
By default, it is the name of the project.
Note: This parameter is case sensitive.
Management mode of dataSeveral choices are available:
Management mode of dataBenefitsDrawbacks
No database
A single database shared by all the client accounts
  • Ability to share elements among the different clients (if the site uses large memos, they do not have to be copied for each client).
  • Easier maintenance of the database: a single backup to perform, a single automatic modification if the site analysis evolves.
  • Risk of information leak among the different client accounts in case of bugs in the site.
  • Unable to provide a backup of its database to a client without providing the entire data.
A database per client account
  • High level of security against data leaks: each client account can only access its own database. When using HFSQL in Client/Server mode, this security is increased by the creation of a HFSQL account for each SaaS client account.
  • Ability to save the database of each client separately and to provide the backups.
  • The maintenance of a client database does not affect the other ones.
  • The programming is simplified because there is no need to differentiate between the records of the different clients in the database.
  • Unable to access the data of a client account from another site
Parameters for accessing the dataDepending on the selected management mode of data, you must specify:
  • in case of a HFSQL Client/Server database: the parameters for connecting to the HFSQL server as well as the name of the reference database (optional) that will be duplicated to create each database of client accounts.
  • in case of a HFSQL Classic database: the name of the directory of the reference data files.
    Note: the data directories of the different client accounts are found on the Application Server that is hosting the site, in the data directory of the WEBDEV account that owns the site.
Minimum required version
  • Version 15
Comments
Click [Add] to post a comment