AnterraDataCenter Prerequisites Documentation
AnterraDataCenter™ Prerequisites Documentation
Required Software Components
Sage ODBC
Sage ODBC is required to be fully operational for each computer running the AnterraDataCenter™ tools. This requires a Sage server or client install with a purchased ODBC license, and the option to install it selected. Specific DSN names are not required to be set up, as AnterraDataCenter™ uses a clientless ODBC connection. Anterra supports the current version of Sage and the immediately prior version, in line with the support policy of Sage.
Microsoft SQL Server™
If you are an Anterra Platform (SaaS) customer, you may not need Microsoft SQL Server installed in your environment. An installation of Microsoft SQL Server on-premises is required when one of the following is true:
- Customers with very large datasets
- Slow or high latency internet connection
- ADC-only customers performing on-prem data sync
ADC uses two separate databases, one for the Sage extracted data, and one for the Extraction configuration data. If you are running multiple instances of ADC, each requires it's own configuration databases, however multiple configuration databases can be stored on the same SQL Server. The extracted Sage data can reside on one or more SQL Server instances, either centrally located or on locally on the same machine as ADC.
AnterraDataCenter supports SQL Server 2022, SQL Server 2019, SQL Server 2017, SQL Server 2016, including Express editions. The latest Microsoft SQL Server service pack and recommended security patches should be applied to SQL Server as part of your standard maintenance routine - the latest list is maintained by Microsoft here.
Microsoft .NET Framework v4.8
All AnterraDataCenter™ tools require Microsoft’s .NET Framework 4.8 to be installed and functional on the machine AnterraDataCenter™ is installed on. The appropriate framework is installed automatically during the installation of ADC if it's not already present.
Firebird ODBC (Optional)
Firebird Database engine has to be installed (locally on the same computer as AnterraDataCenter™) in order to extract data from either Firebird (.FDB) database files or Interbase (.GDB) database files. Both the Firebird ODBC driver and Firebird .NET provider must be installed for the extraction to properly function. All required components are available through the Firebird website.
Network Configuration and Permissions
The following network configuration connections and permissions are required:
Sage Security
To access the Sage 300 data a user for ADC must be created in Sage 300 Security. The user must have the Application Admin settings set and it should also be set with a password that never expires. This way you do not have to edit the scheduled task every time the password changes.
To test whether the login and password are valid, start up and log in to Sage Desktop with the newly created user.
Sage Data Folder
It is recommended that AnterraDataCenter™ be installed on the same server that Sage 300 is installed. However, it is possible to set up AnterraDataCenter™ on another computer and access the Sage Data folder(s) through a UNC connection path, but this configuration is not supported for scheduled updates. AnterraDataCenter™ needs to point at the Sage file “ts.ctl”, which is located at the root of every Sage data folder.
A minimum of Application Administrator is required for the user ID which AnterraDataCenter™ will be using.
AnterraDataCenter™ Installation Folder
Local administrator permissions are required for the user ID which AnterraDataCenter™ will be installed with.
MSSQL Service Security Account
If the SQL Server is located on a different server than AnterraDataCenter™, the MS SQL Service must be set to log on using a Domain account, rather than the Local Service account. This is necessary for the Bulk Insert process, which requires access to the share where the bulk insert temporary files are located. The domain account that is used must have permission to access this folder location. For more information on SQL Server security, please consult the following Microsoft document for SQL Server.
Temporary Folder
AnterraDataCenter will require a Shared folder, such as \\SQLServer\ADCTemp, on the SQL Server if the SQL Server is not on the same server as Sage Server. The SQL Service Account will need full read access to this folder and the Windows Account running AnterraDataCenter in Task Scheduler will need full read/write access to the Shared folder.
If the SQL Server is on the same server as Sage, then you can use a local drive such as D:\ADCTemp
System Requirements
The system requirements for the computer running AnterraDataCenter™ are similar to the Sage System Requirements. These are as follows:
Sage 300 - Sage Construction and Real Estate
17.1+
Operating System
Windows 10, and Windows Server 2016, 2017, 2019, 2022. All in x86 as well as x64
Processor
2 GHz multi-core CPU minimum, 2.5+ GHz multi-core CPU is recommended
RAM
6GB minimum, 8GB recommended
Hard Disk Space:
For the computer where AnterraDataCenter™ is installed requires approximately 100MB of disk space.
SQL hard drive space is roughly equivalent to the hard drive space for your Sage data. For safety, space should be at least double the immediate maximum requirement to take into account room for SQL transaction logs, indexes, and temporary files.
Network
Ethernet 100/1000MB
WiFi 802.11a/ac/b/g/n
Pre-Installation Checklist
The following items must be performed before installing AnterraDataCenter™:
- Microsoft .NET framework 4.7.1 or newer installed
- Computer meets or exceeds minimum hardware System Requirements
- Sage ODBC installed and functional.
- SQL Server installed, configured, and functional.
- Sage security account and password for the data sync available. Do not use the sys admin account.
- Sage data folder location is accessible for user account which will install and run AnterraDataCenter™.
- SQL or Integrated Security set up for user account that will administer AnterraDataCenter™
- Scheduled Tasks functional (requires local administrator privileges)
If the SQL Server is on a different computer than AnterraDataCenter™, you must additionally check the following:
- Share folder on destination server for bulk insert files set up on SQL Server which is fully accessible by the account which will be running AnterraDataCenter™
- MS SQL Service running under a domain account with a minimum of read access to the temporary folder share, and with at least minimum security required to run SQL Server.
Anterra Technology Contact Information
Fill out the following form to get a link to schedule assistance with your ADC install:
Related Articles
'Timberline Version Changed' appears when anterraDataCenter opens
Background When anterraDataCenter opens, a dialog box with the title "Timberline Version Changed" appears Each time anterraDataCenter opens, a message appears that has the following text in it: "Timberline version has recently been updated. SQL ...Resolving Pervasive.SQL 3006 error found in AnterraDataCenter Log files
The Pervasive.SQL.3006 error is a result of a timeout between the Pervasive Client and Server which creates a broken or interrupted connection. This can happen if AnterraDataCenter is on a different server from the Sage Pervasive database, or if the ...AP/AR Invoice Image Upload Service Install and Prerequisites
Overview The Anterra Signed Upload Sync Service is a Windows Service that runs on a server in your environment with access to the locations on your internal network which contain PDF or TIF/TIFF images for AP and/or AR invoices. The service supports ...Allow Non-Administrator Users to Run ADC Updates
Running All Connections This is the easiest configuration and allows any user to run the configured connections for all active tables. Create a shortcut to ADCUpdate.exe (located in the anterraDataCenter installation folder). You can place this ...Anterra Platform License Agreement
Hosted Software License Agreement THIS DOCUMENT IS A LEGAL AGREEMENT BETWEEN LICENSEE AND LICENSOR. BY CLICKING ON “I AGREE” BELOW AND INSTALLING THE HOSTED SOFTWARE, YOU, ON BEHALF OF LICENSEE, AGREE AND ARE SUBJECT TO THE LICENSE TERMS SET FORTH ...