7UI 11.3.4 : CA7 WebClient: SEVERE - Failed to load keystore
Article ID: 108058
Updated On:
Products
CA 7 Workload Automation
Issue/Introduction
CA 7 Web Client 11.3.4 can be installed on Windows, Linux and USS on Mainframe.
Regarding the USS Mainframe installation, it is allowed to perform the installation pointing to a product install directory and a product ZFS install and then clone this ZFS install to a target Runlib which is usually always mounted under a path that is different from the initial one where 7UI has been installed.
For example, it is possible to initially install 7UI under path '/CA/ca7webclient1134/install' in ZFS 'CACA1.CA$WC114.ZFS.INSTALL' .
Then the INSTALL ZFS can be cloned to Runlib ZFS 'CACA2.CAIX.CA7WCZFS' mounted under '/usr/lpp/ca7/ca7webclient'.
This can be useful if customers decide to leave the INSTALL ZFS unmounted.
With this scenario it can happen that if the INSTALL ZFS is unmounted, Tomcat starts up but the 7UI is not accessible and In the STDERR file the following error occurs:
...
SEVERE: Failed to load keystore type ÝJKS¨ with path Ý/CA/ca7webclient1134/install/apache-tomcat-8.5.14/conf/.keystore¨ due to Ý/CA/ca7webclient1134/install/apache-tomcat-8.5.14/conf/.keystore (EDC5129I No such file or directory.)¨
java.io.FileNotFoundException: /CA/ca7webclient1134/install/apache-tomcat-8.5.14/conf/.keystore (EDC5129I No such file or directory.)
...
While if the INSTALLl ZFS is mounted, the Tomcat finds the .keystore file under '/CA/ca7webclient1134/install/apache-tomcat-8.5.14/conf' and In this situation 7UI works.
Anyway, the same .keystore file is also located in the runlib environment in '/usr/lpp/ca7/ca7webclient/apache-tomcat-8.5.14/conf' and Tomcat might take it from there.
What kind of modification should be done to bypass the error?
Regarding the USS Mainframe installation, it is allowed to perform the installation pointing to a product install directory and a product ZFS install and then clone this ZFS install to a target Runlib which is usually always mounted under a path that is different from the initial one where 7UI has been installed.
For example, it is possible to initially install 7UI under path '/CA/ca7webclient1134/install' in ZFS 'CACA1.CA$WC114.ZFS.INSTALL' .
Then the INSTALL ZFS can be cloned to Runlib ZFS 'CACA2.CAIX.CA7WCZFS' mounted under '/usr/lpp/ca7/ca7webclient'.
This can be useful if customers decide to leave the INSTALL ZFS unmounted.
With this scenario it can happen that if the INSTALL ZFS is unmounted, Tomcat starts up but the 7UI is not accessible and In the STDERR file the following error occurs:
...
SEVERE: Failed to load keystore type ÝJKS¨ with path Ý/CA/ca7webclient1134/install/apache-tomcat-8.5.14/conf/.keystore¨ due to Ý/CA/ca7webclient1134/install/apache-tomcat-8.5.14/conf/.keystore (EDC5129I No such file or directory.)¨
java.io.FileNotFoundException: /CA/ca7webclient1134/install/apache-tomcat-8.5.14/conf/.keystore (EDC5129I No such file or directory.)
...
While if the INSTALLl ZFS is mounted, the Tomcat finds the .keystore file under '/CA/ca7webclient1134/install/apache-tomcat-8.5.14/conf' and In this situation 7UI works.
Anyway, the same .keystore file is also located in the runlib environment in '/usr/lpp/ca7/ca7webclient/apache-tomcat-8.5.14/conf' and Tomcat might take it from there.
What kind of modification should be done to bypass the error?
Environment
Z/OS - USS - CA7 - CA7 Web Client
Resolution
If directory '/usr/lpp/ca7/ca7webclient/apache-tomcat-8.5.14/conf' should be used, in order to bypass the error it is necessary to do the following steps:
1) Locate the server.xml file (also under the .../conf directory).
2) Edit the server.xml file and look for the <Connector SSLEnabled="true" URIEncoding="UTF-8" line
3) PF11 until you see the keystoreFile= keyword. Here You need to do the update to point to /usr/lpp/ca7/ca7webclient/apache-tomcat-8.5.14/conf/.keystore
1) Locate the server.xml file (also under the .../conf directory).
2) Edit the server.xml file and look for the <Connector SSLEnabled="true" URIEncoding="UTF-8" line
3) PF11 until you see the keystoreFile= keyword. Here You need to do the update to point to /usr/lpp/ca7/ca7webclient/apache-tomcat-8.5.14/conf/.keystore
Feedback
Yes
No
Powered by
