Hybrid Runtime patterns and shortcuts
Go to Shortcut : Patterns for e-business (Page 1 of 2)
Domino application with WebSphere Integration platform
This hybrid Runtime pattern is common in sites where you are providing more than just a single application or system to the Web users.
Review:
WebSphere loaded on a Domino Server
Loading WebSphere on top of a Domino server is often the simplest and best pattern for smaller systems. This pattern gives Domino the WebSphere servlet engine which is fast robust and scalable.
Review:
WebSphere application with Domino services
Sites which are data-oriented are well suited to this design. Within this hybrid Runtime pattern, the WebSphere server will authenticate users if required.
Review:
Single sign-on between Domino and WebSphere
In an environment with both Domino and WebSphere, when switching to the other server, users would normally be prompted to log in. Implementing a single sign-on between WebSphere and Domino remedies that situation.
Review:
Using a security server to manage authentication and connections
An alternative to depending on the Domino/WebSphere single sign-on is to use an authentication manager between the user and the servers.
Review:
Domino User-to-User hybrid Runtime pattern
In looking at User-to-User patterns, probably the most basic one we can picture is one with just Domino. Users could be interacting with each other via e-mail, news groups, or Web discussion forums.
Review:
Sametime User-to-User hybrid Runtime pattern
While the previous hybrid Runtime pattern dealt with asynchronous User-to-User interaction, inserting Sametime introduces the idea of synchronous User-to-User interaction.
Review:
Combined Sametime and Domino (single machine)
When Sametime is installed on a pre-existing Domino server, Sametime uses the core of the Domino server as it's basis. This means that if the user has authenticated with the Domino server already, they are automatically authenticated with the Sametime server as well.
Review:
Combined Sametime and Domino (separate machine)
Like the previous hybrid Runtime pattern, our primary interest in this design is in providing the infrastructure for user-to-user interactions. In this hybrid Runtime pattern, those interactions could be either synchronous via the Sametime server or asynchronous via the Domino server.
Review:
Sametime and Domino with Policy Director
By inserting Policy Director between the users and the servers, we can take advantage of Policy Director's ability to provide Web single sign-on across multiple disparate systems.
Review:
Single sign-on with Sametime, Domino, and WebSphere
When we combine WebSphere with Domino and Sametime in a hybrid Runtime pattern we find that we are extending previous designs, namely Single sign-on between Domino and WebSphere, and Combined Sametime and Domino (separate machines).
Review:
Combined Sametime, Domino, and WebSphere with Policy Director
This hybrid Runtime pattern is similar to the previous one except we are no longer making use of the Domino/WebSphere single sign-on token.
Review:
Domino as a central loosely-coupled broker
It is possible to use Domino as a central hub in an environment where a number of disparate systems need to be coordinated and where user interaction is also needed.
Review:
Combining caching proxy and load balancer
In this section we discuss the benefits of combining caching proxy serving as a reverse proxy and the load balancer (Network dispatcher) to improve your organization's security and scalability.
Review:
Using Tivoli Policy Director as a load balancer
Tivoli Policy Director can also be made to work as a basic load balancer for Domino, WebSphere, or any back-end Web application server that is a part of the namespace.
Review:
Domino app with WebSphere Application Server services: Single server
This Runtime pattern is easily deployed, and fairly common in situations where WebSphere Application Server is being implemented for the first time within a Lotus Domino-based organization.
Review:
Domino app with WebSphere Application Server services: Multiple servers
This Runtime pattern is a logical extension of the previous Domino app with WebSphere Application Server services: Single server pattern.
Review:
Web redirector with Domino and WebSphere Application Server
This Runtime pattern takes advantage of the WebSphere HTTP plug-in, which allows Lotus Domino and WebSphere Application Server to be physically separated from a Web server that is providing HTTP access to system information.
Review:
WebSphere Application Server application with Domino services
Web sites that are primarily transaction-centric will typically utilize this pattern. Domino services may be provided to support a back-end calendaring system, electronic mail, or custom Domino databases, such as discussion groups or workflow-oriented databases.
Review:
WebSphere Web services with Domino
This Hybrid Runtime pattern will likely become more prevalent as Web services mature and their use becomes more widespread. This pattern assumes the use of WebSphere Application Server as a provider of Web services
Review:
WebSphere Web services with Domino
This pattern is a simple solution to the problem of the administrative overhead of maintaining more than one directory for user information and authentication. Using an external directory for these tasks is a way to get around this issue.
Review:
Using both Active Directory and Domino Directory
This pattern is most applicable for organizations that want to maintain a central Microsoft Active Directory to store user and resource information and for authentication, but still need to use Domino for e-mail.
Review:
Using both External and Domino directories
This pattern is most applicable for organizations that want to maintain a central non-Domino directory to store user information and authenticate against but still need to use Domino for mail routing.
Review:
Using a security server to manage authentication and connections
This pattern is an alternative to using the Domino/WebSphere single sign-on feature it uses an authentication manager between the user and the servers.
Review:
Domino for collaboration - Simplest pattern
This is the most basic Collaboration pattern with just Domino. Users could be interacting with each other via e-mail, news groups, or Web discussion forums.
Review:
Sametime only
This pattern allows synchronous collaboration. The synchronous collaboration is provided by Sametime 3, which will only run on top of Domino 5.0.10.
Review:
Sametime and Domino 6
In this pattern, asynchronous collaboration is provided by Domino and synchronous collaboration is provided by Sametime. Sametime 3 will only run on top of Domino 5.0.10, so any pattern that requires Sametime 3 and Domino 6 will require two versions of Domino.
Review:
Single sign-on with Sametime, Domino, and WebSphere
The Runtime pattern is dependent on implementing the single sign-on between all three servers. We are starting to get into quite complex Runtime patterns, which can be used to implement powerful Web environments with many uses.
Review:
Sametime and Domino with Tivoli Access Manager
By inserting Access Manager between the users and the servers, we can take advantage of Access Manager's abilities to provide single sign-on across multiple disparate systems with this pattern.
Review:
Combined Sametime, Domino, and WebSphere with Access Manager
This Runtime pattern is similar to the previous one except we are no longer making use of the Domino/WebSphere single sign-on token.
Review:
Load Balancer and Domino
When you have multiple identical Domino servers, fronted by Load Balancer, this pattern works well with Basic authentication.
Review:
Caching Proxy and Domino
As in the hybrid pattern with Load Balancer, this pattern shows multiple Domino servers behind a reverse proxy cache (Caching Proxy) can be set up to work well with Basic authentication.
Review: