1. WCM Social Rendering - this is a specialized approach if you happen to mean the instance of FileNet used by Connections, and the libraries created in Connections Content Manager. There is a generalization of this pattern though that will apply to any FileNet instance, which leads us to:
2. Pluggable List Framework - this is a generalization of the WCM Social Rendering which allows WCM to render content from external datasource. For a FileNet customer who just wants to render a dynamic list of stuff from FileNet in their portal, maybe with links pointing to FileNet UIs like Navigator, this is the way to go. You could further use something like Web Application Bridge (WAB) or Web Application Integrator (WAI) to integrate the full IBM Content Navigator UI.
3. Navigator UI Framework - a set of Dijits provided by FileNet in IBM Content Navigator for building document management UIs. For a FileNet customer who wants highly specialized or customizable document management UIs, this is the way to go.
4. CCM portlet - we provide an out of the box portlet for CCM, which is basically the CCM capabilities we have in Connections, just boxed into a portlet. It literally uses the exact same code as our CCM library widget in communities. Only applies to libraries created by CCM though.