Home
Deploying HCL Connections Docs 2.0.1
Welcome to the HCL Connections Docs 2.0.1 documentation, where you can find information about installing and deploying HCL Docs 2.0.1. HCL Docs is a collaborative productivity suite that enables you to work on documents, spreadsheets and presentations together in the cloud.
Security
You might need to refer to this section during deployment. HCL Docs supports WebSEAL. This section is for setting up single sign-on (SSO) if installing HCL Docs in the same cell as IBM® Connections.
Enabling WebSEAL SSO for Tivoli Access Manager
You can enable WebSEAL single sign-on (SSO) for Tivoli Access Manager.
Configuring SSO between Connections and WebSEAL
To enable single sign-on (SSO) for IBM Security Access Manager (ISAM), you first configure SSO between HCL Connections and WebSEAL.

Deploying HCL Connections Docs 2.0.1
Welcome to the HCL Connections Docs 2.0.1 documentation, where you can find information about installing and deploying HCL Docs 2.0.1. HCL Docs is a collaborative productivity suite that enables you to work on documents, spreadsheets and presentations together in the cloud.
- Overview
  HCL Connections™ Docs extends HCL Connections, offering real-time, co-editing support designed to help users collaborate on documents together.
- Planning
  Before installing HCL Docs, review the system requirements and deployment options, and then complete the worksheets.
- Installing
  To install HCL Docs, complete the following procedures in the sequence shown.
- Upgrading or migrating
  You can upgrade HCL Connections™ Docs from the previous two releases to the current release by using the installer or upgrade scripts. You can also install the latest release on new hardware and then do a side-by-side migration from the old to the new.
- Security
  You might need to refer to this section during deployment. HCL Docs supports WebSEAL. This section is for setting up single sign-on (SSO) if installing HCL Docs in the same cell as IBM® Connections.
  - Forcing traffic to be sent over SSL
    Although HCL Docs supports both http and https protocols, it is best to force https traffic. To force https, you must first configure the HTTP server.
  - Enabling WebSEAL SSO for Tivoli Access Manager
    You can enable WebSEAL single sign-on (SSO) for Tivoli Access Manager.
    - Configuring SSO between Connections and WebSEAL
      To enable single sign-on (SSO) for IBM Security Access Manager (ISAM), you first configure SSO between HCL Connections and WebSEAL.
    - Configuring SSO between HCL Docs, File Viewer and WebSEAL
      After you configure SSO between HCL Connections and WebSEAL, you must then configure HCL Docs, HCL File Viewer and WebSEAL.
  - Enabling single sign-on for SiteMinder
    Configure HCL Docs to use Computer Associates' SiteMinder to implement user authentication and single sign-on (SSO).
  - Enabling single sign-on for Windows desktop
    Configure HCL Docs to use SPNEGO for single sign-on (SSO). This configuration permits users to sign in to the Microsoft Windows desktop and automatically authenticate with HCL Docs.
  - Setting up SAML 2.0 for HCL Docs
    The steps for setting up SAML 2.0 are different depending on whether HCL Docs and Connections are installed on the same cell or on two cells.
- Performance tuning
- Troubleshooting and support
  To isolate and resolve problems with your deployment, you can use the troubleshooting and support information.

Configuring SSO between Connections and WebSEAL

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

Procedure

To configure SSO between Connections and WebSEAL, see

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

Notes:

If you are adding Active Directory after deploying Connections, take the following actions, detailed in the 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 Security Access Manager keystore, see step 3c in Enabling single sign-on for Security Access Manager in the 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

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.