Migrating Live! 2019.04.x and earlier builds to the latest build
Live! was providing a single-room modeling capability in each installation until the 2019.04.x builds. If someone wanted to organize and maintain different projects, they had to install multiple instances of Live! for each project and had to download and move the data between the different projects manually. This was a very tedious process and error-prone. To overcome the problems and to support various projects in a single instance, the latest versions of Live! comes with multiple projects support that allows you to maintain multiple projects in different rooms. The multiple-projects support enables the administrator to manage and migrate users and whiteboards data easily across projects.
Before you begin
Note: This topic is intended for the Home and Room administrators who have the access to
export and import data across Live! rooms.
Since Live! server runs on port 443 by default, you
might end up having both the new and old versions of the product running on the same port, unless
you changed them in both or in one of the versions. If both versions of the product run on the same
port, you will lose the old instance of Live! That way you will not be able to compare and verify
data of the new instance with the old data if want to. Hence for verification purposes, or if you
want to retain both instances, you must ensure that you change the default authorization and audio
server ports in either the old or new instance or both.Important: If both the old and
new instances of Live! are run on the same port (for example, port 443), the data on the old
instance will be lost as it will be overwritten with the data of the new instance.
About this task
Remember:
- If the administrator decides to retain the old version of Live! for comparing data and decides to modify its default server port, then ensure that the old instance of Live! is restarted after the port is changed.
- The administrator in the old instance of Live! must export the data of users and whiteboards before starting with the migration procedure.
- The administrator must also take a copy of the <old-live-install-folder>\DR_Install\dr-config.json file, <old-live-install-folder>\lib_server\config folders that contains the license keys and the certificates, and the <old-live-install-folder>\user_config.js file, so that the configuration information can be reused in the new installation.