WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIXHP-UXLinuxSolarisWindows

Planning to install Network Deployment

This topic describes common installation scenarios and links to component installation procedures.

Before you begin

In Version 6.0, installing WebSphere Application Server Network Deployment is a two-step process. The first step is using the installation wizard to install a shared set of core product files. The second step is using 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 WebSphere Application Server Network Deployment.

Relationship between binaries and profiles

Scenarios for installation

The following information describes scenarios for installing the product in various topologies on one or more machines. Two types of WebSphere Application Server topologies are possible using the Network Deployment product:
  • Topologies for a stand-alone application server
  • 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.

The following topologies are described in this topic.
  • Scenario 1: Single-machine installation of a stand-alone application server
  • Scenario 2: Single-machine installation of a stand-alone application server and a Web server
  • Scenario 3: Two-machine installation of a stand-alone application server and a Web server
  • Scenario 4: Two-machine installation of multiple stand-alone application servers and a Web server

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:
  • Federating the node within an Application Server profile into the cell
  • Federating the node within a custom profile into the cell

The deployment manager is the single point of administration for all of the managed nodes in the cell. The deployment manager maintains the configuration files for nodes that it manages and deploys applications to those managed nodes.

The following topologies for a cell are described in this topic.
  • Scenario 5: Single-machine installation of a cell of application servers
  • Scenario 6: Single-machine installation of a cell of application servers and a Web server
  • Scenario 7: Two-machine installation of a cell of application servers and a Web server
  • Scenario 8: Three-machine installation of a cell of application servers and a Web server

Why and when to perform this task

Each of the following scenarios includes a diagram and a list of detailed installation steps.

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 and 4 are typical production environments for a stand-alone application server. Scenario 8 is a typical production scenario for a cell environment.

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

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_scenario3.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)