Saturday, August 18, 2007

New features in IBM Lotus Domino 8

The following list represents an overview of the new features that are available in IBM Lotus Domino 8. For more comprehensive information about new features, please refer to the Documentation Updates chapter of these release notes.

Notes Client support
  • Improved user registration
  • Better single log-on integration
  • Mail thread support
  • Recall message support
  • Support for administration of Windows navigation and management themes
  • Notes client version view in the Domino Directory

Messaging
  • SMTP Sender Authentication
  • Reverse-path setting for forwarded messages
  • Error limit before a connection is terminated - Specify the number of protocol errors that can be returned for a session before the session connection is terminated
  • Reject ambiguous names that are retuned during directory lookups
  • Deny mail to group names returned during directory lookups
  • Router group expansion
  • Transfer and Delivery Delay reports
  • Convert TNEF file attachments to Notes file attachments
  • Support Mail Threads when sending/receiving internet mail
  • Enable SMTP outbound authentication to relay hosts

Domino and DB2**
  • Enhanced management of Domino Master DB2 Account (Domino server user account)
  • Move Container feature in UI
  • SQL updates/inserts/deletes are transactional
  • DB2 Query view setting row limits is supported
  • DAV/QV design elements supported in a non-DB2 environment
  • Domino and DB2 enabled on Linux platform
  • HTTP access for QueryView
  • New DB2 Group server commands
  • Recreate links to DB2 enabled Notes databases tool
  • Compacting DB2 groups

Domino Web Access support
  • Domino administrators can enable Domino Web Access security settings via policies using a Security Policy Settings document. For additional information, see the release note "Using Security Policy Settings"
  • Domino Web Access will have a new look and feel when viewed in a portal, when the URL includes the &client=wps argument.

Administration
  • Improved throughput of critical administration process requests
  • Domino Portal Integration Wizard for Domino Extended Product Portlets
  • Integrated Administration Frame in Domino Administration Client for embedding External Administration Interfaces (such as portal)
  • DDM improvements (modular correction actions, event clearing, etc.)
  • DDM probe for monitoring LDAP requests
  • DDM WebSphere Services probe
  • DDM Administration probe type and Automatic Report Closing probe subtype
  • DDM Common Actions button on Events document
  • A new "updatesite.ntf" template which implements a complete, bona-fide Eclipse Update Site
  • Integration with Tivoli Enterprise console1
  • Performance and other improvements to server task monitoring
  • New options in Administration Preferences UI
  • Web enablement improvements to Domino Directory and Administration Process databases
  • Policies -- How to apply setting
  • Policies - Activities policy settings document
  • Policies - IBM Lotus Productivity Tools settings document
  • Policies - Window Naviigation settings in desktop policy settings document
  • Policies - Policy managment of Inbox cleanup on desktop policy settings document
  • Server command - Tell adminp process restart
  • Option to synchronize unread marks when creating replicas
  • Allow diagnostic data to be sent to IBM**

Java
  • Java console enhancements, for example, auto-connecting multiple, recently connected servers at startup
  • Support Same Java Runtime

Replication
  • Streaming cluster replication

Security
  • AES cipher support for SSL. Domino 8 introduces the ability to configure the Domino server to use the TLS_RSA_WITH_AES_128_CBC_SHA and TLS_RSA_WITH_AES_256_CBC_SHA ciphers for SSL, as defined in RFC 3268.
  • Use of xACLS to protect Internet password fields in the Domino directory

Web Server
  • User-defined attributes can now be added to the tag generated by the web engine. If the field $$HTMLFrontMatter is present on a form, its contents will be placed in the generated HTML, ahead of the tag, and the web server will not generate anything there automatically. The expected use of this feature is to supply a custom declaration for the generated HTML.
  • Note that as with other of these special fields, it is the application designer's responsibility to insure that the field is not visible on the form and that it does not allow POSTing of that field.
  • The content of the field is not used by the web server in any other way - it has no other effect on the generated HTML other than as described above. For example, suppling a doctype of HTML 4.01 STRICT will not cause the web engine to generate strict HTML. The content of the field is not validated in any way.
  • Limitation of thecurrent implementation: the special field is not recognized in custom response forms..
  • Users can now specify a custom declaration on a per form basis. If the field $$HTMLTagAttributes is present on a form, its contents is placed in the attribute list of the tag. Note that as with other of these special fields, it is the application designer's responsibility to insure that the field is not visible on the form and that it does not allow POSTing of that field.
  • The content of the field is not used by the web server in any other way - it has no other effect on the generated HTML other than as described above. The content of the field is not validated in any way.
  • Limitation of current implementation: the special field is not recognized in custom response forms.

Footnotes
** These features are not available for the System i platform in the current release.

No comments: