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
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 run-time environment for an application server process.
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.
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 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.
Scenarios for installation
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 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.
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.
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
Installing WebSphere Application Server Network Deployment by itself on a single machine lets you create a stand-alone Application Server profile. Each stand-alone application server profile includes a server1 application server process. Installing Network Deployment creates the set of system files.
The Profile creation wizard creates the profile for the application server. The profile is a separate data partition with files that define the stand-alone application server environment.
In this scenario, the application server uses its internal HTTP transport chain for communication, which is suitable for handling an application with a relatively low request workload. For example, this type of installation can support a simple test environment or a departmental intranet environment.
Installing a Web server, such as IBM HTTP Server, on the same machine as the application server provides a more robust Web server environment. Installing a Web server plug-in is a requirement for the Web server to communicate with the application server. This type of installation supports rigorous testing environments or production environments that do not require a firewall. However, this is not a typical production environment.
In the typical production environment, the application server on one machine communicates with a Web server on a separate (remote) machine through the Web server plug-in. Optional firewalls can provide additional security for the application server machine.
The Profile Creation wizard can create a deployment manager profile, an application server profile, or a custom profile. Each profile is a separate data partition containing the files that define the run-time environment. After creating a profile and installing a dedicated Web server, use the Plug-ins installation wizard to install a plug-in and to update the Web server configuration file. The Web server can then communicate with the application server.
This topology lets each profile have unique applications, configuration settings, data, and log files, while sharing the same set of system files. Creating multiple profiles creates multiple application server environments that you can dedicate to different purposes.
For example, each application server on a Web site can serve a different application. In another example, each application server can be a separate test environment that you assign to a programmer or a development team.
Updating the core product files
Another feature of having multiple profiles is enhanced serviceability. When a refresh pack or a fix pack updates the core product files on a machine, all of the application server profiles that were created from the core product files begin using the updated files. However, the profile itself is not updated unless the maintenance package contains required maintenance for existing profiles. The Update Installer issues a message for a required update to an existing profile as you install the maintenance package.
In some situations, you might prefer to not update all of the application servers on a machine. In such situations, simply install the product a second time and install the new maintenance. Create application server profiles from both installations to manage the product updates incrementally.
The script that the Plug-ins installation wizard creates works on the default profile only. So, this script can only create a Web server definition on the profile that is the default profile at the time that the script runs.
WebSphere Application Server Network Deployment can create a cell of managed application servers on a single machine from one installation of the core product files.
The Profile creation wizard creates the deployment manager. After starting the deployment manager, use the Profile Creation wizard to create one or more application servers for the cell. Application server profiles have a default application server, called server1, and default applications. An Application Server node becomes a managed node after federating the node into the deployment manager cell.
The deployment manager provides the administration for all managed nodes that are in its cell. Periodically the configuration and application files on a managed node refresh from the master copy of the files hosted on the deployment manager during synchronization.
In certain secure environments, the Profile Creation wizard cannot federate a custom profile into a cell. Such cases require you to use the addNode command instead. If you have configured the deployment manager to use a JMX connector type other than the default SOAP connector, use the addNode command to add the node to the cell.
The deployment manager provides the administration for all managed nodes that are in its cell. Periodically the deployment manager refreshes the configuration files and application files on the managed node. Copying the master version of the files hosted on the deployment manager to the managed nodes is a process called synchronization.
In a cell environment, only the managed nodes serve applications, not the deployment manager. The managed node in this scenario uses its internal HTTP transport chain for communication, which is suitable for an application with a relatively low request workload. For example, this type of installation can support a simple test environment or a departmental intranet environment.
Installing a Web server, such as IBM HTTP Server, on the same machine as the application server provides a richer set of configuration options. Installing a Web server plug-in is required for the Web server to communicate with the server in the managed node. This type of installation can support either rigorous testing in a cell environment or production environments that do not require a firewall.
In a typical production environment, a managed node in a cell communicates with a Web server on a separate (remote) machine through the Web server plug-in. An optional firewall can provide additional security for the application server machine.
You have the option of using the script to create the Web server definition in the configuration of the deployment manager or using the administrative console of the deployment manager to create the Web server definition.
The primary advantage of a cell over a stand-alone application server is its scalability. Managing a cell to keep it in proportion with workload levels is possible. In this scenario, managed nodes exist on Machine C. All of the managed nodes are federated into the same deployment manager. Depending on your needs, an application server in each managed node could serve the same or different applications.
The managed nodes in this scenario communicate with the same Web server. However, the preferred strategy is to have a dedicated Web server for each managed node.
Assign unique ports. Write down the SOAP port for later use when federating this node from the administrative console of the deployment manager.
You have the option of using the script to create the Web server definition in the configuration of the deployment manager or using the administrative console of the deployment manager to create the Web server definition.
Result
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 installation
Installing 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