WAS v8.5 > Set up intermediary services > Implement a web server plug-in > Edit web server configuration files

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.0 and later.

The Web Server Plug-ins Configuration Tool configures the web server plug-in. This topic describes how to configure the Sun Java System Web Server if you must change something in the existing configuration. Other procedures in Edit web server configuration files describe configuring other supported web servers. Configure the Sun ONE Web Server 6.0 or Sun Java System Web Server, v6.1 and later.

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.

  1. Configure entries in the obj.conf configuration file and in the magnus.conf configuration file for v6.0 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 we have configured the system. If the Web server and the application server are on separate machines, we have a remote installation.

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

      The following examples reference the libns61_http.so file, which is only supported for the Sun Java System Web Server 7.0 and 6.1. If we are using a Sun ONE Web Server 6.0, change these references to libns41_http.so. gotcha


        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"


      • 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 JSP files by default. Disable this feature so 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)"

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


Results

This procedure results in editing and re-configuring the Sun Java System Web Server.

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

To unconfigure a web server, reverse the manual steps and remove what was manually added in this procedure.


+

Search Tips   |   Advanced Search