Consider common installation scenarios for Network Deployment to
determine how to install your application serving environment. This topic
links to procedures for installing each scenario.
Before you begin
IBM WebSphere Application Server Network Deployment is an integrated
platform that contains an application server, Web development tools, a Web
server, and additional supporting software and documentation.
In Version 6.1, installation of WebSphere Application Server
Network Deployment typically performs two actions. First the installation
wizard installs a shared set of core product files. Second, the installation
wizard optionally creates a profile.
A profile is a separate data partition
that includes the files that define a runtime environment for an application
server process, such as a deployment manager or an application server.
A running application server process can create,
read, update, or delete the configuration files, data files, and log files
in its profile. The application server process can access the system files,
which include command files and other shared product binary files. However,
most system files are updated only by installing fix packs, interim fixes,
or products that extend Network Deployment.
During installation, you
can choose to create an application server profile, a deployment
manager profile, a cell set of profiles which
contains a deployment manager and a federated application server, or a custom
profile. The installation wizard also has an option not to create
a profile during installation. However, at least one profile must exist to
have a functioning application server environment.
Avoid trouble: It
is suggested that you configure WebSphere Application Server Network Deployment
with a single subnet for network traffic. You can use one Network interface
card (NIC) on a physical machine or logical partition (LPAR). You can also
reference a single Domain name system (DNS) server in the network configuration
for the physical machine or LPAR.
gotcha
After installation,
use the Profile Management Tool to create additional profiles.
Scenarios
for installation
The following information describes scenarios for
installing the product in various topologies on one or more machines. Two
types of WebSphere Application Server topologies are possible using the Network
Deployment product:
- Topologies for a stand-alone application server
- Each stand-alone application server has its own administrative console
and runs independently of other application servers.
The following topologies
are described in this topic.
- Topologies for a managed group of application servers in a cell
- A cell consists of one deployment manager and one or
more federated application servers that are managed nodes.
A
node can become a managed node in several ways:
- By creating the cell with a federated node during installation
- By federating the node within an application server profile into the cell
- By federating the node within a custom profile into the cell
The deployment manager is the single point of administration for
all of the managed nodes in the cell. The deployment manager maintains the
configuration files for nodes that it manages and deploys applications to
those managed nodes.
The following topologies for a cell are described
in this topic.
Scenarios 5, 6, 7, and 8 assume that all nodes in a cell reside
on a particular machine and operating system. However, this precise node assignment
does not need to apply. The deployment manager node can exist on Machine A,
other managed nodes (that have been federated into the deployment manager)
can exist on differing machines and operating systems. Such a configured cell
of differing machines or operating systems is called a heterogeneous cell and
expands the possible topologies you can consider for your network deployment.
About this task
Each of the following scenarios includes a diagram and a list
of detailed installation steps.
Some scenarios are more typical in
production environments. For example, Scenario 1 supports a lighter workload
than Scenario 3 or Scenario 4. However, Scenario 1 is a fully functional environment.
Scenarios 3 and 4 are typical production environments for a stand-alone application
server. Scenario 8 is a typical production scenario for a cell environment.
- Scenario 1: Install a stand-alone application server
on a single machine.
Installing WebSphere Application Server
Network Deployment by itself on a single machine lets you create a stand-alone
Application Server profile. Each stand-alone application server profile includes
a server1 application server process. Installing Network Deployment creates
the set of system files.
The Profile Management Tool
creates the profile for the application server. The profile is a separate
data partition with files that define the stand-alone Application Server environment.
In this
scenario, the application server uses its internal HTTP transport chain for
communication instead of a using a separate web server (on a separate machine)
to possibly offload some processing.
- Install WebSphere Application Server Network Deployment.
Create an application server profile during the
installation.
- Scenario 2: Install a stand-alone application server
and a Web server on a single machine.
Installing a Web server,
such as IBM HTTP Server, on the same machine as the application server provides
more configuration options. Installing a Web server plug-in enables the Web
server to communicate with the application server. This installation scenario
supports rigorous testing environments or production environments that do
not require a firewall. However, this scenario is not a typical production
environment. When everything is on one machine, neither the web server or
the application server will run as fast as if they were on separate machines
because they are both competing for the same CPU resources.

