Relocating Apache Tomcat to a different server
[Image: jOXYNk0M5BfBDT-O13S0qHGRXBR7gXlwjAbtNs2j...fMgJCddWqC]Relocating Apache Tomcat to a different server

Download guide here:
.pdf   Relocating Apache Tomcat to a different server.pdf (Size: 79.59 KB / Downloads: 13)

Overview
  •  The browser scheduler is hosted by your Apache Tomcat installation.  Tomcat is not just contained in a folder that exists on the server, it is also configured as a service.  This means if you are changing the server Tomcat is hosted on, you need to remove the current installation on the old server and perform a fresh install on the new server.

Steps
  • On the original server that you are retiring as the Tomcat host, ensure the Tomcat service has been stopped.
  • You may delete the entire Apache Tomcat folder and remove it as a service. You may also delete the Synoptix client from this server if you like.  Please note that the Apache Tomcat service points to a local installation of the Synoptix client in order to run, so you will need an installation of the Synoptix client on the new server.  You do not need to use the full installation wizard, you can simply copy the existing Synoptix client on the original server to the new server, or copy it from another workstation.  We have detailed instructions on this process available.
  • Once you have removed Tomcat from the original server and have an updated client installation on the new server, you are ready to install and configure Apache Tomcat.  Before doing so, please ensure the new server meets adequate system settings.  You can view minimum requirements in our Forum guide.


INSTALLATION OVERVIEW FOR BROWSER SCHEDULER
See install tutorial video 

During the installation of the Scheduler, run with the Apache Tomcat service, the following rights / access will be required.  We recommend having an internal IT administrator participate in the install.
  • Rights to Program Files
  • Ability to start and stop server Services
  • Access to the server that Apache Tomcat is being installed on, IP address and port number
  • Outgoing email server setup (type, port, if TLS, etc.)

Access to the Scheduler recommended with latest edition of standard browser:
Internet Explorer, Google Chrome, Safari, Edge. Note that security exceptions may need to be configured in your internet browser to permit access to the Scheduler.
Firefox is not supported.


WHERE TO INSTALL
  • You must be logged into and have admin rights to the server you wish to run the Apache Tomcat service from. This should be a 64 bit computer with 8 GB available space.
    This service will only run from this machine and does not need to be installed to individual user workstations.

  • You will need to know the IP of this server and the available port you would like to use.
  • The Synoptix client folder should be copied to the server where you are going to run Tomcat from, in order for Tomcat to access necessary files within the client folder.

HOW TO INSTALL
  • The Synoptix client must be installed and updated to the most recent version prior to installing the Scheduler.
  • Download Tomcat 8.5 from Apache site, 32/64 bit installer, and run the install wizard. 
  • Do not use Java path that auto-fills for the Java Virtual Machine; click ellipsis & direct it to the JRE folder inside of the Synoptix folder in Program Files.
    If both a JRE and JRE8 folder exist within the Synoptix folder, JRE8 takes precedence and should be where the Java path is pointed.

  • Once Tomcat is installed, you need to stop the Service and update the ROOT.war file.
    You can contact Synoptix Support to provide this file to you, or assist with the install. The ROOT.war file will match the version of the Synoptix client, so you will need to provide the version number to Support.

  • You will log in to the browser using the IP and port you have set for this service, and be prompted for connection parameters upon log in.
  • You will configure Scheduler settings through the browser Admin Setup, as well as configure Tomcat on the Windows machine.
  • The Report Save Path must be a folder created on the server running Tomcat and cannot be created on a mapped drive.