Plan to install Network Deployment

 

+

Search Tips   |   Advanced Search

 

  1. Overview
  2. Scenarios for installation
  3. Topologies for a stand-alone application server
  4. Topologies for a managed group of application servers
  5. Steps for this task (dependent on configuration)
  6. Scenario 1: Install a stand-alone application server on a single machine.
  7. Scenario 2: Install a stand-alone application server and a Web server on a single machine.
  8. Scenario 3: Install a stand-alone application server and a Web server on separate machines.
  9. Scenario 4: Install multiple stand-alone application servers on one machine and a Web server on a separate machine.
  10. Scenario 5: Install a cell of managed application server nodes on one machine.
  11. Scenario 6: Install a cell of managed application server nodes and a Web server on one machine.
  12. Scenario 7: Install a cell of managed application server nodes on one machine and a Web server on a separate machine.
  13. 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.

 

Overview

In v6, installing WAS (WAS) Network Deployment is a two-step process.

  1. Use the installation wizard to install a shared set of core product files.

  2. Use the Profile creation wizard to create a deployment manager profile, an Application server profile, or a custom profile.

A profile is a separate data partition that includes the files that define a run-time environment for an application server process.

A running application server process, such as a deployment manager, can create, read, update, or delete the configuration files, data files, and log files in its profile. The application server process has read-only access to the system files, which include command files and other shared product binary files. System files are updated only by installing refresh packs or fix packs, or by products that extend WAS Network Deployment.

 

Scenarios for installation

Two types of WAS topologies are possible using the Network Deployment product:

  1. Topologies for a stand-alone application server

  2. Topologies for a managed group of application servers

 

Topologies for a stand-alone application server

Each stand-alone application server has its own administrative console and runs independently of other application servers.

 

Topologies for a managed group of application servers

A managed group of application servers is called a cell. A cell consists of one deployment manager and one or more federated application servers, which are called managed nodes.

A node becomes a managed node in either of two ways:

 

Steps for this task (dependent on configuration)

 

Result

You can review common installation scenarios to find a possible match for the topology that you intend to install. Each product installation diagram provides a high-level procedure for installing the components that comprise the topology.

 

What to do next

After determining a possible topology, follow the steps in the overall procedure. Useful links to the installation procedures for each installable component are in the list of related topics.


 

Related Tasks

Installing the product and additional software
Using the Profile creation wizard
Installing IBM HTTP Server
Installing Web server plug-ins

 

Related Information

startManager command
startServer command

 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.