Migrating Apache SOAP security

One can use the following steps when migrating a WebSphere Application Server, Version 4.0 application that uses Apache SOAP 2.2 security, to a WebSphere Application Server, Version 5.0 application that uses Apache SOAP 2.3 security.

 

1. If you have any scripts or .bat files that set up the CLASSPATH before running your application, make sure that the j2ee.jar file, located in the WebSphere V5<WebSphere/AppServer>/install root directory is in the CLASSPATH.

2. (Optional)Replace security key files, if needed. You might need new security key files if you get the following error:

   "conf/cl-sig-config.xml"  javax.security.cert.CertPathBuilderException: 
   No end-entity certificate matching the selection criteria could be found
   

   The three security key files are named SOAPclient , SOAPserver , and sslserver.p12 . To locate the key files:

   1. If the application is already installed these files are found in the directory <WebSphere/AppServer>/installedApps/<yourAppName>.ear/soapsec.war/key/

   2. If the application is not yet installed, these files are found by expanding <yourAppName.ear>. Then, expand the soapsec.war. The files are in the key/directory.

3. Stop and restart the server if you made any updates or replaced the key files.
   
   

    

   WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

    

   IBM is a trademark of the IBM Corporation in the United States, other countries, or both.