Editing web server configuration files
Edit web server configuration files to configure a web server.
Before you begin
The Web Server Plug-ins Configuration Tool configures supported web servers. Use this topic to understand how the tool configures the web server configuration files.
If you must change a configuration for some reason, you can run the Web Server Plug-ins Configuration Tool again to re-configure the web server or you can edit the files.
- The plugin-cfg.xml and plugin-key.kdb properties on the Servers > Server Types > Web servers > web_server_name > Plug-in Properties page of the administrative console are grayed-out because they cannot be edited.
- After the web server definition is created, the /config/webserver_name value that is appended to the end of plugins_root cannot be edited.
To support a nondefault profile, edit the configuration to point the web server to the correct location of the plug-in configuration file (plugin-cfg.xml). In this case, you would change the profile path from the default profile to the secondary profile.
- For Apache-based web servers, including IBM® HTTP Server,
you can determine the architecture using the following techniques:
- Run the
command:
apachectl -V | grep Architecture
This command displays the Architecture value for the web server, which will be either 32-bit or 64-bit.
- Run the following command from the
IBM_HTTP_Server_install_root\bin
directory:
apache -V
Look for the value of the
Architecture:
line in the output. This value is either 32-bit or 64-bit.
- Run the
command:
- For other, non-Apache based web servers, use the following techniques. These techniques also
work for Apache-based web servers.
- Run the file command against the primary
web server application executable file to display its type. For example, run the following command
on an AIX®
system:
file /usr/bin/httpd
This command results in the following output:- For a 64-bit web server:
httpd: 64-bit XCOFF executable ...
- For a 32-bit web server:
httpd: executable (RISC System/6000)...
64
in the output, then the application is 32-bit application. - For a 64-bit web server:
- Open the Microsoft Windows Task Manager when the server is running and locate the server in the process list. A 32-bit application has *32 after its name.
- Run the file command against the primary
web server application executable file to display its type. For example, run the following command
on an AIX®
system:
If the web server application uses a 64-bit architecture, the plug-in library should be loaded from the plugin_root/bin/64bit directory. If the web server application uses a 32-bit architecture, the plug-in library should be loaded from the plugin_root/bin/32bits directory. If the plugin_root/bin/64bits directory does not exist, you must use the 32-bit architecture.
About this task
This task points you to information on editing web server configuration files. Select a link appropriate for your web server.
Procedure
- Configure Apache HTTP Server 2.2 or 2.4. See Configuring Apache HTTP Server V2.2 or V2.4.
- Configure Lotus® Domino® Web Server Version 5 and Version 6.x. See Configuring Lotus Domino.
- Configure IBM HTTP Server powered by Apache 2.x.
- Configure IBM HTTP Server. See Configuring IBM HTTP Server.
- Configure Microsoft Internet Information Services (IIS). See Configuring Microsoft Internet Information Services (IIS).
- Configure Sun Java™ System Web Server (formerly Sun ONE and iPlanet). See Configuring the Sun Java System Web Server.
Results
You can use the Web Server Plug-ins Configuration Tool to configure supported web servers. You can also configure a web servers by editing its configuration.