What's new in IBM® Domino® 9.0.1 Social Edition?

This topic describes the new features of the IBM® Domino® server and Domino® Administrator client in release 9.0.1 Social Edition. This topic also describes new features and functionality for administering IBM® iNotes® 9.0.1 Social Edition.

Server - new features

Server configuration settings for Social Edition are expanded

You can now enable or disable the use of locked domains and of SSL for OAuth redirect URLs.

For more information, see the related topic on the configuration settings document for servers that run Shindig.

Security - new features

Federated login password improvement

You can now use a security policy to prevent use of client passwords in the ID vault when federated login is configured.

For more information, see the related topic on the security settings policy federated login configuration.

Web SSO configuration now has custom cookie fields

The new fields LtpaToken2 Custom cookie name and LtpaToken Custom cookie name in the Web SSO Configuration document allow you to specify cookie names useful to your organization, for example, a name compatible with WebSphere®.

For more information, see the related topic on creating a Web SSO configuration document.

Ability to prevent loading of Java code on client

For more information, see the technote Enhancement to current Execution Control Lists mechanism in Notes® client to allow Notes® applications with the Ability to load Java code in the related topics.

Widgets and Embedded Experiences - new features

The OpenSocial component can now run on clustered Domino® servers

In general, you can configure the OpenSocial component to run in a cluster by specifying the host name of the load balancer or reverse-proxy (ip sprayer) network device rather than the host name of a single Domino® server running Shindig.

For more information, see the procedures under the related topic on setting up the Domino® server to run the OpenSocial component and Shindig.

OpenSocial widgets now have approval history and expanded status information

The Widget document in the catalog has a new Approval History section showing when each status change occurs, who makes it, and the action that causes it. The Approval History section is visible to users listed in the ACL of the Widget Catalog application with the [Admins] role

The following actions cause a status change:
  • An administrator approves a widget.
  • An administrator removes approval for a widget.
  • Either an administrator or a widget author updates an approved widget, thus removing approval from the widget.

For more information, see the related topics on widget approval.

The widget catalog has a new column showing the approved state of each widget. The Approved State column appears in the All Widgets, By Author, By Category and By Type views. There are several states for a widget:
  • Needs Review : the widget has not been reviewed by an administrator.
  • No Approval Needed : the widget has been reviewed and does not require further approval.
  • Needs Approval : the widget has been reviewed and requires further approval.
  • Approved : the widget has been approved by an administrator.
In the XPages user interface of the widget catalog, a green checkmark icon shows widgets that are approved, and widgets that have been reviewed and do not need further approval. No icon displays for widgets that are not approved or have not been reviewed.

In addition, widget users now can see approval state in the client sidebar. For more information, see the topic What are the My Widgets sidebar panel toolbar options? in IBM® Notes® 9.0.1 Social Edition Help.

Link to classic user interface for administering widgets

In the Notes® client, if you are in the XPages user interface and need to administer widget approval, you can use a new Administration link at the end of the widget view list to open the classic user interface.

The OpenSocial component no longer requires client NOTES.INI setting ENABLE_EE

If you upgrade all Notes® clients in your organization to 9.0.1, the NOTES.INI setting ENABLE_EE=1 used in 9.0 is not required. If, however, you still have some clients running 9.0, continue to use a desktop settings policy to set ENABLE_EE=1 for all affected clients. Also, if you need to disable Embedded Experiences, you can set ENABLE_EE=0 in the policy. For more information, see the related topic on creating policies for the OpenSocial component.

Accessible features in iNotes® full mode

In the IBM® iNotes® full mode, Mail, Calendar, Contacts, and Preferences are accessible. Users can set a preference that enables them to limit full mode functionality to the accessible features only. Administrators can use the server-wide notes.ini setting iNotes_WA_A11y=1 to limit all iNotes® users to the accessible feature set.

Mail Auto Save in iNotes®

The auto save feature in IBM® iNotes® automatically saves the body of mail messages created by users, so that drafts and changes made to them are maintained should users forget to save them, or if something happens to their workstation (for example, a crash or power outage). Auto Save is on by default and occurs at a default interval of 1 minute of idle time, or 10 minutes of active time. Idle time refers to the elapsed time since the document was last edited or created. Active time refers to the running elapsed time since the document was last edited, without any intervening idle time of the 1 minute duration. All of the contents of the message including, but not limited to, the body, will be saved in the Drafts folder. Users see a status bar message when the message is saved. By default, users see this setting on the Basics tab in their Preferences, where they can disable it.

There are new notes.ini file parameters on the Domino® server for enabling aspects of Auto Save.
Table 1. Notes®.ini file parameters for Auto saveTable shows parameters and acceptable values, followed by a description.
Parameter Acceptable Values Description

Default Value = 1

0,1 Disabling this setting removes the client preference setting and turns off Auto Save. The setting is enabled by default.

Default Value = 1 minute

A number Specifies the idle time interval. Default is 1 minute.

Default Value = 10

A number Specifies the active time interval. Default is 10 minutes.