Creating policies for the OpenSocial component

You can use an existing policy or create new policy and settings documents for OpenSocial component users. You need three policy settings documents: a mail policy settings document, a desktop policy settings document and a security policy settings document. For more information about policies or about configuring widgets using a policy, see the related topics.

Before you begin

This task requires that the Domino® Directory for the domain is refreshed from the current pubnames.ntf template.
Important: While no specific mail settings are required for the OpenSocial component, a mail settings document must exist in any policy that is configured for the OpenSocial component to ensure that certain profile notes are populated as part of mail processing for the administration process.

About this task

  • The administration process (AdminP) runs every 12 hours to push these policies to Notes® client users. AdminP runs on the home mail servers of each user.
  • To force the push, from the Domino® server console, enter the command tell adminp process mail on the home mail server for each user.
  • You can also use the notes.ini file setting ADMINP_POLL_INTERVAL=time in minutes to process mail policy at intervals other than the default 12 hours.
    Note: This notes.ini setting processes every mail file on your system and can take a long time.  Keep this in mind when setting the interval.
  • See the related topic on Domino Policy FAQ for more information.


  1. In the desktop policy settings document, click Widgets.
  2. In the Widget catalog application name field, enter the widget catalog application name.
  3. In the Widget catalog server field, enter the name of the server on which the widget catalog application resides. 
  4. In the Gadget Server URL field, perform one of the following actions:
    • If your organization has a single server running Shindig, enter its URL. Use the format http://server_name. For example, enter
      Note: If you want to use SSL (a URL of https), see the technote OpenSocial Component on Domino using TLS or SSL in the related topics.
    • 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

  5. Optional: In the Gadget Cache URL field, enter the URL for the Domino server running Shindig, or, if servers running Shindig are clustered, enter the host name of the load balancer or reverse-proxy (ip sprayer) network device. Use the same format you used for the Gadget Server URL field.
  6. Click the Custom Settings tab.
  7. If the desktop settings policy affects clients running 9.0 as well as 9.0.1, add ENABLE_EE=1 to the list of NOTES.INI settings. If all clients are upgraded to 9.0.1, this setting is no longer necessary.
    Tip: If you as administrator need to disable Embedded Experiences in clients affected by the policy, you can set ENABLE_EE=0.
  8. Click the Accounts tab.
  9. Click Update Links.
  10. In the Accounts dialog box, select Selected supported. Click OK.
  11. In the Select accounts to push dialog box, select the account created to support embedded experiences.
  12. Click OK. The account appears in the Account Links section.
  13. Save the desktop settings document.
  14. In the security policy settings document, click elect the Execution Control List tab.
  15. Click Edit. (Next to Admin ECL)
  16. In the ECL list section, specify an administrator who approves widgets.
  17. Ensure that Ability to configure widget capabilities is enabled for the administrator.
  18. Save the security settings document.