To Specify the Location and Password of the Certificate Key Store

1. Copy the .war file to a temporary directory:

   The location of the HTTPS tunnel servlet’s .war file varies, depending on how Message Queue was installed (see Appendix A, Distribution-Specific Locations of Message Queue Data):

   IPS packages: cp IMQ_HOME/lib/imqhttps.war /tmp

   
   

   Solaris SVR4 packages: cp /usr/share/lib/imq/imqhttps.war /tmp

   
   

   Linux RPM packages: cp /opt/sun/mq/share/lib/imqhttps.war /tmp

   
   

2. Make the temporary directory your current directory.

      cd  /tmp
   

3. Extract the contents of the .war file.

      jar xvf  imqhttps.war
   

4. List the .war file’s deployment descriptor.

   Enter the command

      ls  -l WEB-INF/web.xml
   

   to confirm that the deployment descriptor file (WEB-INF/web.xml) was successfully extracted.

5. Edit the deployment descriptor to specify the key store location and password.

   Edit the web.xml file to provide appropriate values for the keystoreLocation and keystorePassword elements (as well as servletPort and servletHost, if necessary): for example,

      <init-param>
         <param-name>keystoreLocation</param-name>
         <param-value>/local/tmp/imqhttps/keystore</param-value>
      </init-param>
      <init-param>
         <param-name>keystorePassword</param-name>
         <param-value>shazam</param-value>
      </init-param>
      <init-param>
         <param-name>servletHost</param-name>
         <param-value>localhost</param-value>
      </init-param>
      <init-param>
         <param-name>servletPort</param-name>
         <param-value>7674</param-value>
      </init-param>
   

   ---

   Note –

   If you are concerned about exposure of the key store password, you can use file-system permissions to restrict access to the imqhttps.war file.)

   ---

6. Reassemble the contents of the .war file.

      jar uvf  imqhttps.war  WEB-INF/web.xml