Overview

This document details instructions for migrating the Eleos integrations from one web server to another and was created to assist clients during a server migration.


Please note that these instructions will not work for a client whose web server is hosted in Azure. This document outlines general steps for migration and exact steps may vary per client.  Also, note that these instructions do not cover firewall and security information, which is custom to each client’s servers.


Instructions to Migrate Eleos Integrations

  1. Install IIS on the new web server.
  2. Copy the entire contents of the Eleos Integration directories over to the new server, most likely putting them in the "inetpub" directory that is typically used by IIS, but this is entirely up to your preference.
    1. Copy not only the "Active" folder for each integration, but also the other folders at that level - Backups, Staging, etc.  
  3. Configure the new IIS instance to host the integrations in the same way as the old instance.  This will be the most involved step, because it will require:
    1. Set up sites for the integration, or a site for each of the integrations being hosted, if you previously had multiple integrations. Ensure the URL routes are set up to point to the appropriate integration.
      1. If the external URLs are going to change, then you must also make sure to update the Service Configuration endpoints appropriately. To update the Service Configuration, log into Drive Axle, navigate to the app Manager, and select Service Config. from the App Configuration drop down.  In the Service Config. you can update the URLs and Save the changes.
      2. If it's possible, we advise giving the new web server a different URL, at least temporarily, to facilitate a smooth transition.  That way, the old server can be left online and running normally until the new server is fully set up, swap the endpoints in service configuration to test, and then can swap them back to the old server immediately if there are any issues.  Re-using the same URL will work too, it will just be harder to swap back and forth between old and new integration locations if it's needed.
    2. Configure the firewall to allow incoming traffic through those routes to the new machine.
    3. Ensure the Application Pool workers for each are configured correctly.
      1. .NET CLR Version is "No Managed Code" and Managed Pipeline Mode is "Integrated".
      2. If any of the current Application Pools are running as a different user, make sure the new pools are running as those same users (This could be the 'asrsvc' account).
      3. Set idle timeout minutes to 0 in advanced configuration to ensure the workers don't go idle during periods of low activity.