Framework Integration is a powerful solution to replicate and synchronise data between database systems. To ensure a smooth implementation of Framework Integration, there are some key requirements that must be met.
- A detailed discussion of desired outcomes from Framework 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 Framework ECM 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 Framework 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 Framework 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 Framework 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 live 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.The following information outlines important analysis questions and activities that MUST be performed before undertaking the installation and configuration of Framework Integration.
Each question should be considered and the responses recorded. The responses will be required when installing and configuring Framework Integration.
Email Configuration
Analysis Questions | Response |
|---|---|
Email Server Name (Integration emails are sent via this server) |
|
Email Server IP Address |
|
Contact Person (IT contact person's name and email address) |
|
Do emails sent to this server HAVE to be from a valid user? (To ensure emails are not rejected) |
|
If Yes, what is the valid user email address? |
|
Is security needed to send emails to this server? (To ensure emails are not rejected) |
|
If Yes, what is the:
|
|
Internal Staff Email Address (Who will receive log emails) |
|
Internal Public Folder Email Address (A public folder to store emails) |
|
Insula Software Support Archive |
WMS Configuration
Analysis Questions | Response |
|---|---|
WMS Server Name (Server where the WMS database is installed) |
|
WMS Server IP Address |
|
WMS Version Number |
|
WMS Database Name (what is the data referred to?) |
|
Native Folder (e.g., C:\Data\WMS\) |
|
Database File Name (e.g., wms.fdb) |
|
WMS Security User Account: - Username (e.g., ODBC) - Password (e.g., secure) |
|
Material Class to Orders Link Method: - Description Code (default) Code for the Cost Centre (Material Class) will be all characters up to the first space (typically three numbers) - Internal Code (use the internal BuilderMT WMS primary key number) |
|
Data Requirements
Analysis Questions | Response |
|---|---|
Earliest Date of Orders to Import (this is determined by the oldest job still on-site and when the orders for that job were issued/released) |
|