The eG Installation Guide - eG Innovations

Installing and Configuring on Windows Environments
-alias : the alias name of the certificate being requested; make sure that you provide the same alias
name that you provided while generating the keystore file (see Section 3.4.1 of this document).
-file : Provide a name for the text file to which the certificate request will be saved.
-keypass : the password used to protect the key that was generated; make sure that you provide
the same password that you provided while generating the keystore file (see Section 3.4.1 of this document).
Also, note that -storepass and -keypass should be the same.
-keystore : Provide the name of the keystore file in which the key has been stored; specify the
same file name that you used to store the key (see Section 3.4.1 of this document).
If this command executes successfully, then a certificate will be issued by a certifying authority.
Note:
If you follow the procedure discussed in Section 3.4.3 to generate a valid certificate through a
certificate authority, then, you need not follow the procedure discussed in Section 3.4.2 to extract
a certificate from the keystore file.
3.4.4 Configuring Tomcat for Using the Keystore File
The eG manager on Windows uses Tomcat as the web server. Therefore, to SSL-enable the eG
manager, you need to configure the server.xml file of Tomcat with the name and full path to the
keystore file which was created earlier.
Note:
The procedure discussed in this section applies only if the keystore file you generated is not
stored as egmanager.bin and/or is not stored in the \manager\tomcat\webapps folder.
1. Edit the server.xml file in the \conf directory.
2. In the file, search for the XML block where the SSL Coyote HTTP connector on port 8443 is
defined. If this block is commented, uncomment it as indicated below:
238