- Accept the default location for the installation root
directory for the plug-ins. Click Next.
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.
Restriction: The installation directory cannot contain any unsupported
characters. See "Object names: what the name string cannot contain"
for more information.
A possibility exists that the Web server
might run on a platform that WebSphere Application Server does not
support.
- Click Browse to select the configuration
file 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 Plug-ins installation
wizard verifies that the files exist but the wizard does not validate
either file.
- IBM HTTP Server
- IHS_root/conf/httpd.conf
- Microsoft Internet Information Services (IIS)
- The Plug-ins installation wizard can determine the correct files
to edit.
- Sun ONE Web Server 6.0 or Sun Java System Web Server, Version
6.1
- obj.conf and magnus.conf
The wizard displays a naming panel for the nickname
of the Web server definition.
- Specify a nickname for the Web server. Click Next when
you are finished.
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.
If the
application server profile already has a Web server definition, delete
the Web server definition before continuing. Use the following commands
to delete the Web server definition:
$AdminTask deleteServer { -serverName webserver1 -nodeName webserver1_node }
$AdminTask removeUnmanagedNode { -nodeName webserver1_node }
$AdminConfig save
In these commands,
webserver1 is the
Web server name.
- Type a value for the location of the plugin-cfg.xml file.
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.
- Identify the host name or IP address of the application
server machine, then click Next.
- Examine the summary panel. Click Next when
you are finished.
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.
- Click Next on the pre-installation
summary panel to begin the installation or click Back to
change any characteristics of the installation.
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.
- After the wizard installs the code and creates the uninstaller
program, examine the post-installation summary panel. Click Next when
you are finished to display the Plug-ins installation roadmap.
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.
- Close the road map and click Finish to
exit the wizard.
Log files from the installation are
in the plugins_root/logs/install directory.