202 WebSphere Application Server V8.5 Concepts, Planning, and Design Guide
4. Configure the web server plug-in and create the web server definition. For details about
this task, see the Websphere Application Server V8.5 Information Center at:
5. Repeat steps 2c, 3, and 4 to install subsequent IBM HTTP Server instances or other
supported web servers.
Setting up System B
To set up System B, complete these steps:
1. Install IBM Installation Manager.
2. Using Installation Manager, install WebSphere Application Server V8.5.
3. Create an application server profile by using the
app_server_root/profileTemplates/default profile template.
4. Create a web server definition through the administrative console or by running the
configureweb_server_name script locally from the profile_root/bin path. This script is on
Server A in the plugins_root/bin directory. If just one system is running Windows, the
script is in the plugins_root/bin/crossPlatformScripts directory.
5. Repeat steps 3 and 4 to create additional profiles, and configure them to use the
corresponding web server.
8.3.3 Liberty profiles managed by a job manager
Liberty profiles provide the option to run small footprint servers. You can install multiple
applications in one Liberty profile server, and multiple Liberty profile servers can run on the
same hardware. The same application can run on multiple Liberty profile servers to achieve a
To manage the Liberty profiles in your topology, use the WebSphere job manager. It provides
a central asynchronous management of all local and remote Liberty profiles. To install a job
manager, you need WebSphere Application Server Network Deployment.
Chapter 8. Topologies 203
The example shown in Figure 8-5 shows using two HTTP servers to avoid a SPOF. You can
manage the plug-ins for the HTTP Servers by using the job manager. The job manager can
map one application to multiple Liberty profiles.
Figure 8-5 Liberty profiles that are controlled by a job manager
Using a Liberty profile has the following advantages:
You can prepare each Liberty profile as one or more compressed files by using one of the
– Prepare a file that contains the Java software development kit (SDK), the Liberty profile
installation run time, the server definitions, and the applications. This file is
self-contained and does not require any preinstalled software on the target host.
– Prepare a file that contains the Liberty profile installation run time, the server
definitions, and the applications. You can install this file on a server that has a Java
– Prepare a file that contains only the parts that you need, for example only applications,
or only applications and server configurations. This method allows you to deploy each
part separately as needed.
– Prepare a compressed file that contains a new version of the Java SDK.
While deploying the file, the job manager analyzes it to ensure that the new resources do
not collide with other resources already deployed.
Low maintenance effort
Each server can be prepared by the developer, including all the server resources that the
application needs. The administrator can modify the server.xml file before deploying it to
include database names, user names, and passwords for the production environment.
Outside World DMZ Internal Network