[AIX Solaris HP-UX Linux Windows]

Planning to install WebSphere Application Server

Consider common installation scenarios for the product to determine how to install your application serving environment.

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.

The installation of the application server product installs a shared set of core product files. Afterwards, you create at least one profile, which 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 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 core product files, which include command files and other shared product binary files. However, most core product or system files are updated only by installing fix packs, interim fixes, or products that extend the product.

After installation, you can create an application server profile, a management profile, a cell set of profiles that contains a deployment manager and a federated application server, or a custom profile. At least one profile must exist to have a functioning application server environment. You can use the Profile Management Tool or the manageprofiles command to create profiles.

You must first prepare your operating system for installation before installing any of the below topologies. See Preparing the operating system for product installation for more information.

Avoid trouble 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

The following information describes scenarios for installing the product in various topologies on one or more machines. Two types of application server topologies are possible using the Network Deployment product.

Topologies for a standalone application server
Each standalone application server 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. 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.
An application server can become a managed node in the following ways:
  • By creating the cell with a federated node
  • By federating the node within an application server profile into the cell
  • By federating the node within a custom profile into the cell

Scenarios 6 - 10 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 that you can consider for your network deployment.

Topologies that include DMZ Secure Proxy Server for IBM WebSphere Application Server
DMZ Secure Proxy Server for IBM WebSphere Application Server delivers a high performance reverse proxy capability that can be used at the edge of the network to route, load balance, and improve response times for requests to web resources. Comapared to a web server, DMZ Secure Proxy Server for IBM WebSphere Application Server provides increased flexibility, improved integration with WebSphere systems management, improved workload balancing, and other enhancements. DMZ Secure Proxy Server for IBM WebSphere Application Server does not contain a web container and therefore does not have an administration console.
The product can be administered in a number of secure ways depending on various possible topologies.
  • Administration with the wsadmin utility.

    This requires local access to the DMZ Secure Proxy Server for IBM WebSphere Application Server.

  • Administration from an external web console.

    The product is configured through a profile on the deployment manager node, exported, and imported to the DMZ Secure Proxy Server for IBM WebSphere Application Server node.

  • Flexible administration from a remote job manager.

    A secure proxy profile is deployed on the DMZ Secure Proxy Server for IBM WebSphere Application Server node and registered to an administrative agent on that same machine. The administrative agent is then registered to and managed by a remote job manager.

The second administrative topology for the DMZ Secure Proxy Server for IBM WebSphere Application Server is described in this article.

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 - 5 are typical production environments for a standalone application server. Scenarios 9 is a typical production scenario for a simple cell environment.

Procedure

Results

You have reviewed many of the most common installation scenarios to find a possible match for the topology that you intend to install.

What to do next

See the IBM HTTP Server, web server plug-in, and DMZ Secure Proxy Server for IBM WebSphere Application Server documentation for more information on installing those products.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 09:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=tins_scenario3
File name: tins_scenario3.html