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.
Before making any kind of update we have to make a back up of the component that is currently working.
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.
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”.
Notice: It is advisable to make periodic backups of the files from which the replicator depends on.
In the WINDOWS folder:
Component Serverr
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.