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.
- When you name the servers that you create, it is a best practice
to indicate the type of server in the server name. Otherwise, when
you configure Content Engine by
using Enterprise Manager, it can be
difficult to determine which server to select for an action. For example,
use server_name_broker to
indicate a Broker Server service.
- Record the server names, port numbers, and settings that you define.
Much of the following information will be required later when you
configure the IBM FileNet® P8 Content Engine for content-based retrieval
later.
- A range of ports is recommended in the Verity K2 Dashboard for
each service you create. You do not have to choose a port number from
within that range.
- Repeat the related step in the procedure below to add additional
services. Some guidelines must be adhered to when adding additional
services:
- Multiple brokers can be assigned, so that if one goes down the
others will be used. However, each broker must have all K2 Servers
(search servers) attached that are needed to access collections (index
areas). The Content Engine Server
will not call multiple brokers and merge the results.
- If you add additional Index Servers and K2 Servers (search servers),
they will not be activated until you enable them through Enterprise Manager. See Configure Content Engine for content-based
retrieval for details.
- Each K2 Administration Server must contain a Ticket Server for Content Engine.
- For good stability and performance, Broker Servers must be attached
to local Ticket Servers for security on each machine.
- In the following procedure you must import the IBM FileNet Styleset only once, regardless how
many K2 Administration Server machines you install.
To configure IBM Legacy
Content Search Engine:
- (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
- Access the K2 Dashboard by launching your browser and
entering:
http://Master Administration Server
hostname:9990/verity_dashboard/main.jsp
Note: In a highly available environment, use the cluster
name for the K2 Dashboard URL entry.
- Create a K2 Index Server, as follows:
- Click K2 Index Servers under System
View.
- Click Add a K2 Index Server on
the K2 Index Server Summary page.
- 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)
- Click Next to continue with
the installation.
- Enter the following information on the Configure threads
for the K2 Index Server page:
- Synchronous Threads: 25
- Asynchronous Threads: 3
- Access Type: Authorized Administrator
- Click Finish to continue with
the installation.
- Set the Index Server logging properties:
- Click the Index Server, under System View, that you
want to adjust.
- Click Edit Properties under
Actions.
- Click the Logging tab.
- For Status Log Nominal Size, enter the following value:
9000 kilobytes
- Click Modify.
- Create a K2 Broker Server:
- Click K2 Brokers under System
View.
- Click Add a K2 Broker on the K2
Broker Summary page.
- 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)
- Click Finish.
- Create a K2 Server (search server) and attach the Broker:
- Click K2 Servers under System
View.
- Click Add a K2 Server under Actions on
the K2 Server Summary page.
- 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)
- Click Next.
- Click Next on the Set
security options for this service page.
- 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.
- Click Finish.
- Import the IBM FileNet Styleset.
- Click Collections under System
View.
- Click Manage Style Sets under Actions on
the Collection Summary page.
- Click Import on the Manage
Style Sets page (top right).
- 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
- 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.
- Navigate to the source path you specified in the preceding
step and complete the following substeps:
- Open the file style.ufl for editing.
- 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
}
- Save and close the file.
- Create a K2 Ticket Server.
- Click K2 Ticket Servers under System
View.
- Click Add a K2 Ticket Server under
Actions on the K2 Ticket Server
Summary page.
- 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)
- Click Next.
- Enter the following information on the Configure the
login module to use with this K2 Ticket Server page:
- Click Next.
- 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.
- Click Finish.
- (Windows only)
Specify local login settings:
- Click Edit Properties.
- Click Windows Login
Module.
- Check Use Local Credentials:.
- Check Enable Built-in Groups.
- Click Modify.
- Set Autonomy K2 Administration Security.
- Click the K2 Ticket Server you created.
- Click Manage Administration Security under
Actions.
- 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.
- 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.
- Launch the K2 Dashboard and log on.
- Restart K2 services:
- 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.
- 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.
- Enable additional K2 Admin Users (optional).
- From the K2 Dashboard home page, click Administration
Servers.
- Click Manage K2 Administrative Users.
- Click Add User on the Manage
K2 Administrative Users page.
- Enter the name of an authenticated user on the directory
service that you want to make a K2 Administrator and click Add.
- Enable security on the K2 services you have created.
- From the K2 Dashboard home page, click K2
Ticket Servers.
- Click your ticket server server_name_ticket_server.
- Click Manage K2 Broker/K2 Server Security in
the Services Secured by this K2 Ticket Server section of the page
(bottom right).
- Click the K2 Servers button
on the Manage K2 Broker/K2 Server Security page.
- 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.
- Click the K2 Brokers button
on the Manage K2 Broker/K2 Server Security page.
- Click the Broker in the window on the right that you
want to attach to the local K2 ticket server you selected above.
- Click Modify to save your changes.
- Restart K2 services, as follows:
- Click Home in the top left corner
of the page.
- 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.