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 all of the details for your server’s firewall and security configuration. This is custom to each client’s servers.  If there are any additional questions or concerns about migrating the integration to a new server, please contact ASR by reaching out to support. Note that if you need resources at ASR to assist with a migration, it requires us to know the date/time of the migration and would come at an added cost so that we can ensure support during the change.


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. Ensure that the .NET CLR needed to support your integration is installed on the new webserver.  Note that the version of .NET that you need may vary.
  4. 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 proper 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 there are changes to the DNS, it needs to be adjusted in the Service Configuration in Drive Axle, and DNS needs to be updated to the new IP address. The Service Config section in our   Eleos - Drive Axle Walkthrough  article contains info on how a firewall should be configured using a wildcard DNS entry.
      3. If it's possible, we recommend 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. When choosing how code should be run within your application pool, if you're using .NET, "No Managed Code" should be selected. If you're using a Manage Pipeline for code, "Integrated" should be selected.
      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.
  5. If the SQL server moves or if there are changes, connection strings in appsettings may need to be updated as well.
    1. The connection string needs to be updated in the appsettings.json file if:
      1. The SQL Server's IP address is changed,
      2. The database name has changed,
      3. or web_eleos' password has changed for the database user.

  6.  If no DNS is being used, and the new server’s IP address is the same as the old server’s IP address, then there are no further changes that would need to be made. If the new server’s IP address is different than the old one and is the correct one to use moving forward, please notify ASR, as there's more configuration, we'll need to do on our end to support the new location.

If the DNS is changing, or the IP changes and no DNS is present, ASR needs to be made aware of these changes to update their forwarding processes in Azure, which includes Azure Tenant Forwarding, Azure Email Forwarding, Azure Request Forwarding and Geotab Notifications for customers with Geotab as their Telematics provider. Updates that need to be made can be provided to [email protected], since an ASR staff member with access to Azure must make these changes.