- Install WebSphere Application Server Network Deployment.
Create an application server profile during the
installation.
- Install IBM HTTP Server or another supported
Web server.
While installing IBM HTTP Server, use its installation
wizard to install the Web server plug-ins. After installing IBM HTTP Server,
proceed to step 4.
- If you use another supported Web server or
an existing installation of IBM HTTP Server, use the Plug-ins installation
wizard to install the Web server plug-ins and configure the Web server. Because
the Web server and the application server are on the same machine, the Plug-ins
installation wizard creates a Web server definition and you can skip step
4.
- Create a Web server definition
using the administrative console. Click Servers > Web servers > New.
- Scenario 3: Install a stand-alone application server
and a Web server on separate machines.
In the typical production
environment, the application server on one machine communicates with a Web
server on a separate (remote) machine through the Web server plug-in. Optional
firewalls can provide additional security for the application server machine.
- Install WebSphere Application Server Network Deployment on Machine
A.
Create an application server profile during
the installation.
- Install IBM HTTP Server or another supported
Web server on Machine B. While installing IBM HTTP Server, use its installation
wizard to install the Web server plug-ins.
- If you use another supported Web server or
an existing installation of IBM HTTP Server, use the Plug-ins installation
wizard to install the Web server plug-ins and configure the Web server on
Machine B. The Plug-ins installation wizard creates a script
named configureWeb_server_name in
the plugins_root/bin directory
on Machine B.
- Copy the configureWeb_server_name script
on Machine B to the app_server_root/profile_name/bin directory on Machine A.
- Run the configureWeb_server_name script
on Machine A to create a Web server definition in the administrative console.
You can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file
on Machine A from the application server to the Web server using the administrative
console. Click Servers > Web servers > Web_server_name >
Propagate Plug-in. Web servers other than IBM HTTP Server require
manual propagation.
- Scenario 4: Install multiple stand-alone application
servers on one machine and a Web server on a separate machine.
The Profile Management tool can create a deployment
manager profile, an application server profile, or a custom profile. Each
profile is a separate data partition containing the files that define the
run-time environment. After creating a profile and installing a dedicated
Web server, use the Plug-ins installation wizard to install a plug-in and
to update the Web server configuration file. The Web server can then communicate
with the application server.
This topology lets each profile have unique
applications, configuration settings, data, and log files, while sharing the
same set of system files. Creating multiple profiles creates multiple application
server environments that you can dedicate to different purposes.
For
example, each application server on a Web site can serve a different application.
In another example, each application server can be a separate test environment
that you assign to a programmer or a development team.
Another
feature of having multiple profiles is enhanced serviceability. For example,
when a fix pack updates the system files, all application servers begin using
the updated core product files.

