Level 2 Support has indicated that more and more people are setting up their environments with WebSEAL, TAM, Sametime and STLinks. When they do this, the users' browsers can exhibit 'sluggish' behavior. It turns out that Sametime's use of persistent HTTP to maintain awareness impacts thread consumption on WebSEAL. Details were just published in this technote:
WebSEAL, TAM and Sametime awareness portlets and STLinks applications
In some situations, using Tivoli Access Manager WebSEAL to front-end Sametime servers (as a reverse proxy where clients pass through a TAM or WebSEAL junction to access Sametime services) can cause the user's browser to appear sluggish or even lock up between requests to the Portal applications.
Jennifer Kelley | 23 April 2008 06:25:39 AM ET | Westford, MA | Comments (0)