Installing multi-server Sage CRM
Install Sage CRM on the primary web server. The first install installs the CRM database to the database server. This is the only web server on which you install the database for the multi-server Sage CRM installation. Follow the instructions in the installation wizard for a typical Sage CRM installation. Note the installation name as you'll need this when installing the other servers.
You should install only one single Replication Engine instance on the primary server. To ensure that installing subsequent nodes won’t break any existing Exchange synchronizations:
- Disable the integration from SCRM UI on the first server.
- Install the next node.
- Stop the Apache Tomcat 9.0 <SageCrmInstallName>Tomcat9 Windows service.
- To remove the Replication Engine from the new node, remove the following:
- File %ProgramFiles(x86)%\Sage\CRM\<InstallName>\
tomcat\webapps\<InstallName>ExchangeSyncEngine.war
- Folder %ProgramFiles(x86)%\Sage\CRM\<InstallName>\
tomcat\webapps\<InstallName>ExchangeSyncEngine
- File %ProgramFiles(x86)%\Sage\CRM\<InstallName>\
- Start the Apache Tomcat 9.0 <SageCrmInstallName>Tomcat9 Windows service.
- Enable integration on the first node.
Then install Sage CRM on the other web servers in the cluster. Follow the instructions in the installation wizard for a typical Sage CRM installation. Set the installation name and database server name to the values used for the primary web server. Do not install the database on these web servers.
A Tomcat service is installed on the web server to support the Interactive Dashboard and SData features . In a multi-server CRM environment, the Tomcat service is installed in %ProgramFiles(x86)%\Sage\CRM\<InstallName>\tomcat on each web server in the cluster. If changes are made to custom tables on the database, the Tomcat service and the eware.dll on each web server reloads its metadata. Ensure the database server has enough concurrent connections to reload the sum of one DLL per web server plus one Tomcat database connection pool per web server.
For the Document Library feature to work correctly in multi-server environments, you must define a shared UNC network path with the appropriate access rights to the Library folder.
- Click <My Profile> | Administration | Email and Documents | Documents & Reports Configuration.
- Click Change.
- Enter the network path in Physical root directory for mail merged documents.
- Enter the network path in Default document templates location for mail merge.
- Click Save.