Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Notes and Domino wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL Forums and Blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • API Documentation
Search
Community Articles > Lotus Domino > Deployment Architecture
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Integration with XPage Embedded Experiences

XPages can be leveraged as embedded experiences in Notes and iNotes. This article outlines the considerations one should make to enable this functionality.

Gadget data flow

OpenSocial Component functionality in Notes and iNotes relies on several different pieces of data, including proxy rules, OAuth consumer information, and gadget capability information. This article outlines how this data is used and how its use can be customized.

Collecting support data

In the event that verification of the OpenSocial Component fails an administrator will need to collect support data. This article outlines how an administrator can collect support data for Notes, iNotes, and Domino.

Verification

Once the OpenSocial Component is installed and configured, administrators need to verify that their environment is working properly. This article outlines how an administrator can do such verification.

Troubleshooting

In the event that verification of the OpenSocial Component fails an administrator may need to troubleshoot his or her environment. This article outlines how an administrator can do such troubleshooting.
Community articleDeployment Architecture
Added by ~Vera Umponetexings | Edited by ~Lily Bubveluski on March 4, 2014 | Version 20
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
This article provides a high-level, deployment architecture view of the OpenSocial Component.
ShowTable of Contents
HideTable of Contents
  • 1 Overview
  • 2 Common Deployment Types
    • 2.1 A Single Server
    • 2.2 A Single Mail Server and a Single Domino Server with Shindig
    • 2.3 Clustered Mail Servers and a Single Domino Server with Shindig
    • 2.4 Clustered Mail Servers and Clustered Domino Servers with Shindig
  • 3 Detailed Deployment View

< Previous | Cookbook Contents | Next >


Overview


The OpenSocial Component is deployed and configured as two server components:
  • A Domino mail server
  • A Domino server running Shindig

The Domino mail server supports Notes and iNotes users and hosts a replica of the Widget Catalog. The Domino server running Shindig, alternatively called "Domino server with Shindig", hosts the credential store application and renders OpenSocial Gadgets utilizing portions of the Apache Shindig library.

Both components require running the OpenSocial Component installer and it is the configuration that differentiates their behavior at runtime.

Common Deployment Types


This section outlines several common deployment types. Each diagram depicts a "DNS Server". This server is part of a company's network infrastructure and is used for Locked domains 9.0 or Locked domains 9.0.1.

A Single Server


This is the simplest deployment in which both server components are setup on the same Domino server, called a "Domino Mail Server with Shindig" for the purpose of this scenario. This type of setup is useful for development and testing. This is not a recommended setup for a production environment.

A Single Mail Server and a Single Domino Server with Shindig


This deployment scenario has two Domino servers, one for each component. This is useful for trying out OpenSocial Component functionality with an existing mail server. This type of environment could also support a small pilot deployment.

Clustered Mail Servers and a Single Domino Server with Shindig


This deployment scenario has clustered mail servers along with a single Domio Server with Shindig. This type of environment is suitable for smaller production deployments. In the diagram the mail servers are shown as clustered but they do not need to be. Any number of clustered or non-clustered servers could be configured to utilize a single Domino Server with Shindig.

Clustered Mail Servers and Clustered Domino Servers with Shindig


This deployment scenario has clustered mail servers along with a cluster of Domino Server with Shindig. This is the most common production deployment. In the diagram the mail servers are shown as clustered but they do not need to be. Any number of clustered or non-clustered servers can be configured to utilize a Cluster of Domino Servers with Shindig.





Detailed Deployment View


The following diagram is a "zoomed in" version of the "Single Mail Server and a Single Domino Server with Shindig" configuration shown above. This diagram shows the individual databases and components as they appear on each server. This diagram will be used in the related materials to depict data flow and the results of installer execution.



< Previous | Cookbook Contents | Next >


  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (20)Mar 4, 2014, 7:39:44 PM~Lily Bubveluski  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility