Migrating from the Sun ONE V4.1 plug-in to the Sun ONE V6.0 plug-in with WebSphere Application Server V4.0
 Technote (troubleshooting)
 
Problem(Abstract)
Instructions for setting up Sun ONE V6.0 plug-in for use with all releases of IBM® WebSphere® Application Server V4.0 when migrating from Sun ONE V4.1
 
Cause
If you are upgrading from Sun ONE V4.1 (formerly iPlanet) to Sun ONE V6.0 and want to use the WebSphere Application Server V4.0 plug-in, this document explains how.
 
Resolving the problem

Statement of support regarding Sun ONE web servers with WebSphere Application Server:
  • IBM supports the use of the WebSphere Application Server V4.0 plug-in with Sun ONE 4.1 and Sun ONE 6.0 web servers
  • IBM supports the use of the WebSphere Application Server V5.0 and V5.1 plug-in with Sun ONE 6.0 web server
  • IBM officially does not support Sun ONE 4.1 web server with WebSphere Application Server V5.0 and V5.1 releases
  • IBM officially does not support Sun ONE 6.1 web servers with WebSphere Application Server V5.0 and V5.1 releases, because neither V5.0 nor V5.1 were tested with the Sun ONE 6.1 plug-in. IBM provides support for it only on a best-effort basis. Customers should re-create the same plug-in problem with a supported SUN ONE configuration before reporting any Sun ONE 6.1 WebSphere Application Server plug-in defect to IBM.

Before calling IBM for any plug-in support issues, IBM recommends that you first install the latest cumulative plug-in fix.

The following URL provides information on minimum hardware and software requirements for the Web Server & WebSphere Application server products.

http://www-3.ibm.com/software/webservers/appserv/doc/latest/prereq.html

Background:

Starting with PTF3 for WebSphere Application Server (V4.0.3), IBM included support for Sun ONE 6.0 web server. Sun ONE 6.0 is supported in WebSphere Application Server V5.0 and V5.1 in the GA releases.

Sun ONE web server Enterprise Edition V6.0 plug-in directives are now split between the magnus.conf and obj.conf files:

  • init functions, such as those used to load the WebSphere Application Server V4.0 plug-in, are configured in the magnus.conf file
  • service as_handler functions remain in the "default object" stanza of the obj.conf file

Note: It is still a requirement that the service as_handler function be the first service function defined in the default object stanza.


Steps for automatic configuration of Sun ONE plug-in for WebSphere Application Server:

You can perform a Sun ONE upgrade automatically by:

  1. Uninstalling all WebSphere Application Server fix packs & fixes on Sun ONE server
  2. Follow instructions to uninstall Sun ONE 4.1(all modifications)
  3. Follow instructions to install Sun ONE 6.0 (all modifications)
  4. Install WebSphere Application Server fix pack (this will install the plug-in for all releases of Sun ONE 6.0)
  5. Install any needed WebSphere Application Server fixes
  6. Review all plug-in entries in Sun ONE configuration files
  7. Start Sun ONE & WebSphere Application Server

Steps for manual configuration of Sun ONE plug-in for WebSphere Application Server:
  1. Verify that your current WebSphere Application Server configuration is running.
  2. Stop Sun ONE and WebSphere Application Server
  3. Save magnus.conf and obj.conf files from the Sun ONE 4.1 (all modifications) configuration
  4. Follow directions to uninstall Sun ONE 4.1 (all modifications)
  5. Follow directions to install Sun ONE 6.0 (all modifications)
  6. Manually add the needed directives to magnus.conf & obj.conf. (See "Manual upgrade of SunOne plug-in in the web server configuration files" for details)
  7. Start Sun ONE and WebSphere Application Server.

Manual upgrade of Sun ONE plug-in in the web server configuration files:

When upgrading from Sun ONE 4.1 (all modifications) to Sun ONE 6.0 (all modifications), some of the WebSphere Application Server plug-in entries that were in the obj.conf files in Sun ONE 4.1 (all modifications) need to be moved to magnus.conf:
Init fn="load-modules" funcs="as_init,as_handler,as_term" shlib= ...
Init fn="init_exit" bootstrap.properties= ...

The rest of WebSphere Application Server plug-in directives will stay in the obj.conf:
Service fn="as_handler"

Conclusion

This document should be used as a guideline toward the migration of WebSphere Application Server 4.0 plug-in from Sun ONE 4.1 (all modifications) to Sun ONE 6.0 (all modifications) web server.

You can review attached sample Sun ONE 4.1 (all modifications) & Sun ONE 6.0 (all modifications) configuration files with WebSphere Application Server V4.0 plug-in module on a Unix platform. The lines added by the WebSphere Application Server install script are preceded with a "*" so they stand out. The actual configuration directives are identical for the two versions of Sun ONE, the only change is the two lines responsible for getting the plug-in loaded and initialized have been moved from the obj.conf to the magnus.conf in Sun ONE 6.0 (all modifications)

You have to disable completely the Servlet Engine/Java in Sun ONE web server on the global level. The Servlet Engine/Java is enabled by default in the Sun ONE 4.1 (all modifications) & Sun ONE 6.0 (all modifications) web server & it collides with the WebSphere Application Server Servlet engine.

 
obj_SunOne4.confmagnus_SunOne6.confobj_SunOne6.conf
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Plug-in
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1154378
IBM Group: Software Group
Modified date: Sep 10, 2004