Friday, April 17, 2009

Using the Web Application Integrator for IBM WebSphere Portal


Web Application Integrator for IBM WebSphere Portal is a solution which allows external web applications to be integrated with WebShpere Portal. It allows Portal customers to further leverage their investment in Portal by using it to access to web applications, like Quickr
Why is WebAppIntegrator solution unique?

Typically, when an external web application like Lotus Quickr is integrated with Portal, two approaches are considered: either write a set of portlets that expose the web app's UI/functionality or use Portal's web clipper portlet (an iFrame based portlet). WebAppIntegrator offers a third approach. It is particularly attractive because:

1. No portlet development is required to implement this integration since it does not use portlets at runtime. Portal administrators, in concert with the internal web application owner, can do this integration.
2. It does not use an iFrame. Consequently, the viewing area of the web application is not constrained in any way (i.e. no iFrame scroll bars). Also, all JavaScript and links within the integrated web app continue to function as expected.
3. Integration is achieved in three simple steps.
How does WebAppIntegrator integration work?

WebAppIntegrator integration is achieved by "injecting" Portal navigation markup into Lotus Quickr at render time. The solution implementation leverages the existing Portal URL page feature and makes use of a new Portal entry point - WebAppIntegrator theme template - which returns JavaScript that generates Portal page navigation markup (e.g. page tabs, launch menu and bread crumbs). This markup can be "injected" into Quickr by adding exactly one HTML