Migrate Web services security
Use the following steps when migrating a WebSphere Application Server Version 4 application that uses SOAP 2.2 security, to a WAS Version 5 application that uses SOAP 2.3 security.
- If you have any scripts that set up the CLASSPATH before running your application, make sure that the j2ee.jar file, located in the Version 5 /QIBM/ProdData/WebAS5/product/lib directory, where product is either Base or ND, is in the CLASSPATH.
- (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 foundThe three security key files are named SOAPclient, SOAPserver, and sslserver.p12. To locate the key files:
- If the application is already installed these files are found in the directory /QIBM/UserData/WebAS5/product/instance/installedApps/yourAppName.ear/soapsec.war/key/, where product is either Base or ND, instance is the name of your WAS instance, and yourAppName is the name of your application.
- 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.
- Stop and restart the server if you made any updates or replaced the key files.