Planning to install Network Deployment

Consider common installation scenarios for Network Deployment 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 Network Deployment is an integrated platform that contains an application server, Web development tools, a Web server, and additional supporting software and documentation.

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, a stand-alone application server profile, or a custom profile.

A profile is a separate data partition that includes the files that define a runtime environment for an application server process, such as a deployment manager or an application server.

A necessary part of installation and configuration is the creation of profiles, which is shown as step 2 in the following diagram. You must create a deployment manager profile, for example, to have a functional cell.Relationship between binaries and profiles

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 system files, which include command files and other shared product binary files. However, most system files are updated only by installing refresh packs, fix packs, interim fixes, or products that extend Network Deployment.

Avoid trouble: It is suggested that you configure WebSphere Application Server Network Deployment with a single subnet for network traffic. You can use one Network interface card (NIC) on a physical machine or logical partition (LPAR). You can also reference a single Domain name system (DNS) server in the network configuration for the physical machine or LPAR.gotcha

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
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 in a cell
A cell consists of one deployment manager and one or more federated application servers that are managed nodes.
A node can become a managed node in several ways:
  • By federating the node within an application server profile into the cell
  • By 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.

Scenarios 5, 6, 7, and 8 assume that all nodes in a cell reside on a particular machine and operating system. However, this precise node assignment does not need to apply. The deployment manager node can exist on Machine A, other managed nodes (that have been federated into the deployment manager) can exist on differing machines and operating systems. Such a configured cell of differing machines or operating systems is called a heterogeneous cell and expands the possible topologies you can consider for your network deployment.

About 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.

Procedure

Results

Following this procedure results in reviewing common installation scenarios to find a possible match for the topology that you intend to install. Each high-level procedure shows the installation order for the components that comprise the topology.

What to do next

After determining a possible topology, follow the steps in the overall procedure.

One step not mentioned in any of these scenarios is to prepare the operating system for installation. Useful links to the installation procedures for each installable component are in the list of related topics.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 11:08:29 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=tins_scenario3
File name: tins_scenario3.html