...
| Panel | ||||
|---|---|---|---|---|
| ||||
The method of indexing content in XperienCentral was changed in version R28 and further refined in version R29. |
Beginning in version R29R28, GX Software uses an XperienCentral-optimized implentation exclusively for indexing content on the frontend. This implementation was introduced in In XperienCentral version R28 and it , the implementation ran alongside the Apache Jackrabbit JCR index functionality. In XperienCentral versions R27 and earlier, XperienCentral used only Apache Jackrabbit for frontend searches.
In This Topic
| Table of Contents | ||
|---|---|---|
|
Configuring Apache Jackrabbit
Beginning in XperienCentral version R29, the Apache Jackrabbit JCR index functionality is disabled by default. If you want to use Apache Jackrabbit
...
with XperienCentral, follow the steps below in this topic. If you do not configure XperienCentral to use Apache Jackrabbit, the following functionality does not work:
- The JCR Browser
- The JCR Import/Export Tool
- Custom code which has not been rewritten to use the new index
In This Topic
| Table of Contents | ||
|---|---|---|
|
...
Configuring Apache Jackrabbit
If you want to use Apache Jackrabbit for frontend searches instead of the XperienCentral-optimized implementation, you must make a few configuration changes to your deployment.
To configure XperienCentral to use the Apache Jackrabbit JCR index implementation, follow these steps:
...