Configuring the Domino® OpenSocial component for iNotes® clients

Configuring IBM® Domino® Social Edition Open Social component features in IBM® iNotes® includes configuring the server session authentication, configuring automatic updates for widgets, and configuring policies.

About this task

To provide iNotes® clients with access to embedded experiences and OpenSocial widgets, you must first configure Domino® to support Widgets and Live Text for iNotes® clients. After you complete the Widgets and Live Text configuration, you then perform additional steps to enable OpenSocial support. Widgets features are only available to iNotes® clients that run in Full Mode.

Procedure

  1. Install the Domino® OpenSocial component on the iNotes® server.

    The OpenSocial component is a prerequisite for enabling Widgets and Live Text support. To support Widgets and Live Text for iNotes® clients, you must install the OpenSocial component even if you do not plan to use OpenSocial widgets or embedded experiences.

  2. Create a Widget Catalog and replicate it to all of your iNotes® Mail servers.
  3. Optional: Configure widgets for specific versions of iNotes® clients.
  4. Enable session authentication for each iNotes® server.
  5. Enable automatic updates for user's widgets.
  6. Create mail policy and desktop policy settings documents and apply them to the iNotes® users who will use Widgets and Live Text.
    Note: If you are setting up an iNotes® deployment to support Widgets and Live Text only, no value is required in the Gadget Server URL field of the desktop policy settings document.
  7. Enable the following settings in the notes.ini file of each iNotes® server: iNotes_WA_LiveText and iNotes_WA_Widgets. For more information, see Using notes.ini file settings to enable widgets, embedded experiences, live text and OpenSocial features.

    You have now completed the configuration for Widgets and Live Text. To enable support for embedded experiences and OpenSocial widgets, complete the remaining steps.

  8. Install the Domino® OpenSocial component on any additional servers that will run Shindig.
  9. Enable locked domains.
  10. Create and configure the credential store application on each server that runs Shindig.
  11. Create a configuration settings document that applies to all servers that run Shindig.
  12. Add a Gadget Server URL to the desktop settings document and create a security policy settings document. For more information, see Creating policies for Domino Social Edition Open Social component.
  13. Specify the settings iNotes_WA_EnableEE and iNotes_WA_OpenSocial in the notes.ini file of each iNotes® server. For more information, see Using notes.ini file settings to enable widgets, embedded experiences, live text and OpenSocial features.
  14. Approve OpenSocial widgets and embedded experiences to make them available to users.