-
Bug
-
Resolution: Fixed
-
Blocker
-
Jenkins ver. 2.32.2
websphere-deployer: 1.3.4
was 8.5
I have spent hours trying to figure out how to resolve this apparent conflict but have had no success.
The test connection works; however the test connection appears to not care about the validity of the credentials so it doesn't appear to be a very clear indicator.
I have gone through the additional steps of verifying the certificate installation and CAN connect using SSLPoke on the assigned port.
We have copied the jar files from the WAS server to the plugins/websphere-deployer//web-inf/lib directory .
I have tried including the slf4j jar files in both the plugins/websphere-deployer//web-inf/lib and the jenkins lib files; neither was met with any difference.
The issue appears to be two fold.
One there appears to be an issue with the jar files and a potential library conflict? This is of minor concern except that it seems to be preventing me from getting a real error.
Second I seem to having trouble making the connection work. We are working with cluster environment and there isn't much documentation on this. Do I still need to include the server name / node if I'm providing the cluster ?
At this point I am simply out of ideas and frustrated. I appreciate any help or guidance that you can provide.