Consider common installation scenarios for the product
to determine how to install your application serving environment.
Before you begin
IBM® WebSphere® Application
Server is an integrated platform
that contains an application server, web development tools, a web
server, and additional supporting software and documentation.
The
installation of the application server product installs a shared set
of core product files. Afterwards, you create at least one profile,
which is a separate data partition that includes the files that define
a runtime environment for an application server process, such as 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 core product files,
which include command files and other shared product binary files.
However, most core product or system files are updated only by installing
fix packs, interim fixes, or products that extend the product.
After
installation, you can create an application server profile,
a management profile, or a custom profile. At
least one profile must exist to have a functioning application server
environment. You can use the Profile Management Tool or the manageprofiles command to create
profiles.
You must first prepare your operating system for installation
before installing any of the below topologies. See Preparing the operating system for product installation for more information.
The following information describes scenarios for
installing the product in various topologies on one or more machines.
- Topologies for a standalone application server
- Each standalone
application server runs independently of other
application servers.
The following application server topologies
are described in this article.
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 - 5 are typical production environments for a standalone
application server.
- Scenario 1: Install a
standalone application
server on a single machine.
Install WebSphere Application Server by itself on a single machine,
and create a standalone application server profile. Each standalone
application server profile includes a server1 application server process.
Each profile defines a separate standalone application server that
has its own administrative interface.
You can use the Profile Management Tool or the manageprofiles command to create
profiles after installation.
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.

Table 1. Installing a standalone application server on a single machine. Complete these steps:
Step |
Task |
1 |
Install IBM Installation
Manager. |
2 |
Use Installation Manager to install WebSphere Application Server. |
3 |
Use the Profile Management Tool or the manageprofiles command to create
a standalone application server profile. |
- Scenario 2: Install
a standalone 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.

Table 2. Installing a standalone application server and
a web server on a single machine. Complete these steps:
Step |
Task |
1 |
Install IBM Installation
Manager. |
2 |
Use Installation Manager to install the following:- WebSphere Application
Server
- Web Server Plug-ins
for WebSphere Application
Server
- WebSphere Customization
Toolbox
|
3 |
Use the Profile Management Tool or the manageprofiles command to create
a standalone application server profile. |
4 |
Use Installation
Manager to install IBM HTTP
Server, or install another
supported web server. |
5 |
Open the WebSphere Customization
Toolbox, and launch the Web Server Plug-ins Configuration Tool to
configure the web server plug-in and create the web server definition. The
web server definition is automatically created and configured during
the configuration of the plug-in.
|
- Scenario 3: Install
a standalone 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. After creating a profile and installing a
dedicated web server, use the Web Server Plug-ins for WebSphere Application Server and Web Server
Plug-ins Configuration Tool to install a plug-in and to update the
web server configuration file. The Web server can then communicate
with the application server. Optional firewalls can provide additional
security for the application server machine.

Table 3. Installing a standalone application server and a web server
on separate machines. Complete these steps:
Step |
Machine |
Task |
1 |
A |
Install IBM Installation
Manager. |
2 |
A |
Use
Installation Manager to install WebSphere Application
Server. |
3 |
A |
Use the Profile Management Tool or the manageprofiles command to create
a standalone application server profile. |
4 |
B |
Install IBM Installation
Manager. |
5 |
B |
Use
Installation Manager to install the following:- Web
Server Plug-ins for WebSphere Application
Server
- WebSphere Customization
Toolbox
|
6 |
B |
Use
Installation Manager to install IBM HTTP
Server, or install another
supported web server. |
7 |
B |
Open the WebSphere Customization
Toolbox, and launch the Web Server Plug-ins Configuration Tool to
configure the web server plug-in and create the web server definition. The
script for creating and configuring the web server is created under
the plugins_root/bin directory.
|
8 |
B |
Copy
the configureweb_server_name script
to paste on 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.
|
9 |
A |
Paste
the configureweb_server_name script
from Machine B to the profile_root/bin directory
on Machine A. |
10 |
A |
Start
the application server. |
11 |
A |
Run the configureweb_server_name script
on Machine A to create a web server definition in the administrative
console. |
12 |
A |
Open
the administrative console, and save the
changed configuration. |
13 |
B |
Start the web server. Source the plugins_root/setupPluginCfg.sh script
for a Domino® Web Server before
starting a Domino Web Server.
|
14 |
A |
Propagate
the plugin-cfg.xml file
on Machine A from the application server to the web server using the
administrative console.- Click .
- On the web servers page,
place a check mark beside the web server
for which you want to propagate a plug-in, and click Propagate
Plug-in.
Web servers other than IBM HTTP
Server require manual propagation. |
- Scenario 4: Install
multiple standalone
application servers on one machine and one or more web servers on
a separate machine.
The Profile Management Tool or the manageprofiles command can
create a deployment manager profile, an application server profile,
or a custom profile. After creating a profile and installing a dedicated
web server, use the Web Server Plug-ins for WebSphere Application Server and Web Server
Plug-ins Configuration Tool to install a plug-in and to update the
web server configuration file. The web server can then communicate
with the application server. In this configuration, this process must
be done for each profile and web server combination.
This topology
lets each profile have unique applications, configuration settings,
data, and log files while sharing the same set of core product files.
Creating multiple profiles creates multiple application server environments
that you can dedicate to different purposes. For example, each application
server on a website 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. When
a fix pack updates the system files, for example, all application
servers begin using the updated core product files.

