Laura is right, WSAD comes with the IBMJCE and IBMJSSE, which is only a
problem if you absolutely require Sun's JSSE, or are using a signed third
party JCE provider. If you do not require either of these, then all you
need to do is make sure the java.protocol.handler.pkgs system property is
pointing at: com.ibm.net.ssl.internal.www.protocol. And if you have been
specifying a specific provider, stop doing that.
If you do require Sun, then things get a little tricky. You will need to
remove the following jars from your server's vm... another point - WSAD
uses at least two vm's... the one that matters when debugging/running is
the server vm... if I remember correctly it is under plugins.server.jdk
(something like that).
Ok, the jars:
ibmjcefw.jar
ibmjceprovider.jar
ibmjsse.jar
The above jars need to be replaced with the Sun JCE and JSSE jars (all of
the jars from both packages).
Then, you need to modify the java.security file, removing all of the IBM
JCE/JSSE related provider lines, and replacing them with the Sun JCE/JSSE
provider lines provided in the installation documents of both of the JCE
and JSSE packages.
Hope this helps.
- Matt
Laura Werner <[EMAIL PROTECTED]>
07/01/2003 05:57 PM
Please respond to "Commons HttpClient Project"
To: Commons HttpClient Project <[EMAIL PROTECTED]>
cc:
Subject: Re: WSAD & HTTPClient question
Hi Claudio,
> Does any one know any special consideration I have
> to know in order to make this work under WSAD 4.03?
If WSAD uses an IBM version of the JDK, which I think it does, you
probably need to get the corresponding IBM version of JSSE. We once ran
into a problem trying to use the Sun JSSE jars with an IBM JDK (1.3, if I
remember right).
-- Laura
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
