midcom.services.indexer

1. Installing MidCOM indexer
2. Configuring the MidCOM Indexer Daemon (Quick start guide)
1. bind and port
2. logfile
3. loglevel

midcom.services.indexer is the integrated full-text search system in MidCOM. It utilizes the Apache Lucene for actual search capabilities.

Installing MidCOM indexer

See the midcom.services.indexer installation document.

Configuring the MidCOM Indexer Daemon (Quick start guide)

The MidCOM index daemon takes an optional filename as an argument during startup. It allows you to control four parameters: IP and port to bind to, log file name and log level. We are using standard Java Property files here, which consist of name = value pairs.

So a debug.conf example config file could look like this:

logfile = debug.log
loglevel = FINEST

which would be used like this:

java -jar indexer.jar debug.conf

bind and port

These two parameters control where the daemon binds to. By default bind is set to 127.0.0.1 and port to 2222, which matches the MidCOM default configuration and is thus fine if you are working in the default installation environment.

logfile

This parameter defaults to stderr which, naturally, logs to the stderr pipe the daemon launches with. You can set any valid filename here, of course we need write permission.

Log files are limited to 5 MB in size and are automatically rotated 4 times.

loglevel

Specifies what to log, we use the log levels defined in the Java package java.util.logging.Level here, defaulting to WARNING. Valid log levels, from most terse to most verbose:

• SEVERE
• WARNING
• INFO
• CONFIG
• FINE
• FINER
• FINEST

Note, that not all of these log levels are in use yet, so don't wonder if you have no differences when moving between adjecant log levels.

WARNING is recommended for day-to-day operation, FINEST for debugging only. If you want to log each connection attempt, use INFO.