HCL TECHNOLOGIES ABOUT US PRODUCTS & SOLUTIONS RESOURCES CONTACT US

Home
Deploying IBM Connections Docs 2.0 CR3Welcome to the IBM Connections Docs 2.0 CR3 documentation, where you can find information about installing and deploying IBM Docs 2.0 CR3. IBM Docs is a collaborative productivity suite that enables you to work on documents, spreadsheets and presentations together in the cloud. If you have IBM Docs 2.0, IBM Docs 2.0 CR1, or CR2 already installed, to install CR3, you only need to download the IBM Docs 2.0 CR3 zip package from FixCentral and extract the package. Then follow the instructions in the PDF file to install CR3. But if you have a version prior to IBM Docs 2.0, before installing CR3 package, you must follow instructions in this guide to install and deploy IBM Docs 2.0.
SecurityYou might need to refer to this section during deployment. IBM Docs supports WebSEAL. This section is for setting up single sign-on (SSO) if installing IBM Docs in the same cell as IBM® Connections.
Enabling WebSEAL SSO for Tivoli Access ManagerYou can enable WebSEAL single sign-on (SSO) for Tivoli Access Manager.
Configuring SSO between IBM® Connections and WebSEALTo enable single sign-on (SSO) for Tivoli® Access Manager, you first configure SSO between IBM® Connections and WebSEAL.

Configuring SSO between IBM Connections and WebSEAL

To enable single sign-on (SSO) for Tivoli® Access Manager, you first configure SSO between IBM® Connections and WebSEAL.

Procedure

To configure SSO between Connections and WebSEAL, see

Enabling single sign-on for Tivoli Access Manager in the IBM Connections wiki.

Notes:

If you are adding Active Directory after deploying IBM Connections, take the following actions, detailed in the IBM Connections wiki:
- Set up federated repositories.
- Add the Active Directory administrator as the administrator. See Changing references to administrative credentials.
- Populate the LDAP user to the profiles database. See Using the Profiles population wizard.
  Note: Make sure that the "sn" field in Active Directory is populated.
To import the truststore, see Adding certificates to the WebSphere® trust store.
For the correct .kdb file to import your IBM HTTP Server certificate into the Tivoli Access Manager keystore, see step 3c in Enabling single sign-on for Tivoli Access Manager in the IBM Connections wiki.
The .kdb file is usually in the WebSphere plug-in folder, with the host name as the file name, for example, /opt/IBM/WebSphere/Plugins/config/docs01/docs01.kdb