Help / Developing an application or website / WEBDEV specific features / SaaS
  • Overview
  • SaaS
  • Operating mode
  • Operating mode and use of a SaaS site from the point of view of the user
  • Prerequisites
  • Developing a SaaS site
  • Deploying a SaaS site
  • Managing a SaaS site
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures


WEBDEV allows you to easily create, host and manage SaaS sites, and to convert the existing sites to this distribution mode.
In the SaaS model, the application is accessible remotely via an Internet browser. The user does not have to install or maintain anything locally, ...
In most cases, these applications are invoiced by subscription (according to the number of users and by month for example) but several other invoicing methods can be used (according to the resources used, to the space occupied by the data, ...).
Operating mode

Operating mode and use of a SaaS site from the point of view of the user

A SaaS site can be used by several client companies.
Each company has its own list of users and each company accesses its own data.
To access the SaaS site, each user must be authenticated (via a login and password). You can:
  • to check that the user has an account indeed,
  • check whether the user has purchased a license allowing him to access to the entire site or part of the site,
  • check whether this license is still valid,
  • present data corresponding to the company of the user.
The diagram below presents the use of a SaaS site by two distinct companies:
Using a SaaS site
The "SaaS Supplier" company proposes a site in SaaS mode. This site is used by two client companies ("Company A" and "Company B"), each one owning:
  • A specific database,
  • Different graphic styles,
  • A different database of user accounts.
Therefore, each company can be invoiced according to its use of the Web site.
Operating mode and use of a SaaS site from the point of view of the site administrator
The diagram below presents the six main elements involved in the SaaS model:
Principle of the SaaS model
These elements are:
SaaS siteThe SaaS site is a WEBDEV site deployed on a WEBDEV Application Server. It is associated with a SaaS Webservice used to control the site.
ServiceThe Services are the different features of a site.
Client AccountA Client Account represents a company that uses the SaaS site.
Each Client Account includes its own database and its own custom version of the SaaS site (logo, graphics, etc.).
UserThe Users are the members of the company represented by the Client Account.
The users are the physical persons who are using the SaaS site.
PricingA Pricing represents a set of Services accessible by a User.
A Pricing can include one or more Services.
A Service can be proposed in one or more Pricing.
SubscriptionA Subscription represents the availability of a number of licenses for a Pricing (and therefore of the associated Services) for a User Account.
Then, these licenses must be be distributed among the Users.
The Subscriptions are used to monitor the use of the SaaS site and the invoicing.
To deploy and manage a SaaS site, the following elements are required:
  • A WEBDEV Application Server,
  • The Webservice for managing the SaaS sites,
  • The management site of SaaS sites.
The last two elements must be selected when installing the WEBDEV Application Server.
The Webservice for managing SaaS sites will be used via its Web alias (WDSAAS290_WEB for example) that must correspond to the directory of same name in the setup of the Application Server (by default: C:\WEBDEV29\WDSaaS\WDSaaS290\WDSAAS290_WEB).
Developing a SaaS site
The method for developing a SaaS site is the same as the method for developing any other WEBDEV site. For more details, see Developing a SaaS site.
Deploying a SaaS site
When SaaS is enabled for a site, the deployment requires the following additional parameters:
  • Choosing the Webservice associated with the site: you have the ability to use the Webservice found on the same Application Server as the one that is hosting the site (most common case) or a Webservice found on another WEBDEV Application Server (when several SaaS sites share a Webservice).
  • The name and password of the administrator of the SaaS Webservice. This information is required to perform some deployment steps (automatic modification of HFSQL data files for example).
  • In some cases, the site developer may not know the username and password of the administrator of the SaaS Webservice. In this case, you can use the setup by physical media or the setup packages and ask a person with sufficient rights to perform the setup.
  • If the address of the SaaS Webservice was not specified during the deployment, the alias of the SaaS Webservice (WDSAAS290_WEB) must exist on the same virtual server as the SaaS site.
  • If the address of the SaaS Webservice was specified during the deployment, the site manager must check whether the alias of the Webservice is actually available at the specified location.
Managing a SaaS site
Once it is deployed, a SaaS site must be configured before it can be used. The following operations must be performed:
All these operations (as well as the access to the logs regarding the use of the site for invoicing purposes) can be done by using the SaaS Administrator. For more details, see SaaS administrator.
Related Examples:
WW_SAASClientSite Training (WEBDEV): WW_SAASClientSite
[ + ] The "WW_SAASClientSite" example is an example for using the SAAS management functions of WEBDEV.

This example is presented like a site for selling SAAS solutions.
To use this example, a SAAS site must be configured as defined in the initialization code of the project.
The Web user can subscribe to a given pricing of a SaaS site without having the call the administrator of the SaaS server.
Minimum version required
  • Version 15
Click [Add] to post a comment

Last update: 06/22/2023

Send a report | Local help