Follow these instructions to install SigningHub Enterprise with a load-balanced configuration.


Launch the installer by right-clicking the file name [SigningHub Installation Directory]/setup/install.bat and select Run as administrator.


Follow the installation wizard as described previously until the Installation Type screen is shown:

 

Click the Next button to show the License Agreement:



Click the I Agree button to proceed.  


The following screen to prompt for database details is displayed:



The information displayed above is an example and you should configure the relevant settings for your own environment.
  • The SigningHub Enterprise database schema and the version required by the installer must be the same. 
  • If the current SigningHub Enterprise database schema is older than the version required by the installer, and you click Next, the installer will prompt you that SigningHub Enterprise database schema will be upgraded to the latest version. Click OK to authorize the schema update.


Click the Next button to select specific modules:



Select the appropriate modules to install the required features.


Click the Next button to show the summary and complete the installation:

 



This screen shows the installation summary by listing the different product modules that will be installed. 


If you think any listed item is incorrect then use the Back button (arrow towards the top-left of the dialogue box) to correct your choices before proceeding ahead.

 



Click the Next button to continue with the installation.



Click the Finish button to complete the installation process.

The site IDs of deployed IIS websites should be the same across all the instances in a load balanced environment to run SigningHub Enterprise properly.
Please note that Local Signing will not be available in a Load Balanced environment by using sessionState mode SQLServer. However, if users still require performing Local Signing, then please follow these steps to replace sessionState mode with InProc:

  1. Open the [SigningHub-Installation-Dir]/web/web.config file of all deployments of SigningHub
  2. Replace: 

<sessionState mode="SQLServer" allowCustomSqlDatabase="true" sqlConnectionString="AdocsEntities" cookieName="SH_ID" timeout="60"  compressionEnabled="true"> </sessionState>

With: 

<sessionState mode="InProc" timeout="60" cookieName="SH_ID" cookieSameSite="None" />

  1. Configure sticky session on load balancer server
  2. Configure an AJP Connector as mentioned in Appendix A


Also note that if someone wants to change email templates in case of a Load Balanced environment, then email templates will have to be replaced manually across all instances.