FileNet P8 Content Search Engine, Version 5.0.+            Operating systems:  Windows

Windows-specific options

You can configure a read-only Autonomy K2 Administration server which will remotely read collections (note that you cannot have a second K2 Administration server that writes the collections). To do this, you must map a drive on the read-only Administration server to the file system on the Autonomy K2 machine that writes collections.

To do this, share the Autonomy K2 machine's collections drive (for example, D:\) as some name other than D$ , because you can't set permissions on D$ . For example, set it as DDrive .

Map the D:\ drive on the read-only Autonomy K2 machine to \\servername\DDrive .

Now D:\collections on the read-only Autonomy K2 machine references the same file system as the D:\ drive on the Autonomy K2 machine that writes the collections.

By default, the k2admin.exe program on the read-only Autonomy K2 machine runs as a Windows service. This is a problem because Windows services can not mount mapped drives.

One solution to this problem is to run the k2admin.exe program from a command line instead, so that it doesn't run as a Windows service. To launch the service manually from a command line on a default installation, run the following command:

C:\Program
Files\verity\k2_61\k2\_nti40\bin\k2admin.exe" -cfg "C:\Program
Files\verity\k2_61\k2\common\verity.cfg
Important: Only the Verity K2 6.1.1 Administration Server service (k2admin.exe) must be started this way. The Verity Administration Web Server might be left as a Windows service.
Another solution is to use a tool like the srvany.exe program (supplied as part of the Windows Resource kit) to run a .cmd file that first maps the drives, and then issues the command above to start the k2admin.exe service . The command to map drives, using the above example, is:
net use D: \\servername\DDrive

Independent software vendor products are available that function the same as the svrany.exe program.

Although the svrany.exe program will start the service correctly, it cannot stop the service. You must use the Autonomy rcadmin command line tool to stop the service, or use TaskManager and stop all the processes that start with the prefix k2 .

To use the Autonomy rcadmin program from a command line:
  1. Access a command line and type the following command: rcadmin
  2. Enter the following command to log on: login k2_os_user
  3. Enter the following command to initiate the shutdown: adminsignal
  4. Enter one of the following responses to the Type of Signal query:
    • 2 - Shutdown
    • 3 - WS Refresh
    • 4 - Restart all servers


Feedback

Last updated: November 2010


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