- Install WebSphere Application Server Network Deployment on Machine
A.
Create an application server profile during
the installation.
- Install IBM HTTP Server or another supported
Web server on Machine B. While installing IBM HTTP Server, use its installation
wizard to install the Web server plug-ins.
- If you use another supported Web server or
an existing installation of IBM HTTP Server, use the Plug-ins installation
wizard to install the Web server plug-ins and configure the Web server on
Machine B. The Plug-ins installation wizard creates a script
named configureWeb_server_name in
the plugins_root/bin directory
on Machine B.
- Copy the configureWeb_server_name script
on Machine B to the app_server_root/profile_name/bin directory on Machine A.
- Run the configureWeb_server_name script
on Machine A to create a Web server definition in the administrative console.
You can then use the administrative console to manage the Web server.
- Propagate the plugin-cfg.xml file
on Machine A from the application server to the Web server using the administrative
console. Click Servers > Web servers > Web_server_name >
Propagate Plug-in. Web servers other than IBM HTTP Server require
manual propagation.
- Create subsequent Application Server profiles
using the Profile Management tool on Machine
A.
- Install subsequent IBM HTTP Servers or other
supported Web servers on Machine B. While installing an IBM HTTP Server, use
its installation wizard to install the Web server plug-ins.
- If you use another supported Web server or
an existing installation of IBM HTTP Server, use the Plug-ins installation
wizard to configure each additional Web server on Machine B. Installation
of the Web server plug-ins creates a script named configureWeb_server_name in
the plugins_root/bin directory
on Machine B.
- Copy the configureWeb_server_name script
on Machine B to the app_server_root/profile_name/bin directory on Machine A.
- Run the configureWeb_server_name script
on Machine A to create a Web server definition in the administrative console.
You can then use the administrative console to manage the Web server.
- On Machine A, propagate the plugin-cfg.xml file
from the second application server to the Web server using the administrative
console. Click Servers > Web servers > Web_server_name >
Propagate Plug-in. Web servers other than IBM HTTP Server require
manual propagation.
- Scenario 5: Install a cell
of managed application servers on one machine.
WebSphere Application
Server Network Deployment can create a cell consisting of a deployment manager
and one federated application server node on a single machine. During installation
choose to install the cell set of profiles.
The Profile Management tool can
create other stand-alone application server profiles or custom profiles. You
can use the administrative interface of the deployment manager to federate
the additional servers to the cell.
Stand-alone application server profiles
have their own administrative interface until you federate them into a deployment
manager cell, at which point the administrative interface of the deployment
manager controls the servers, or managed nodes. An application
server profile has a default application server process called server1, and
optionally might include the default application and Sample applications.
A custom profile does not have a default server process nor does it have any
applications.
The deployment manager provides the administration for
all managed nodes that are in its cell. Periodically the configuration and
application files on a managed node refresh from the master copy of the files
hosted on the deployment manager during synchronization.
In
a cell environment, only the managed nodes serve applications, not the deployment
manager. The managed node in this scenario uses its internal HTTP transport
chain for communication, instead of a using a separate web server (on a separate
machine) to possibly offload some processing.

- Install WebSphere Application Server Network Deployment.
Create a cell environment during the installation.
The cell environment creates a deployment manager profile and an application
server profile that is federated to the deployment manager cell.
- Start the deployment manager using its First steps console or
by running the startManager command in the bin directory
of the deployment manager profile, app_server_root/profile_name/bin.
- Start the administrative console of the deployment manager using
its First steps console.
- Start the node agent process by running the startNode command
in the bin directory of the application server profile, app_server_root/profile_name/bin.
- Use the administrative console of the deployment manager to
create and start application server processes. Click Servers > Application
servers > Start.
- Scenario 6: Install a cell
of managed application servers and a Web server on one machine.
Installing
a Web server, such as IBM HTTP Server, on the same machine as the application
server provides more configuration options. Installing a Web server plug-in
is required for the Web server to communicate with the server in the managed
node. This type of installation can support either rigorous testing in a cell
environment or production environments that do not require a firewall.

- Install WebSphere Application Server Network Deployment.
Create a cell environment during the installation.
The cell environment creates a deployment manager profile and an application
server profile that is federated to the deployment manager cell.
- Start the deployment manager using its First steps console or
by running the startManager command in the bin directory
of the deployment manager profile, app_server_root/profile_name/bin.
- Start the administrative console of the deployment manager using
its First steps console.
- Start the node agent process by running the startNode command
in the bin directory of the application server profile, app_server_root/profile_name/bin.
- Use the administrative console of the deployment manager to
create and start application server processes. Click Servers > Application
servers > Start.
- Install IBM HTTP Server or another supported Web server.
While installing IBM HTTP Server, use its installation wizard to
install the Web server plug-ins. After installing IBM HTTP Server, proceed
to step 4.
- If you use another supported Web server or an existing installation
of IBM HTTP Server, use the Plug-ins installation wizard to install the Web
server plug-ins and configure the Web server. Because the Web server and the
application server are on the same machine, the Plug-ins installation wizard
creates a Web server definition and you can skip step 4.
- Create a Web server definition using the administrative
console. Click Servers > Web servers > New.
- Scenario 7: Install a cell
of managed application servers on one machine and a Web server on a separate
machine.
In a typical production environment, a managed node
in a cell communicates with a Web server on a separate (remote) machine through
the Web server plug-in. An optional firewall can provide additional security
for the application server machine.

