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.
Installing
To install HCL Docs, complete the following procedures in the sequence shown.
Installing the HCL Docs components
You can run theHCL Docs GUI Installer or use the scripts to install the components.
Installing HCL Docs in another cell rather than Connections
Perform the tasks in this section to install HCL Docs and Connections in two different cells.
Merging IHS plugin-cfg.xml files for two IHS
Merge IHS plugin-cfg.xml files for two IHS.

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.
  - Pre-installation tasks
    A series of pre-installation tasks must be completed before you can deploy the HCL Docs infrastructure. These tasks include installing the system prerequisites and configuring both Windows™ and Linux™ operating systems.
  - Installing the HCL Docs components
    You can run theHCL Docs GUI Installer or use the scripts to install the components.
    - Installing the HCL Docs components using the installer
      To install HCL Docs, run the IBM Installation Manager installation program on the system where the WebSphere Application Server is installed and a node is federated into the Deployment Manager.
    - Installing the HCL Docs components using the scripts
      If you do not want to use the installer to install the components, you can use the scripts.
    - Installing HCL Docs in another cell rather than Connections
      Perform the tasks in this section to install HCL Docs and Connections in two different cells.
      - Installing required features on Deployment Manager
        Use the IBM Installation Manager (IM) installer to install required components in both HCL Docs Deployment Manager and Connections Deployment Manager.
      - Settings on Deployment Manager of Connections Docs and Connections
        Specify settings on Connections Docs DM and Connections DM.
      - Merging IHS plugin-cfg.xml files for two IHS
        Merge IHS plugin-cfg.xml files for two IHS.
    - Special cases for manually installing the extensions
      Installing the extensions and daemons was automated as part of the HCL Docs and File Viewer extension installation process since HCL Connections™ Docs 1.0.6. However, because the extensions and daemons must be installed on a server with access to the HCL Connections shared directory (where the provisions directory is located), there are some scenarios in which you must manually install the HCL Docs and File Viewer extensions and daemons, instead of relying on our script-based install to deploy these components.
  - Post-installation tasks
    These post-install steps are required after an installation or uninstall/install of HCL Docs. During an upgrade, these changes are preserved so do not need to be repeated during the upgrade process.
  - Uninstalling HCL Docs components
    You can use the installer or use uninstall scripts to uninstall HCL Docs automatically.
- 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.
- Performance tuning
- Troubleshooting and support
  To isolate and resolve problems with your deployment, you can use the troubleshooting and support information.

Merging IHS plugin-cfg.xml files for two IHS

Merge IHS plugin-cfg.xml files for two IHS.

Procedure

Merge IHS plugin-cfg.xml.
1. Get the plugin-cfg.xml file from IHS-1(Docs IHS) and put it in a folder, such as IHS1_FOLDER.
2. Get the plugin-cfg.xml file from IHS-2(Connections IHS) and put it in a folder, such as IHS2_FOLDER.
3. Run command to merge: WAS_HOME/bin/pluginCfgMerge.bat IHS1_FOLDER/plugin-cfg.xml IHS2_FOLDER/plugin-cfg.xml RESULT_FOLDER/plugin-cfg.xml
  Where:
  - IHS_ROOT is the folder where your IBM HTTPClient is installed.
  - IHS1_FOLDER is the folder that your Connections Docs plugin-cfg.xml file is located.
  - IHS2_FOLDER is the folder that your Connections plugin-cfg.xml file is located.
  - RESULT_FOLDER is the folder that your output is located.
  Note: You will lose some information if you put Connections plugin-cfg.xml files in first place for merging. The merged plugin-cfg.xml will be used to replace original file, but you must revise it manually before copying it because the configuration folder might be different for the two source plugin-cfg.xml files. For example, the reference folder might be /opt/IBM/HTTPServer/Plugins/config/IHS1 on IHS-1/plugin-cfg.xml, but the reference folder might be /opt/IBM/HTTPServer/Plugins/config/IHS2 in another.
Manually revise the merged plugin-cfg.xml on IHS-1 and IHS-2. Make a copy of the merged plugin-cfg.xml, open it with an text editor.
1. Find the reference path and replace it with the real path on IHS-1.
2. Copy and replace original plugin-cfg.xml on IHS-1
3. Stop/Start IHS service: /opt/IBM/HTTPServer/bin/apachectl stop/start
  Note:
  - As the merged plugin-cfg.xml comes from two xml, the reference path have both the path on IHS-1 and IHS-2, we need replace all the path referenced to IHS-2 path.
  - Do this step for IHS-2, we need replace all the path referenced to IHS-1 path
Go to proxy Clusters, add Connections IHS host name to trusted server list.
1. Log in WebSphere Application Console on Deployment Manager.
2. Select Servers > Cluster > Proxy Server Cluster.
3. Select IBMDocsProxyCluster, click proxy settings on Configuration tab.
4. Go to Security > Trust security proxies field.
5. Click New button, and enter Connections host name, for example, connections.ibm.com.
6. Click Apply and then click Save.
7. Restart proxy server to take effect.

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.