< Previous |
Contents | Next
The following steps show how to install the WebSphere® Application
Server Deployment Manager using the IBM® Lotus® Quickr installation CD.
- After reading a description of the WebSphere Application Server
Network Deployment installation click Next.
This edition of WebSphere Application Server supports multinode, multiprocess
The WebSphere Application Server Network Deployment installation is a two-part
procedure that allows you to install both WebSphere Application Server
core products and a Deployment Manager profile.
The first part of the installation guides you through the installation
of the WebSphere Application Server core products.
The Profile creation wizard guides you through the second part of the installation
process of creating a run-time environment for WebSphere Application Server
called the profile. At least one profile must exist to have a functional
- Read the Software License Agreement, accept the conditions, and
then click Next. If you do not accept the terms of the
license agreement, you will not be able to complete the installation process.
- When the system prerequisites check indicates successful completion,
This check ensures that a supported operating system is running with appropriate
service packs and patches and also checks for existing WebSphere Application
- Either accept the default installation directory for the IBM
WebSphere Application Server Network Deployment, V6, or click Browse
to find a different directory to install to, and then click Next.
- When the installation program indicates that the core product
files have installed successfully, select the Launch the Profile
creation wizard option and then click Next.
The Profile creation wizard creates a run-time environment known as a profile
that contains either a deployment manager or a stand-alone application
server. At least one profile must exist to have a functional installation.
If you do not create a profile now, you will need to launch the Profile
creation wizard at a later time or else use the wasprofile
command line utility to create it.
- Review the important information on the Welcome screen for the
Profile creation wizard for Version 6, and then click Next.
- Provide a unique profile name, for example, lq.
- Specify a profile directory to contain the files that define
the run-time environment, such as commands, configuration files, and log
files. You can accept the default directory provided or click Browse
for a different directory.
Important: Deleting a profile directory manually does
not completely delete the profile. Use the wasprofile
command to completely delete a profile.
- Specify a node name, a host name, and a cell name for this profile.
Node name: quickr3
Host name: quickr3.acme.com
Cell name: lq
The node name is for administration by the deployment manager and must
be unique within the cell. Refer to the installation guide for detailed
field descriptions and migration considerations.
- To avoid run-time port conflicts, verify that each of port values
that appear on the Port value assignment screen are unique.
It is important that the ports for the deployment manager do not conflict
with other profiles in this installation. Another installation of WebSphere
Application Server or other programs might use the same ports.
- Decide whether or not to use a Microsoft® Windows™ service to
run the WebSphere Application Server. If you to decide to do so, select
the Run the Application Server process as a Windows service
Windows services can start up and stop WebSphere Application Server and
configure startup and recovery actions.
Choose whether to log on using a local system account or a specified user
account. If a local system account, enter a User Name and password and
specify a startup type of Manual or Automatic.
The user account that runs the Windows service must have the following
- Act as part of an operating system: Windows
designates this user right as a privilege for the user account.
- Log on as a service: Windows designates
this user right as a logon right for the user account.
- Review the characteristics that constitute the profile summary.
If you need to make changes, click Back to change a
characteristic; otherwise click Next to complete creating
- Click Finish when you are notified that Profile
creation has completed.
The next procedure in creating a Network Deployment environment is to start
the deployment manager so that other nodes can be federated to its cell.
You can start and stop the deployment manager from the command line or
the First steps console.
The First steps console also has links to other information and features
of the deployment manager. Click Launch the First steps console
to use it.
After starting the deployment manager, return to the Profile creation wizard
to create either the Application Server profile or a custom profile and
then federate it to the cell.
IMPORTANT Make sure the Deployment Manager is running
when installing the primary and secondary nodes.
Deployment Manager timeouts and heap size
- Log into the WebSphere Application Server Administrative Console
for the Deployment Manager. For example:
- Increase the HTTP connection timeouts for the deployment manager.
a. Click System Administration > Deployment Manager > Web
container transport chains.
b. Increase the timeout values. For the WCInboundAdmin
and WCInboundAdminSecure entries listed in the web container
transport chains section, complete the following steps to increase the
i. Click HTTP Inbound Channel.
ii. Change the Read timeout value to 180.
iii. Change the Write timeout value to 180.
iv. Save the configuration changes.
- Change the timeout request period for the Java Management Extensions
a. Click System administration > Deployment Manager > Administration
Services > JMX connectors > SOAPConnector > Custom Properties.
b. Select the requestTimeout property, and increase
the value from 600 to 6000.
c. Save the configuration changes.
- Update the maximum Java heap size used by the deployment manager:
a. Click System Administration > Deployment Manager > Java
and Process Management > Process Definition > Java Virtual Machine.
b. Update the value in the Maximum Heap Size field.
A value of at least 1408 MB is recommended.
c. Click OK, and then save your changes.
- Restart the deployment manager.
Configuration of the WebSphere Application Server Deployment Manager
Contents | Next