Migrating to the new AutoDispatch Gateway

Overview

We have created a new modern technology replacement for the AutoDispatch Gateway (ADGW). It was written in .NetCore and allows easier expansion to support new dispatch type integrations. We can also add new input types to support integration with other BoldGroup products very easily. This document covers specifically converting from the old ADGW to the new one.

Make SURE that the customer has worked with TMA to get a full certificate bundle and settled on the new URLs BEFORE doing the switchover!!! All IT ports need to be setup and working!

Technical Information / Usage

All Technical information is covered in the documentation for ADGW2.
 

Installation

In this specific case, we are first removing the old ADGW and then installing the new one.

You can follow the steps for the Install of the new one up to the point of installing the service. You can follow all the configuration steps in the new one. This will increase the speed of changeover.

Or you could completely set up the new on a secondary server and then just change the configuration in SWS to use that one.

If this is being done as a "hot-fix" or "Beta" testing, you will need to run the attached migration script manually. It will be run if this part of a normal upgrade process. It can be run at any time and is backward compatible with the old ADGW.

Remove old ADGW

  1. Open a command prompt as an Administrator.
  2. Navigate to the Manitou primary directory.
  3. Open SWS and remove the configuration parameters from the ADGW. Save.
  4. Stop the running ADGW process in the MSM.
  5. run "AutoDispatch.exe -remove" in the command prompt.
  6. Remove the following files from the primary Manitou directory:
    1. AutoDispatch.Core.dll
    2. AutoDispatch.exe
    3. AutoDispatchApplication.exe
    4. AutoDispatchSimulator.exe

Install the new ADGW

Follow the instructions in this document to install the new ADGW. The document does show screenshots for setting up a different dispatch provider. This changeover uses the same setup in MWC/SWS as the old one so you will not have to redo that. 

AutoDispatch Gateway 2 - Installation Instructions

Follow the instructions in this document to setup the core configuration for the new ADGW. The dispatch provider we are using is "TmaAsapDispatchProvider.dll" which is different from the example.

AutoDispatch 2 - Core Configuration

Follow the instructions in this document to configure the TMAASAP provider specifically. This is where the URLs that used to be set in the configuration parameters are stored.

 AutoDispatch Gateway 2 - Dispatch Integrations: TMA ASAP

Pay special attention to the certificate section.

Finally, finish the install by registering the new service and then restart from the MSM.

Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.