Performance Analysis of a Portal application is an area that is usually time consuming, since the typical portal is made up of numerous distinct task flows. The traditional approach relies on testing task flows in isolation and trying to gauge the performance impact each task flow makes to a page. With WebCenter Portal 184.108.40.206 however, this process becomes extremely simple and efficient.
WebCenter Portal 220.127.116.11 has an internal flag that customers can turn on, to show the performance of each ShowDetailFrame on the page. Since ShowDetailFrames enclose task flow regions on a page, this feature lets you instrument WebCenter pages on the basis of individual task flows. When enabled, you can visually analyze the performance of every single task flow on the page like this:
The feature is disabled by default, and users should take care to keep this disabled on their production instances, since exposing this debug information may not be desirable. Enabling the feature is done through MDS customization, so there is no need to restart the servers when enabling or disabling the feature.
In order to enable/disable this feature, customer needs to use exportMetaData/importMetadata in WLST to modify webcenter-config.xml.
Assuming /tmp/WCconfig exists:
exportMetadata(application='webcenter', server='WC_Spaces', toLocation='/tmp/WCconfig', docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')
This creates the file webcenter-config.xml in the path /tmp/WCconfig. Now we can edit the file and set perfdebug-enabled element to true or false:
Now we can import the configuration file:
importMetadata(application='webcenter', server='WC_Spaces',fromLocation='/tmp/WCconfig', docs='/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml')
Once this is done, any page in WebCenter Portal 18.104.22.168 can be instrumented. To instrument a page, simply append 'perfDebug=on' to the end of the URL to the page.
When the page loads, the page will report the overall performance of each ShowDetailFrame on the page. The property is saved in the current session. If you want to disable it simply append perfDebug=off on the end of the URL link.
For more information, see the documentation under "How to Identify Slow Page Components":
The one caveat for this method to work, in the Task Flow binding properties, the Task Flow activation should be set to deferred (which is the default in 22.214.171.124).