Configuring HCL Docs to automatically check in documents to FileNet in IBM Content Navigator

In HCL Docs 2.0 CR3 integration with FileNet, auto check-in is supported and content input in HCL Docs can be automatically checked into FileNet repository when closing the edit session.

About this task

You can set default auto check-in on or off by configuration. With auto check-in on, the content is automatically checked in as a new major version by default when the user who checked out the document closes the edit session. With auto check-in off, the content is automatically saved in minor version by default when the user who checked out the document closes the edit session.
Note: If the file has no change, it will not be automatically checked in when the user who checked out the document closes the edit session.

Procedure

  1. Revise Docs configuration.
    1. Locate file in $WAS_INSTALL_ROOT/profiles/Dmgr01/config/cells/${CELLNAME}/IBMDocs-config, for example, on Linux, it is: /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/${CELLNAME}/IBMDocs-config/concord-config.json.

      Where: ${CELLNAME} is the actual cell name

    2. Change section as below:
      "auto-checkin" :
      {
      "default-auto-checkin" : "true"
      },

      Where:

      true means to set auto check-in on by default and false means to set auto check-in off by default. The user who checked out the document can enable or disable auto check-in later by clicking File > Check in Automatically from the main menu.

      Note:
      • It is strongly recommended to set auto check-in as false if there is a need of real time co-editing.
      • After changing the configuration file, when you restart the Docs server, make sure that there is no problem found in SystemOut.log of Docs server.
  2. Synchronize the changes to all nodes after revising Docs configuration.
    1. Open WebSphere console.
    2. Click System administration > Nodes.
    3. Select all nodes and click the Synchronize button.
  3. Restart Docs Cluster.
    1. Open WebSphere console.
    2. Click Servers > Clusters > WebSphere application server clusters > IBMDocsCluster.
    3. Select Stop and then Start to restart the cluster.