Zheng Tech Blog

In this post, I will go over the basics of two features in WebCenter Content (WCC) - Profile and Folder - and then talk about their own design considerations and usages, and finally discuss their differences. In WCC, the Profile (a.k.a metadata profile or content profile, to differentiate from user profile) is an approach of metadata modeling. The profile is a powerful tool that can be used to manage the metadata fields to achieve efficient processing of content items, such as check-in, update, search, etc. Essentially, content profiles consist of set of rules that manage the display of the metadata fields of content items. Through content profiles, you can control what metadata fields should be displayed/hidden, required or not, read-only/editable, initialized with default value or not, and grouped based on the action to the content – whether you are viewing the content information, checking in, updating or searching. Profile provides the capability to customize the user ...

As of late April 2014, FrameworkFolders support on Oracle WebCenter Portal has been enabled by Oracle WebCenter 11.1.1.8.3 . Previously, Oracle WebCenter Portal only supported Folders_g. Now it's time to review the essentials on what , why and how . What's Framework Folders? Introduced in WebCenter PS5, the framework folders (also called folders component) provide a hierarchical folder interface, similar to conventional file system, for organizing and locating some or all of the content in the repository. It's a scalable, enterprise solution and is meant to be a replacement for contribution folders (folders_g component). Why it's better than Folders_g (FrameworkFolders vs. Folders_g)? With the FrameworkFolders component as the underlying folder architecture, many functionalities and features have been made available. Mass metadata updates with folders (metadata propagation):  "Query Folders" is added in the FrameworkFolders component. Query fold...

Update : The Oracle Patch on the bug has been released: Patch 17328920 : CONTENT PRESENTER THROWS STUCK THREAD AND OOM WHEN UCM RETURNS MANY PROFILES.  In this fix, a system parameter "contentTypeLazyCaching=true" is requested to be added on the JVM startup. Custom code has been added into the ContentTypeFactory.class in the two places: %ORACLE_HOME%/webcenter/modules/oracle.webcenter.content.integration_11.1.1/ucm_spi.jar/oracle/webcenter/content/integration/spi/ucm/factory/ContentTypeFactory.class %ORACLE_HOME%/webcenter/modules/oracle.webcenter.content.integration_11.1.1/content-app-lib.ear/APP-INF/lib/ucm_spi.jar/oracle/webcenter/content/integration/spi/ucm/factory/ContentTypeFactory.class The directory could be either on your local Jdev folder or on the remote WebCenter portal server. The added custom code is a new method getMinimalContentTypes():   public synchronized List<ContentType> getMinimalContentTypes()     throws RepositoryExc...