Install IBM WebSphere Application Server

WebSphere Application Server Network Deployment is provided with Connections. We can deploy one node on the same system as the dmgr but use separate systems for all other nodes in a cluster. To install and configure...

1. Install WebSphere Application Server Network Deployment.

   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 to federate.

2. Apply the available fix packs.

3. Java 2 security is disabled by default in WebSphere and must remain disabled for Connections.

   To confirm, from WAS console click...

   Security | Global | Java 2 security

   ...and ensure the option...

   Use Java 2 security to restrict application access to local resources

   ...is not selected.

4. Logout on HTTP Session Expiration must be disabled

   This WebSphere feature, disabled by default, is only applicable to single web applications that do not integrate with other web applications through single sign-on. Since IBM Connections is a set of tightly integrated web applications and not a single web application, this setting cannot be applied. Ensure that this setting is not enabled:

   In WAS console click....

   Security | Global | Custom properties

   ...and make sure that...

   com.ibm.ws.security.web.logoutOnHTTPSessionExpire

   ...is either not listed or set to false.

5. Configure WAS to communicate with the LDAP directory.

6. Configure Application Security

   Perform this step on the dmgr WAS console.

7. Add more nodes, if required, to the cell.
   cd app_server_root/profiles/profile/bin
   addNode.sh DM_host dmgr_SoapPort -username AdminUserId -password AdminPwd

   ...where...

   • DM_host is the host name of the deployment manager
   • DM_SoapPort is the SOAP port number of the dmgr
   • AdminUserId is the user ID for the deployment manager
   • AdminPwd is the password for the deployment manager

8. Synchronize all the nodes.

What to do next

• Create admin account for Connections, and FileNet
• We can add nodes after you have deployed IBM Connections.
• We can set up single sign on after you have deployed Connections.

Parent topic:
Pre-installation tasks

Related :

Deployment options
Set up federated repositories
Create the Cognos administrator account
Add a node to a cluster
System requirements
Before installing for migration