This topic describes common installation scenarios and links to
component installation procedures for each scenario.
Before you begin
The primary production configuration is an application server on
one machine and a Web server on a separate machine. This configuration is
referred to as a remote configuration. Contrast the remote
configuration to the local configuration, where the application server and
the Web server are on the same machine.
Guidelines for installing the Microsoft® Internet Information Server (IIS) 7 plug-in on Microsoft Windows Vista™ and Windows 2008 operating systems: WebSphere
® Application Server Version 6.1.0.9
and later support IIS 7 in IIS 6 compatibility mode. If you want to
install the IIS 7 Web server plug-in on the Microsoft
® Windows
® Vista
operating system, you must perform the following actions.
- Install the IIS 6 Management Compatibility component into IIS
7.
Note: This component is not automatically installed by default
because it is not normally used by IIS 7. It is there for backward
compatibility.
Use the following procedure to install the
IIS 6 Management Compatibility component into IIS 7:
- To open the Windows Vista
Control Panel, go to one of the following (depending on your personal
settings for the Start menu):
- Start > Control Panel
- Start > Settings > Control Panel
- Go to Programs and Features.
- In Classic View, this is located in the main Control Panel folder.
- In Control Panel Home, it is located at Programs > Programs
and Features.
- In the left-hand navigation frame, click Turn Windows features on or off.
- If the User Account Control dialog appears, click Continue.
- When the Windows Features
dialog appears, make sure that the following options are selected:
- Internet Information Services
- Web Management Tools
All default options, plus the following
options:
- IIS 6 Management Compatibility
- IIS 6 Management Compatibility
- IIS 6 Management Console
- IIS 6 Scripting Tools
- IIS 6 WMI Compatibility
- IIS Metabase and IIS 6 configuration compatibility
- IIS Management Console
All default options
- World Wide Web Services
All default options, plus the following
options:
- Application Deployment Features
- ISAPI Extensions
- ISAPI Filters
- Click OK to enable the selected options.
- Take the following actions when you install the IIS 7 Web server
plug-in using the Windows installer
provided with WebSphere Application
Server:
- To start the Web server plug-in installer, right click its shortcut
and select Run as Administrator.
- Accept all of the security dialogs that are presented.
- Select Microsoft Internet
Information Services V6.
- If necessary, configure a Web server definition as described in Plug-ins configuration.
- Make sure that you have installed a service pack containing Websphere
Application Server Version 6.1.0.9 or later.
- Perform the following actions:
- Open a command window.
- Change to the plugins_root/bin directory.
- Run the postConfigureIIS7.bat script.
For
example:
c:\plugins_root\bin> postConfigureIIS7.bat
-plugin.home c:\WebSphere\Plugins
-webserver.name webserver2
-webserver.site "Plugin Web Site"
To install and configure the IIS 7 plug-in
on Windows 2008, see Configuring Microsoft Internet Information Services (IIS).
- Set up a remote Web server installation.
The remote Web server configuration is recommended for production
environments.
The remote installation installs the Web server plug-in
on the Web server machine when the application server is on a separate machine,
such as shown in the following graphic:

Remote
installation scenario
Step |
Machine |
Task |
1 |
A |
Install Network Deployment and create an application
server profile. See Installing the product and additional software. |
2 |
B |
Install IBM HTTP Server or another supported Web server.
|
3 |
B |
Install the binary plug-in module using the Plug-ins
installation wizard. See Configuring a Web server and an application server on separate machines (remote). The script
for creating and configuring the Web server is created under the plugins_root/
bin directory.
|
4 |
B |
Copy the configureweb_server_name script
to Machine A. If one machine is running under an operating system such as
AIX or Linux and the other machine is running under Windows, copy the script
from the plugins_root/
bin/ crossPlatformScripts directory. |
5 |
A |
Paste the configureweb_server_name script
from Machine B to the app_server_root/
bin directory on Machine A. |
6 |
A |
Run the script from a command line. |
7 |
A |
Verify that the application server is running. Open
the administrative console and save the changed configuration. |
8 |
B |
Run the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before starting a Domino Web server.
Otherwise,
start the Web server. |
9 |
B |
Run
the Snoop servlet. To verify with your own application, regenerate
and propagate the plugin-cfg.xml file after installing
the application.
|
Regeneration of the plugin-cfg.xml file
During
the installation of the plug-ins, the temporary plugin-cfg.xml file
is installed on Machine B in the plugins_root/
config/ web_server_name directory.
The Web server plug-in
configuration service regenerates the plugin-cfg.xml file
automatically.
To use the real plugin-cfg.xml file
from the application server, propagate the plugin-cfg.xml file
as described in the next section.
Propagation of the plugin-cfg.xml file
The
Web server plug-in configuration service propagates the plugin-cfg.xml file
automatically for IBM HTTP Server only.
For all other Web servers,
propagate the plug-in configuration file manually. Copy the plugin-cfg.xml file
from the profile_root/
config/ cells/ cell_name/ nodes/ web_server_name_node/
servers/ web_server_name directory on Machine
A. Paste the file into the plugins_root/
config/ web_server_name directory on Machine
B.
- Set up a local Web server configuration.
The local Web server configuration is recommended for a development
or test environment.
A local installation includes the Web server plug-in,
the Web server, and the application server on the same machine:

Local
installation scenario
Step |
Machine |
Task |
1 |
A |
Install the Network Deployment product and create an
application server profile. See Installing the product and additional software. |
2 |
A |
Install the IBM HTTP Server, or another supported Web
server. |
3 |
A |
Install the binary plug-in module using the Plug-ins
installation wizard. See Configuring a Web server and an application server profile on the same machine. The Web server
definition is automatically created and configured during the installation
of the plug-ins.
|
4 |
A |
Verify that the application server is running. Open
the administrative console and save the changed configuration. |
5 |
A |
Run the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before starting a Domino Web server.
Otherwise,
start the Web server. |
6 |
A |
Run
the Snoop servlet. To verify with your own application, regenerate
and propagate the plugin-cfg.xml file after installing
the application.
|
Regeneration of the plugin-cfg.xml file
The
Web server plug-in configuration service regenerates the plugin-cfg.xml file
automatically.
The plugin-cfg.xml file is generated
in the profile_root/config/cells/cell_name/nodes/web_server_name_node/servers/web_server_name directory. The
generation occurs when the Web server definition is created.
Propagation
of the plugin-cfg.xml file
The local file does not require propagation.
-
Set up a remote Web server installation in a cell.
The
remote Web server configuration is recommended for production environments.
The
remote installation installs the Web server plug-in on the Web server machine
when the application server is on a separate machine, such as shown in the
following graphic:

