FileNet P8 Content Search Engine, Version 5.0.+            Operating systems:  AIX, HP-UX, Linux, Solaris, Windows

Configuring IBM Legacy Content Search Engine

Use this procedure to configure services required on the K2 Master Administration Server, and on additional Administration Servers you might install for IBM® Legacy Content Search Engine. All servers are configured through the Master Administration Server Dashboard.

To configure IBM Legacy Content Search Engine:

  1. (Optional) Configure the Autonomy K2 Dashboard to use SSL security. The Autonomy K2 Dashboard web application, by default, uses a non-SSL web site and sends username and password information in plain text. For information on how to modify your Tomcat web applications to use SSL, access the following address:

    http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html

  2. Access the K2 Dashboard by launching your browser and entering:

    http://Master Administration Server hostname:9990/verity_dashboard/main.jsp

    High availability Note: In a highly available environment, use the cluster name for the K2 Dashboard URL entry.
  3. Create a K2 Index Server, as follows:
    1. Click K2 Index Servers under System View.
    2. Click Add a K2 Index Server on the K2 Index Server Summary page.
    3. Enter the following information on the Configure basic settings for the new K2 Index Server page:
      • Service Alias: server_name _index_server
      • Port: 9960 - 9979 (suggested range)
    4. Click Next to continue with the installation.
    5. Enter the following information on the Configure threads for the K2 Index Server page:
      • Synchronous Threads: 25
      • Asynchronous Threads: 3
      • Access Type: Authorized Administrator
    6. Click Finish to continue with the installation.
  4. Set the Index Server logging properties:
    1. Click the Index Server, under System View, that you want to adjust.
    2. Click Edit Properties under Actions.
    3. Click the Logging tab.
    4. For Status Log Nominal Size, enter the following value:

      9000 kilobytes

    5. Click Modify.
  5. Create a K2 Broker Server:
    1. Click K2 Brokers under System View.
    2. Click Add a K2 Broker on the K2 Broker Summary page.
    3. Enter the following information on the Configure basic settings for the new K2 Broker page:
      • Service Alias: server_name _broker
      • Port: 9900 - 9909 (suggested range)
    4. Click Finish.
  6. Create a K2 Server (search server) and attach the Broker:
    1. Click K2 Servers under System View.
    2. Click Add a K2 Server under Actions on the K2 Server Summary page.
    3. Enter the following information on the Configure basic settings for the new K2 Server page:
      • Service Alias: server_name _search_server
      • Port: 9920 - 9949 (suggested range)
    4. Click Next.
    5. Click Next on the Set security options for this service page.
    6. Enter the following information on the Attach to K2 Brokers page:
      • Select the K2 Brokers that will provide access to this service: Select the K2 Broker you created in step 3 from the drop-down menu, server_name _broker.
    7. Click Finish.
  7. Import the IBM FileNet Styleset.
    1. Click Collections under System View.
    2. Click Manage Style Sets under Actions on the Collection Summary page.
    3. Click Import on the Manage Style Sets page (top right).
    4. Enter the following information on the Import page:
      • Style Set Alias: P8_CSE50
      • Gateway Type: --Auto-detect--
      • Source Administration Server. If multiple servers are installed, choose the server to which you will import the Styleset.
      • Source Path:
        Windows®
        verity_install_path\data\stylesets\P8_CSE50
        UNIX®
        verity_install_path/data/stylesets/P8_CSE50
    5. Click Import.
    Tip: The K2 Dashboard displays a notification that the StyleSet Editor web application cannot be accessed. You can ignore this message because it relates to a function that is not used by IBM Legacy Content Search Engine.
  8. Navigate to the source path you specified in the preceding step and complete the following substeps:
    1. Open the file style.ufl for editing.
    2. If it is not already present, add the CEMP definition at the bottom of the file:
      data-table: fce
      {
      fixwidth: cemp_partition_date 4 unsigned-integer
      }
    3. Save and close the file.
  9. Create a K2 Ticket Server.
    1. Click K2 Ticket Servers under System View.
    2. Click Add a K2 Ticket Server under Actions on the K2 Ticket Server Summary page.
    3. Enter the following information on the Configure basic settings for the new K2 Ticket Server page:
      • Service Alias: server_name _ticket_server
      • Port: 9910 - 9919 (recommended range)
    4. Click Next.
    5. Enter the following information on the Configure the login module to use with this K2 Ticket Server page:
      • Select which Login Module type to use with this K2 Ticket Server:
        • Windows
        • UNIX
        Restriction: LDAP Ticket Servers are not currently supported.
      • Default Domain (Windows only): Enter the domain on which this user and K2 Server are authenticated. If the server is in a workgroup, leave this field blank.
    6. Click Next.
    7. Enter the following information on the Configure the persistent store module to use with this K2 Ticket Server page:
      • Select the Persistent Store Module type to use with this K2 Ticket Server: Choose File and Memory.
    8. Click Finish.
    9. (Windows only) Specify local login settings:
      1. Click Edit Properties.
      2. Click Windows Login Module.
      3. Check Use Local Credentials:.
      4. Check Enable Built-in Groups.
      5. Click Modify.
  10. Set Autonomy K2 Administration Security.
    1. Click the K2 Ticket Server you created.
    2. Click Manage Administration Security under Actions.
    3. Enter the following information on the Manage Administration Security page:
      • Select a K2 Ticket Server to configure for administration security: From the drop-down menu, select the K2 Ticket Server you just created.
      • User Name: Enter the k2_os_user. For UNIX installs, this is the user you logged in as to run the installation.
      • Password: Enter the authentication password.
      • Default Domain (Windows only): Enter the domain on which this user and K2 Server are authenticated. If the server is in a workgroup, leave this field blank.
    4. Click Modify.

      The K2 software will authenticate the user based on the information you entered. If the check fails, an error message will indicate what failed and request that you re-enter the information.

      If administrator access is successful, Autonomy K2 will close the Dashboard and require that you log on again as the Dashboard Administrator to complete the configuration.

  11. Launch the K2 Dashboard and log on.
  12. Restart K2 services:
    1. Under Notifications on the K2 Dashboard Home page, a number of servers are listed as requiring a restart. Click Start/Stop this Service to access the settings page and follow the instructions listed there. Choose Full Restart to ensure that all services start as expected.
    2. Click Home in the top-left corner of the page after each restart to view the remaining notifications. Repeat the process until there are no notifications remaining.
  13. Enable additional K2 Admin Users (optional).
    1. From the K2 Dashboard home page, click Administration Servers.
    2. Click Manage K2 Administrative Users.
    3. Click Add User on the Manage K2 Administrative Users page.
    4. Enter the name of an authenticated user on the directory service that you want to make a K2 Administrator and click Add.
  14. Enable security on the K2 services you have created.
    1. From the K2 Dashboard home page, click K2 Ticket Servers.
    2. Click your ticket server server_name_ticket_server.
    3. Click Manage K2 Broker/K2 Server Security in the Services Secured by this K2 Ticket Server section of the page (bottom right).
    4. Click the K2 Servers button on the Manage K2 Broker/K2 Server Security page.
    5. Click the service you just created which is listed in the window on the right to enable security.
      Important: If you have a multi-server configuration, numerous services, installed on other machines, will be listed also. Select only the service to which you want to attach a broker. Brokers must be attached to local ticket servers for IBM Legacy Content Search Engine.
    6. Click the K2 Brokers button on the Manage K2 Broker/K2 Server Security page.
    7. Click the Broker in the window on the right that you want to attach to the local K2 ticket server you selected above.
    8. Click Modify to save your changes.
  15. Restart K2 services, as follows:
    1. Click Home in the top left corner of the page.
    2. Under Notifications on the Verity K2 Dashboard Home page, a number of servers are listed as requiring a restart. Click Start/Stop this Service to access the settings page and follow the instructions listed there. Choose Full Restart to ensure that all services start as expected. Click Home in the top left corner of the page after each restart to view the remaining notifications. Repeat the process until there are no notifications remaining.


Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)