Configuring the Sun Java System Web Server

This topic describes how to change configuration settings for the Oracle iPlanet Web Server (formerly Sun ONE Web Server, iPlanet Web Server, and Sun Java System Web Server), Version 6.0 and later.

1. Configure entries in the obj.conf configuration file and in the magnus.conf configuration file for Version 6.0 and later of Oracle iPlanet Web Server.
   1. Add two directives to the obj.conf file after the <Object name=default> tag:

      Service fn="as_handler"
      AddLog fn="as_term"

   2. Add two directives at the end of the magnus.conf file:

      The location for the bootstrap.properties directive varies, depending on how you have configured your system. If the Web server and the application server are on separate machines, you have a remote installation.

      If the two servers are on the same machine, you have a local installation.

      If the two servers are on the same machine and the application server is a managed node, you have a local distributed installation.

      Avoid trouble: The following examples reference the libns61_http.so file, which is only supported for the Oracle iPlanet Web Server 7.0 and 6.1. If you are using a Sun ONE Web Server 6.0, change these references to libns41_http.so.

      • 
        Local distributed example:

        Init fn="load-modules" 
             funcs="as_init,as_handler,as_term" 
             shlib="/opt/IBM/WebSphere/Plugins/bin/libns61_http.so"
        Init fn="as_init" 
             bootstrap.properties="profile_root/config/
                cells/dmgrcell/nodes/managed_node/servers/webserver1/plugin-cfg.xml"

        Example:

        Init fn="load-modules" 
             funcs="as_init,as_handler,as_term" 
             shlib="/opt/IBM/WebSphere/Plugins/bin/libns61_http.so"
        Init fn="as_init" 
             bootstrap.properties="/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml"

      • 
        Local distributed example:

        Init fn="load-modules" 
             funcs="as_init,as_handler,as_term" 
             shlib="C:\IBM\WebSphere\Plugins\bin\ns41_http.dll"
        Init fn="as_init" 
             bootstrap.properties=
             "profile_root\config\cells\
                dmgrcell\nodes\managed_node\servers\webserver1\plugin-cfg.xml"

        Example:

        Init fn="load-modules" 
             funcs="as_init,as_handler,as_term" 
             shlib="C:\IBM\WebSphere\Plugins\bin\ns41_http.dll"
        Init fn="as_init" 
             bootstrap.properties="C:\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml"

2. Set the shared library path on HP-UX machines.
   On some installations of Oracle iPlanet Web Server on an HP-UX machine, it is necessary to manually set the SHLIB_PATH variable to /usr/lib before starting Oracle iPlanet Web Server with a plug-in that is configured for Secured Sockets Layer (SSL). For example, in the korn shell, issue the following command before invoking the command to start the Oracle iPlanet Web Server:

   export SHLIB_PATH=/usr/lib:$SHLIB_PATH

3. Disable the feature of Oracle iPlanet Web Server Version 6.1 that supports servlets and JavaServer Pages files by default.
   Disable this feature so that the WebSphere Application Server plug-in can handle the requests.

   Perform the following steps to disable the feature:

   1. Remove or comment out the following two lines from the obj.conf configuration file:

      NameTrans fn="ntrans-j2ee" name="j2ee"
      Error fn="error-j2ee"

   2. Remove or comment out the following line from the magnus.conf configuration file:
      

      Init fn="load-modules"
          shlib="C:/Sun/WebServer6.1/bin/https/bin/j2eeplugin.so" 
             shlib_flags="(global|now)"

      

      Init fn="load-modules"
          shlib="C:\Sun\WebServer6.1\bin\https\bin\j2eeplugin.dll" 
             shlib_flags="(global|now)"

4. If you are configuring a 64-bit version of the Oracle iPlanet Web Server, modify the loadModule entry in the magnus.conf configuration file to point to the plugin_root/bin/64bit/libns61_http.so file.