This content has been marked as final. Show 3 replies
If you mean ingesting content from a CMS, that is pretty straightforward. I assume you must mean integrating the front-end experience management aspects of a CMS with Oracle Endeca Experience Manager? Is that right? If so, which CMS?
Hi Mandar -
Ok, so you just want to pull CMS data into Endeca?
There are lots of ways to do that. Here is one high-level recipe.
1 - Get the data from the CMS.
Most CMS systems have the concept of "preview" and "live" content in a given environment, so you'll need to know how to tell the difference between unpublished and published content. For a simple integration we did with one CMS, we created a JSP display view to produce an Endeca-friendly XML representation of the CMS content. Most CMS systems have business user-friendly query languages - we tied our display view to a query for all published content.
There are likely going to be a lot of ways you can do this even within a single CMS, we'd suggest you find a way that makes use of the CMS's display cache so that your updates run faster than if you were hitting the CMS database/content store directly.
2 - Get the content into Endeca.
To do this you create an Endeca Content Adaptor for the CMS. For the example above, we set the QUERYURL passthrough to the URL of the display view described above. The Content Adaptor gets the XML from the CMS and pulls it in.
3 - Display data from Endeca (e.g. search results). This part is hard to describe generally, but in the example I've been going through above, we created a JSR 286 portlet for displaying search results. The portlet queries Endeca via APIs.
I am not very technical. If you needed to go deeper than this, you'd need to talk to one of our developers.