This topic describes common installation scenarios and links to
component installation procedures for each scenario.
- 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
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
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.
See Installing the product and additional software
. |
2 |
A |
Create a deployment manager profile. See Creating profiles through the graphical user interface
. |
3 |
A |
Start the deployment manager with the profile_root/bin/
startManager.sh command or its Windows equivalent. |
4 |
B |
Install WebSphere Application Server Network Deployment.
See Installing the product and additional software
. |
5 |
B |
Create an application server profile. See Creating profiles through the graphical user interface
. |
6 |
B |
Federate the node with the profile_root/bin/addNode.sh dmgrhost 8879 -includeapps command or its Windows equivalent. |
7 |
C |
Install IBM HTTP Server or another supported Web server.
|
8 |
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.
|
9 |
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.
|
10 |
A |
Paste the configureweb_server_name script
from Machine C to the app_server_root/
bin directory on Machine A. |
11 |
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.
|
12 |
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. |
13 |
C |
Run the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before starting a Domino Web server.
Otherwise,
start the Web server. |
14 |
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. |
2 |
A |
Create a deployment manager profile. |
3 |
A |
Start the deployment manager with the profile_root/
bin/ startManager.sh command or its Windows equivalent. |
4 |
B |
Install WebSphere Application Server Network Deployment. |
5 |
B |
Create an application server profile. |
6 |
B |
Federate the node with the profile_root/bin/addNode.sh dmgrhost 8879 -includeapps command or its Windows equivalent. |
7 |
B |
Install IBM HTTP Server or another supported Web server. |
8 |
B |
Install the binary plug-in module using the Plug-ins
installation wizard. The script for creating and configuring the Web server
is created in the plugins_root/
bin directory.
|
9 |
B |
After verifying that the deployment manager is running
on Machine A, run the configureweb_server_name script
from a command line in the plugins_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.
|
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 |
B |
Run the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before starting a Domino Web server.
Otherwise,
start the Web server. |
12 |
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:
