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.
Before you begin
The Web Server Plug-ins Configuration Tool configures the web server plug-in. This topic
describes how to configure the Oracle iPlanet 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.
About this task
Configure the Sun ONE Web Server 6.0 or Oracle iPlanet Web Server, Version 6.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.
Procedure
- 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.
- Add two directives to the obj.conf file after the
<Object name=default> tag:
Service fn="as_handler"
AddLog fn="as_term"
- 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"
- 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
- 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:
- Remove or comment out the following two lines from the obj.conf
configuration file:
NameTrans fn="ntrans-j2ee" name="j2ee"
Error fn="error-j2ee"
- 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)"
- 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.
Results
This procedure results in editing and re-configuring the Oracle iPlanet Web Server.
What to do next
After configuring a web server, you can install applications on it. See the Applications section
of the documentation for more information.
Tip: To unconfigure a web server, reverse the manual steps and remove what was manually
added in this procedure.