Creating a configuration settings document for all servers that run Shindig

Every Domino® server running Shindig is required to have a configuration settings document.

Before you begin

The OpenSocial component must be installed on all servers running Shindig. For the installation procedure, see the related topics.

The Domino® Directory on the servers running Shindig must be using the current pubnames.ntf template.

Note: If you already have a widget catalog application, you do not need to create one, but you do need to replace its design from the toolbox.ntf template supplied with the current release of Domino. You can then skip to step 6 of the procedure.

Procedure

  1. Open the Domino® Administrator client.
  2. Select File > Open Server and open the Domino® server running Shindig.
  3. Click Configuration, and then click Server > Configurations.
  4. Click Add Configuration to create a new configuration settings document.
  5. On the Basics tab, in the Group or Server name field, enter the name of a server that runs Shindig or the name of a group containing all servers that run Shindig.
  6. For the Configuration for Domino Server with Shindig field, select Enabled.
    The Social Edition tab appears.
    Note: If you are administering a Domino 9.0 Social Edition server, this field does not appear, and the Social Edition tab should appear by default.
  7. Click Social Edition.
  8. Click the Basics tab, complete the fields based on your deployment topology. Locked and unlocked domains are used only if your organization has iNotes® clients. For more information, see the iNotes® administration documentation.
    Table 1. Configuration settings
    Field Description
    Locked domains Locked domains control gadget rendering for iNotes clients. If your organization uses locked domains, for example because you have iNotes clients, or Notes OpenSocial widgets that use OAuth, select Enabled, and complete the Locked domain suffix field.
    Locked domain suffix Enter a suffix to use when generating URLs with which to render locked gadgets. The URLs isolate gadgets from each other within the container. Domino® combines a generated string for each locked domain gadget with the suffix you enter. For example, enter

    -locked.gadgets.renovations.com and a locked gadget is assigned a URL such as xxxxx.locked.gadgets.renovations.com
    Domain name for unlocked gadgets and content fetching Enter the DNS name of the domain used for rendering unlocked gadgets and for fetching content. For example, enter

    unlocked.gadgets.renovations.com
    Shindig server(s) host name If you are using a single Shindig server, enter the fully qualified Internet host name as it appears in the server document. For example, enter host1.renovations.com.

    If your organization has clustered Shindig servers, enter the host name of the load balancer or reverse-proxy (ip sprayer) network device. For example, enter shindig-hosts.acme.com.

    Important: This host name should be the same host name used to register callback URLs for any OAuth 1.0a or OAuth2 services.
    Use HTTPS for OAuth redirect URLs Select Enabled to use SSL to secure OAuth redirect URLs.
  9. Optional: Set the cache fields. These fields can remain blank to use the defaults.
  10. (Optional) On the Advanced tab, configure settings for both shindig.properties and container.js files. These settings map directly to settings used in the configuration files of the same name in Apache Shindig.
  11. Click Save and Close.