Search
Contribute
Navigation
- 1.0
- 1.0.x
- 2.0
- 2.0.1
- 2.0.1.1
- 6.0
- 8.1.1
- 8.2
- activities
- activities entry type
- activities files
- activities quickr integration
- activities templates
- administrators
- adoption
- api
- api dogear
- applications
- atlas4connections
- atlas_connections
- best-practice
- Blackberry
- blog
- blogs
- bookmarks
- broadcast chat
- business card
- business_card
- c11n
- cluster
- cluster 2.0
- comments
- communities
- confluence wiki lotus connections person-card integration development
- connections
- connections 2.0.1
- course
- Creating Bookmark with DogEar API
- customization
- customize
- customize
- DB2
- demos
- deployment
- deployments
- deplyment 1.0
- design rebranding customization css theme
- developers
- development
- dogear
- dogear bookmark_this
- dogear dynamic list
- domino
- Edge server
- education
- error codes
- error messages
- expertbriefing
- feature
- frontpage
- groups
- guide
- guidelines
- home
- homepage
- Homepage Tab
- how-to
- How To Configure SMTP after installation
- How to Map Lotus Connections Features to the HTTP Server
- How To Support Multiple Document Type in Blog
- HTTP server
- IBM WebSphere Portal 6.0 SSO to Lotus Connections 2.0 using LTPA
- ibm_mashup_center
- ifixes
- infrastructure
- installation
- instruction
- Integration
- issl
- iwidget
- j2ee
- JSP
- LDAP
- learning
- Learning experience. workshop
- links
- livewriter
- load balancing
- lotus
- Lotus Connections
- lotus connections 2.0.1 quickr deployment edge proxy integration 8.1.1
- Lotus Sametime
- mashup
- mashups
- membership
- Microsoft
- Migrating
- offline
- Oracle
- outlook
- overview
- people
- person card
- person_card
- pilot
- plugin
- portal
- portlet
- portlet_factory
- productivity
- profiles
- profiles connections customization
- Profiles custom fields
- Profiles TDI
- Profiles types custom fields
- Profiles widgets
- programming
- proxy server
- proxy server 1.0
- quickr
- rebrand banner footer logo
- rebrand banner footer logo tab navigator
- rebrand skin theme
- Redbooks
- redbooks wiki
- REST
- reverse proxy server
- RIM
- roles
- Sametime
- Sametime Advanced
- Sametime Integration
- sample
- scriptfire
- self-paced
- sharepoint
- single server
- siteminder
- social_networking
- software-services
- solutions catalog
- SQL Server
- step by step
- tags
- tam
- TDI assembly lines
- TDI multiple data sources
- template
- test
- test infrastructure
- tivoli access manager
- topology
- tour
- troubleshooting
- upgrade
- using
- VIC
- virtual education
- WAI
- WebAppIntegrator
- WebSphere
- WebSphere Portal
- Why my Rich Text Editor does not support Chinese Characters
- Widgets
- word
Go elsewhere
11.2 Web Application Integrator
![]() |
Redbooks Wiki: Customizing Lotus Connections 2.0
customization , portal , WAI , WebAppIntegrator |
Shu Lukito 08/19/2008 |
Debbie Willmschen 01/06/2009 |
Back to main topic 11. IBM WebSphere Portal Server
Introduction
Web Application Integrator for IBM WebSphere Portal (WebAppIntegrator) is a solution that allows you to integrate external Web applications with WebSphere Portal version 6.0 or later. It allows organizations to centralize access to external Web applications within the enterprise.
In this topic, we show how to use WebAppIntegrator to integrate Lotus Connections 2.0 and WebSphere Portal 6.1.
The WebAppIntegrator solution does not require any portlet development because it does not use portlets at runtime. The integration can be performed by Portal administrators and the Web application owner. Additionally, the WebAppIntegrator solution does not use an iFrame. Such an approach is desirable because the viewing area of the Web application is not constrained in any way (that is, there are no iFrame scroll bars). Also, all JavaScript and links within the integrated Web application continue to function as expected.
How WebAppIntegrator works
WebAppIntegrator integration is achieved by "injecting" Portal navigation markup into the external Web application when the Web application is rendered. The solution implementation uses the existing Portal URL page feature and makes use of a new Portal entry point, the WebAppIntegrator theme template, which returns JavaScript that generates Portal page navigation markup (for example page tabs, launch menu, and bread crumbs). This markup can be "injected" into an external Web application by adding exactly one HTML <script> tag to the Web application.
The user experience suggests that the user is still within the Portal environment even though the user is, in reality, natively browsing the external Web application.
Adding WebAppIntegrator to Lotus Connections 2.0
Assuming that you have installed WebAppIntegrator, you can add WebAppIntegrator to any Web application by following these steps:
- Create a standard Portal URL page.
- Use the Web Application Integrator portlet to generate an HTML <script> tag.
- Add the <script> tag to the header component of the Web application.
Step 1: Creating a standard Portal URL page
To create a standard Portal URL page, follow these steps:- Log in to WebSphere Portal as an administator.
- Go to Administration -> Manage Pages.
- Navigate to where you want the link to Lotus Connections to be. For this sample, go to Content Root -> Applications.
- Click New URL.
- Enter Connections 2.0 as the title and the URL to the Connections home page (see Figure 1).

Figure 1: New URL - Click OK.
The newly created URL displays in the list of pages (see Figure 2).

Figure 2: Manage Pages Portlet
Step 2: Generating the HTML <script> tag
To generate the HTML <script> tag, follow these steps:- Copy the unique name/identifier of the URL that you just created (highlighted in Figure 2).
- Paste the unique name/identifier to the Web Application Integrator portlet (see Figure 3).
- Click Generate HTML <script> tag.

Figure 3: Web Application Integrator Portlet
Step 3: Adding the <script>
After you complete step 2, you have the script that you can paste to your external Web applications as shown in Figure 4. To add this script to Lotus Connections, you need to modify the .jsp pages that control the appearance of each component (Home, Blogs, Activities, Dogear, and Communities). See the following topics for details:
11.2.1 Home
11.2.2 Profiles
11.2.3 Communities
11.2.4 Blogs
11.2.5 Dogear
11.2.6 Activities

Figure 4: HTML <script> tag
(Edited by DW)



