PQ59500: CUSTOMER TRIES TO INSTAL IPLANET PLUGIN FOR WAS 4.01 FROM CD ON WINNT, OBJ.CONF FILE DOES NOT GET UPDATED WITH PLUGIN LINES. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Customer has installed WAS 4.01 on WinNt 4.0, when selecting the IPlanet plugin the obj.conf file is not updated properly. The customer has to manually add the following lines to th obj.conf file. Init fn="load-modules" funcs="as_init,as_handler,as_term" shlib= "E:/WebSphere/AppServer/bin/ns41_http.dll" Init fn="as_init" bootstrap.properties= "E:/WebSphere/AppServer/config/plugin-cfg.xml" After adding the lines to obj.conf file the customer is then able to load the plugin.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * Advanced and Single Server edition on * * Windows platform using iPlanet. * **************************************************************** * PROBLEM DESCRIPTION: During the base install of WebSphere * * 4.0.1 AE or AEs on Windows the install * * crashes if you choose iPlanet as your * * plugin. * **************************************************************** * RECOMMENDATION: * **************************************************************** The base WebSphere AE and AEs install crashes on Windows when iPlanet is chosen as the plugin to be installed. The plugin files are layed down in the %WAS_HOME%\bin directory but the obj.conf file is not updated to add the necessary lines in order for iPlanet to work properly with WebSphere.Problem conclusion This issue will be addressed in WebSphere 4.0.3 during the ptf install the user will be prompted on whether they want to update their iPlanet configuration. The user will also be asked if the iPlanet they want to upgrade is iPlanet 4 or 6. The reason behind this is because in iPlanet 4 all the configuration changes are done in obj.conf whereas in iPlanet 6 changes are needed in obj.conf and magnus.conf. If the installer does not find any lines that it wants to add in the configuration file(s) then it will add them. FYI, on other platforms where the iPlanet plugin gets installed properly, iPlanet 6 may be installed but the user has to install the iPlanet 4 plugin from the base WAS cd. This will work fine except two lines need to be moved from obj.conf to magnus.conf. The lines that need to be moved from the obj.conf file in /opt/iplanet/servers/https-<hostname>/config directory to the magnus.conf file in the same directory are: Init fn="load-modules" funcs="as_init,as_handler,as_term" shlib ="/opt/WebSphere/AppServer/bin/libns41_http.so" Init fn="as_init" bootstrap.properties=/opt/WebSphere/AppServer /config/plugin-cfg.xml The 4.0.3 ptf install will move these lines for the user.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ59500
IBM Group: Software Group
Modified date: Apr 22, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.