Plan to install ND

 

+

Search Tips   |   Advanced Search

 

Overview

Consider common installation scenarios for IBM WAS ND (WAS ND) to determine how to install your application serving environment. This topic links to procedures for installing each scenario.

WAS ND is an integrated platform that contains...

In V6.1, installation of WAS ND typically performs two actions. First the installation wizard installs a shared set of core product files. Second, the installation wizard optionally creates a profile.

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

A running appserver process can create, read, update, or delete the configuration files, data files, and log files in its profile. The appserver 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 fix packs, interim fixes, or products that extend ND.

During installation, you can choose to create...

The installation wizard also has an option not to create a profile during installation. However, at least one profile must exist to have a functioning appserver environment.

After installation, use the Profile Management Tool to create additional profiles.

 

Scenarios for installation

The following information describes scenarios for installing the product in various topologies on one or more machines. Two types of WAS topologies are possible using the ND product:

  1. Topologies for a stand-alone appserver

    Each stand-alone appserver has its own console and runs independently of other appservers. are described in this topic.

  2. Topologies for a managed group of appservers in a cell

    A cell consists of one deployment manager and one or more federated appservers that are managed nodes.A node can become a managed node in several ways:

    • By creating the cell with a federated node during installation

    • By federating the node within an appserver 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. The following topologies for a cell are described in this topic.

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

 

Overview

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


 

Related information


Planning the installationInstalling the product and additional software
Preparing the operating system for product installation
Creating profiles through the graphical user interface
Installing IBM HTTP Server
Installing Web server plug-ins
startManager command
startServer command