I have generated SOAP JAX-RPC Client from WSDL and deployed on WebSphere. JAX-RPC SOAP WebService is also deployed on WebSphere.
When the client invokes the web service via SSL, I am getting 404 error. The same end point URL is accessible via browser, SOAP UI, through a SOAP client deployed on JBoss. All of them are able to access SSL endpoint except SOAP Client on WebSphere. SOAP Client on WebSphere works with HTTP URL pointing to a node directly, but does not work with load-balanced SSL URL. Imported the required certificate into WebSphere trust store in the Admin Console. There is no Certificate issue.
When accessed via SSL, the request comes to IBM HTTP Server which sends 404 error. It is trying to find a directory (appended to DocumentRoot) and it's not found. It's unable to route to WebSphere plugin.
How does the same IBM HTTP Server and WAS Plugin setup work with all other SOAP Clients via SSL and doesn't work with SOAP Client running on IBM WebSphere alone ?
What exactly is wrong with the code or configuration that needs to be changed ?
Ew. You guys are ugly with a capital UG. Here, maybe this tiny ad can help:
SKIP - a book about connecting industrious people with elderly land owners