Performance tuning of Portal Access Control
From the developerWorks archives
Date archived: January 3, 2017 | First published: August 24, 2005
This article provides portal administrators with essential performance background information so you can improve your portal's performance, including login, read-only operation, and administration performance. You learn how to prevent future portal access control performance issues by making the best use of Portal Access Control (PAC), an authorization model introduced in IBM WebSphere Portal V5. You learn about the PAC configuration artifacts, performance considerations, individual fixes you should consider installing, and the benefits and drawbacks of individual access tuning options such as tuning the caching layers, and the best use of performance flags for your setup. You also see how to configure two portal services so they automatically clean up redundant configuration settings and pre-fill access control caches during portal start-up. To learn more about WebSphere Portal administration and PAC basics refer to the WebSphere Portal InfoCenter (see Resources).
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.