Content Services: Dependencies for indexing different types of content

Indexing of content in LiveCycle Content Services 9 depends on different LiveCycle ES2 components and services. Here are a few important prerequisites:

  • Indexing of PDF files (except for dynamic PDF forms) requires the Assembler service, which is part of all LiveCycle ES2 installations.
  • Indexing of dynamic PDF files requires LiveCycle Output 9. If Output is not installed, the FormDataIntegration service, available on all LiveCycle ES2 installations, is used instead. However, in such cases, for dynamic PDFs created in Acrobat, only the form data is indexed. The form design is left unindexed.
  • Indexing of Microsoft Word 2007/2010 files (.docx) requires PDF Generator 9 (the GeneratePDF service).
Additionally, files protected by LiveCycle Rights Management 9 are not indexed.

Content Services ES2: Improving performance

Thumbnail image for livecycle.jpg

You can disable content indexing to improve Content Services ES2 performance. However, keep in mind that disabling indexing will also disable text-based search within new content. To disable indexing:
  1. In the adobe-contentservices.ear file, navigate to
    LiveCycle Content Services.ear/contentservices.war/WEB-INF/classes/alfresco/model and open the contentModel.xml file for editing.
  2. Locate the following line:
    <type name=”cm:content”>
  3. Set the index enabled and tokenized properties to false.
  • Change <index enabled=”true”> to <index enabled=”false”>.
  • Change <tokenized>true </tokenised> to <tokenized>false </tokenised>.
For additional performance improvements, you can disable the conversions required for indexing. To disable conversions:
  1. In adobe-contentservices.ear, browse to
    contentservices.war\WEB-INF\classes\alfresco\extension.
  2. Preserve a backup of the custom-metadata-extractors-context file.
  3. Delete this file from the EAR.