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 > Terminology
  • 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 articleTerminology
Added by ~Vera Umponetexings | Edited by ~Lisa Elfanalyettu on January 27, 2014 | Version 10
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
This article defines the key terminology involved with the OpenSocial Component in IBM Notes/Domino Social Edition versions 9.0 and above
Tags: 9.0, 9.0.1, domino, notes, inotes, opensocial, social, embedded experiences

Cookbook Contents | Next >


OpenSocial
OpenSocial is an open standard which defines APIs that can be used to build social applications using HTML, JavaScript, and CSS. The specification includes both JavaScript and REST APIs. OpenSocial leverages many other standards, such as Activity Streams and OAuth.
See: http://opensocial.org/external link

Embedded Experiences
Embedded experiences is a method of embedding the “experience” or functionality from one application into a different, host application. The end user experiences the 3rd party application in their host application environment as if they were using it directly from the 3rd party provider.
See: Embedded Experiences in the OpenSocial 2.5 Specificationexternal link

Activity Streams
Activity Streams is an open standard which defines a data model to represent a stream or list of actions performed by users and applications. This specification DOES NOT define any APIs, it simply defines the data model.
See: http://activitystrea.ms/external link

Apache Shindig
Apache Shindig is an OpenSocial container and helps to start hosting OpenSocial apps quickly by providing the code to render gadgets, proxy requests, and handle REST and RPC requests. Shindig is the reference implementation for the OpenSocial specification.
See: http://shindig.apache.org/external link

Domino Server with Shindig
A Domino Server with the OpenSocial Component installed. This server runs portions of the Apache Shindig project as a web application based on OSGi. This server is responsible for rendering OpenSocial gadgets.

DOTS
An acronym for “Domino OSGi Tasklet Service”, it is a server task that allows OSGi plugins to contribute scheduled “tasklets” that perform some amount of work on the server. The Widgets framework in iNotes contributes a DOTS tasklet to push Widgets to iNotes users by policy.

Widget Catalog
A database that is used to store metadata (i.e. a “widget”) about services for use within Notes and iNotes. In the case of OpenSocial Component, the focus is on OpenSocial gadgets for which widgets are created and stored in the Widget Catalog.

Credential Store
As it relates to the OpenSocial Component, the Credential Store is a secure database that is used to store proxy rules, gadget capabilities, and OAuth information on the Domino Server with Shindig.

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 (10)Jan 27, 2014, 9:29:08 PM~Lisa Elfanalyettu  
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