|
|
|
|
|
|
|
|
|
|
- Overview
- 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
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 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: - check that the user has an account,
- 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: 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: These elements are: | | | Element | Role |
|---|
| SaaS site | The SaaS site is a WEBDEV site deployed on a WEBDEV Application Server. It is associated with a SaaS web service used to control the site. | | Service | The Services are the different features of a site. | | Client Account | A 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.). | | User | The Users are the members of the company represented by the Client Account.
The users are the physical persons who are using the SaaS site. | | Pricing | A 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. | | Subscription | A 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 web service 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 SaaS site management webservice will be used via its web alias (e.g. WDSAAS300_WEB), which must correspond to the directory of the same name in the Application Server installation (default: C:\WEBDEV30\WDSaaS\WDSaaS300\WDSAAS300_WEB). The method for developing a SaaS site is the same as the method for developing any other WEBDEV website. For more details, see Developing a SaaS site. When SaaS is enabled for a site, the deployment requires the following additional parameters: - Choice of Webservice associated with site: it is possible to use the Webservice located on the same Application Server as the one hosting the site (this is the most frequent case) or a Webservice located on another WEBDEV Application Server (when several SaaS sites share a Webservice).
- The name and password of the administrator of the SaaS web service. This information is required to perform some deployment steps (automatic modification of HFSQL data files for example).
Remarks: - In some cases, the site developer may not know the username and password of the administrator of the SaaS web service. In this case, you can use the setup by physical media or the installation packages and ask a person with sufficient rights to perform the setup.
- If the address of the SaaS web service was not specified during the deployment, the alias of the SaaS web service (WDSAAS300_WEB) must exist on the same virtual server as the SaaS site.
- If the address of the SaaS web service was specified during the deployment, the site manager must check whether the alias of the web service is actually available at the specified location.
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:
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|