Over the years, the platform is evolving and incorporating new features while still maintaining compatibility with facilities that are already in production.

In every project, there comes a time when you have to consider the fact of “catching up”. On this page we will try to resolve any doubts that may arise when updating the different components of the platform.

With the new functionalities that have been added, new tables and fields have to be created both in the BD of the xonemanager and in the DB of a project.

In order to know the structure of tables and fields that there are now in these two Databases, we have two .DB files in the xonesupport website with the updated structure of the tables of these two databases, so that we can compare with the xonestudio the structure of tables of the downloaded file with the structure of the Databases that we have in production and we can know the changes that we have to make in our project to update to the latest version.

1.- We open the xonestudio and we go to the option Database-DB Tools	2.- In Source, we select the DB that we have download from the xonesupport

3.- After clicking the Wizard button in the previous screeen, we have an assistant to achieve a connection string to the SQLite file .	4.- After clicking Next, we select that we want to compare the source database (SQLite) with the destination one (DB of our project).

5.- After clicking Next, we have to select the DB of our project.	6.- After clicking the Wizard button in the previous screeen, we have an assistant to achieve a connection string to the database of our project.

7.- After clicking Start, it will come up the results of the comparative between the two databases in the form of SQL query, in such way that if we want, we can launch these queries in the destination DB (Our Project), in order to create the missing new tables-fields.

By last, after creating the new tables-fields in the DB of our project, we will repeat this process with the DB of the xonemanager.

1. The XOnemanager is a web interface made with .Net framework 4, if it is not installed it would be installed with all its Service Packs.
   (NOTICE, there are servers where the .NET 4 can be added as a feature and it is installed by itself. We ignore what Microsoft has included or not in this version, but we have find some situations in which after installing this way, IT DOESN´T WORK, better downloading the .NET Framework 4 from the Microsoft download page.)
2. We make a backup of the current xonemanager folder, which we will rename or copy in another location.
3. We download the latest version of the xonemanager from the xonesupport page.
4. We download the latest structures of tables of the project Database and from the xonemanager there is in the xonesupport page to be able to know the new fields or tables we have to create in our project for the correct operation of the new version.
   (See how to compare the structure of the .db files we download from the xonesupport with the DB of our project in the first section of this page. )
5. We create the new fields or tables in our project´s DB and in the DB of the xonemanager, according the comparison of the previous step.
6. We edit the WEB.CONFIG file from the new xonemanager with the values we had configured in the formerWEB.CONFIG we had working.
   DO NOT CRUSH THE NEW CONFIG WITH THE OLD ONE!!!.
7. In the IIS configuration we make sure that the xonemanager uses the Framework .Net 4.0.

1. The xoneprovisioning services makes use of the Framework .NET 4, if it is not installed, just install it with all its Service Pack from the Microsoft download web.
2. We stop the :xoneprovisioning service.
3. We create a backup of the current service folder.
4. We download the latest version of the xoneprovisioningfrom the xonesupport web.
5. We replace the old folder with the new version and we EDIT the new Provisioning.Config file with the configuration parameters we had operating in the old one. DO NOT CRUSH THE NEW CONFIGURATION FILE WITH THE OLD ONE!!!
6. We start again the service.

1. The Interface, Interclient ​or Integration, is programed with .Net 4.0, if it is not installed, just downlad it and install it with its Service Pack from the Microsoft download page.
2. Stopping the current Service.
3. Making a backup of the current folder.
4. Downloading the latest version of the interface of the xonesupport web.
5. Copying the configuration files of the different interfaces we had operating in the new folder.
6. Starting again the new Service.

Notice:If it is migrating from the previous visual basic version to .Net, just keeping in mind that in the configuration section of the connections to BD, the node changed its name by “connection”.

1. The replica server is programed with .Net 4.0, if it is not installed, just downlad it and install it with its Service Pack from the Microsoft download page.
2. Stopping the current service.
3. Making a backup of the current replicator folder, as well as the files from which the replicator depends on.
4. Requesting a compilation of the latest version of the Replicator Server for the project in question to CGSOFT.
5. Replacing the old files with the new ones.
6. Starting the new Service.

Notice: It is advisable to make periodic backups of the files from which the replicator depends on.

Component Serverr

1. The xonelive in the server, is a webservice.
2. We make backup of the current xonelive folder, that we will rename or copy in another location.
3. We download the latest version of the :xonelive from the xonesupport page.
4. We edit the WEB.CONFIG file of the new xonelive with the values we had configured in the WEB.CONFIG we had operating.
   DO NOT CRUSH THE NEW CONFIG WITH THE OLD ONE!!!.

Component Client

The xonelive client in Android may generate the latest version in the web of the xonesupport for an specifi project. By sending to the device a download link, in the device will appear a message to replace the version we had installed already.

From the 3.4.x verdion of the xonelive, if the user cancels the installation of the new xonelive when this one is sent in update way for the devices (by executing the .apk after the download), this one still keeps trying to update the next time the pending updates will be checked.

In the rest of the devices (IOS, Blackberry, Windows Phone, Windows 8…) the xonelive is integrated with the Framework, in such way that it will be necessary to generate a new installation.

In Android we can download the latest version of the xonesupport framework. We will put the new Framework in the corresponding folder on the server's START web. By sending to the device a link with the download or just opening again a browser pointing out to the START web to download again the framework, in the device will appear a message to replace the version already installed by the new one. .

From the 3.4.x version of the xonelive, if the user cancels the installation of the new Framework when this one is sent in updates way for the devices (executing the .apk after the download), this one still keeps trying to update the next time the pending updates will be checked.
In the rest of the devices (IOS, Blackberry, Windows Phone, Windows 8…), it will be necessary to generate a new installation.