Consider common installation scenarios for the product to determine how to install your application serving environment. This topic links to procedures for installing each scenario.
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 typically performs two actions. First the installation process installs a shared set of core product files. Second, the installation process optionally creates a 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.
During installation, you can choose to create an application server profile, a management profile, a cell set of profiles which contains a deployment manager and a federated application server, or a custom profile. The installer also has an option not to create a profile during installation. However, at least one profile must exist to have a functioning application server environment. After installation, 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.
Scenarios for installation
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.
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 you can consider for your network deployment.
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.
Solution Installation Diagrams
Each of the following scenarios includes a diagram and a list of detailed installation steps.
Install WebSphere Application Server Network Deployment by itself on a single machine and create a standalone application server profile. Each standalone application server profile includes a server1 application server process. Each profile defines a separate standalone application server that has its own administrative interface.
You can use the Profile Management Tool or the manageprofiles command to create profiles after installation.
In this scenario, the application server uses its internal HTTP transport chain for communication instead of a using a separate web server (on a separate machine) to possibly offload some processing.
Step | Task |
---|---|
1 | Install WebSphere Application Server Network Deployment. Create an application server profile during the installation. |
Installing a Web server, such as IBM HTTP Server, on the same machine as the application server provides more configuration options. Installing a Web server plug-in enables the Web server to communicate with the application server. This installation scenario supports rigorous testing environments or production environments that do not require a firewall. However, this scenario is not a typical production environment. When everything is on one machine, neither the Web server or the application server will run as fast as if they were on separate machines because they are both competing for the same CPU resources.
Step | Task |
---|---|
1 | Install WebSphere Application Server Network Deployment . Create an application server profile during the installation. |
2 | Install the IBM HTTP
Server or another supported Web server. While installing IBM HTTP Server, use its installation wizard to install the Web server plug-ins. After installing IBM HTTP Server, proceed to step 4. |
3 | If you use another supported Web server or an existing installation of IBM HTTP Server, use the Plug-ins installation wizard to install the Web server plug-ins and configure the Web server. Because the Web server and the application server are on the same machine, the Plug-ins installation wizard creates a Web server definition and you can skip step 4. |
4 | Create a Web server definition using the administrative console. Click Servers > Server Types > Web servers > New and complete the steps in the Create new Web server definition wizard. |
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. 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. Optional firewalls can provide additional security for the application server machine.
Step | Machine | Task |
---|---|---|
1 | A | Install WebSphere Application ServerNetwork Deployment. Create an application server profile during the installation. |
2 | B | Install IBM HTTP Server or another supported Web server on Machine B. While installing IBM HTTP Server, use its installation wizard to install the Web server plug-ins. |
3 | B | If you use another supported Web server or an
existing installation of IBM HTTP Server, use the Plug-ins
installation wizard to install the Web server plug-ins and configure
the Web server on Machine B. The Plug-ins installation wizard creates a configureWeb_server_name script in the plugins_root/bin directory on Machine B. |
4 | B | Copy the configureWeb_server_name script on Machine B to the app_server_root/profile_name/bin directory on Machine A. |
5 | A | Run the configureWeb_server_name script on Machine A to create a Web server definition in the administrative console. You can then use the administrative console to manage the Web server. |
6 | A | Propagate the plugin-cfg.xml file
on Machine A from the application server to the Web server using the
administrative console.
|
The Profile Management Tool can create a deployment manager profile, an application server profile, or a custom profile. 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. In this configuration, this process must be done for each profile and Web server combination.
This topology lets each profile have unique applications, configuration settings, data, and log files, while sharing the same set of core product 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.
Another feature of having multiple profiles is enhanced serviceability. For example, when a fix pack updates the system files, all application servers begin using the updated core product files.
Step | Machine | Task |
---|---|---|
1 | A | Install WebSphere Application ServerNetwork Deployment. Create an application server profile during the installation. |
2 | B | Install IBM HTTP Server or another supported Web server on Machine B. While installing IBM HTTP Server, use its installation wizard to install the Web server plug-ins. |
3 | B | If you use another supported Web server or an
existing installation of IBM HTTP Server, use the Plug-ins
installation wizard to install the Web server plug-ins and configure
the Web server on Machine B. The Plug-ins installation wizard creates a script named configureWeb_server_name in the plugins_root/bin directory on Machine B. |
4 | B | Copy the configureWeb_server_name script on Machine B to the app_server_root/profile_name/bin directory on Machine A. |
5 | A | Run the configureWeb_server_name script on Machine A to create a Web server definition in the administrative console. You can then use the administrative console to manage the Web server. |
6 | A | Propagate the plugin-cfg.xml file
on Machine A from the application server to the Web server using the
administrative console.
|
7 | A | Create subsequent application server profiles using the Profile Management Tool or the manageprofiles command on Machine A. |
8 | B | Install subsequent IBM HTTP Servers or other supported Web servers on Machine B. While installing an IBM HTTP Server, use its installation wizard to install the Web server plug-ins. |
9 | A - B | Repeat steps 4 - 6 to configure the second web server on Machine B with your newly-added application server (Profile 02). Each application server profile is now directly associated with its own Web server. |
The application servers on one machine communicate with a Web server on a separate (remote) machine through the Web server plug-in. The application servers are registered with the administrative agent. The administrative agent provides a single location from which to administer the nodes registered to it. Optional firewalls can provide additional security for the application server machine.
Step | Machine | Task |
---|---|---|
1 | A | Install WebSphere Application ServerNetwork Deployment. Create an application server profile during the installation. |
2 | A | Create a management profile using the Profile Management Tool or the manageprofiles command and select the administrative agent server type option. |
3 | A | Register the application server with the administrative agent by running the registerNode command in the bin directory of the administrative agent profile, app_server_root/profile_name/bin. |
4 | B | Install IBM HTTP Server or another supported Web server on Machine B. While installing IBM HTTP Server, use its installation wizard to install the Web server plug-ins. |
5 | B | If you use another supported Web server or an
existing installation of IBM HTTP Server, use the Plug-ins
installation wizard to install the Web server plug-ins and configure
the Web server on Machine B. The Plug-ins installation wizard creates a script named configureWeb_server_name in the plugins_root/bin directory on Machine B. |
6 | B | Copy the configureWeb_server_name script on Machine B to the app_server_root/profile_name/bin directory on Machine A. |
7 | A | Run the configureWeb_server_name script on Machine A to create a Web server definition in the administrative console. You can then use the administrative console to manage the Web server. |
8 | A | Propagate the plugin-cfg.xml file
on Machine A from the application server to the Web server using the
administrative console.
|
9 | A | Create subsequent application server profiles using the Profile Management Tool or the manageprofiles command on Machine A. |
10 | A | Register the new application server with the administrative agent by running the registerNode command in the bin directory of the administrative agent profile, app_server_root/profile_name/bin. |
11 | B | Install subsequent IBM HTTP Servers or other supported Web servers on Machine B. While installing an IBM HTTP Server, use its installation wizard to install the Web server plug-ins. |
12 | A - B | Repeat steps 6 - 8 to configure the second web server on Machine B with your newly-added application server (Profile 02). Each application server profile is now directly associated with its own Web server. |
WebSphere Application Server Network Deployment can create a cell consisting of a deployment manager and one federated application server node on a single machine. During installation choose to install the cell set of profiles.
You can use the Profile Management Tool or the manageprofiles command to create other standalone application server profiles or custom profiles. You can use the administrative interface of the deployment manager to federate the additional servers to the cell. The cell profile type is not recommended for production.
Standalone application server profiles have their own administrative interface until you federate them into a deployment manager cell, at which point the administrative interface of the deployment manager controls the servers, which are at that point called managed nodes. Periodically the configuration and application files on a managed node are refreshed from the master copy of the files hosted on the deployment manager during synchronization. An application server profile has a default application server process called server1, and optionally might include the default application and Sample applications. A custom profile does not have a default server process nor does it have any applications.
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, instead of a using a separate web server (on a separate machine) to possibly offload some processing.
Step | Task |
---|---|
1 | Install WebSphere Application Server
Network Deployment . Create a cell environment during the installation. The cell environment creates a deployment manager profile and an application server profile that is federated to the deployment manager cell. |
2 | Start the deployment manager using its First steps console or by running the startManager command in the bin directory of the deployment manager profile, app_server_root/profile_name/bin. |
3 | Start the administrative console of the deployment manager using its First steps console. |
4 | Start the node agent process by running the startNode command in the bin directory of the application server profile, app_server_root/profile_name/bin. |
5 | Use the administrative console of the deployment manager to create and start application server processes. Click Servers > Server Types > WebSphere application servers > server_name.. |
Installing a Web server, such as IBM HTTP Server, on the same machine as the application server provides more 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.
Step | Task |
---|---|
1 | Install WebSphere Application Server
Network Deployment . Create a cell environment during the installation. The cell environment creates a deployment manager profile and an application server profile that is federated to the deployment manager cell. |
2 | Start the deployment manager using its First steps console or by running the startManager command in the bin directory of the deployment manager profile, app_server_root/profile_name/bin. |
3 | Start the administrative console of the deployment manager using its First steps console. |
4 | Start the node agent process by running the startNode command in the bin directory of the application server profile, app_server_root/profile_name/bin. |
5 | Use the administrative console of the deployment manager to create and start application server processes. Click Servers > Server Types > WebSphere application servers > server_name. |
6 | Install IBM HTTP Server or another supported
Web server. While installing IBM HTTP Server, use its installation wizard to install the Web server plug-ins. After installing IBM HTTP Server, proceed to step 4. |
7 | If you use another supported Web server or an existing installation of IBM HTTP Server, use the Plug-ins installation wizard to install the Web server plug-ins and configure the Web server. Because the Web server and the application server are on the same machine, the Plug-ins installation wizard creates a Web server definition and you can skip step 4. |
8 | Create a Web server definition using the administrative console. Click Servers > Server Types > Web servers > New. |
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.
Step | Machine | Task |
---|---|---|
1 | A | Install WebSphere Application Server
Network Deployment. Create a cell environment during the installation. The cell environment creates a deployment manager profile and an application server profile that is federated to the deployment manager cell |
2 | A | Start the deployment manager using its First steps console or by running the startManager command in the bin directory of the deployment manager profile, app_server_root/profile_name/bin. |
3 | A | Start the administrative console of the deployment manager using its First steps console. |
4 | A | Start the node agent process by running the startNode command in the bin directory of the application server profile, app_server_root/profile_name/bin. |
5 | A | Use the administrative console of the deployment manager to create and start application server processes. Click Servers > Server Types > WebSphere application servers > server_name.. |
6 | B | On Machine B, install IBM HTTP
Server or another supported Web server. While installing IBM HTTP Server, use its installation wizard to install the Web server plug-ins. |
7 | B | If you use another supported Web server or an
existing installation of IBM HTTP Server, use the Plug-ins
installation wizard to configure each additional Web server on Machine
B. Installation of the Web server plug-ins creates a script named configureWeb_server_name in the plugins_root/bin directory on Machine B. |
8 | B | Copy the configureWeb_server_name script on Machine B to the app_server_root/profile_name/bin directory on Machine A |
9 | A | Run the configureWeb_server_name script on Machine A to create a Web server definition in the administrative console. You can then use the administrative console to manage the Web server. |
10 | A | On Machine A, propagate the plugin-cfg.xml file
from the second application server to the Web server using the administrative
console.
|
The primary advantage of a cell over a standalone 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, an alternative strategy could have a dedicated Web server for each managed node.
Step | Machine | Task |
---|---|---|
1 | A | Install WebSphere Application Server
Network Deployment. Create a deployment manager profile during the installation. |
2 | A | Start the deployment manager using its First steps console or by running the startManager command in the bin directory of the deployment manager profile, app_server_root/profile_name/bin. |
3 | A | Install WebSphere Application Server
Network Deployment on Machine C. Create an application server profile during the installation. |
4 | C | On Machine C, start the first application server using its First steps console or by running the startServer server1 command in the bin directory of the first application server profile, app_server_root/profile_name/bin. |
5 | C | On Machine C, create a second application server profile using the Profile Management Tool or the manageprofiles command. |
6 | C | Start the second application server . |
7 | A | On Machine A, add both application server nodes to the cell using the administrative console of the deployment manager. Click System Administration > Nodes > Add Node. |
8 | B | On Machine B, install IBM HTTP
Server or another supported Web server. While installing IBM HTTP Server, use its installation wizard to install the Web server plug-ins. |
9 | B | If you use another supported Web server or an
existing installation of IBM HTTP Server, use the Plug-ins
installation wizard to configure each additional Web server on Machine
B. Installation of the Web server plug-ins creates a script named configureWeb_server_name in the plugins_root/bin directory on Machine B. |
10 | B | Copy the configureWeb_server_name script on Machine B to the app_server_root/profile_name/bin directory on Machine A. |
11 | A | Run the configureWeb_server_name script on Machine A to create a Web server definition in the administrative console. You can then use the administrative console to manage the Web server. |
12 | A | On Machine A, propagate the plugin-cfg.xml file
from the second application server to the Web server on Machine B
using the administrative console.
|
Install a deployment manager and a managed node on one machine, an administrative agent and multiple registered application server nodes on a second machine, a job manager on a third machine, and a Web server on a fourth machine.
The cell in machine A communicates with a Web server, while machine C is an internal server that could be used for testing or some other purpose.
Step | Machine | Task |
---|---|---|
1 | A | Install WebSphere Application Server
Network Deployment on Machine A. Create a deployment manager profile during the installation. |
2 | A | Start the deployment manager using its First steps console or by running the startManager command in the bin directory of the deployment manager profile, app_server_root/profile_name/bin. |
3 | A | Create an application server and federate the application server into the cell using the administrative console of the deployment manager. Click System Administration > Nodes > Add Node |
4 | C | Install WebSphere Application Server
Network Deployment on Machine C. Create an application server profile during the installation. Create any additional application servers using the Profile Management Tool or the manageprofiles command. |
5 | C | Create an administrative agent on Machine C and then register the standalone application servers on Machine C with the administrative agent by running the registerNode command in the bin directory of the administrative agent profile, app_server_root/profile_name/bin. You must register standalone (unfederated) nodes with an administrative agent. The nodes that you register with an administrative agent must be on the same computer as the administrative agent. |
6 | D | Install WebSphere Application Server
Network Deployment on Machine D. Create a job manager profile during installation. |
7 | D | Register the administrative agent on Machine
C and the deployment manager on Machine B with the job manager on
Machine D by connecting to the wsadmin tool on the job manager and
running the registerWithJobManager command in the
AdminTask object. AdminTask.registerWithJobManager('[-host myhost -conntype SOAP -port 8878 -managedNodeName myhostNode01]') Alternatively, you can register with the job manager using an administrative console. In the deployment manager console, click System Administration > Deployment manager > Job manager, select a deployment manager node, and click Register with Job Manager. In the administrative agent console, click System Administration > Administrative agent > Nodes, select one or more standalone nodes, and click Register with Job Manager. The deployment manager and standalone nodes that you register with the job manager become managed nodes of the job manager. The federated node, Profile01, on Machine A does not become a managed node of the job manager; it remains a federated node that is managed by the deployment manager. |
8 | B | On Machine B, install IBM HTTP
Server or another supported Web server. While installing IBM HTTP Server, use its installation wizard to install the Web server plug-ins. |
9 | B | If you use another supported Web server or an
existing installation of IBM HTTP Server, use the Plug-ins
installation wizard to configure each additional Web server on Machine
B. Installation of the Web server plug-ins creates a script named configureWeb_server_name in the plugins_root/bin directory on Machine B. |
10 | B | Copy the configureWeb_server_name script on Machine B to the app_server_root/profile_name/bin directory on Machine A. |
11 | A | Run the configureWeb_server_name script on Machine A to create a Web server definition in the administrative console. You can then use the administrative console to manage the Web server. |
12 | A | On Machine A, propagate the plugin-cfg.xml file
from the second application server to the Web server on Machine B
using the administrative console.
|
The most secure way to administer the DMZ Secure Proxy Server for IBM WebSphere Application Server is locally using wsadmin commands. The DMZ Secure Proxy Server for IBM WebSphere Application Server does not contain a web container and therefore does not have an administrative console. Local administration can only be done using the command line.
Secure proxy server configurations can also be managed within a network deployment application server cell and then imported locally into the DMZ Secure Proxy Server for IBM WebSphere Application Server using wsadmin commands. The configurations are created and maintained inside the network deployment application server cell as configuration-only profiles. The profiles are registered with the administrative agent and are then managed using the administrative console. You configure the secure proxy server profile in the network deployment application server cell, export the configuration to a node in the DMZ, and import the configuration into the DMZ Secure Proxy Server for IBM WebSphere Application Server. You then repeat the process if any changes are made to the secure proxy server configuration.
Step | Machine | Task |
---|---|---|
1 | A | Install WebSphere Application Server
Network Deployment. Create an administrative agent profile during the installation. |
2 | A | Start the administrative agent. |
3 | A | Create a secure proxy (configuration-only) profile using the Profile Management Tool or the manageprofiles command. |
4 | A | Register the secure proxy (configuration-only) profile with the administrative agent using the registerNode command. |
5 | A | Restart the administrative agent. |
6 | A | When the administrative agent prompts you with a list of the nodes that it manges, select the node from the secure proxy (configuration-only) profile. |
7 | A | Create a secure proxy profile through the administrative console. Click Servers > Server Types > WebSphere proxy servers > New and use the Proxy Server Creation wizard. |
8 | A | Export the server configuration by connecting
to the wsadmin tool for the administrative agent and running the exportProxyServer command
in the AdminTask object. Consider the following examples using Jython
strings.![]() AdminTask.exportProxyServer('[-archive c:\myProxyServer.ear -nodeName node1 -serverName server1]') ![]() ![]() ![]() ![]() AdminTask.exportProxyServer('[-archive /myProxyServer.ear -nodeName node1 -serverName server1]') |
9 | B | On Machine B, install the DMZ Secure Proxy Server for IBM WebSphere Application Server. |
10 | A | Transfer the server configuration file to Machine B using FTP. |
11 | B | Import the server configuration on Machine B
by connecting to the wsadmin tool for the secure proxy and running
the importProxyServer command in the AdminTask
object. Consider the following examples using Jython strings.![]() AdminTask.importProxyServer('[-archive c:\myProxyServer.ear -nodeName node1 -serverInArchive server1 -deleteExistingServer true]') ![]() ![]() ![]() ![]() AdminTask.importProxyServer('[-archive /myProxyServer.ear -nodeName node1 -serverInArchive server1 -deleteExistingServer true]') |
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.
In this information ...Related tasks
Related 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. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |