® Application Server Network Deployment.
Before you begin
Application Server Network Deployment is provided with IBM
Connections to support network deployments of IBM
If you are migrating from IBM
Connections version 2.5, uninstall the 6.1 version of WebSphere
To establish a Network Deployment environment with one Deployment Manager and one or several managed nodes, use the following table to determine the installation option that you should choose when installing WebSphere
Application Server on target systems:
Table 1. WebSphere Application Server Network Deployment options
|IBM Connections deployment||WebSphere Application Server Network Deployment option|
|Deployment Manager and one node on the same system||Cell|
|Deployment Manager and nodes on separate systems||
- Deployment Manager on the system hosting the DM
- Application Server on each system that hosts a node.
Connections installation wizard creates server instances that require each node to have an application server. Therefore, you must choose either one of these two options when installing WebSphere
Application Server to ensure that each node has an application server.
Install the DM and at least one node.
You can deploy one node on the same system as the DM but you must use separate systems for all other nodes in a cluster.
About this task
To install and configure WebSphere
Application Server Network Deployment, complete the following tasks:
Parent topic: Pre-installation tasks
Securing IBM Connections
Preparing to configure the LDAP directory
Setting up federated repositories
Populating the Profiles database
Installing IBM Connections 3.0.1
Adding a node to a cluster
IBM Connections system requirements
- Install WebSphere Application Server Network Deployment.
For more information, go to the WebSphere Application Server 7.0 information center
Enable security when the installation wizard requests it. The administrative user ID that you create must be unique and must not exist in the LDAP repository that you plan to federate.
- Apply the available fix packs.
See the IBM Connections system requirements topic for details.
- Configure WebSphere Application Server to communicate with the LDAP directory. For more information, see the Setting up federated repositories topic.
Perform this step on the Deployment Manager Integrated Solutions Console.
- Configure Application Security after you have completely installed WebSphere Application Server Network Deployment. For more information, see the Securing IBM Connections topic. For an overview of application server security, go to the Security topic in the WebSphere Application Server information center.
Note: Perform this step on the Deployment Manager Integrated Solutions Console.
- Optional: Add further nodes, if required, to the cell. Complete the following steps for each node that you want to add to the cell:
- Open a command prompt and change to the app_server_root/profiles/profile/bin directory, where <profile> is the name of the WebSphere Application Server installation on the node.
- Enter the following command:
addNode.sh|bat <DM_host> <DM_SoapPort> -username <AdminUserId> -password <AdminPwd>
- <DM_host> is the host name of the Deployment Manager
- <DM_SoapPort> is the SOAP port number of the Deployment Manager
- <AdminUserId> is the user ID for the Deployment Manager
- <AdminPwd> is the password for the Deployment Manager
- Repeat this step for each additional node that your want to add to the cell.
- Synchronize all the nodes.
Note: You can also add nodes after you have deployed IBM Connections. For more information, see the Adding a node to a cluster topic.