manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: config files for ManifoldCF
Date Sun, 02 Oct 2011 23:43:06 GMT
Hi Swapna,

To clarify Piergiorgio's answer a little, ManifoldCF uses a
properties.xml file for its basic configuration information.  However,
everything else is kept in the database.  That includes connection
definitions and job definitions.  I recommend that you start by using
the Quick-Start example uses an embedded Apache Derby database
instance, by default.  You can change this later, of course.  For real
work we recommend PostgreSQL.

You can find more information at
Have a look at the quick-start instructions.


On Sun, Oct 2, 2011 at 1:43 PM, Piergiorgio Lucidi
<> wrote:
> Hi Swapna,
> 2011/10/2 Swapna Vuppala <>
>> Hi,
>> Am new to using ManifoldCF and I have got couple of doubts about using it.
>> Am interested in knowing about what are the config files that are used in
>> ManifoldCF, where they are located and how they are used. Also, I was
>> wondering where all the information about output connection definitions,
>> repository definitions and job definitions, defined by a user using the
>> crawler UI, are stored.
> The unique config file is the properties.xml that you need to add a new JVM
> parameter:
> -Dorg.apache.manifoldcf.configfile=<configuration file path>
> This only if you are deploying ManifoldCF in an application server.
> Otherwise you can leave properties.xml in your "<user home>/lcf" folder.
> You can find an example of the properties.xml file in the dist/example
> folder of the distribution bundle.
> All the information managed by the UI Crawler are stored in a database, HSQL
> by default but you can configure a Postgresql DBMS changing the
> properties.xml file, for more information about all the parameters you can
> visit the following page:
> Hope this helps.
> Piergiorgio
>> Can you please help me in clarifying these doubts ?
>> Thanks and Regards,
>> Swapna.
> --
> Piergiorgio Lucidi

View raw message