The eG Installation Guide - eG Innovations

Installing and Configuring on Windows Environments
In other words, to extract installation inputs from the eGAgent.iss file that was created in our
example above (see step 4), the command will be: eGAgent_.exe -a –s
/f1”c:\script\eGAgent.iss”.
The eG agent uninstallation will then begin and proceed in the silent mode. Setup will extract
the required inputs from the iss file and perform the uninstallation automatically, requiring no
user intervention of any kind.
3.3 Configuring Redundancy for the eG Manager on
Windows
To enable redundancy for a manager on Windows, a special batch file needs to be executed. This
batch file, named setup_cluster.bat, resides in the \lib directory, and when executed,
requests the following inputs.
The setup_cluster batch file will first request your confirmation to proceed with enabling manager
redundancy.
Would you like to enable eG Manager redundancy y/n [n]? y
Specifying n here will terminate the script execution. If you enter y, steps 12 to 22 of Section 2.1.4 will
follow.
3.4 SSL-enabling the eG Manager on Windows
The eG manager on Windows includes a default SSL certificate. If you choose not to use the default
certificate, then, you can generate a self-signed certificate by following the steps given below:
Generating the Keystore file
Extracting the certificate to a Certificate file (OR) requesting a Certificate Authority for a Valid
Certificate
Configuring Tomcat for using the Keystore file
The sections that follow will discuss each of these steps in detail.
3.4.1 Generating the Keystore File
The keystore file stores the details of the certificates necessary to make the protocol secure.
Certificates contain the information pertaining to the source of the application data, and helps validate
the source. To generate the keystore, use the keytool command. For this purpose, login to the Windows
manager and go to the command prompt. Then, execute the following commands, one after another:
cd %JAVA_HOME%\bin
keytool -genkey -alias egitlab1 -keypass mykey -keystore .keystore -storepass mykey -keysize
1024 -validity 1095
The text in Bold in the above command line indicates those inputs that can change according to the
requirements of your environment. These inputs have been described below:
-alias : an alias name for the certificate being generated
235