Transfer Server (Classic/Evo) installation from one machine to another

This article provides information on how to move the Server installation from one machine to another.  

The document uses several terms like <user home> / App data - terms for which you may need a system administrator to help you to find or give you permission to access (see the end of this article for more information as to where to find them).

Warning: We strongly recommend that you set up your new Server machine first, and make sure everything is working as expected before you delete Omniscope from the existing machine. Visokio is happy to provide a temporary key to help with migration, contact support[at]visokio.com for more information.

NOTE: This document is valid for both Omniscope Classic and Omniscope Evo installations.

Step 1: Install Omniscope

Install Omniscope (Classic/Evo) onto the new machine and make sure the license is activated. Visokio would be happy to provide a temporary key for the transition.

Step 2: Moving files to the new location

This step involves moving all the required files from your current installed machine to the new machine.

You need to move the following files to the new machine in the appropriate folders e.g. when moving “Omnicope-server” folder you would need to move it to the correct user home folder.

List of files/configurations you need to move:

1. "omniscope-server" folder, in the user home directory; it contains your Files folder with all projects. This folder also contains the config.xml with app settings and top level permissions, which would be copied once you move the entire folder.
   
   NOTE: You may need to adjust the paths in the config.xml and folder.xml, if necessary, by editing them manually using a text editor.

              (before moving make a copy of the existing omniscope-server folder in case something goes wrong).

2. <INSTALLATION_LOCATION>/installconfig.properties (Windows)

           <INSTALLATION_LOCATION>/_launch.sh (Linux) 

If you have not customised this, or if porting between platforms, skip this file. 

            (before moving make a copy of the existing omniscope-server folder in case something goes wrong). 

3. This step only applies to Omniscope Evo installations
   
   <APP_DATA_VISOKIO>/Omniscope/LocalStorageRegistry.xml

           <APP_DATA_VISOKIO>/Omniscope/diskManagerSettings.xml

           <APP_DATA_VISOKIO>/Omniscope/MonetDb/ (maybe customised in diskManagerSettings.xml)

           (before moving make a copy of the existing omniscope-server folder in case something goes wrong).

Step 3: update configuration

If the new server has identical installation, user account, sharing folder (etc.) folder paths, you have nothing to do here. Otherwise you should edit the server configuration to correct any paths. 

For example, if running a production web server with HTTPS certificate, you may need to transfer and update the path of the keystore.jks file. Typically this can be done either by editing config.xml manually or in the Admin UI after starting the server.

For example, if you have a project with an (e.g.) File or Database block accessing some external resource, you may need to reconfigure the project with the correct path or host name (as appropriate) to reach the same resource.

Step 4: New Server testing

This step involves testing to make sure everything is working on the new server, before the changeover. Some of the tasks you should check: 

1. Check the paths in the installconfig.properties/_launch.sh, config.xml, LocalStorageRegistry.xml (Evo only), diskManagerSettings.xml (Evo only) are all valid.

           
            You will need to reconfigure your JDBC drivers again on the new machine through Admin Web App and

            re-apply any Advanced settings you may have set manually outside of Omniscope.

2. Check Admin Web App by checking logs, after you've started the application.
   
   

3. Test opening files and folders with configured Omniscope Server permissions to make sure they are accessible

We advise doing a test run before decommissioning your old machine, lasting one day or more, until you are satisfied everything is working correctly. 

Please contact Visokio Support if you need further assistance.

Technical terms explained and their location

<USER_HOME>

This is user home directory of the user who has activated Omniscope. These are typically the following:

<INSTALLATION_LOCATION>

These are typical locations of where Omniscope has been installed.

<APP_DATA_VISOKIO>

This is location Omniscope uses to store user-specific settings, and is also a standard practice in Operating system to store user specific settings.

NOTE: This location may be customised, depending on the changes in installconfig.properties (Windows / Mac OSX) or _launch.sh on Linux.