Webcenter | Techartifact

January 17, 2014January 20, 2014

Do your Webcenter portal 11.1.1.8 performance analysis

Performance Analysis of a Portal application or any application look tedious and tricky task .Reason portal application consist of various other task flow from different resources.Talking for webcenter portal 11.1.1.8 portal application have awesome feature of performance analysis called Portal Page Performance Analyzer. With WebCenter Portal 11.1.1.8 however, this process becomes extremely simple and efficient.

The portal page analyzer offers a simple way to diagnose slow pages and requires minimal set up or configuration. When this feature is on, the time spent on “high level” page components is calculated and displayed so you can see at a glance which components are slowing down your page. The overall time spent on the page also displays at the top left of the page

In WebCenter Portal, “high level” page components are wrapped in a ShowDetailFrame so they can be moved, hidden or shown on the page, and edited by Oracle Composer and it is the overall timing for each ShowDetailFrame that displays.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.

This feature is default by default.User have to turn on this feature.

How to enable/turn on this feature – -You can do by MDS customization.you need to update the metadata in webcenter-config.xml using WLST command of exportMetaData/importMetadata.

Steps

-> exportMetadata(application=’webcenter’, server=’WC_Spaces’, toLocation=’/tmp/mydata’, docs=’/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml’)

-> Open webcenter-config.xml exported from MDS in a text editor and set the perfdebug-enabled attribute to true to enable or false to disable this feature.

For example:

<webcenter:perfdebug-enabled>true</webcenter:perfdebug-enabled>

-> Save and close webcenter-config.xml.

-> Import the updated webcenter-config.xml file to MDS.

-> importMetadata(application=’webcenter’, server=’WC_Spaces’, fromLocation=’/tmp/mydata’, docs=’/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml’)

See how to run/excute exportMetaData/importMetadata command or update metadata in webcenter-config.xml

After this- any page in WebCenter Portal 11.1.1.8 can be tested. To test a page, simply append ‘perfDebug=on’ to the end of the URL to the page.

Now you can get information, which task flow, or slow page which create problem.Enter the task flow and page and kill the problem . 😛

Note – The one condition 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 11.1.1.8).

Hiding Page Timing Information for Your Current Session– set &perfDebug=off in end of url.

Stop displaying page performance information – &perfDebug=off

Happy performance analysis with Vinay Kumar in techartifact….

January 14, 2014January 20, 2014

Change metadata in MDS/ Metadata command for weblogic

In Weblogic for exporting metadat we use various command like

-> importMetaData – Imports metadata for an application.

-> exportMetaData – Exports metadata for an application.

-> deleteMetaData – Deletes the metadata in the application repository.

-> purgeMetaData – Purge metadata.

-> deleteMetadata – Deletes the selected documents from the application repository. When this command is run against repositories that support versioning (that is, database-based repositories), delete is logical and marks the tip version (the latest version) of the selected documents as “deleted” in the MDS repository partition.

example – wls:/weblogic/serverConfig> deleteMetadata(application=’mdsapp’,server=’server1′, docs=’/mypackage/*’)

-> exportMetadata -Exports application metadata. Use this command and the importMetadata command to transfer application metadata from one server location (for example, testing) to another server location (for example, production).

example – wls:/weblogic/serverConfig> exportMetadata(application=’mdsapp’,server=’server1′,toLocation=’/tmp/myrepos’,docs=’/**’)

-> importMetadata– Imports application metadata. Use the exportMetadata command and this command to transfer application metadata from one server location (for example, testing) to another server location (for example, production).

example – wls:/weblogic/serverConfig> importMetadata(application=’mdsapp’, server=’server1′,fromLocation=’/tmp/myrepos’,docs=”/**”)

-> purgeMetadata– Purges the older (non-tip) versions of unlabeled documents from the application’s repository. All unlabeled documents will be purged if they are expired, based on Time-To-Live (the olderThan argument). This command is applicable only for repositories that support versioning, that is, database-based repositories.

example – wls:/weblogic/serverConfig> purgeMetadata(‘mdsapp’, ‘server1’, 10)

update metadata in webcenter-config.xml –

Now Lets take an example of changing an metadata for webcenter application. So first we export in some temprary location then we make some changes.Then again we import from temp location to specified location.

-> Go to Middleware home/WebCenter Installation directory/common/bin and run wlst.sh (unix) or wlst.cmd(windows)

-> connect(‘weblogic’,’weblogic1′,’locahost:7001′) or give secure files path connect(userConfigFile=’/oracle/config.secure’, userKeyFile=’/oracle/key.secure’, url=’localhost:7001′)
see how to generate secure file

Then export the current configuration by running the following command in WLST command line. Set the toLocation to some “temporary location”.
->exportMetadata (application=’webcenter’, server=’WC_Spaces’, toLocation=’/tmp/Metadata’, docs=’/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml’)

-> Change XXX parameter to XX MB in /oracle/webcenter/webcenterapp/metadata/webcenter-config.xml file.

-> Then import the file back to WebCenter Spaces server following the below mentioned command line.

importMetadata(application=’webcenter’, server=’WC_SpacesXXX’, fromLocation=’/tmp/Metadata’, docs=’/oracle/webcenter/webcenterapp/metadata/webcenter-config.xml’)

-> exit();

Happy Learning with Vinay Kumar in techartifact…

January 9, 2014January 20, 2014

Jdev installation set up for running Webcenter Spaces instance

JDeveloper installation for running webcenter 11.1.1.5

Download JDeveloper 11.1.1.5 for your OS from this location:
http://www.oracle.com/technetwork/developer-tools/jdev/downloads/jdeveloper11116-1377208.html

Install JDeveloper to your local development machine, perform a typical installation.

After JDeveloper is installed, open up „Check for Updates“ dialog under the „Help“ menu.

Check that the following update centers are activated:

Check the two WebCenter updates:

We have to further extend JDeveloper for working with a running WebCenter: Spaces instance.

Download the following package and unzip it:
http://download.oracle.com/otndocs/tech/webcenter/files/DesignWebCenterSpaces_PS5.zip

There you will find three directories, two of them starting with „copy_to_….“.

„copy_to_common“ includes a common directory that contains WebCenter Portal WLST commands. WebCenter Portal’s WLST commands are required to upload customized resources directly to the Spaces application from DesignWebCenterSpaces.jws.

The content (!) of the „copy_to_common“ directory (not the whole directory itself) must be copied to \oracle_common\
„copy_to_jdev_ext“ includes oracle.webcenter.portal.jar. Required update to Oracle JDeveloper WebCenter Portal Framework and Services Design Time Extensions.

The .jar file in the „copy_to_jdev_ext“ directory must be copied to \jdeveloper\jdev\extensions\