Consider common installation scenarios for the product
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 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 typically performs
two actions. First the installation process installs a shared set
of core product files. Second, the installation process optionally
creates a 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.
During
installation, you can choose to create an application server
profile, a management profile, or
a custom profile. The installer 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.
After installation, 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.
Scenarios for installation
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 topic.
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.
Solution
Installation Diagrams
Each of the following scenarios includes
a diagram and a list of detailed installation steps.
- 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 WebSphere Application Server. Create
an application server profile during the installation.
|
- 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 WebSphere Application Server . Create
an application server profile during the installation.
|
2 |
Install the 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.
|
3 |
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. |
4 |
Create a Web server definition using the administrative
console. Click Servers > Server Types > Web servers > New and
complete the steps in the Create new Web server definition wizard. |
- 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 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. 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 WebSphere Application Server. Create
an application server profile during the installation.
|
2 |
B |
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. |
3 |
B |
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 configureWeb_server_name script
in the plugins_root/bin directory
on Machine B.
|
4 |
B |
Copy the configureWeb_server_name script
on Machine B to the app_server_root/profile_name/bin directory
on Machine A. |
5 |
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. |
6 |
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 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 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. 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 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.
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 WebSphere Application Server. Create
an application server profile during the installation.
|
2 |
B |
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. |
3 |
B |
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.
|
4 |
B |
Copy the configureWeb_server_name script
on Machine B to the app_server_root/profile_name/bin directory
on Machine A. |
5 |
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. |
6 |
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. |
7 |
A |
Create subsequent application server profiles
using the Profile Management Tool or
the manageprofiles command
on Machine A. |
8 |
B |
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. |
9 |
A - B |
Repeat steps 4 - 6 to configure the second web
server on Machine B with your newly-added application server (Profile
02). 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 WebSphere Application Server. Create
an application server profile during the installation.
|
2 |
A |
Create a management profile using the Profile Management Tool or the manageprofiles command and
select the administrative agent server type option. |
3 |
A |
Register the application server with the administrative
agent by running the registerNode command in the
bin directory of the administrative agent profile, app_server_root/profile_name/bin. |
4 |
B |
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. |
5 |
B |
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.
|
6 |
B |
Copy the configureWeb_server_name script
on Machine B to the app_server_root/profile_name/bin directory
on Machine A. |
7 |
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. |
8 |
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. |
9 |
A |
Create subsequent application server profiles
using the Profile Management Tool or
the manageprofiles command
on Machine A. |
10 |
A |
Register the new application server with the
administrative agent by running the registerNode command
in the bin directory of the administrative agent profile, app_server_root/profile_name/bin. |
11 |
B |
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. |
12 |
A - B |
Repeat steps 6 - 8 to configure the second web
server on Machine B with your newly-added application server (Profile
02). Each application server profile is now directly associated with
its own Web server. |