Remote installation scenario
Step |
Machine |
Task |
1 |
A |
Install WebSphere Application Server Network Deployment
and create a deployment manager profile. See Installing the product and additional software. |
2 |
A |
Start the deployment manager with the profile_root/bin/
startManager.sh command or its Windows equivalent. |
3 |
B |
Install WebSphere Application Server Network Deployment
and create an application server profile. See Installing the product and additional software. |
4 |
B |
Federate the node with the profile_root/bin/addNode.sh dmgrhost 8879 -includeapps command or its Windows equivalent. |
5 |
C |
Install IBM HTTP Server or another supported Web server.
|
6 |
C |
Install the binary plug-in module using the Plug-ins
installation wizard. See Configuring a Web server and an application server on separate machines (remote). The script for
creating and configuring the Web server is created under the plugins_root/
bin directory.
|
7 |
C |
Copy the configureweb_server_name script
to Machine A. If one machine is running under an operating system such
as AIX or Linux and the other machine is running under Windows, copy the script
from the plugins_root/
bin/ crossPlatformScripts directory.
|
8 |
A |
Paste the configureweb_server_name script
from Machine C to the app_server_root/
bin directory on Machine A. |
9 |
A |
Run the script from a command line after verifying that
the deployment manager is running. If you have enabled security or changed
the default JMX connector type, edit the script and include the appropriate
parameters on the wsadmin command.
|
10 |
A/B |
Use the administrative console of the deployment manager
on Machine A to start the application server on Machine B. Wait for synchronization
to occur and save the new configuration. |
11 |
C |
Run the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before starting a Domino Web server.
Otherwise,
start the Web server. |
12 |
C |
Run
the Snoop servlet. To verify with your own application, regenerate
and propagate the plugin-cfg.xml file after installing
the application.
|
Regeneration of the plugin-cfg.xml file
During
the installation of the plug-ins, the temporary plugin-cfg.xml file
is installed on Machine C in the plugins_root/
config/ web_server_name directory.
The Web server plug-in
configuration service regenerates the plugin-cfg.xml file
automatically.
To use the real plugin-cfg.xml file
from the application server, propagate the plugin-cfg.xml file
as described in the next section.
Propagation of the plugin-cfg.xml
file
The Web server plug-in configuration service propagates the plugin-cfg.xml file
automatically for IBM HTTP Server only.
For all other Web servers,
propagate the plug-in configuration file, by manually copying the plugin-cfg.xml file
from the profile_root/
config/ cells/ cell_name/ nodes/ node_name/
servers/ web_server_name directory on Machine
A to the plugins_root/
config/ web_server_name directory on Machine
C.
-
Set up a local distributed Web server configuration.
The
local Web server configuration is recommended for a development or test environment.
A
local distributed installation includes the Web server plug-in, the Web server,
and the managed application server on the same machine:

Local
distributed installation scenario
Step |
Machine |
Task |
1 |
A |
Install WebSphere Application Server Network Deployment
and create a deployment manager profile. See Installing the product and additional software. |
2 |
A |
Start the deployment manager with the profile_root/
bin/ startManager.sh command or its Windows equivalent. |
3 |
B |
Install WebSphere Application Server Network Deployment
and create an application server profile. See Installing the product and additional software. |
4 |
B |
Federate the node with the profile_root/bin/addNode.sh dmgrhost 8879 -includeapps command or its Windows equivalent. |
5 |
B |
Install IBM HTTP Server or another supported Web server.
|
6 |
Bˋ |
Install the binary plug-in module using the Plug-ins
installation wizard. See Configuring a Web server and an application server profile on the same machine. The script for
creating and configuring the Web server is created in the plugins_root/
bin directory.
|
7 |
B |
After verifying that the deployment manager is running
on Machine A, run the configureweb_server_name script
from a command line in the app_server_root/
bin directory on Machine B. If you have enabled security or
changed the default JMX connector type, edit the script and include the appropriate
parameters.
|
8 |
A/B |
Use the administrative console of the deployment manager
on Machine A to start the application server on Machine B. Wait for synchronization
to occur and save the new configuration. |
9 |
B |
Run the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before starting a Domino Web server.
Otherwise,
start the Web server. |
10 |
B |
Run
the Snoop servlet. |
Regeneration of the plugin-cfg.xml file
The
Web server plug-in configuration service regenerates the plugin-cfg.xml file
automatically.
The plugin-cfg.xml file is generated
at the location profile_root/
config/ cells/ cell_name/ nodes/ node_name/
servers/ web_server_name directory, when the
Web server definition is created.
Regenerate the plugin-cfg.xml file
in the Web server definition in the application server whenever the configuration
changes. The Web server has immediate access to the file whenever it is regenerated.
When the Web server plug-in configuration service (an administration
service) is enabled on Machine A, the plugin-cfg.xml file
is automatically generated for all Web servers.
Propagation of the plugin-cfg.xml file
Node
synchronization is used to propagate the plugin-cfg.xml file
from Machine A to Machine B.
When the Web server plug-in configuration
service (an administration service) is enabled on Machine A, the plugin-cfg.xml file
is automatically propagated for all Web servers.
Alternate configuration
This
procedure describes installing the plug-ins on two machines. However, you
can perform this procedure on a single machine as shown in the following graphic.
A local distributed installation also includes the Web server plug-in, the
Web server, the Application Server, and the deployment manager on the same
machine:
