Summary of iplanet 4.0 WebSphere plugin Notes
- defect 80693 - iPlanet Plugin work for v
3.02.2. Note, defect 73047 was used for the v 3.5
changes done by Kurt Deitrick.
- 7/31/00 - Current status:
- Changes to create the new plug-in have been integrated into cmvc, are
participating in the ptf builds successfully, but the new plug-in module is
not being packaged into the PTF package. Note was sent to Raj Baberwal
asking him to make changes to fix pack installer to package new plug-in into
the ptf files.
- Windows support for plug-in has been tested and is working except for a
concern about EJB samples not all running. Current thinking is the EJB
samples that didn't work are likely due to a setup problem with the test
environment and not due to a problem in the plug-in itself.
- For reference here are some chronological
notes relating to this work.
- Suggestion for testing with iPlanet 4.0 on Win/NT attempting to simulate a
customer scenario for moving to the new iPlanet 4.0 plugin. This assumes one
is starting with an environment where Netscape Enterprise Server 3.6 and
WS 3.0.2.1 are installed and working together. Directory references below are
for host RCB2.
- Install WS 3.0.2.2, version ptf2a0029.01, by running "C:\websphere\v3.0.2.2\ptf2a0029.01\fixpack_Adv_NT\install.bat".
- Copy the new iPlanet 4.0 plugin, "C:\websphere\build\ncf\build\Netscape40\bin\ns40.dll",
to the WebSphere install directory, "C:\websphere\AppServer\bin". Note this only needs to be
done until ns40.dll gets packaged into the PTF by the build process.
- Verify that NS 3.6 and WS 3.0.2.2 work ok together.
- Install iplanet 4.0 web server.
- iplanet 4.0 can be downloaded from the Netscape
Download site as "C:\self_ext\iPlanet40\e40diu.exe".
- Install parms took defaults for everything, choose not to configure a
JDK with the server.
- Edit the "C:\Netscape\Server4\https-rcb2.raleigh.ibm.com1\config\obj.conf"
file and altered according to the plugin
configuration instructions.
- Do WS DB setup and run the WS Samples.
- So far, everything seems to be working OK except some of the ejb
samples.
- For ejb samples, some worked but had trouble with those
requiring extra DB init in the sample DB. I'm suspecting I have something
wrong there so need to ensure that the sample DB has been initialized
completely.
[ Mail Comment | Commenting
help | Author
help | Next
Higher Info Node | Top of
tree ]