PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Operating mode of the SaaS model
  • Main menu of SaaS administrator
  • Using the SaaS administrator
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
The dashboard of the SaaS Administrator is used to quickly view the main information regarding the SaaS sites of a WEBDEV Application Server.
It includes the following elements:
  • The management links: these links propose the most common actions.
  • A chart displaying the 5 SaaS sites with the greatest number of assigned licenses.
  • The list of SaaS sites.
Operating mode of the SaaS model
The diagram below presents the six main elements involved in the SaaS model:
Principle of the SaaS model
These elements are:
ElementRole
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.
Main menu of SaaS administrator
The main menu gives access to all the management operations:
  • Dashboard: Back to the summary overview of the saaS sites of WEBDEV Application Server.
  • Sites
    • Add a site: Used to declare a new SaaS site.
    • Manage a site: Used to define the services, the pricing and the parameters of a SaaS site.
  • Customers
    • Add a client account: Used to declare a new SaaS Client Account.
    • Manage a client account: Used to handle the users associated with the client account as well as the Subscriptions.
  • Reports: Used to consult the statistics regarding the use of SaaS sites.
Using the SaaS administrator
To exploit a SaaS site, the following operations must be performed:
  1. Deploying the SaaS site on a WEBDEV Application Server.
    For more details, see: Deploying a site.
    During the deployment, you have the ability to specify the address of the SaaS Webservice that will handle the site.
    The SaaS Webservice can be located on the same application server as the site (by default) or on a different application server.
    The operations for SaaS configuration will be performed thereafter via the SaaS Administrator located on the same application server as the Webservice.
  2. Declaring the site in the SaaS Administrator.
    See Adding a SaaS site into the Administrator for more details.
  3. Declaring the services proposed by the site in the SaaS Administrator.
    See Managing a SaaS site in the administrator for more details.
  4. Creating the pricing for the site in the SaaS Administrator.
    See Managing a SaaS site in the administrator for more details.
  5. Adding the client accounts into the SaaS Administrator.
    See Adding a SaaS client account for more details.
  6. Adding one or more users for the SaaS client accounts.
    See Managing the SaaS client accounts for more details.
  7. Subscribing the SaaS client accounts to the pricing of the SaaS site and assigning some licenses.
    See Managing the SaaS subscriptions for more details.
Versions 22 and later
Note: If you propose to send the security code to the user (forgotten password), you must configure the SMTP email serveur associated with the SaaS administrator. This configuration can be performed:
  • by programming, via SaaSAdminConfigureSMTP.
  • in the SaaS administrator, via the "SMTP configuration" link found in the dashboard.
New in version 22
Note: If you propose to send the security code to the user (forgotten password), you must configure the SMTP email serveur associated with the SaaS administrator. This configuration can be performed:
  • by programming, via SaaSAdminConfigureSMTP.
  • in the SaaS administrator, via the "SMTP configuration" link found in the dashboard.
Note: If you propose to send the security code to the user (forgotten password), you must configure the SMTP email serveur associated with the SaaS administrator. This configuration can be performed:
  • by programming, via SaaSAdminConfigureSMTP.
  • in the SaaS administrator, via the "SMTP configuration" link found in the dashboard.
Minimum required version
  • Version 15
Comments
Click [Add] to post a comment