Skip to main content
All CollectionsBusiness System IntegrationsIntegration ServiceGeneral
Integration Service - What's the Difference Between V1 and V2?
Integration Service - What's the Difference Between V1 and V2?
Micah A. Parker avatar
Written by Micah A. Parker
Updated over 3 months ago

Product: Transaction Manager & Integration Service


If you're looking to integrate Transaction Manager with your local (On-Premise) ERP you will need a way to transfer data from Transaction Manager to your ERP in order to process orders, invoices, inventory, and more.

The Integration Service allows a connection to be made and ultimately performs the data transfer from TrueCommerce's Transaction Manager system with your ERP. While both the V1 and the V2 Integration Service perform this task - it's how they connect that separates them from each other.

While both V1 and V2 Integration Services are supported - it's recommended to migrate over to the V2 service for the added benefits provided by its design to reduce integration interruptions


Integration Service V1 (Legacy)


With the Legacy Integration Service (V1) each Workstation installs the Integration Service and must have direct access to the ERP Server from that machine in order to perform integrated actions with Transaction Manager.

Each Workstation that interacts with Transaction Manager does so locally through the Integration Service installed on their machine. Every time an Import or an Export is performed the service (from the workstation's machine) will attempt to reach out to your ERP Server from the perspective of the Workstation.

With this configuration, every Workstation would require access to your ERP, Transaction Manager, and most often your SQL/ERP Server depending on your setup often requiring setting up of Network Paths, ODBCs, as well as the Integration Service with each machine requiring a proper copy of TrueCommerce's Integration DLL

V1 Configuration

  • Installed per Workstation

  • Each Workstation must manually update the Integration DLL to match

    • Any update requires it to be applied to all Workstations

  • Utilizes Ports

    • Ports must be open/available

    • Firewalls/Port Blocking can interfere

  • Every Windows User per machine must have a Port assigned

  • Uses standard HTTP stateless commands


Integration Service V2


The Advance Integration Service (V2) uses a single Integration Service installation (typically on the Server) that all Workstations can then leverage to perform Integrated actions with your ERP by creating a direct connection to Transaction Manager.

Whenever an Import or an Export operation is performed Transaction Manager pushes that request to the Server that has the Integration Service installed and all operations run through that regardless of which machine requested it, reducing the number of connections required to the ERP Server and the number of Integration Services required to be installed.

Benefits of the Advance Integration Service (V2)


While you can utilize the V2 service by installing it on each individual machine, the main benefit of the Advance Integration Service (V2) is to allow a single setup that is responsible for all interactions between Transaction Manager and your ERP to reduce the complexity of your setup, and need for maintenance to keep your EDI process running smoothly.

Summary

  • Single Install on Server

    • Workstations do not require installation

  • Single Integration DLL Required

    • No Workstations need to be modified for updates

  • Utilizes a unique Service ID (GUID)

  • Single Setup for All Window Users

  • Uses a SignalR stateful connection

Additional Resources


rev 8/26/2024

Did this answer your question?