Secure Sockets Layer (SSL) Key File and Trust File Administrative Console Changes don't Update sas.client.props or soap.client.props Values
 Technote (troubleshooting)
 
This document applies only to the following language version(s):
US English
 
Problem(Abstract)
When changes are made to the SSL Key file and Trust file from the administrative console, the sas.client.props and soap.client.props files are not updated with the information. This causes problems when running commands from the command line.
 
Resolving the problem
The following are the server default settings for the SSL Key store and Trust store files in the Administrative Console:
Key File Name: ${USER_INSTALL_ROOT}/etc/DummyServerKeyFile.jks
Trust File Name: ${USER_INSTALL_ROOT}/etc/DummyServerTrustFile.jks

Soap.client.props and sas.client.props contain the client side files, and do not update from the administrative Console. These files must be manually updated if you change the Key/Trust files.

An example problem from using different Key and Trust files, but not setting them in the soap.client.props file, would be the inability to stop the server, nodeAgent or deployment manager from the command line.

Below are the values that need to be manually set within the soap.client.props and sas.client.props files located in the $WAS_HOME/properties directory:


com.ibm.ssl.keyStore
com.ibm.ssl.trustStore

You may also need to change the passwords and file types for the new files.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1152962
IBM Group: Software Group
Modified date: Nov 26, 2003