 |
Integrating the Self-Service and Collaboration patterns using WebSphere and Domino
Overview
The Custom designs that follow illustrate various ways to integrate WebSphere and Domino servers to bring Self-Service and Collaboration functionality to an e-business application.
WebSphere/Domino Integration as a Composite Design
The designs that follow are based on two IBM Redbooks published two years apart. The first Redbook, Applying the Patterns for e-business to Domino and WebSphere Scenarios was written prior to the publication of Patterns for e-business: A Strategy for Reuse and did not follow the formal approach used in this book to document composite designs made up from multiple Business and Integration patterns. These designs are instead based on a somewhat improvised approach used to predict solutions to emerging e-business problems. In the tables below, these designs are documented as "WebSphere V3.5 and V4.0/Domino Integration patterns". They are valuable for developers who may still be using back-level releases of WebSphere Application Server and Lotus Domino.
The second IBM Redbook, Patterns: Custom Designs for Domino & WebSphere Integration, expands on the concepts explored in the first, and updates the Runtime patterns for use with IBM Lotus Domino 6 and IBM WebSphere Application Server V5.
What's Next
If you're not yet sure that your business problem can be solved by the functionality enabled through a WebSphere/Domino custom design, the WebSphere/Domino Integration general guidelines page provides additional information on choosing from this set of Custom designs. Business and IT drivers, the e-business context appropriate for this solution type, and additional solution details are discussed here.
If you've determined that the WebSphere/Domino custom design set can provide an appropriate solution design for your business need, you should identify the release level of WebSphere Application Server and Lotus Domino you plan to use for the solution. Then, review the specific connection methods and hybrid Runtime patterns for your choice:
|
|
|
Feasibility: This material will help you determine the high-level shape of a WebSphere/Domino integration solution.
Risk: Basing new projects on prior designs and ideas helps to lower the risk of failure. Creating or inventing designs for each project tends to result in a lower success rate. Frequently, projects begun "from scratch" simply do not work and have major exposures in such areas as security, performance, availability, undefined requirements, and cost over-run.
Cost-benefit: By starting with reasonably complete architectures you save considerable development time and obtain assurance that the end solution will have a much higher chance of success. Actual savings will vary, but project teams have realized a 10% to 50% reduction of work effort in their design and architecture phases alone.
|
|
If you haven't already joined our mailing list to be notified when we make updates or add new patterns, subscribe today.
|
|
Discuss the patterns with your peers. Visit our newsgroup for patterns.
|
|
