Introduction

A vertical provisioner has been created as a solution for managing the different verticals available, each with its own applications, from a single Onesait Platform installation.

Furthermore, the aim is to take advantage of the economy of scale in the installation of different verticals, allowing a single application to be installed in each vertical that needs it and exploit it with its own data through a Bundle Marketplace. Its operation is based on the multi-tenant capabilities of the Platform.

Technically speaking, each vertical of the provisioner is a vertical and a tenant of the Platform, so that both the applications installed in each vertical and the data that these applications exploit are isolated.

The main characteristics of the vertical provisioner are explained below.

Provisioning Features

Global User Management

All users of the verticals must be registered in Onesait Platform, as the security of both the vertical provisioner and the applications of each vertical will be provided by the Platform's own Identity Manager module.

A user with an administrator role will be able to import users from the Platform and manage them from the user administration manager. The administrator can indicate whether they are going to be administrative users, who will be able to use the provisioner (for example, the managers of the vertical who will be able to enter to manage it), or if on the contrary, they are users of the vertical who will have access roles to the applications installed in the vertical, but not to the provisioner.

Open

Open

Verticals Management

The management of verticals offers a first view in the form of a list with the verticals registered. The following example shows a set of municipalities, each municipality being a vertical with its own applications and data.

Vertical registration

To create a new vertical, you must first provision the vertical's databases and create the tenant in Onesait Platform. Information on this can be found in the following guide:

Once the databases are available, the vertical can be created from the supplier. To do this, click on the New Vertical button to access the wizard for creating verticals, where the following information must be indicated:

• Name and description of the vertical.

• Name of the vertical and Tenant created in Onesait Platform: together with the token of the vertical’s Administrator User, which will be used to create different concepts.

• Import of the users that have to register in the Vertical: either because they will be administrators of the vertical in the provisioner, or because they will be users of the Applications that will be installed.

• Classification of users into application users and technical administrators.

Once this wizard is completed, click on the «Create Vertical» button and all users will be imported into the corresponding vertical of the Platform.

Registration of Applications 

Once a vertical has been created, it is possible to access its detail view from which you can consult everything related to the vertical, as well as see the list of Applications installed in it and register new Applications; this is the registration of an Application in the corresponding Onesait Platform vertical, using precisely the Application concept.

You will be able to install a new Application through the Application registration wizard by completing the following steps:

• Name and description of the Application.

• Security domain (Platform Realm), with Application roles.

• GIT configuration, where the project created to support the Application will be backed up.

• Mapping of security domain roles to users.

• Bundles to be installed from the Platform Marketplace.

• Each Bundle will be associated with the roles that have access.

Vertical en Onesait Platform 

La gestión de un vertical en el provisionador se materializa sobre el vertical correspondiente en la instalación de Onesait Platform mediante:

• Registration of users in the vertical.

• Creation of Applications, where for each Application is carried out:

  • Creation of application user.

  • Registration of security domain (Realm).

  • Association of users to the security domain.

  • Installation of Bundles.

  • Analysis of Bundles to extract their access url and integrate them in the web project of the application.

  • Creation of Web Project from template.

  • Creation of the Web project configuration (menu, security, navigation).

  • Versioning of the Web project in GIT.

  • Deployment of the Web project.

  • Association of all the elements created to the application.

Deployed Application 

For end-users, everything materialises in the Web Applications published in the vertical, to which they have access according to their assigned role.