A connection represents a single Sage Timberline Office database and a single Prolog Manager database that Integrator should exchange data between. The connection represents not only the identification of these databases but also the integration settings that will be used to exchange the data and a history of past exchanges.
Connection Information
The information for each connection is held in two places:
Local Connection File
A connection file exists for each connection. Connection files reside in the Connections folder that is under the Integrator application folder where the software is installed. This typically is located on each workstation that has Integrator installed. The connection file is a plain text file with an "eic" file extension. It contains general information about the connection and acts as a "shortcut" to the connection which is defined in the Integrator database. To utilize the same list of connections on different workstations, the connection files from one workstation can be copied to another. Each workstation will then point to the same connection definition in the Integrator database. Connection files are reqiured in order to see a list of connections to select from when opening a connection.
Integrator Database
The Integrator database resides on the same SQL Server that holds the Prolog Manager database associated with the connection. The Integrator database contains information about the connection including all settings, mappings, substitution tables and historical data.
Multiple Connections
There is no restriction to the number of connections that can be created. Multiple connections can be created that identify the same Sage Timberline Office and Prolog Manager database as well. This can be desirable if different groups of projects within the same databases require different integration settings.
WARNING
Care should be taken if defining multiple connections with the same Sage Timberline Office database and different Prolog Manager databases or vice versa. If implemented incorrectly, this could result in unintended propogation or overwriting of data between two or more Prolog Manager databases or two or more Timberline Office databases. This type of implementation should involve a qualified and experienced consultant. Event 1 Software does not support this type of implementation without such involvement.