This topic describes installing a Web server plug-in and configuring an application server that is not the default profile.
When multiple profiles exist, the plug-ins installer configures only the default profile. You need the configureweb_server_name script to configure a non-default profile. See Plug-ins configuration for a description of the flow of logic that determines how the installer selects the profile to configure.
If you intend to create a Web server definition for an application server that is not the default profile, you must force the Plug-ins installation wizard to configure a profile that is not the default profile.
This procedure assumes that you have installed the Web server on one machine and the WebSphere Application Server product on a separate machine. This procedure also works when the Web server and the application server profile are on the same machine. In such a case, select the Remote installation type when installing the plug-ins so that the Plug-ins installation wizard creates the configuration script for the application server.
This procedure describes how to create a Web server definition for an application server that is not the default profile. This procedure describes selecting a remote installation scenario and issuing a command for the configuration script that points the command to a profile that you select.
The ordinary behavior of the configuration script is to work on the default profile on the machine where the script runs. This procedure describes how to redirect the script to configure a profile that is not the default.
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.
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.
Look for the appropriate log file for information about missing prerequisites. If you stop the installation, see the temporaryPluginInstallLog.txt file in the temporary directory of the user who installed the plug-ins. For example, the /tmp/temporaryPluginInstallLog.txt file might exist if the root user installed the plug-ins on an operating system such as AIX or Linux.
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.
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.
$AdminTask deleteServer { -serverName webserver1 -nodeName webserver1_node } $AdminTask removeUnmanagedNode { -nodeName webserver1_node } $AdminConfig saveIn these commands, webserver1 is the Web server name.
For a stand-alone application server node, the application server creates the file in the profile_root /config/cells/ cell_name /nodes/ web_server_name_node/servers/ web_server_name /plugin-cfg.xml file path.
Specify the location in the field so that the Web server can access the file when the Web server and the application server are on the same machine. Accept the default value if the Web server and the application server are on separate machines.
The location of the plugin-cfg.xml file is used in the Web server configuration file. If you cannot enter the location correctly at this point, you can edit the Web server configuration file manually to correct the location so that the location points to the plugin-cfg.xml file in the non-default application server profile. On a remote installation, the default location is within the plug-ins installation root directory. Propagation copies the current file from the application server machine to the Web server machine.
The panel notifies you that you have manual steps to perform to complete the installation and configuration. The type of Web server, the nickname of the Web server, and the location of the plugin-cfg.xml file displays on the panel.
The Plug-ins installation wizard creates the configureweb_server_name script in the plugins_root/bin/ directory.
The Plug-ins installation wizard also creates a default plugin-cfg.xml file in the plugins_root/config/web_server_name directory.
The panel specifies the plug-ins installation root directory, the Web server plug-ins feature, and the disk size of the code that installs when you click Next.
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.
For example, on a Linux system with an IBM HTTP Server named webserver1 in the default location, copy /opt/IBM/WebServer/Plugins/bin/configurewebserver1.sh to the /opt/IBM/WebSphere/AppServer/bin directory on the application server machine.
The content of the configureweb_server_name.bat script or the configureweb_server_name.sh script can be corrupt if the default file encoding of the two machines differs. This scenario is possible when one machine is set up for a double-byte character set (DBCS) locale and the other machine is not.
Determine the file encoding and use one of the following procedures to circumvent the failure. To determine the default file encoding, run the appropriate command.
locale
CHCP
Procedures for compensating for encoding differences
Suppose that the Web server is running on a Linux machine and Network Deployment is running on a Windows machine.
Web server running on a system such as AIX or Linux
iconv -f web_server_machine_encoding \ -t application_server_machine_encoding \ configureweb_server_name.batOmit the continuation characters (\) if you enter the command on one line.
Suppose that the Web server is running on a Windows machine and Network Deployment is running on a machine with a system such as AIX or Linux.
Web server running on a Windows machine
iconv -f web_server_machine_encoding \ -t application_server_machine_encoding \ configureweb_server_name.shOmit the continuation characters (\) if you enter the command on one line.
If the conversion mapping is not supported by the iconv command on your system, copy the contents of the Web server configuration script to a clip board and paste it onto the machine where the application server is running.
wsadmin -profileName profile_name_of_the_non-default_profile -f configureWebserverDefinition.jacl ...
Open a command window to run the script that you copied to Machine A.
As soon as the Web server definition is created, the application server creates a plugin-cfg.xml file for the Web server. For example, the file on a Linux system might have the following file path: profile_root/config/cells/cellname/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml
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"
This procedure results in the installation of the Web server plug-ins for WebSphere Application Server on a Web server machine. After modification, the resulting script creates a Web server definition for an application server that is not the default profile. The Plug-ins installation wizard also configures the Web server to support the application server.
If you can see the Snoop servlet through the Web server, you have successfully configured the Web server and the application server.
After configuring a Web server and creating a Web server definition, you can deploy applications and serve them through the Web server. See Fast paths for WebSphere Application Server to get started deploying applications.
In this information ... | IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |