Updating IBM Architecture Room LIVE!

To update an existing IBM Architecture Room LIVE! installation to the latest version, perform the following steps:

Procedure

Note: When you plan to install in a new location or overwriting an existing version, ensure that you take a copy of the <live-install-folder>\DR_Install\dr-config.json file, lib_server\config folder that contains the license keys and the certificates, and <live-install-folder>\user_config.js file, so that you can reuse the configuration in the new installation.

  1. Extract the file IBM_Architecture_Room_LIVE_<version>_setup.zip to an empty folder <live-install-folder>. For example, the name of the ZIP file might be IBM_Architecture_Room_LIVE_V9.7_setup.zip.
    Note:
    • 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.
  2. If you want to delete the old installation folder, you need to perform this step to ensure that there is no process running, which can prevent the folder from being deleted.
    1. Open an administrative command shell and run the following command:
      pm2 kill
      Note: Sometimes, running the pm2 kill command stops the Mongo database.
    2. If you find Mongo server still running after the previous step, then enter the Mongo shell by running the following command: <mongo-install>\bin\mongo, where <mongo-install> is specified either by mongo-win-install-folder or mongo-linux-install-folder in the file <live-install-folder>\DR_Install\dr-config.json.
    3. Run the following commands in the Mongo shell for stopping the Mongo database:
      use admin 
      db.shutdownServer()
    4. Ensure that the version of Node JS is the same in the new version of the application that you are updating to. Go to a command prompt and run the following command:
      node --version

      Compare the output of this command with the version of Node JS that is in the new installation. On Windows, the Node JS installer is located in <live-install-folder>\server-sw\win32_x86_x64\, and on Linux, it is located in <dr-install-folder>/server-sw/linux_x86_x64/. If the version is not the same, you should uninstall Node JS (using the normal procedure for uninstalling installed programs) and then install the new Node JS version.

    5. Copy the following files from the old installation or from the backup location to the new installation folder:
      • dr-config.json file from the old installation (<live-install-folder>\DR_Install\) to the new installation (<live-install-folder-new>\DR_Install\)
      • config folder from (<live-install-folder>\lib_server\) to (<live-install-folder-new>\lib_server\)
      • user_config.js file from (<live-install-folder>\) to (<live-install-folder-new>\)
    6. Open an administrative command shell and navigate to cd <live-install-folder>\DR_Install\, and run the following command:
      node deploy-dr.js
    7. You can delete the old install folder (<live-install-folder>) at this point.

    The deployment script first stops the currently running IBM Architecture Room LIVE! web server. However, it does not stop the PM2 daemon process or the Mongo database. That is the reason you need to perform step 2 if you want to avoid lingering processes that prevent the old installation folder from being deleted.

    The deployment script then starts the new version of the server. The version of Node JS, Mongo, and PM2 remains the same.