Coding IBM Collaboration Solutions
New to Quickr or just not the IBM infocenter type ... here's a starting point for Lotus Quickr Services for WebSphere Portal.
Lotus Quickr Support
Lotus Quickr Wiki
Lotus Test (SVT) Configurations
Common Issues on IBM® Lotus® Quickr™ services for WebSphere® Portal
IBM Fix Central
Lotus Quickr Technotes
Cluster DRS Tuning for Lotus Quickr to avoid native Out of Memory error
Optimize Portal caches for Lotus Quickr
Enable WMM Names and Attribute Caches for Lotus Quickr
Set correct HTTP response-cache headers to improve response times
Enable GZIP compression on HTTP server to improve response time
IBM Lotus Quickr library linker: Content interoperations between Lotus Quickr libraries
Introducing IBM Lotus Quickr REST services
Lotus Quickr Developers Guide
Customizing themes in IBM Lotus Quickr services for IBM WebSphere Portal V8.0
Introducing IBM Lotus Quickr Web services
Build up your own search center using IBM Lotus Quickr content services
Customizing components in IBM Lotus Quickr services for IBM WebSphere Portal 8.0
The LtpaToken is IBM's predominate form of Single Sign On (SSO) support. It allows users to freely roam between servers within the same DNS domain without being challenged for authentication. As we move more into the world of asynchronous communication, one of the emerging patterns on the WebSphere Portal server is use of the proxy servlet.
If you haven't worked with LtpaTokens before, it becomes confusing as to how SSO is maintained. Since the Java code is responsible for requesting the data from the external server, the programmer must ensure the LtpaToken is made available to the external server to maintain SSO. In this model, you simply don't have the luxury of letting the browser pass the LtpaToken in the manner that occurs when you surf through web content. The programmer needs to ensure this happens.
The article makes use of Abdera's CommonsClient object to make the request to the Quickr server from Portal. Simply provide the CommonsClient object with the LtpaToken in the form of a Cookie header with the LtpaToken name value pair.
Now simply update the JSP file (CmSearchPortletResult.jsp) which calls into the class such that it provides the cookie to the above code. Remember that the cookie contains the LtpaToken.
The approach is the same for any of the java.net objects. Before sending the request to the IBM server, set the header such that it contains the LtpaToken. The same approach is also used for architectures involving an external authentication manager such as Siteminder. Consequently when implementing code that makes such request through external security managers, programmers need to ensure that the SSO tokens (such as SMSESSION in Siteminder environments) are present.