Configure the Sun Java System Web Server

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

 

Before you begin

When you install the Web server plug-ins for WebSphere Application Server, as described in Installing Web server plug-ins, the Plug-ins installation wizard configures the Web server. This topic describes how to configure the Sun Java System Web Server if you must change something in the existing configuration. Other procedures in Editing Web server configuration files describe configuring other supported Web servers.

 

Overview

Configure the Sun ONE Web Server 6.0 or Sun Java System Web Server, V6.1 and later, on a Linux, UNIX, or Windows platform.

Examples and messages are sometimes shown on more than one line for ease of presentation. Verify that each directive in a Web server configuration file is on one line.

 

Procedure

  1. Configure entries in the obj.conf configuration file and in the magnus.conf configuration file for v6 and later of Sun Java System 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.

      Local distributed example:

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

      Local stand-alone example:

      Init fn="load-modules" 
           funcs="as_init,as_handler,as_term" 
           shlib="/opt/IBM/WebSphere/Plugins/bin/libns41_http.so"
      Init fn="as_init" 
           bootstrap.properties="/opt/IBM/WebSphere/AppServer/profiles/default/config/
             cells/sa_cell/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml"
      

      Remote example:

      Init fn="load-modules" 
           funcs="as_init,as_handler,as_term" 
           shlib="/opt/IBM/WebSphere/Plugins/bin/libns41_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=
           "C:\IBM\WebSphere\AppServer\profiles\custom01\config\cells\
              dmgrcell\nodes\managed_node\servers\webserver1\plugin-cfg.xml"
      
      

      Local stand-alone 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\AppServer\profiles\default\config\cells\
               sa_cell\nodes\webserver1_node\servers\webserver1\plugin-cfg.xml"
      
      

      Remote 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 Sun Java System Web Server on an HP-UX machine, it is necessary to manually set the SHLIB_PATH variable to /usr/lib before starting Sun Java System 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 Sun Java System Web Server

    export SHLIB_PATH=/usr/lib:$SHLIB_PATH
    

  3. Disable the feature of Sun Java System Web Server V6.1 that supports servlets and JavaServer Pages files by default. Disable this feature so that the WAS 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)"
      
      

 

Result

This procedure results in editing and reconfiguring the Sun Java System Web Server.

 

What to do next

After configuring a Web server, one can install applications on it. See the Applications section of the information center for more information.


 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.