IBM WebSphere 5.1 SOAP and Certs

installCert.java will just suck the certificate out of a ssl site and place it in the user.home/.keystore file. This will place the file in the home directory of the account you are logged into.

 

 

A way to verify that the keystore is created is to run the keytool -list command to list out the contents of the keystore. You should see the certificate from the target system in there.

 

 

You can also test that the certificate is installed properly by running any of the soap java sample applications in the SDK.

 

 

Most likely is that your problem is that the WebSpere runtime is not running under the same user context that you installed the certificate into.

 

 

The easiest solution I can see would be to move the .keystore file to a common location that is accessible to the WebSphere runtime and then configure your code in there to point to the new location.

 

 

So, let's say you create a directory /trustedstuff and put the file in there. Then in your code you need to specify the location of this keystore

 

 

System.setProperty("javax.net.ssl.trustStore", "/trustedstuff/.keystore"); 
  
 ... 
 call.invoke(...); 
 ...

 

 

Then the ssl runtime will know the correct location to look.

 

 

Another debugging trick is to add the -Djavax.net.debug=ssl runtime argument to enable ssl level tracing. Not sure how this works from a non-console based app but it's worth a try if things still aren't working out.

 

 

Let me know if this works for you or not.

 

 

-Joe