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


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, enter the URL for the Domino server running Shindig. Use the format http://server_name. For example, enter

5. Optional: In the Gadget Cache URL field, enter the URL for the Domino server running Shindig. Use the same format you used for the Gadget Server URL field.

6. Click the Custom Settings tab.

7. Add ENABLE_EE=1 to the list of notes.ini settings.

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.

Parent topic: Setting up the Domino server to run the OpenSocial component and Shindig
Previous topic: Configuring a managed account for the OpenSocial component

Related concepts
Controlling Widgets and Live Text access using Domino policy