Tulisalo, Tommi; Cawthorne, Edward; Czernel, Jonathan; Hertenstein, Bradley; Reed, Kenneth; IBM: Patterns: Custom Designs for Domino and WebSphere Integration, IBM Corporation 2003.

THEMES: Tulisalo, Tommi | Cawthorne, Edward | Czernel, Jonathan | Hertenstein, Bradley | Reed, Kenneth | IBM\Redbook
META STRUCTURES: IE\...\Material | IE\...\Artikel BP Buc... | LN\...\09_Pavone-Powe...
YEAR: 2003
Busi Patterns

p 46
49 Domino - Websphere Hybrid runtime patterns

Several Hybrid Runtime patterns may be utilized in a mixed Domino and WebSphere
Application Server environment. There are two common application types that emerge when
analyzing Application Integration patterns associated with these products.
The first is based on the premise that a pre-existing Domino application requires an interface
to WebSphere Application Server to support J2EE functionality, or interfaces to other
back-end systems through software components provided in the WebSphere Application
Server environment. An application of this nature may be described as being
The second typical application type involves an existing J2EE-based application that lives in
the WebSphere Application Server realm, requiring access to one or more back-end Domino
and relational databases. An example of this scenario may include a J2EE application that
presents the contents of a view in a Domino database. Applications architected in this fashion
are typically associated with more robust transaction-based processing, or
transaction-centric systems, which may include some collaborative components, such as
real-time chat interfaces with customer support personnel.

Similarly, while components can be built onto the WebSphere Application Server to address
the needs of a collaborative workspace, Lotus Domino and other Lotus Software products
provide this capability out-of-the-box.
Our discussion of Domino-WebSphere Hybrid Runtime patterns includes patterns that are
both collaboration-centric and transaction-centric. The following Domino-WebSphere Hybrid
Runtime patterns are described:

The typical Business patterns that might apply to the described Hybrid Runtime pattern,
such as Self-Service, Collaboration or Information Aggregation. In some cases, the extent
of either application or access integration that is found in the pattern is described, which
may include specific access integration technologies that enable Lotus Domino to work
with WebSphere Application Server

Note: It is important to remember that the Lotus Domino server and the Domino databases
are not easily separated. Both typically exist on the same machine, unless an external
storage mechanism is utilized for database storage (external hard drive arrays). For this
reason, the logical nodes presented in any diagrams in this chapter with either the title
Lotus Domino Server or Collaboration Server also imply the existence of one or more
Lotus Domino databases within the same node.

This topology represents a pattern where users are interacting with a Web-based business
The collaborative functions of the Lotus Domino server are used for user-to-user