Table 4. Installing multiple standalone
application servers on one machine and one or more web servers on
a separate machine. Complete these steps:
Step |
Machine |
Task |
1 |
A |
Install IBM Installation
Manager. |
2 |
A |
Use
Installation Manager to install WebSphere Application
Server. |
3 |
A |
Use the Profile Management Tool or the manageprofiles command to create
a standalone application server profile. |
4 |
B |
Install IBM Installation
Manager. |
5 |
B |
Use
Installation Manager to install the following:- Web
Server Plug-ins for WebSphere Application
Server
- WebSphere Customization
Toolbox
|
6 |
B |
Use
Installation Manager to install IBM HTTP
Server, or install another
supported web server. |
7 |
B |
Open the WebSphere Customization
Toolbox, and launch the Web Server Plug-ins Configuration Tool to
configure the web server plug-in and create the web server definition. The
script for creating and configuring the web server is created under
the plugins_root/bin directory.
|
8 |
B |
Copy
the configureweb_server_name script
to paste on 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.
|
9 |
A |
Paste
the configureweb_server_name script
from Machine B to the profile_root/bin directory
on Machine A. |
10 |
A |
Start
the application server. |
11 |
A |
Run the configureweb_server_name script
on Machine A to create a web server definition in the administrative
console. |
12 |
A |
Open
the administrative console, and save the
changed configuration. |
13 |
B |
Start the web server. Source the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before
starting a Domino Web Server.
|
14 |
A |
Propagate
the plugin-cfg.xml file
on Machine A from the application server to the web server using the
administrative console.- Click .
- On the web servers page,
place a check mark beside the web server
for which you want to propagate a plug-in, and click Propagate
Plug-in.
Web servers other than IBM HTTP
Server require manual propagation. |
15 |
A |
Create subsequent
standalone application server
profiles using the Profile Management Tool or
the manageprofiles command
on Machine A. |
16 |
B |
Install
subsequent IBM HTTP
Servers or other supported web servers on Machine B. |
17 |
A - B |
Repeat steps
7through 14 to configure each additional
web server on Machine B with each newly-added application server.
Each application server profile is now directly associated with its
own web server. |
- Scenario 5: Install an administrative agent
and multiple registered application servers and multiple web servers
on separate machines.
The application servers on one
machine communicate with a web server on a separate (remote) machine
through the web server plug-in. The application servers are registered
with the administrative agent. The administrative agent provides a
single location from which to administer the nodes registered to it.
Optional firewalls can provide additional security for the application
server machine.

Table 5. Installing an administrative agent and multiple
registered application servers and multiple web servers on separate
machines. Complete these steps:
Step |
Machine |
Task |
1 |
A |
Install IBM Installation
Manager. |
2 |
A |
Use
Installation Manager to install WebSphere Application
Server. |
3 |
A |
Use the Profile Management Tool or the manageprofiles command to create
a management profile of the administrative agent server type. |
4 |
A |
Use
the Profile Management Tool or the manageprofiles command to create
an application server profile. |
5 |
A |
Register the application server with the administrative
agent by running the registerNode command in the
bin directory of the administrative agent profile, profile_root/bin. |
6 |
B |
Install IBM Installation
Manager. |
7 |
B |
Use
Installation Manager to install the following:- Web
Server Plug-ins for WebSphere Application
Server
- WebSphere Customization
Toolbox
|
8 |
B |
Use
Installation Manager to install IBM HTTP
Server, or install another
supported web server. |
9 |
B |
Open the WebSphere Customization
Toolbox, and launch the Web Server Plug-ins Configuration Tool to
configure the web server plug-in and create the web server definition. The
script for creating and configuring the web server is created under
the plugins_root/bin directory.
|
10 |
B |
Copy
the configureweb_server_name script
to paste on 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.
|
11 |
A |
Paste
the configureweb_server_name script
from Machine B to the profile_root/bin directory
on Machine A. |
12 |
A |
Start
the application server. |
13 |
A |
Run the configureweb_server_name script
on Machine A to create a web server definition in the administrative
console. |
14 |
A |
Open
the administrative console, and save the
changed configuration. |
15 |
B |
Start the web server. Source the plugins_root/setupPluginCfg.sh script
for a Domino Web Server before
starting a Domino Web Server.
|
16 |
A |
Propagate
the plugin-cfg.xml file
on Machine A from the application server to the web server using the
administrative console.- Click .
- On the web servers page,
place a check mark beside the web server
for which you want to propagate a plug-in, and click Propagate
Plug-in.
Web servers other than IBM HTTP
Server require manual propagation. |
17 |
A |
Create subsequent
application server profiles
using the Profile Management Tool or
the manageprofiles command
on Machine A. |
18 |
A |
Register
the new application server with the
administrative agent by running the registerNode command
in the bin directory of the administrative agent profile, profile_root/bin. |
19 |
B |
Install
subsequent IBM HTTP
Servers or other supported web servers on Machine B. |
20 |
A - B |
Repeat steps
9 through 16 to configure each
additional web server on Machine B with each newly-added application
server. Each application server profile is now directly associated
with its own web server.
|