Install WAS ND on the deployment manager machine
Overview
IBM WebSphere Application Server Network Deployment (WAS ND) on the deployment manager machine must be installed to the same product revision and corrective service levels as the WAS ND levels used on cluster nodes.
If the portal server nodes in the cluster will include IBM WebSphere Process Server to support business process integration, the deployment manager must also be created using a custom profile from WebSphere Process Server.
If this cluster will include WebSphere Process Server, an existing installation of WAS ND cannot be used for the deployment manager. Instead, follow the instructions below to create a deployment manager that includes WebSphere Process Server.
If you are planning to install WebSphere Portal and the deployment manager on the same machine, the preferred approach is to create separate profiles for the portal server and the deployment manager. Both profiles use the same installation of WAS ND. This documentation does not provide detailed instructions for the scenario of installing multiple profiles on the same machine.
If you are planning to install two separate copies of WAS ND on the same machine for the deployment manager and WebSphere Portal on the same machine, review the coexistence requirements in the WebSphere Application Server documentation before installing these products:
- Windows and UNIX:
- i5/OS:
Also be aware that the WebSphere Portal installation automatically installs WAS ND.
WAS ND is automatically installed as part of the WebSphere Portal installation. However, IBM recommends that you install WAS ND on a dedicated system to serve as the deployment manager machine.
- Installing WAS ND on Windows and UNIX (with WebSphere Process Server)
WebSphere Portal provides a customized installation package (CIP) that includes IBM WAS ND, IBM WebSphere Process Server, and all required maintenance packages. Use the discs supplied with WebSphere Portal to install WAS ND and WebSphere Process Server on a dedicated machine.
- Installing WAS ND on Windows and UNIX (without WebSphere Process Server)
WebSphere Portal provides a CIP that includes IBM WAS ND and all required maintenance packages. Use the discs supplied with WebSphere Portal to install WAS ND on a dedicated machine.
- Installing WAS ND on i5/OS
WebSphere Portal provides a CIP that includes IBM WAS ND and all required maintenance packages. Use the discs supplied with WebSphere Portal to install WAS ND on a dedicated machine.
Parent topic:
Setting up a cluster
Next topic
Installing and federating the primary node