This procedure describes installing a Web server and its plug-in on a machine where the default profile is a deployment manager.
When multiple profiles exist, the plug-ins installer configures only the default profile. See Plug-ins configuration for a description of the flow of logic that determines how the installer selects the profile to configure.
This procedure configures the deployment manager profile that is the default profile on the machine. A managed node must exist to define a Web server definition, which is always on a managed node. If the deployment manager is the default profile, the Plug-ins installation wizard looks for a managed custom node in the deployment manager configuration. If the deployment manager does not have a managed custom node, the Plug-ins installation wizard looks for a managed application server node. If the deployment manager does not have a managed node, then the Plug-ins installation wizard classifies the installation as a remote installation.
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.
Use the following procedure to install the Web server plug-in, configure the Web server, and create a Web server definition in the default profile.
Log on as root on an operating system such as AIX or Linux, or as a member of the administrator group on a Windows system.
umaskTo set the umask setting to 022, issue the following command:
umask 022
The installation wizard
grants your Windows user ID the advanced user rights, if the user ID belongs
to the administrator group. The silent installation does not grant these rights.
If you create a new user ID on a Windows platform to perform a silent installation,
you must restart the system to activate the proper authorizations for the
user ID before you can perform a successful silent installation.
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 problem, install with a user ID that does
not contain spaces.
See Installing IBM HTTP Server or the product documentation for your Web server.
Select the Plug-ins installation wizard from the launchpad or change directories to the plugin directory on the product disc or in the downloaded installation image and issue the install command.
If you are unsure of which installation scenario to follow, display the roadmap instead. Print and keep the roadmap as a handy overview of the installation steps.
Press Ctrl-P to print the roadmap if the Web browser navigation controls and the menu bar are not present on the browser window that displays the Plug-ins roadmap. Press Ctrl-W to close the browser window if the navigation controls and the menu bar do not display. Or close the browser window with the window control in the title bar.
See Troubleshooting installation for more information about log files.
The Plug-ins installation wizard panel prompts you to identify the Web servers to configure. Actually you can select only one Web server each time you run the Plug-ins installation wizard.
Stop any Web server while you are configuring it. A step later in the procedure directs you to start the Web server as you begin the snoop servlet test.
If you select the Web server identification option labeled None, the Web server installs the binary plug-ins but does not configure the Web server.
You can type another new directory or click Browse to select an empty directory. The fully qualified path identifies the plug-ins installation root directory.
The default location is shown in Directory conventions .
A possibility exists that the Web server might run on a platform that WebSphere Application Server does not support.
The fully qualified path identifies the installation root directory for the Network Deployment product core files.
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 wizard prompts for the notes.jar file. The actual name is Notes.jar.
The Plug-ins installation wizard verifies that the files exist but the wizard does not validate either file.
The wizard displays a naming panel for the nickname of the Web server definition.
The wizard uses the value to name configuration folders in the plug-ins installation root directory. The wizard also uses the name within the deployment manager as the name of the Web server definition.
See Plug-ins configuration for a description of the logic that determines what path is configured by default. The wizard determines the characteristics of the deployment manager to determine the best path for the file.
plugins_root/config/ web_server_name/plugin-cfg.xml
Accept the default value.
profile_root /config/cells/cell_name/nodes/ node_name_of_custom_profile/servers/ web_server_name/plugin-cfg.xml
You can use the administrative console of the deployment manger to delete an existing Web server or to create new ones. Federated nodes can have more than one Web server definition.
The wizard begins installing the plug-ins and configuring the Web server and the deployment manager.
The wizard shows an installation status panel as it installs the plug-ins.
The wizard displays the Installation summary panel at the completion of the installation.
The Plug-ins installation wizard installs the binary plug-in module. On a Linux system, for example, the installation creates the plugins_root directory. The plugins_root/config/Web_server_name directory contains the plugin-cfg.xml file.
The wizard displays the name and location of the configuration script and the plugin-cfg.xml file. The wizard also displays the type of Web server that is configured and the nickname of the Web server.
If a problem occurs and the installation is unsuccessful, examine the logs in the plugins_root/logs directory. Correct any problems and reinstall.
Log files from the installation are in the plugins_root/logs/install directory.
You must create an application server profile or a custom profile and federate the node before you can use the administrative console of the deployment manager to create a Web server definition. The same is true for running the configuration script that the Plug-ins installation wizard created. You must assign the Web server to a managed node when you create it.
The managed node must exist before running the Plug-ins installation wizard. Otherwise, the installation is considered a remote installation.
Adding the node starts the nodeagent process. If the node agent is not running for some reason, start the node.
See startNode command for more information.
The script already contains all of the information that you must gather when using the administrative console option.
Click Servers > Web servers > New and use the Create new Web server entry wizard to create the Web server definition.
If the node has only a deployment manager profile, then the plug-ins installer reverts to a remote plug-in configuration. You must manually copy the plugins_root/ bin/ configureweb_server_name.sh script or the plugins_root\ bin\ configureweb_server_name.bat script to the app_server_root/bin directory of the deployment manager to run the script.
If you have enabled security or changed the default JMX connector type, edit the script and include the appropriate parameters on the wsadmin command.
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.
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.
Test your environment by starting your Application Server, your Web server, and using the snoop servlet with an IP address.
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:
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 and any installed Samples. The snoop servlet is part of the DefaultApplication. Change the port to match your actual HTTP Transport port.
Either Web address should display the Snoop Servlet - Request/Client Information page.
Verify that the automatic propagation function can work on a remote IBM HTTP Server by using the following steps. This procedure is not necessary for local Web servers.
"Could not connect to IHS Administration server error"
The Plug-ins installation wizard configures the Web server to use the plugins_root/plugin-cfg.xml file.
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 Plug-ins installation wizard configures supported Web servers.
See Installing Web server plug-ins for information about other installation scenarios for installing Web server plug-ins.