The XOne Platform provides a tool to make a first installation of the different components in a server.
This installer is an assistant that is going to allow us to pick the components we want to install.

The components we can install with this assistant are:

Starting web for downloading XOneLive or the necessary components for the installation of the application into the devices.
Usually is a web that redirects to one or another folder from the server, according the device from which we are accessing the web.

At the server, the XOneLive is a Web Service that checks the licenses that are registered in the different projects hosted in the server, and monitorizes the updates there are for the different devices in theXOneRepository folders structure.

The devices management tool of the Platform, is a .NET web where we will be able to register, remove, association of users-devices, putting updates, etc…

The installer will ask us if we want to register the MIME type necessaries in the IIS to be able to download the differetn kind of files of the different platforms: apk, ipa, appx, etc…

Also, it will ask us if we want to configure the SMTPparameters in order the XOneManager may notify by email when we register a device, the address to download the app in the device that is defined in the adm_client_installation table, according the platform of the device in question.

Web Service that is called from the development tool XOne Studio for publishing new projects, once we have them tested.

Replica service that can provide service to all the XOne projects that may be hosted in the server.

Service responsible for monitoring at any time the adm_provisioning_task table for generating a database for a device, by filtering the database of the project withthe selectivity criteria there are defined for the user associated with this device.
After the database generation specific for the device, this one is put as an update in the folders structured monitored by the XOneLive, in order the device download it.
The installer checks if there are the necessary DLL to be able to generate an SQLite database and, in case not find them, it installs them.

Service responsible for monitoring if some determined rules are met defined in an XML configuration file to make an associated action.
For instance: Checking if there is any service stopped and starts it again or checking if there are a determined number of operations stuck in any table and that sends an email to check it. What is called a Watchdog.

For the databases, in case they do not exist, the installer proposes create them, for all the databases systems, except for Oracle, since the system cannot create them and its scheme must be previously created.

Together with the web, there is an associated database.
With the installer we will be able to create the necessary tables in this database, as well as inserting some necessary data for its proper initial operation.

Along with the replicator service, we have associated a database that will have all the parameters configuration for the operation of that service.

The installer will create the structure and will register the necessary data for its proper initial operation.
This database known as scratch, is the one that replaces to the parameters previously defined in the configuration file replicator.ini.

The installer also allows us to create the necessary tables structure for starting an XOne project.

It will insert, in the database with the name we indicate it, the replica and the “system” tables necessaries for the proper operation of the different components.
To this database structure is necessary to add later the tables of the application we are developing in order it will be a project fully functional.

For the proper functioning of the different services, the isntaller also allow us to create automaticall the folders structure XOneRepository.
In this structure is where we will find the installations for the different platforms and projects, as well as the updates generated for the devices.

Before starting the installation of the different components, the installer checks a series of previous requirements for its proper operation.

Among these checks and requirements we can find:

1. Internet Information Server
   
2. ASP .NET
   
3. Frameworks .NET
   
4. Existence of the databases
   
5. See components and services previously installed
   

In this screen if any of the pre-requirements are not met, it would indicate us which one is to be able to fix it.

As soon as all of them will be met, we will be able to click into “Continue”.

If the replicator service were not installed, here we can install it by clicking into the “Install” button.

Also, it indicate us that the replicator service will be installed further on:

We will have to specify the port we are going to use for the replica (by default, 7757) and the license of the project we want touse (is included with the installation).
Once these parameter are defined, we can click into “Check” and if everything is filled and ok, the “Continue” button will be enabled.

In this screen we have to specify the values to be able to connect with the “xonemanager” database.

If the “xonemanager” data base does not exist, the installer will propose its creation, just by clicking into a button:


After filling up the values, we have to click into “Check connection” to enable the “Continue” button.

In this screen it will create the database structure with the necessary tables for the replica and the functioning of the different services with an XOne project, subsequently to this structure that the installer generates us, it will be necessary to add to this database the tables of the developed application.

Same than in the previous screen, if the project database did not exist, it will ask us if we want to create it:

After filling the values, we have to click into “Check connection” to enable the “Continue” button.

In this screen we have to specify the values to be able to connect to the “XOneReplicator” database, that will be the database where the configuration parameters from the replica service will be specified.

If the “XOneReplicator” database did not exist, the installer will propose its creation just by clicking into a button:

After filling up the values, we have to click into “Check connection” in order to enable the “Continue” button.

After the creation of the databases, it will ask us for the path where it will create the “XOneRepository” folders structure, which will have the installations and updates of the different projects.

In the last parameter, we have to specify the IP or the external address of the server.

After the creation of the “XOneRepository” folders structure, it will ask us if we want to fill up some extra parameters of the installed components such as the MIME types of the IIS to download apk, ipa, appx files… in the devices, if we want to specify the SMTP parameters for enabling the email sending when we register a device in the XOneManager, etc….


And lastly, the confirmation screens of the Web sites installation:

XOneManager, XOneLive, Start, :XOneProvisioning,:XOneMonitor, XOnePublish, Framework Web.


As soon as all the components have been installed, the installer execution ends.