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

When you want to upgrade from Live! 2019.04.x and earlier builds to 2019.07 or later builds, you must ensure that the user and whiteboard data from the older version is migrated to the latest version.
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.

Procedure

  1. Download the IBM_Architecture_Room_LIVE_<version>_setup.zip file.
  2. Extract the file to an empty folder <new-live-install-folder>. For example, the name of the ZIP file might be IBM_Architecture_Room_LIVE_V9.7_setup.zip.
    Notes:
    • The built-in “Extract All…” utility in Windows has a limitation on the length of the path names of the extracted files. You can reduce the risk of running into this limitation by extracting the compressed file into a folder where the full path name is short. If this doesn’t help, use a better extraction utility, such as 7-zip.
    • Make sure to extract the files into an empty folder. Do not overwrite an existing IBM Architecture Room LIVE! installation, especially when the application is running.
    • Since this is an update to an existing IBM Architecture Room LIVE! installation, Node JS from the previous installation must be available. If not, perform step 2 in the Installation on Windows with internet access to install Node JS.
  3. Copy the drlive.crt and drlive.key files from <old-live-install-folder>\lib_server\config folder to the following folders:
    • <new-live-install-folder>\liveAuthServer\libsever\Config\
    • <new-live-install-folder>\liveHomeServer\libsever\Config\
    • <new-live-install-folder>\liveRoomServer\libsever\Config\
  4. Review the <old-live-install-folder>\user_config.js file and update the <new-live-install-folder>\liveHomeServer\user_config.js as required.
  5. Goto the command prompt and run the following command as an administrator:
    node deploy-dr.js
    The new instance of Live! server is started.
  6. Goto a web browser and type the following URL to start the application: https://<hostname>/home.html, where <hostname> is the name or IP address of the Live! home server.
  7. Browse to the location of the exported data of the old Live! instance and select the folder that you want to import at <old-install folder>\ExportImportScripts\data\<tagname.zip>, where <tagname.zip> is the file that you want to import. Extract the <tagname.zip> file.
  8. Copy the content of the <tagname.zip> file and paste it into the new Live! instance at <new-live-install-folder>\liveRoomServer\ExportImportScripts\data\home.
  9. Log in as a home administrator.
  10. To import the user data from the old Live! instance, goto the administration menu in the Home dashboard, and import the <tagname.zip> folder. For more information about how to import, see Importing groups and users.
  11. To import the whiteboards and whiteboard templates from the old Live! instance into a specific room, click the room link or log in to the room as an administrator.
  12. In the Room page, import the <tagname.zip> where <tagname> is the exported folder, to import the whiteboards and whiteboard templates data. For more information about how to import whiteboard data into rooms, see Importing whiteboards.

    After the users and whiteboards are imported into the new Live! instance, you can compare the new user data on the Home dashboard and the new whiteboards data in the Rooms dashboard data with the old Live! instances.