Posts tagged Content Services
- Abhijit Ghosh, TRT Engineer @ Adobe
Content services uses the filesystem to store Apache Lucene indexes (/lucene-indexes). At times we are faced with the need of re-building indexes hence just wanted to summarize the ways in which the same can be achieved:
1. Include the JVM argument –Dindex.recovery.mode=FULL and restart the server.
2. Stop the server, delete the lucene indexes under the index root directory and restart the server.
3. Change the index directory to a different location during restart so that indexes are re-built again.
Adobe Content Services sometimes takes a lot of amount to delete a directory if there are a lots of nodes under the tree.
Suppose we need to delete Myapp node in the figure above. The conventional way to delete is through the Content Space UI. However, if the subtree rooted at Myapp is relatively large, it may take long time to delete the sub-tree.
A script has been written specifically for Oracle DB which helps in deleting the node in a definite amount of time. Here are the steps to be followed:
Read the complete post at Adobe LiveCycle Blog.
A source of confusion I’ve come across when explaining the new world of ADEP to those familiar with the LiveCycle days is what has happened to Content Services. Content Services was essentially the repository for storing files and anything else you needed persisting in your application. It was built around the Open Source CMS by Alfresco and was used on almost all of the projects I worked on. In the move to ADEP it’s the one module the fate of which I wasn’t 100% sure of.
You can disable content indexing to improve Content Services 9 performance. Disabling indexing also disables text-based search within new content. However, you can still search within already-indexed content.
Follow these steps to disable indexing:
- 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.
- Locate the following line:
- 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>.
Disable the conversions required for indexing
To realize additional performance improvements, disable the conversions required for indexing. Follow these steps:
- In adobe-contentservices.ear, browse to contentservices.warWEB-INFclassesalfrescoextension.
- Preserve a backup of the custom-metadata-extractors-context file.
- Delete this file from the EAR.
Original article at http://blogs.adobe.com/livecycledocs/2010/12/content-services-disable-content-indexing.html.