- Install WebSphere Application Server Network Deployment on Machine
A.
Create a cell environment during the installation. The cell
environment creates a deployment manager profile and an application server
profile that is federated to the deployment manager cell
- Start the deployment manager using its First steps console or
by running the startManager command in the bin directory
of the deployment manager profile, app_server_root/profile_name/bin.
- Start the administrative console of the deployment manager using
its First steps console.
- Start the node agent process by running the startNode command
in the bin directory of the application server profile, app_server_root/profile_name/bin.
- Use the administrative console of the deployment manager to
create and start application server processes. Click Servers > Application
servers > Start.
- On Machine B, install IBM HTTP Server or another supported Web
server.
While installing IBM HTTP Server, use its installation
wizard to install the Web server plug-ins.
- If you use another supported Web server or an existing installation
of IBM HTTP Server, use the Plug-ins installation wizard to configure each
additional Web server on Machine B. Installation of the Web
server plug-ins creates a script named configureWeb_server_name in
the plugins_root/bin directory
on Machine B.
- Copy the configureWeb_server_name script
on Machine B to the app_server_root/profile_name/bin directory on Machine A.
- Run the configureWeb_server_name script
on Machine A to create a Web server definition in the administrative console.
You can then use the administrative console to manage the Web server.
- On Machine A, propagate the plugin-cfg.xml file
from the second application server to the Web server using the administrative
console. Click Servers > Web servers > Web_server_name >
Propagate Plug-in. Web servers other than IBM HTTP Server require
manual propagation.
- Scenario 8: Install a deployment manager on one
machine, multiple managed application server nodes on a second machine, and
a Web server on a third machine.
The primary advantage of a
cell over a stand-alone application server is its scalability. Managing a
cell to keep it in proportion with workload levels is possible. In this scenario,
managed nodes exist on Machine C. All of the managed nodes are federated into
the same deployment manager. Depending on your needs, an application server
in each managed node could serve the same or different applications.
Machine
A and Machine C represent both types of scaling, vertical and horizontal scaling:
- Vertical scaling creates multiple managed nodes on
the same physical machine.
- Horizontal scaling creates cell members on multiple
physical machines.
The managed nodes in this scenario communicate with the same Web
server. However, an alternative strategy could have a dedicated Web server
for each managed node.

- Install WebSphere Application Server Network
Deploymenton Machine A.
Create a deployment manager profile
during the installation.
- Start the deployment manager using its First
steps console or by running the startManager command in
the bin directory of the deployment manager profile, app_server_root/profile_name/bin.
- Install WebSphere Application Server Network
Deployment on Machine C.
Create an application server profile
during the installation.
- On Machine C, start the first application server
using its First steps console or by running the startServer server1 command
in the bin directory of the first application server
profile, app_server_root/profile_name/bin.
- On Machine C, create a second application server
profile using the Profile Management Tool.
- Start the second application server using its
First steps console or by running the startServer server1 command
in the bin directory of the first application server
profile, app_server_root/profile_name/bin.
- On Machine A, add both application server nodes
to the cell using the administrative console of the deployment manager. Click System
Administration > Nodes > Add Node.
- On Machine B, install IBM HTTP Server or another
supported Web server.
While installing IBM HTTP Server, use
its installation wizard to install the Web server plug-ins.
- If you use another supported Web server or
an existing installation of IBM HTTP Server, use the Plug-ins installation
wizard to configure each additional Web server on Machine B. Installation
of the Web server plug-ins creates a script named configureWeb_server_name in
the plugins_root/bin directory
on Machine B.
- Copy the configureWeb_server_name script
on Machine B to the app_server_root/profile_name/bin directory on Machine A.
- Run the configureWeb_server_name script
on Machine A to create a Web server definition in the administrative console.
You can then use the administrative console to manage the Web server.
- On Machine A, propagate the plugin-cfg.xml file
from the second application server to the Web server using the administrative
console. Click Servers > Web servers > Web_server_name >
Propagate Plug-in. Web servers other than IBM HTTP Server require
manual propagation.
What to do next
After determining a possible topology, follow the steps in the
overall procedure.
One step not mentioned in any of these scenarios
is to prepare the operating system for installation. Useful links to the installation
procedures for each installable component are in the list of related topics.