Before installing SmartConnect components the following SmartConnect pre-requisites should be checked to ensure they meet the minimum requirements.
Processors:
• | 32 bit processor machines, 2 GHz or greater. |
• | 64 bit processor machines, 2 GHz or greater. |
Memory (RAM):
• | 1 GB of RAM is required, at least 4GB is recommended. |
Processor and memory considerations:
While a faster processor and more memory will generally always speed up SmartConnect processing the following considerations should be made.
• | Installations that will be handling large data volumes will require more RAM. |
• | Installations that will make extensive use of data lookups will require more RAM. |
• | Installations that will make extensive use of scripting and calculations will require more ram and processing speed. |
Disk space:
• | SmartConnect application installation requires approximately 100MB of disk space. |
• | SmartConnect Excel Add-In requires 5MB of disk space. |
• | SmartConnect Web Service requires 20MB of disk space. |
• | SmartConnect WCF Rest service requires 20MB of disk space. |
• | SmartConnect Windows Service requires 60MB of disk space. |
• | SmartConnect Dynamics GP add-in requires 60MB of disk space. |
Operating systems:
• | Windows Server 2012 (including R2) |
• | Windows 7 SP1 (32 and 64 bit) |
• | Windows Server 2008 SP2+ (32 and 64 bit) |
Database:
• | The SQL Server Native Client 10.0 driver is required for the installation of SmartConnect. The driver is used to connect to the SQL Server as it creates the new database and users or connects to an existing database and user. |
Microsoft windows components:
• | SmartConnect 2016 requires Microsoft .NET framework 4.5.2 or greater to be installed on all clients or servers where SmartConnect will be run. The SmartConnect installer will check for the required framework and install it if it does not exist. However the framework can be added manually as part of setting up the environment. The latest Microsoft .NET framework may be downloaded from http://www.microsoft.com/net/download.aspx |
• | Microsoft IIS 8.0+ is recommended for machines running either the SmartConnect web service or SmartConnect WCF Rest services. The IIS server must be set up to allow the running of .NET applications. For WCF Rest installations the server must also be set up to enable WCF http activation. |
• | For installations that will be required to connect to a Microsoft CRM IFD or Online system will require the installation of Windows Identity Foundation. Note: this software is currently unsupported on windows XP operating systems. |
• | For installations that will be connecting to Microsoft Dynamics GP, a Windows Domain is required. |
Windows user permissions:
All windows users who are to access SmartConnect should have access to the following:
• | For 32 bit machines Read / Write access to the HKEY_LOCAL_MACHINE \ Software \ eOneSolutions \ SmartConnect registry keys |
• | For 64 bit machines Read / Write access to the HKEY_LOCAL_MACHINE \ Software \ Wow6432Node \ eOneSolutions \ SmartConnect registry keys |
• | Access to the SmartConnect installation (standard install path is c:\program files\eOneSolutions\SmartConnect\ ) |
User requirements:
SmartConnect installation requires users with which to run the following processes:
• | eConnect is the process that SmartConnect uses to update Microsoft Dynamics GP. This user also needs to be able to log into the MSSQL Server that contains the Microsoft Dynamics GP databases using windows authentication. |
• | SmartConnect Web Service controls integrations coming into SmartConnect from Excel, Microsoft Dynamics CRM, and third party applications that use the web service to connect. This user will need to be set up within SmartConnect after installation have been completed. This user may be the same user as the eConnect user. |
• | SmartConnect Windows Service is used by scheduled maps to run integrations. This user must also be set up within SmartConnect after installation has been completed. This user will be used as the default user for all scheduled integrations (unless a user has been specified on the scheduled map) and as such should have security to access/run all SmartConnect integrations. |
• | Salesforce Web Service is used to connect Salesforce real time data source maps to SmartConnect. This web service must be installed externally so it can be accessed by Salesforce. The internal user the web service uses to connect to SmartConnect should be restricted to only access required by Salesforce real time data source maps so as to reduce security issues associated with externally facing web services. |