Post-deployment tasks for Db2 Text Search (Db2TS) Services Support

After successfully installing the Db2 Text Search Services Support, follow the procedure given in this topic.

Before you begin

Content Collector 4.0.1 fix pack 14 (4.0.1.14) and later: Refer to the 'IBM Content Manager Db2 Text Search (Db2TS) support' section of Prerequisites for running Content Collector Server and its components.

Procedure

  1. Navigate to the Db2TS installation directory: <Db2TS_Services_Support_InstallDir>.
  2. The installer deploys the following two scripts to insert the custom constructors of Content Collector for Email and SharePoint.
    1. If you select Email as your source document at the time of installation of Db2TS, run the following scripts to insert the Email specific constructor to the database:

      Windows: Run the AddICCConstructor_Email.ps1 script.

      Non-Windows: Run the AddICCConstructor_Email.sh script as a Db2 instance user. For example, su db2inst1.

    2. If you select SharePoint as your source document at the time of installation of Db2TS, run the following scripts to insert the SharePoint specific constructor to the database:

      Windows: Run the AddICCConstructor_SharePoint.ps1 script.

      Non-Windows: Run the AddICCConstructor_SharePoint.sh script as a Db2 instance user. For example, su db2inst1.

    3. If you select Email as well as SharePoint as your source document at the time of installation of Db2TS, run the following scripts one after the other to insert both Email and SharePoint specific constructors to the database:
      Windows:
      1. Run the AddICCConstructor_Email.ps1 script.
      2. Run the AddICCConstructor_SharePoint.ps1 script.
      Non-Windows:
      1. Run the AddICCConstructor_Email.sh script as a Db2 instance user. For example, su db2inst1.
      2. Run the AddICCConstructor_SharePoint.sh script as a Db2 instance user. For example, su db2inst1.
    4. If you select File System as your source document at the time of installation of Db2TS, you do not need run any scripts because the File System source documents use the default constructor provided by the CM8.

      Note that the default constructor is added during the Content Manager profile configuration.

  3. Provide the following details to establish a connection with the library server database:
    • Library Server database: icmnlsdb
    • Library Server username: icmadmin
    • Enter the Library Server password.
    Attention: If the script(s) in Step 2 fails, you need to add the constructors manually to the Content Manager repository using the Db2 Command Line or the SQL client. For adding the constructors manually, refer to the relevant section below, and perform the rest of the procedure.
  4. Restart the Db2TS service so that the database related changes are picked up.

Steps to manually insert the Email constructor to the database

  1. When using Db2 command line, establish a connection with CM8, Connect to the <library server database>user<library server user>, press Enter and provide the password.
  2. Run the following query to verify if the constructor entry of the email already exists:
    SELECT COUNT(*) AS COUNT from SYSIBMTS.SYSTSDEFAULTS WHERE NAME = 'DATAPREP:AFUCTOR4EMAIL'
  3. Run the following query to add the Email constructor entry if not already present:
    INSERT INTO SYSIBMTS.SYSTSDEFAULTS VALUES('DATAPREP:AFUCTOR4EMAIL ', '', 1)
  4. Run the following query to verify if the constructor has been inserted:
    SELECT COUNT(*) AS COUNT from SYSIBMTS.SYSTSDEFAULTS WHERE NAME = 'DATAPREP:AFUCTOR4EMAIL'

Steps to manually insert the SharePoint constructor to the database

  1. When using Db2 command line, establish a connection with CM8, connect to the <library server database>user<library server user>, press Enter and provide the password.
  2. Run the following query to verify if the constructor entry of the SharePoint already exists:
    SELECT COUNT(*) AS COUNT from SYSIBMTS.SYSTSDEFAULTS WHERE NAME = 'DATAPREP:AFUCTOR4SHAREPOINT'
  3. Run the following query to add the SharePoint constructor entry if not already present:
    INSERT INTO SYSIBMTS.SYSTSDEFAULTS VALUES('DATAPREP:AFUCTOR4SHAREPOINT ', '', 1)
  4. Run the following query to verify if the constructor has been inserted:
    SELECT COUNT(*) AS COUNT from SYSIBMTS.SYSTSDEFAULTS WHERE NAME = 'DATAPREP:AFUCTOR4SHAREPOINT'