Home
Configuring
Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
Configuring users and servers
Topics in this section describe how to set up users and servers.
Configuring the Domino® OpenSocial component
The Domino® OpenSocial component adds social and web features to make third-party processes available directly in the client user's mail. The OpenSocial component supports embedded experiences in the Notes® client, including OpenSocial Gadgets in the sidebar, pop-ups, and tabs.
Setting up the Domino® server to run the OpenSocial component and Shindig
The setup for running the OpenSocial component and Shindig includes creating the credential store application on the server running Shindig, configuring the credential store application, and creating a configuration settings document for all servers running Shindig.
Configuring a managed account for the OpenSocial component
The OpenSocial component uses the Accounts framework to manage security between the Notes® client and the Domino® server running Shindig.

Configuring
Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
- Configuring a network
  This section presents the planning concepts and setup procedures necessary for a successful IBM® Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
- Configuring users and servers
  Topics in this section describe how to set up users and servers.
  - Understanding the Server document
    The Server document is set up when you register a server. It contains many of the settings that define how your server operates.
  - Policies
    Use Domino® policy settings to control how users work with Notes®. A policy is a document that identifies a collection of individual policy settings. Policy settings documents define a set of defaults that apply to the users and groups to which the policy is assigned. You can change policy settings and they will be automatically applied to the assigned users and groups.
  - Defining default settings for Notes® user registration
    Before you register new Notes® users, you can specify default settings that apply to all users. Default settings simplify user registration and ensure user settings consistency. You can define many default settings, such as what mail server users have or what certifier ID to use for user registration. You can also specify a default workstation execution control list (ECL) to protect data from unauthorized workstation access.
  - Managing users
    The Administration Process helps you manage users by automating many of the associated administrative tasks. For example, if you rename a user, the Administration Process automates changing the name throughout databases in the Notes® domain by generating and carrying out a series of requests, which are posted in the Administration Requests database.
  - Using groups
    Groups are lists of users, groups, and servers that have common traits. They are useful for mailing lists and access control lists. Using groups can simplify administration tasks.
  - Replicas
    You can make a database available to users in different locations, on different networks, or in different time zones, by creating replicas of the database.
  - Domain Search
    Notes® client and Web users can use Domain Search to search an entire Domino® domain for database documents, files, and attachments that match a search query.
  - Calendars and scheduling
    The calendar and scheduling features allow users to check the free time of other users, schedule meetings with them, and reserve resources, such as conference rooms and equipment.
  - Configuring Widgets and Live Text
    Widgets and Live Text enables end users to see and act on Live Text in supported documents, including IBM® Notes® mail, using XML extensions (widgets) created specifically for their use.
  - Configuring the Domino® OpenSocial component
    The Domino® OpenSocial component adds social and web features to make third-party processes available directly in the client user's mail. The OpenSocial component supports embedded experiences in the Notes® client, including OpenSocial Gadgets in the sidebar, pop-ups, and tabs.
    - Setting up the Domino® mail server for the OpenSocial component
      Setting up the Domino® mail server to support the OpenSocial component includes creating a widget catalog (or configuring your existing catalog with some additional settings), configuring ACL and roles in the widget catalog, enabling agents in the widget catalog, and setting launch options for the widget catalog in Notes® clients.
    - Widgets created from an OpenSocial gadget
      A widget created from an OpenSocial gadget is referred to as an OpenSocial widget. After a client user has added an OpenSocial widget or a Web widget configured for embedded experience to the widget catalog, the Domino® administrator must follow an approval process to review, approve, and make the widget available as an embedded experience to client users. Only OpenSocial widgets and Web widgets that provide client users with embedded experiences must be approved and require some additional configuration.
    - Setting up the Domino® server to run the OpenSocial component and Shindig
      The setup for running the OpenSocial component and Shindig includes creating the credential store application on the server running Shindig, configuring the credential store application, and creating a configuration settings document for all servers running Shindig.
      - Creating the credential store application on the server running Shindig
        Creating the credential store application on the server running Shindig is part of the procedure to set up the Domino® server to run the OpenSocial component and Shindig.
      - Configuring the credential store application for the OpenSocial component
        This procedure is part of the procedure to set up the Domino® server to run the OpenSocial component and Shindig.
      - Creating a configuration settings document for all servers that run Shindig
        Every Domino® server running Shindig is required to have a configuration settings document.
      - Configuring server session authentication
        Specify session authentication to support the OpenSocial component and embedded experiences features in Notes® clients.
      - Configuring a managed account for the OpenSocial component
        The OpenSocial component uses the Accounts framework to manage security between the Notes® client and the Domino® server running Shindig.
      - 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.
    - 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.
- Editing the NOTES.INI file
  You should rarely, if ever, need to modify a server's or client's NOTES.INI file. The NOTES.INI file contains many settings that Domino® and Notes® rely on to work properly. An accidental or incorrect change may cause Domino or Notes to run unpredictably. Therefore, you should edit the NOTES.INI file only if special circumstances occur or if IBM® Support Services recommends that you do so.
- Configuring directory services
  This section describes how to plan, set up, and use IBM® Domino® directory services.
- Configuring messaging
  This section provides an overview of messaging and describes how to set up mail routing, how to set up and customize mail servers, and how to track mail.
- Configuring iNotes®
  IBM® iNotes® (previously IBM Domino® Web Access) provides IBM Notes® users with browser-based access to Notes mail and to Notes calendar and scheduling features. Administrators specify mail policy and security policy settings as well as notes.ini file settings to complete the full implementation of IBM iNotes.
- Configuring Web servers
  This section describes how to set up the IBM® Domino® Web server, the Domino Web Navigator, and other Web servers such as IBM HTTP.
- Domino® Off-Line Services
  Domino® Off-Line Services (DOLS) provides a way for users to take Domino Web applications offline, work in them, and synchronize the changes with an online replica on the Domino server. Users are not required to have Notes® client because the applications are accessed with a browser.
- Setting up a cluster
  Setting up a cluster includes the tasks of creating and verifying that it is working correctly, and then setting up user access, mail, replications, size quotas, directory assistance, roaming, web navigation, and use of a private LAN in the cluster.

Configuring a managed account for the OpenSocial component

The OpenSocial component uses the Accounts framework to manage security between the Notes® client and the Domino® server running Shindig.

Procedure

From the Domino® Administrator client, open the Domino® Directory (names.nsf) for the domain.
Select People > Policies > Accounts.
Select Add Account. Unless otherwise specified, keep the default settings.

Click Basics, and complete these fields:

Table 1. Fields on the Basics tab
Field	Description
Account name	This descriptive name appears in the Accounts preferences user interface in Notes®.
Account description	For example, “Manages SSO between the Notes® client and the Domino® Server running Shindig.
Account type	Other
Account server name	If you organization has a single Domino server running Shindig, enter `http://domino_server_running_shindig_host_name/fiesta/container` 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 `http://shindig-hosts.acme.com/fiesta/container`.
Protocol	HTTP
Use Domino® single sign-on if available	Enabled
Domino® single sign-on server	`domino_server_running_shindig_host_name` (no protocol)
Allow other accounts to use this log in information	Disabled

Click Advanced, and complete these fields; do not set any of them to editable.
Table 2. Fields on the Advanced tab

Field Description

Authentication type DOMINO-SSO

Enforce SSL Yes

Enforce trusted sites Yes
Still on the Advanced tab, click Edit list, and then enter PreferredUsernameField=fullname.
Save the account document.