Best Practices from Oracle Development's A‑Team

Improving WebCenter Performance – Part 2


If you have read A-Team's previous post you can improve the client side performance. This is useful if you are running a demonstration, workshop or have a controlled IT environment where you have mandate to configure the client browser environment.  This post will look at how we can improve the client side experience of the performance and also limit the computation time for certain common operations.

This post is written for WebCenter Portal

Main Article

Login process

The login process takes in general a longer time than the subsequent operations.  There are several reasons for this. One is the caching, which George has already addressed. Second, if you have large identity store or limited response times from the directory servers, you can implement caching so the LDAP bind, authentication and user information retrieval impact can be reduced.  Add following lines to jps-config.xml:

<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">   <property name="idstore.config.provider"             value="oracle.security.jps.wls.internal.idstore.WlsLdapIdStoreConfigProvider"/>   <property name="CONNECTION_POOL_CLASS"             value="oracle.security.idm.providers.stdldap.JNDIPool"/>   <extendedProperty>     <name>user.object.classes</name>     <values>       <value>top</value>       <value>person</value>       <value>inetorgperson</value>       <value>organizationalperson</value>       <value>orcluser</value>       <value>orcluserv2</value>       <value>ctCalUser</value>     </values>   </extendedProperty> </serviceInstance>

The jps-config.xml can be found in the domain configuration where the affected managed server is running [domains/wc_domain/config/fmwconfig]. For more information see: http://download.oracle.com/docs/cd/E21764_01/webcenter.1111/e12405/wcadm_security_id_store.htm#BGBGIAHC

Browser tuning

Many organizations are using Internet Explorer in various versions.  Currently when Internet Explorer is installed it comes with following download concurrency support:

  • Version 7: Two simultaneous download threads
  • Version 8: Six simultaneous download threads

Considering George's previous blog, there are about 100 downloads for some page requests when caching is not present. Tuning the browser can improve the perception of the performance for the user. Microsoft has released two self fixing steps that can be taken to increase the concurrency to 10.  If you want to implement the steps manually or automatic please refer to the link below, remember to use the browser version you want to target so you get the right fix.

For more information see: http://support.microsoft.com/kb/282402
If you click the Fix it link then it will download the registry fix and install it for you, alternatively you can use the manual procedure.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha

Recent Content