element <config>

Namespace:	<global>
Type:	anySimpleType
Content:	simple
Defined:	locally at 1 location

May be included in elements (1):

searcher (type searcher)

Usage / Definition Locations

Within global complexTypes (1):
searcher

Annotation

Searcher configuration. This node is passed to the searcher object and its schema is specific for each searcher implementation. Schema for Default Implementation (className="lumis.search.lucene.LuceneSearcher") Example: <CODE> <indexBasePath>${lum_portalDataPath}lucene/index/${lum_serviceInstanceId}</indexBasePath> <indexBasePath indexerId="default" /> </CODE> Element <CODE>indexBasePath</CODE>: Define the path to the directory used by Lucene to search for data. The value can contain EL tags to be replaced in runtime by the respective field value. (e.g. <CODE>${lum_portalDataPath}</CODE> will be replaced by the value of the field with name <CODE>"lum_portalDataPath"</CODE>). The <CODE>config</CODE> element must contain at least one <CODE>indexBasePath</CODE> and can contain more than one of this element, to define one or more indexes to use when searching for data. The <CODE>indexerId</CODE> attribute can be used to specify that the <CODE>indexBasePath</CODE> element must use all <CODE>indexBasePath</CODE> definition of the specified indexer. This allows the reuse of a <CODE>indexBasePath</CODE> definition set.

XML Source

<xsd:element maxOccurs="1" minOccurs="1" name="config">

<xsd:annotation>

<xsd:documentation>

Searcher configuration. This node is passed to the searcher object and its schema is specific
for each searcher implementation.

Schema for Default Implementation (className="lumis.search.lucene.LuceneSearcher")

Example:

<CODE>

<indexBasePath>${lum_portalDataPath}lucene/index/${lum_serviceInstanceId}</indexBasePath>

</CODE>

Element

<CODE>indexBasePath</CODE>

: Define the path to the directory used by Lucene to search for data.

The value can contain EL tags to be replaced in runtime by the respective field value.
(e.g.

<CODE>${lum_portalDataPath}</CODE>

will be replaced by the value of the field with name

<CODE>"lum_portalDataPath"</CODE>

The

<CODE>config</CODE>

element must contain at least one

<CODE>indexBasePath</CODE>

and can contain more than
one of this element, to define one or more indexes to use when searching for data.

The

<CODE>indexerId</CODE>

attribute can be used to specify that the

<CODE>indexBasePath</CODE>

element
must use all

<CODE>indexBasePath</CODE>

definition of the specified indexer. This allows the reuse of a

<CODE>indexBasePath</CODE>

XML Schema documentation generated with DocFlex/XML (Kit) v1.6.2

DocFlex/XML is a powerful template-driven documentation and report generator from any data stored in XML files. Based on an innovative technology developed by FILIGRIS WORKS, this new tool offers virtuoso data querying and formatting capabilities not found in anything else!

Need to convert your XML data into a clear nice-looking documentation or reports? Web-ready hypertext HTML or printable MS Word / OpenOffice.org friendly RTF? DocFlex/XML may be a cheap, quick and effective solution exactly for this task!

Have questions? Not sure how to use it? Just send us e-mail to contact@filigris.com and we are always happy to help you! See also our services at www.filigris.com