Zheng Tech Blog

For easy reference, here is a list of version contrast between patchset, WebCenter Portal, Jdeveloper with corresponding WebCenter extensions. (the info is extracted from Oracle doc  1627574.1) Patchset + Bundle Patch WebCenter Portal JDeveloper WebCenter Extension 12c 12.2.1.0.0 12.2.1.0.0 Framework: 12.2.1.0.0.151013.2001 Core: 12.2.1.0.0.151005.0601 dot9 + BP3 11.1.1.9.160119 11.1.1.9.0 11.1.1.9.0.160107.0701 dot9 + BP2 11.1.1.9.8 11.1.1.9.0 11.1.1.9.0.151005.2311 dot9 + BP1 11.1.1.9.2 11.1.1.9.0 11.1.1.9.0.150701.0100 dot9 11.1.1.9.0 11.1.1.9.0* 11.1.1.9.0.150521.2301* dot8 + BP8 11.1.1.8.8 11.1.1.7.0 11.1.1.8.0.150618.0701 dot8 + BP7 11.1.1.8.7 11.1.1.7.0 11.1.1.8.0.150331.0703 dot8 + BP6 11.1.1.8.6 11.1.1.7.0 11.1.1.8.0.141219.1406 dot8 + BP5 11.1.1.8.5 11.1.1.7.0 11.1.1.8.0.141001.1208 dot8 + BP4 11.1.1.8.4 11.1.1.7.0 11.1.1.8.0.140627.1403 dot8 + BP3 11.1.1.8.3 11.1.1.7.0 11.1.1.8.0.140404.0207 dot8 + BP2 11.1.1.8.2 11.1.1.7.0...

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 ...

Today, by using a simple example, I am going to demonstrate on how to build a concurrent web page in ADF using Jdeveloper. From time to time, I see requirements from various contexts with such needs to build concurrencies on web pages. The performance can be greatly benefited since multiple processes are executed at the same time so that the response time is greatly improved. It's also very suitable for the use cases that the processes are not associated with any user interface interactions, such as sending an email to user after performing some action but the web page does not need to know if/when the email is sent. Such processes can be executed in a separate thread from the main thread dealing with the web page rendering and other user interactions. Even if you don't have hard requirement on such concurrency needs, why waste it? Nowadays, all servers are built with multi-core computation capabilities and designed for parallel processing. In years the speed of the CPU is n...

In WebCenter Portal, you can define the URL parameter name/value pair in the URL parameters section in the Navigation Model. When you do that, the name/value pair will be added to the URL as a query string, such as "?name=value". As the header suggests, the URL parameter in the Navigation Model of WebCenter Portal application cannot be a NULL object. If the URL parameter is a static value, then it's not a concern. In case there is a need to dynamically populate the URL parameter in the navigation model, it's important to make sure the dynamical value cannot be NULL object. Because when the value is NULL, the navigation model does NOT know how to construct the query string. Note the NULL object is not equivalent to empty string. In this case, WebCenter Portal will not able to recognize the requested URL. In such case, it will redirect to the application context root which will induce the index page or whatever page you have define as the default page to render...