AYUDA EN LÍNEA
 WINDEVWEBDEV Y WINDEV MOBILE

Este contenido se ha traducido automáticamente.  Haga clic aquí  para ver la versión en inglés.
Ayuda / Administrador SaaS
  • Overview
  • How to?
WINDEV
WindowsLinuxJavaReportes y ConsultasCódigo de Usuario (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Código Navegador
WINDEV Mobile
AndroidWidget Android iPhone/iPadIOS WidgetApple WatchMac Catalyst
Otros
Procedimientos almacenados
Overview
Adding a SaaS site is used to declare a SaaS site deployed on a WEBDEV Application Server to a SaaS web service 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 using the SaaSAdminAddSite function.
How to?
To add a SaaS site, from the SaaS Administrator's main menu, select the "Sites .. Add a site" option.
Reminder: The SaaS Administrator is located on the Application Server hosting the SaaS web service 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 supplied during the site deployment procedure in the installation wizard.
By default, it is the name of the project.
Note: This parameter is case sensitive.
Management mode of dataSeveral options are available:
Data management modeBenefitsDrawbacks
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).
  • Simplified database maintenance: only one backup to be made, only one automatic modification in the event of changes in site analysis.
  • 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 security against information leakage: each customer account can only access its own database. When using HFSQL in Client/Server mode, this security is increased by the creation of an 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 the case of an HFSQL Client/Server database: HFSQL server connection parameters and the name of the reference database (optional) that will be duplicated to create each customer account database.
  • in the case of an HFSQL Classic database: the directory name of the reference data files.
    Note: the data directories of the various customer accounts are located on the Application Server hosting the site, in the data directory of the WEBDEV account owning the site.
Versión mínima requerida
  • Versión 15
Comentarios
Haga clic en [Agregar] para publicar un comentario

Última modificación: 11/01/2025

Señalar un error o enviar una sugerencia | Ayuda local