Over the years there have been many attempts at integrating WebCenter Sites with WebCenter Portal (and vice versa). None of these attempts were without significant issues and none have met with wide acceptance in the field.
This blog post suggests a very simple pattern that would provide a lot of value for many clients. The primary goal here is not to attempt to propose an "all encompassing" integration that does everything. Instead, it does one thing very well and uses both products for what they are good at.
It should be obvious where I'm going with this: one of the primary use cases for WebCenter Sites is to provide aggregated static content for re-use by WebCenter Portal. Yet most integrations to date have focused on either getting dynamic WCS content to be rendered within the Portal or to get dynamic portlets to be somehow be made reusable on other rendering frameworks. Given that the technical hurdles on integrating the two products at the dynamic/stateful level are significant, the rest of this blog will deal with the less-sexy but just as viable "Static WCS-managed content repurposed on WebCenter Portal" pattern.
This blog is in reality just another extension of the "Three Patterns for Integrating WebCenter Sites with Oracle Commerce" technical white paper published in August 2014 here on the A-Team Chronicles blog. You should study this document as the details described within that document pertain directly to what is being proposed here in this blog post. The details are not duplicated here in this blog post. Link here: Three Patterns for integrating Webcenter Sites with Oracle Commerce
In the aforementioned document, if one were to globally replace "Oracle Commerce" with "WebCenter Portal" and "Oracle Commerce Guided Search" (i.e. Endeca) with "WebCenter Content", you would then have the gist of the patterns/use cases needed to support either:
The core pattern leveraged in this integration is simple:
WebCenter Sites publishes aggregated content and its metadata to WebCenter Content. Once the content is in WCC then the "normal" WCC + WCP integrations described in other Oracle documents, blogs, and white papers are implemented.
Note: the specific integrations between WCC and WCP are not redundantly documented here.
The following diagram shows how the the core CommerceExport DeliveryType mechanism as detailed in the "Three Patterns..." White paper is repurposed to enable a flexible WebCenter Sites integration with WebCenter Portal without the usual downsides.
If we are only talking about the need to support Pattern 1, then each Sites-populated WCC record should contain the following:
If we are talking about the more complex side-by-side deployment where links embedded in the rendered content shown on a Portal page take you to a Sites webpage, the the WCC record should contain the following:
Given that the proposed solution leverages and builds upon the concept of renditions as described in detail in the "Three Patterns for Integrating WebCenter Sites and Oracle Commerce" white paper, we can envision all sorts of "renditions" that might be of use to WebCenter Portal including but not limited to the following:
Note that in the case of lists and other aggregates, it might be required that the list, hierarchy, or navigation should be provided as a JSON or XML data structure for a particular portlet to do the actual rendering (perhaps adding to or removing items per visitor ACL). This is straightforward as the concepts of renditions do not preclude the rendering of plain text, html, xml, json, or whatever.