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

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

In the Navigation Model of a WebCenter Portal application (11g), there is an option to define a navigation resource by "external link". In a normal case, you should NOT define any internal JSPX page using this option, but only if there is a need to navigate to a third party site - by what the name means, an external link. The internal JSPX page should be added to the Navigation Model by the "page" type. The impact of defining internal JSPX page as an external link is, the redundant memory footprint due to the ADF control state token recreations every time this external link is clicked. ADF control token is an identifier used by the Controller to track user's state so that all in process task flows for the same user can be retrieved. Normally, this ADF control state should be not recreated for the same user. With the external link type, the navigation behaves like entering the application in a blank new context so every navigation with external link type will ...

There are a couple of ways to invalidate the session in WebCenter Portal (or ADF) application. They are not the same. They all would invalidate the user session which is intended. The main difference is around whether the session will be removed after it's invalidated. In this post, I will walk through this. In WebCenter Portal framework application, the built-in page template already has a logout function provided. Let's take a look at it. Create a WebCenter portal application and open up the page template as below In this JSPX file, you will find a logout command link with action specified as "#{o_w_s_l_LoginBackingBean.doLogout}". The source code of this bean is not available unless you trace back to the shipped libraries that were installed with Jdeveloper. Let's take a look at the effect of the logout function. Run the portal application. Open the local weblogic console, navigate to the deployment, find your application, go to applicatio...

If you are on edge of using IE as your support browser, IE 11 support on WebCenter has come. The patch for it is initially released via BP4 and included in BP5. Please see the link for the details: https://support.oracle.com/rs?type=doc&id=19194669.8 

With today’s quickly evolving web and advanced rendering capabilities, enterprise continues to seek applications with which to run massive amounts of transactional data on mobile devices. Few applications can support the increasing mobility of interfacing technologies, and those that do require teams of engineers to build and maintain them across multiple platforms. This extra layer of complexity and cost can prohibit some enterprises, and dissuade others seeking more flexible and wide-reaching data infrastructure. Read more ...

Hi there, For those of you who missed out my Collaborate 14 presentation on WebCenter Responsive Web Design, here is another chance for you to regain the opportunity, for free! Here is the summary of the talk. You can register the event by the link provided at the bottom. Thanks! Thursday, July 17th, 2014 12:00 p.m. - 1:00 p.m. CDT Mobilizing emerges as a "must-have" feature for modern web experience. Oracle WebCenter Portal 11.1.1.8 introduces multi-channel portal experience to support mobilized web for smart devices. This session reveals the essential secret sauce of the new mobilizing support – responsive web design, and teaches how to extend the responsive template to support your custom needs. The session helps to determine your mobile enterprise portal strategy and teaches how to build the responsive from scratch to create your own mobilized enterprise portal on WebCenter Portal Framework applications. Further, the session analyzes real world custome...

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

Short after my presentation on Responsive WebCenter Porta l @ Collaborate 14 in Vegas, I had a video interview with Bob Rhubart who runs Oracle ArchBeat - the official blog of the OTN Architect Community. In this 10 min talk, I had reviewed my presentation topic, the hot gossips in the hallway and the visions of hot topics in the next coming collaborate.

In this article I reviewed the essentials of responsive web design, walked through how to design and develop a responsive WebCenter Portal application, and reviewed the essential development considerations. The article covers technical aspects of building a responsive WebCenter Portal as well as the business decision points behind each scenario. It is intended for software architects, developers, and business users who regularly work with Oracle WebCenter Portal.

Thanks Martin Deh from A-Team for identifying it is a recently reported bug. To summarize the problem: during a load testing (>1000 users attempt) on a WebCenter framework application developed with content presenter task flows, the performance (page response time) was greatly impacted by a series of parked threads. The issue was not produced in the 1000 users test. The parked threads took from >30 seconds to minutes to resume. By investigating the stack trace, the culprit is pointed to java.util.concurrent.locks.ReentrantLock.lock() which is called by UCMBridge.getAccessLevel(IdcContext, DataObject, ITrace). This issue has been filed as a bug ( Bug 17330713 ) and the patch/fix is to be provided soon (Update: the patch is available as of date 11/4/2013 for 11.1.1.7.1) The following shows a graphic indication of the parked threads (gray) through the tests. As you can see, the gray areas took the majority of the timeline. Here is the stack track of one particular parked ...

Performance is a broad topic which is never out of date. I'd like to itemize a checklist with specific topics, links and references. Some topic may be more generic and some may be more specific. But this list mainly focuses on WebCenter Portal applications and its relevant products. This is not intended to be a complete list and there will never be. WebCenter Performance Tuning Guide HA for WebCenter Portal and ADF application Configure JOC for WebCenter Portal services Configure Coherence Caching for Content Presenting WebCenter Performance Study (Including Enable Client Caching and Compression) Tuning JVM Weblogic Capacity Planning Middleware Performance Tuning Roadmap Oracle HTTP Server Performance Tuning MDS Performance Tuning Using Cluster and HA Features Some Useful A-Team Blog Posts: High availability considerations for WebCenter Portal and ADF   Improving ADF Page Rendering Time : Progressively Loading Taskflows Configure Coherence for Oracl...

My previous post described a scenario that the OAM DCC programmatic authentication is not supported yet, and here I am presenting a nice alternative to do the DCC authentication non-programmatically. You may have a read on Frank's book "Oracle Fusion Developer Guide" and there is a section in the ADF security talking about "Creating a login form in JSF" programmatically. This approach works for JEE contained security but would not work well with your WebCenter Portal or ADF app integrated with OAM authentication. I am introducing an approach that does not require any programmatic authentication and can be used safely with any type of authentications (contained security or OAM authentication). Note: You can create HTML form in JSF but there are many limitations, such as only one form component can be allowed in a page. Due to this, it's impossible to support a complicated login page in JSF. It induced extra pitfalls and challenges on the skinning as we...