IBM BS029ML Self Help Guide - Page 178

Login delay. There are a number of components involved with the Portal login, such as the database, LDAP, WMM configurations, and so on. Portal login is explained in Chapter 4, "WebSphere Portal security" on page 85. In our environment, we had IBM WebSphere Portal V6 with Active Directory. The login time was a bit long (around 18-20 seconds). We performed a TCP dump and analyzed the dump file and found out that there is a 12 second delay from the LDAP server after a request is sent. We then analyzed the search base for Portal and narrowed the cause down to the user and group objectclasses being used and indexed those object classes in the Active Directory server, which immediately reduced the login time from 15-20 seconds to 2 seconds. However, be aware that the indexing might actually cause some impact on the LDAP server, so before implementing our solution or a similar one, take the LDAP server's processing power and memory into consideration. So, it is not the Portal alone that is entirely responsible for the delay; it is worth looking at the other involved components as well. 5.4 Portal administration tools There are some very efficient administration tools available to you to automate the deployments, move the configuration across environments, and so on. You can administer and configure portal resources by using one of the following tools: Portal administration portlets Portal administrative users can use the administration portlets to perform administrative tasks and actions on portal resources, depending on the access rights that the administrative user has on those resources. This includes: Configuring individual portal resources. Configuring individual portal resources, together with their dependent resources. For example, this can be pages and the pages derived from them. Giving other users, for example, subadministrators, limited access rights on selected portal resources. These subadministrators can then perform administrative tasks to the extent that their access rights allow. As the master administrator, you can widen or limit that extent by modifying the access rights for these users on the portal resources. This way, you can delegate administrative tasks as required., or even deploy your own custom developed artifacts, such as portlets, themes, or skins. You cannot use the administration portlets to perform scripted or automated administration or configuration tasks. For more information about the Portal Administration tools, refer to the InfoCenter at: http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=/com.ibm.wp .ent.doc/wps/adpltadm.html XML configuration interface The XML configuration interface works as follows The XML configuration interface provides a batch processing interface for portal configuration updates. It allows you to export an entire portal configuration or parts of a configuration, for example, specific pages, to an XML file. You can then re-create the exported configuration from such a file on another portal. 164 IBM WebSphere Portal V6 Self Help Guide