S2: Configuring SSL and adding features to the SSL trust store 

Next, the HTTP server needs to obtain the WebSphere^® Application Server certificate to enable trust between the HTTP Server and the WebSphere Application Server. This enables log in to Lotus^® Connections via the HTTP server since all communications will use SSL in this configuration.

Go to the next topic to complete the following actions:

• Adding WebSphere Application Server certificates to the IBM HTTP Server SSL key
• Adding features to the SSL trust store

---

Go to the next topic:

S2: Scenario environment
S2: Prerequisites
  S2: Configuration diagrams
S2: Machine details
S2: Installing Lotus Connections in an Enterprise level deployment

S2: Preinstallation tasks
S2: Installing Lotus Connections on node 1
S2: Adding nodes 2 and 3 to the cluster
S2: Post installation tasks
S2: Setting up the Web server
S2: Configuring SSL and adding features to the SSL trust store
S2: Adding WebSphere Application Server certificates to the IBM HTTP Server SSL key
S2: Adding features to the SSL trust store
S2: Editing the configuration file
S2: Scheduling Activities tasks
S2: Tuning WebSphere Application Server for optimal performance

S2: Starting Lotus Connections
S2: Configuring an administrative user for Blogs
S2: Integrating Lotus Connections with Lotus Quickr for WebSphere Portal
S2: Enabling Sametime awareness on Lotus Connections
S2: Troubleshooting

Table of Contents:
Lotus Connections 2.5 Enterprise level deployment scenario