This procedure describes installing a web server and its plug-in on a machine that
contains a deployment manager and a managed node.
Before you begin
When multiple profiles exist, you can select the profile that the Web Server
Plug-ins Configuration Tool configures. See Plug-ins
configuration for a description of the flow of logic that determines how to select the
profile to configure.
This procedure configures the deployment manager profile on the machine. A managed
node must exist to define a web server definition, which is always on a managed node.
Start the deployment manager and the node agent for the managed node. The deployment manager and
the node must be running to successfully change its configuration.
About this task
Use this procedure to install the web server plug-in, configure the web server, and create a web
server definition.
Procedure
-
Log on to the operating system.
If you are installing as a nonroot or non-administrative user, then there are certain
limitations.
When installing as an administrative user on a Windows operating system, a Windows service is automatically created to autostart the application server. The installer
user account must have the following advanced user rights:
- Act as part of the operating system
- Log on as a service
For example, on some Windows operating systems,
click
Control Panel > Administrative Tools > Local Security Policy > Local Policies >
User Rights Assignments to set the advanced options. See your Windows operating system documentation for more information.
If you plan to run the application server as a Windows service, do not install from a user ID that contains spaces. A user
ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To
work around this restriction, install with a user ID that does not contain spaces.
- Install IBM® Installation Manager.
- Use Installation Manager to install the WebSphere® Application Server Network Deployment product.
- Create a deployment manager profile as the first profile on the machine.
- Create a standalone application server or custom profile, and federate the
node.
- Use Installation Manager to install the following:
- Web Server Plug-ins for WebSphere Application
Server
- Websphere Customization Toolbox
- Use Installation Manager to install IBM HTTP
Server, or install another supported web server.
- Open the WebSphere Customization Toolbox and
launch the Web Server Plug-ins Configuration Tool.
- Select a web server plug-in runtime location.
If the location of a previously installed web server plug-in that you want to use is not in the
list, perform the following actions to add the location to your working set:
- Click Add.
- Enter a name for the web server plug-in location.
- Perform one of the following actions:
- Enter the location.
- Click Browse, find the location, and click OK.
- Click Create.
- Select the type of web server that you are configuring, and click
Next.
- Select the architecture of your installed target web server (64 bit or 32 bit) and click
Next if you are asked.
- Click Browse to select the configuration file or files for your
web server, verify that the web server port is correct, and then click Next
when you are finished.
Select the file and not just the directory of the file. Some web servers have two configuration
files and require you to browse for each file.
The following list shows configuration files for supported web servers:
- Apache HTTP Server
- apache_root/config/httpd.conf
- Domino® Web Server
- names.nsf and Notes.jar
The wizard prompts for the
notes.jar file. The actual name is Notes.jar.
The Web Server Plug-ins Configuration Tool verifies that the files exist but the tool
does not validate either file.
- IBM HTTP Server
- IHS_root/conf/httpd.conf
- IHS_profile_root/conf/httpd.conf
- Microsoft Internet Information Services (IIS)
- The Web Server Plug-ins Configuration Tool can determine the correct files to edit.
- Sun Java™ System Web Server (formerly Sun ONE Web Server
and iPlanet Web Server) Version 6.0 and later
- obj.conf and magnus.conf
- If you are configuring an IBM HTTP web server
plug-in, perform the following actions.
- Specify a unique name for the web server definition, and click Next.
- Select the configuration scenario.
- Choose the local scenario.
- Perform one of the following actions:
- Enter the installation location of WebSphere
Application Server (app_server_root).
- Click Browse, find the installation location of WebSphere Application Server (app_server_root), and click OK.
- Click Next.
- Select the profile to configure with the current web server plug-in, and click
Next.
- Review the summary information, and click Configure to begin configuring the web
server, web server plug-in, and profile.
- Verify the success of the installation on the summary panel, and click
Finish.
If a problem occurs and the installation is unsuccessful, examine the logs in the
plugins_root/logs directory. Correct any problems and
re-configure.
-
Domino Web Server only: Set the WAS_PLUGIN_CONFIG_FILE
environment variable.
On platforms such as AIX® or Linux®, sourcing a script to the parent shell allows child processes to
inherit the exported variables. On Windows systems, run
the script as you would run any other command. Sourcing is automatic on Windows systems.
-
Open a command window.
-
Change directories to the plug-ins installation root directory.
-
Issue the appropriate command for the
plugins_root/bin/setupPluginCfg.sh script:
.
plugins_root/bin/setupPluginCfg.sh
(Notice the space between the period
and the installation root directory.)
source
plugins_root/bin/setupPluginCfg.sh
The script is also in the lotus_root/notesdata directory
on operating systems such as AIX or Linux.
Issue the appropriate command for the script before starting the Domino Web Server.
-
From the administrative console of the deployment manager, click System
administration > Save Changes to Master Repository > Synchronize changes with Nodes >
Save.
- Start the Snoop servlet to verify the ability of the web server to retrieve
an application from the application server.
Test your environment by starting your application server, your web server, and using the Snoop
servlet with an IP address.
- Start the application server.
In a Network Deployment
environment, the Snoop servlet is available in the cell only if you included the DefaultApplication
when adding the application server to the cell. The -includeapps option for the
addNode command migrates the DefaultApplication to the cell. If the application
is not present, skip this step.
- Start the IBM HTTP Server or the web server that
you are using.
Use either the 2001 page or use the STRTCPSVR SERVER(*HTTP)
HTTPSVR(instance_name ) command to start the IBM HTTP Server.
Use a command window to change the directory to the IBM HTTP Server installed image, or to the installed image of your web server.
Issue the appropriate command to start the web server, such as these commands for IBM HTTP Server:
To start the IBM HTTP Server from the
command line:
Access the
apache and
apachectl commands in
the
IBMHttpServer/bin directory.
- Point your browser to http://localhost:9080/snoop to test the
internal HTTP transport provided by the application server. Point your browser to
http://Host_name_of_Web_server_machine/snoop to test the web
server plug-in.
The HTTP Transport port is 9080 by default and must be unique for every profile. The port is
associated with a virtual host named default_host, which is configured to host the installed
DefaultApplication. The Snoop servlet is part of the DefaultApplication. Change the port to match
your actual HTTP Transport port.
- Verify that Snoop is running.
Either Web address should display the Snoop Servlet - Request/Client Information page.
Results
The installation of the Web Server Plug-ins results in the creation of the
Plugins directory and several subdirectories. The following directories are
among those created on a Linux system, for example:
- plugins_root/bin contains the binary plug-ins for all
supported web servers
- plugins_root/logs contains log files
- plugins_root/properties contains version
information
The Installation Manager configures the web server to use the
plugins_root/plugin-cfg.xml file.
What to do next
After installing the binary plug-in for the local Web server, you must create a managed node
before you can successfully run the configuration script and use the web server.
See Plug-ins configuration for an overview of the installation procedure.
See Web server configuration for more information about the files involved in
configuring a web server.
See Editing web server configuration files for information about how the Web Server Plug-ins
Configuration Tool configures supported web servers.
See Installing and configuring web server plug-ins for information about other installation scenarios for
installing Web server plug-ins.