Chapter 2: Integration Techniques

---

This chapter provides a detailed overview of the integration techniques available for portalizing a Domino application. It also provides a guide to help you determine the best integration technique for your project.

The chapter concludes with the introduction of a fictitious Domino application case study that will be used in subsequent chapters to provide examples of how to implement each integration technique.

2.1 Choosing an integration technique

As discussed in the previous chapter, there are four main issues to consider when choosing an integration technique:

• Domino applications - the characteristics of the Domino applications

• Integration techniques - knowledge of all the different options

• Portlet pattern - concrete requirements for the portlet

• Conditions - overall project parameters like resources, skills, and so forth

Each of these issues must be addressed to ensure the successful transformation of a Domino application into a useful component of the WebSphere Portal workplace.

Each issue has many complex and potentially competing factors that must be considered. This can make it difficult to identify the integration technique that best satisfies the conditions at hand.

While every project is different, the use of a structured approach can help reduce the complexity of this decision-making process. The following sections detail a four-step approach to identify the appropriate integration technique. These steps are:

1. Pre-project preparation and training

2. Identify project requirements and considerations

3. Select the appropriate portlet pattern

4. Select the appropriate integration technique

2.1.1 Step 1: Pre-project preparation and training

Issues addressed:

• Portlet patterns

• Integration techniques

Description:

Before starting a portal integration project, obtain as much information and training as possible. Focus on understanding the portal patterns and integration techniques, and familiarize yourself with the skills and technologies required to implement each technique.

When learning new technologies, there is no substitute for hands-on training and experience. Try to implement the examples found in this book, or make up your own "case study" with which you can experiment.

2.1.2 Step 2: Identify project requirements and considerations

Issues addressed

• Domino application

• Conditions

Description

While in the requirements gathering phase of your project, obtain the Domino application characteristics as discussed in 1.3.6, "Domino applications" on page 16. It is important to have a solid understanding of the application design, size, performance, and usage patterns before you recommend a portlet pattern or integration technique.

Also, identify the miscellaneous project considerations outlined in 1.3.9, "Considerations" on page 28. The project budget, the skill set of the development team, and the application environment details (including SSO, software versions, and so forth) can each play a significant role in your final decision.

Finally, identify specific functional requirements that your portlet will be required to perform. These requirements may affect your selection of an integration technique.

Together, the Domino application characteristics, project considerations, and functional requirements define the capabilities that the selected integration technique for this project must be able to implement.

2.1.3 Step 3: Select the appropriate portlet pattern

Issues addressed:

• Portlet pattern

Description:

Use the client's functional requirements to identify the best portlet pattern for this application. Table 2-1 on page 40 summarizes some of the main advantages and disadvantages of each portlet pattern.

Table 2-1: Portlet pattern advantages and disadvantages

Portlet pattern	Advantages	Disadvantages
Link	Quick and easy. Accesses existing applications. No modifications to existing functionality.	This is a simple Web link from a portlet. No content or functionality is available within the portal framework.
Display	Minimal enhancements to existing application functionality. Optional link outside portal to access existing application for more advanced functionality.	Minimal or no application functionality within the portal framework.
Integrated	Significant functionality within the portlet.	Requires more development time and might be more difficult to implement.
Migrated	Full application functionality within the portlet.	The most technically challenging and resource-intensive to implement.

A description of each portlet pattern can be found in 1.3.7, "Portlet patterns" on page 19.

2.1.4 Step 4: Select the appropriate integration technique

Issues addressed:

• Integration technique

Description:

Identify one or more integration techniques that will work well with the portlet pattern chosen in the previous step. Guidelines for this process are in the next section. Once the set of candidate integration techniques has been identified, compare each integration technique with the considerations identified in Step 2.

If none of the integration techniques satisfies all of the considerations for this application, identify the restricting factors that are feasible to change. While every project is different, some of the more flexible factors tend to be: estimated development time, developer skill set, and non-essential functional requirements. You may also consider a less complex portlet pattern. Some examples of factors which may be more difficult to change are: performance requirements and Domino application characteristics (database size, usage patterns, and so forth).

Once an integration technique that satisfies all project parameters has been identified, the first and most important step in the process is complete. You are now ready to design, develop, and deploy your portal application.

Considerations

Table 2-2 outlines many of the considerations that will influence your integration technique selection. In the following chapters, the discussion of each integration technique includes a brief discussion of each of these considerations. This will prove useful when comparing and contrasting the available techniques

Table 2-2: Considerations for integration technique selection

Consideration	Description
Portlet patterns	The portlet pattern or patterns most compatible with this integration technique.
Development time	Relative time/resources required to implement this integration technique.
Developer skill set	The technologies with which developers must be familiar to implement this integration technique.
Range of application functionality	The degree of control a developer has over the portlet features and functionality when implementing this technique.
Handle rich text	Can portlets implementing this technique easily display or edit the content of rich text fields?
Performance and scalability	How well do applications using this integration technique scale? Is session pooling used for Domino sessions? Can this technique be used in a clustered environment?
Requires single sign-on	Does this implementation technique require that single sign-on be enabled between WebSphere Portal and Lotus Domino servers?
Required software versions	Versions of server and development software are required to implement this technique?

---