1 person found this helpful
You might be interested in an approach we used for the "FAST connector" we developed as featurepack for CQ 5.3 and 5.4. The approach is to use the build-in capabilities of CQ's replication mechanism to send pages to the search engine, instead of implementing some listener to crawl through CRX. At any page or tree activation, together with the usual replication agents the FAST replication agents is triggered who then assembles a FAST document, adds configurable metadata, and sends the final doc to one or many FAST ESP servers/collections. This way no listener on CQ is required, indexing happens right at content activation. Performance to be verified but should not be an issue as the FAST replication agent for example can be configured to not listen to FAST server response but "fire" one doc after each other to FAST.
Public documentation is available at: http://dev.day.com/docs/en/cq/current/administering/cq2fast.html
Such a connector is not yet developed for Endeca search engines. If you are interested in discussing features, schedule and cost for such a product enhancement in form of a featurepack, please contact email@example.com.
If this idea does not cover your requirements at all, please skip the idea
Is there an updated URL to the FAST feature pack listed above? It returns a 404 and the featurepack doesn't exist on the packageshare.
If this process no longer applies to 5.5, is there any updated documentation, processes, whitepapers, etc. customers can use to integarte Endeca?
Shams link is correct, its for the CQ 5.4 "FAST connector for FAST ESP 5.3": http://dev.day.com/docs/en/cq/5-4/administering/cq2fast.html
We have a new FAST Connector for CQ 5.5, "FAST connector for SP 2010 Fast Searchserver", docs is now under http://dev.day.com/docs/en/cq/current/administering/cq2fast2010.html (we only support the newer Fast Searchserver now, thats why the URL changed. FAST ESP might not be supported by MS anymore in the near future).
Both connectors, the older CQ 5.4 ESP and the newer CQ 5.5 Searchserver one, use the push mechanismn by replicating content to FAST via CQ replication.
We also have the same need. We need to integrate CQ with Endeca.
Please share some information on this. Thanks.