Web Application Integrator for IBM WebSphere Portal
is a solution which allows external web applications to be integrated with WebSphere 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).
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
script> tag to the Quickr theme.
The user experience suggests that the user is still within the Portal environment even though they are, in reality, natively accessing Quickr.
How is the integration achieved?
There are two primary facets to a successful integration: a design time activity and the runtime execution.
There are exactly three steps required to integrate an external web app with Portal:
1. Create a standard Portal URL page.
2. Use the new Web Application Integrator portlet to generate an HTML <
3. Add the script tag to the header component of the web application.
Note: these steps are discussed in detail on the How to Integrate document provided with the solution.
As you review these steps, it is noteworthy to consider the following:
- No portlets needed to be developed;
- A simple modification must be made to the web application being integrated;
- The Portal Admin would complete Portal integration steps (creates URL page and uses WebAppIntegrator portlet to generate HTML <script> tag);
- The web application owner would apply the modification to the web application (adds the HTML script tag);
- The WebAppIntegrator portlet is only used at integration design time.
Typically, these steps can be completed in under 5 minutes, making this Portal integration solution remarkably attractive. It is very reasonable to assume that, within hours, it would be possible to use Portal to centralize access to numerous web applications dispersed throughout an enterprise!
Downloading the Web Application Integrator for IBM WebSphere Portal
This solution is available on the IBM Lotus Business Solutions Catalog: