This procedure describes installing a Web server and its plug-in on a machine where the default profile is a custom profile.
Before you begin
This procedure configures the custom profile that is the default profile on the machine. This procedure assumes that you already have installed a deployment manger on Machine A.
The WebSphere Application Server node on Machine B is the custom node that you create in this procedure. This procedure starts the deployment manager and federates the custom node before installing the Web server plug-ins.
Start the deployment manager. The deployment manager must be running to successfully federate and configure the custom node.
Why and when to perform this task
Use the following procedure to install the Web server plug-in, configure the Web server, and create a Web server definition in the default custom profile (custom node).
Steps for this task
umaskTo set the umask setting to 022, issue the following command:
umask 022
For example, on some Windows systems, click Administrative Tools > Local Security Policy > User Rights Assignments to see the advanced options. See your Windows documentation for more information.
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.
When
installing the WebSphere Application Server as a Windows service, do not use
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, or do not
choose to install Windows services.
Click Servers > Applications servers > New and follow the instructions to create a server. A server is not required for installing the plug-ins but it lets you verify the functionality of the Web server.
The DefaultApplication includes the snoop servlet. The verification step uses the snoop servlet.
Use the stopServer command or the administrative console of the deployment manager to stop the managed node.
See Installing IBM HTTP Server or refer to the product documentation for your Web server for more information.
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. A known problem in the wizard panel causes the English word None to appear in translated versions of the wizard. However, the selectable option is functional in every locale in spite of the missing translation.
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.
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 in the configuration script for the application server to name the Web server definition.
See Configuration behavior of the Plug-ins installation wizard for a description of the logic that determines what path is configured by default. The wizard determines the characteristics of the managed application server node to determine the best path for the file:
WAS_install_root/profiles/profile_name /config/cells/cell_name/nodes/ node_name_of_custom_profile/servers/ Web_server_name/plugin-cfg.xml
Accept the default value.
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 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 /opt/IBM/WebSphere/Plugins directory. The /opt/IBM/WebSphere/Plugins/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 plug-ins_install_root/logs directory. Correct any problems and reinstall.
Log files from the installation are in the plug-ins_install_root/logs/install directory.
You can use the administrative console of the deployment manager to create the Web server definition on a federated node. Or, you can run the configuration script that the Plug-ins installation wizard created.
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 you have enabled security or changed the default JMX connector type, edit the script and include the appropriate parameters on the wsadmin command.
Shell scripts on some operating systems cannot contain double-byte characters or single-byte characters with pronunciation keys.
If the file path to the Web server includes double-byte characters or single-byte characters with pronunciation keys, such as o-umlaut (a diacritic mark over the o), c-cedilla (a mark is under the c), or characters with other keys, the script might not run correctly. Copy the content of such a script to the command line and run the wsadmin command directly.
To configure Domino, you must set the WAS_PLUGIN_CONFIG_FILE
environment variable. On Linux and UNIX-based platforms, 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_install_root/notesdata directory on Linux and UNIX systems.
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.
"Could not connect to IHS Administration server error"
See Fast paths for WebSphere Application Server for help in deploying applications.
Identify the same managed node each time. Give each Web server a different nick name.
Result
This procedure results in the installation of the Web server plug-ins for WebSphere Application Server on a Web server machine. The Plug-ins installation wizard creates a Web server definition within the managed node.
The Plug-ins installation wizard configures the Web server to use the plugin-cfg.xml file that is within the managed custom node.
The deployment manager regenerates the Web server plug-in configuration file, plugin-cfg.xml whenever an event occurs that affects the file. Such events include the addition or removal of an application, server, or virtual host.
was_install_root/profiles/profile_name /config/cells/cell_name/nodes/ node_name_of_custom_node/servers/ Web_server_name/plugin-cfg.xml
What to do next
After installing the binary plug-in for the local Web server, you can start the managed node and the Web server after running the configuration script that completes the installation.
See Configuration behavior of the Plug-ins installation wizard for information about the location of the plug-in configuration file.
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.
Related concepts
Configuration behavior of the Plug-ins installation wizard