/
Requirements

Requirements


Click the logo to return to KB


TFS Intefration Guide - Table of Contents

     

        

TFS Integration is a powerful solution to replicate and synchronise data between database systems. To ensure a smooth implementation of integration, there are some key requirements that must be met.

  • A detailed discussion of desired outcomes from TFS Integration to ensure the process, procedures, and results meet business expectations.
  • Analysis questions and activities must be completed to ensure a full understanding of the target environment.
  • Preparation of TFS data must be completed to address any specific requirements of both existing data in the system and new data moving forward.
  • Installation and configuration of all integration software and the required connectivity to the various systems and databases.
  • A comprehensive process of testing TFS Integration and full acceptance and sign-off of the integration project by required management and staff.

Insula Software Consultation

It is highly recommended that the implementation of TFS Integration be discussed and coordinated with Insula Software. This will ensure that all issues raised in this documentation are reviewed and considered in the context of a client's specific environment.

Test/Production Environment Implementation

Due to the technical nature of integration and a high level of understanding required to configure systems and databases, it is HIGHLY RECOMMENDED that TFS Integration first be installed and configured in a test environment. Once the implementation has been deemed successful and affected users have performed (and signed off on) User Acceptance Testing (UAT), the installation and configuration can be migrated easily to the live production environment.

Where a test environment is not available, consideration as to when integration is activated and tested should be made. Where integration is being installed directly into a production environment, it should be done after hours with no users connected to any of the systems involved. Complete backups of all systems should be taken prior to starting integration so that a clear roll-back point is established and can be used if the results of integration are incorrect or unsatisfactory.