Administration Process now supports updates to Private Design Elements
Notes and Domino supports the renaming of private design elements in Administration Process rename user requests beginning in R5.0.5. Before this enhancement, the rename user request was unable to rename private design elements and sign them. Now, the server builds the list of design elements when the user authenticates and signs the elements after the rename has taken place.
For more information, see the Release Note entitled "AdminP now supports updates to Private Design Elements."
Calendar Printing for International Formats
Calendar and Scheduling printing now supports international formats and characters. For localized language versions of Notes, users can print calendars in the same format as they appear on screen.
Terra Added as Welcome Page Option
The Welcome page for the Notes client now includes access to Terra, a Spanish-language news and entertainment portal. This Welcome page has three frames: the user inbox in the top left frame, a calendar in the bottom left frame, and the Terra portal in the right frame.
For more details on setting up Terra, see the Release Note entitled "Headlines with Terra."
New "By Author" View in TeamRoom Template
The TeamRoom template included with Notes and Domino has been enhanced to include a "By Author" view, so that team room participants can view all documents categorized by author.
New User Preference, "Show in-line MIME images as attachments"
A new setting called "Show in-line MIME images as attachments" has been added to the User Preferences (basics) dialog box, listed under Additional Options. When this setting is checked, all multi-part/mixed in-line images will display as attachment icons. When this option is not checked, multi-part/mixed in-line images will be embedded in a Notes document. The setting corresponds to a NOTES.INI variable called "ShowIMIMEImagesAsAttachments".
Support Added for LDAP Search References
Prior to this release, the Notes Client was unable to correctly handle LDAP search references, which are more correctly known as LDAP Continuation References as defined in RFC 2251 Paragraph 4.5.3. Starting in Release 5.0.5, the Notes client has been enhanced to correctly process these returns (which contain a mix of search results from the responding directory and referrals to other directories that may contain additional results).
For more information regarding LDAP search references, see the Release Note entitled "Client Support for LDAP continuation references".
Extended Directory Catalog
The Extended Directory Catalog combines advantages of the Domino Directory and the standard Directory Catalog by aggregating entries from multiple Domino directories into a single directory database. This is similar to the construction of a standard Directory Catalog but retains the full set of indexed views and other features of the Domino directory. This enables the enterprise to maintain a single consolidated server-based directory structure that responds rapidly to a variety of search patterns and can contribute to enhanced mail router performance.
For more details on the capabilities and configuration of the Extended Directory Catalog, see the Release Note entitled "Extended Directory Catalog".
TrimTrailingSpaces property added for ODBCResultSet
ODBCResultSet has added a new property in 5.0.5, TrimTrailingSpaces, which will indicate whether trailing spaces are trimmed from character values upon retrieval.
For more details on using the TrimTrailingSpaces property, see the Release Note entitled "TrimTrailingSpaces property for ODBCResultSet".
AddressBooks property of NotesSession now returns directory catalogs
As of 5.0.5, the AddressBooks property of NotesSession returns directory catalogs. The (already available) IsDirectoryCatalog property of NotesDatabase is True for a database retrieved through AddressBooks if it is a directory catalog and False if it is not. The database must be explicitly opened to see this property. This property always is False for a database retrieved through a means other than AddressBooks.
New GTR Search Engine Now On by Default
In R5.0.3 and R5.0.4, Lotus included with Notes and Domino a new search engine designated GTR-34 (in addition to the engine that originally shipped with Notes and Domino R5). The GTR-34 engine was not turned on by default in these releases, however.
Beginning in R5.0.5, the newer GTR-34 engine has become the default search engine. It is automatically turned on when you upgrade to R5.0.5. Using the new GTR-34 engine, unicode support becomes available for all searches. You will also see significant improvements in search response time. GTR-34 reduces the size of indices up to a factor of 5. It also delivers query lookup performance that is significantly faster than the original engine.
Note that Domino will re-build indices for all databases that are currently indexed, unless your administrators already activated the GTR-34 engine and allowed it to rebuild all indices when GTR-34 was first released in R5.0.3/R5.0.4. Domino will rebuild indices on both the 5.0.5 server and on Notes client machines which access the 5.0.5 server. The original search engine can be retained by placing the following parameter in your NOTES.INI file. The parameter must be present on any client or server where you want to retain the old search engine and prevent the rebuilding of indices:
FT_LIBNAME = ftgtr
Workstation ECL Refresh Button
The Workstation Security: Execution Control List dialog box has been updated to include a Refresh button that automatically updates the workstation ECL with settings from the Administration ECL on the user's home server. You can use the new Refresh button in place of the previous method that required administrators to create a button with a formula and insert it in a mail message to roll out updated ECLs to users' workstations.
For more details on using the Workstation ECL Refresh button, see the Release Note entitled "Using the Workstation ECL Refresh Button".
Templates Enabled for DOLS
Domino Off-Line Services (DOLS) provides a way for browser users to utilize Domino Web applications offline. Using a browser, the user can take a Domino application offline, make changes, and synchronize those changes with the online version. Beginning in R5.0.5, Webmail (mail50ex.ntf--extended mail template) and the Web Discussion templates are enabled to work with DOLS. For more information about DOLS, refer to the Lotus Web site at:
DOLS 1.0.1 Incorporated into the Domino Server
Domino Off-Line Services (DOLS) 1.0.1 has been incorporated into the Domino kit as of 5.0.5. DOLS enables Web browser users to use Domino applications while disconnected from the network. These applications can be replicated later, either on-demand or on a scheduled basis. As of 5.0.5, DOLS 1.0.1 is also supported on the OS/2, AIX, and Solaris server platforms. Users should refer to the DOLS topics in the Admin and Designer help files for complete information about how to implement and use DOLS.
iNotes Access for Microsoft Outlook - Calendaring and Scheduling and DOLS Support
iNotes Access for Microsoft Outlook now allows Microsoft Outlook users to access their mail, calendaring, and scheduling information using a Domino server instead of Exchange. With iNotes Access for Outlook, organizations can take advantage of the Domino capabilities, such as reliability, scalability and expanded platform coverage, for their messaging infrastructure without changing clients. Additionally, as of 5.0.5, iNotes Access for Microsoft Outlook now utilizes the Domino Off-Line Services (DOLS) technology to not only help in the delivery of the client code to the end users, but by enabling end users to access their mail while disconnected. Users should refer to the iNotes Access for Microsoft Outlook and DOLS topics in the Admin and Designer help files for additional information.
Several new features have been added to WebMail, including client performance improvements, off-line capability enablement, support for server-based Directory Catalogs, and overall user interface improvements.
Websphere and Domino Integration
Several improvements have been introduced in Domino R5.0.5 to better integrate with IBM WebSphere software.
Single sign-on across Domino Web servers
A Web user can now log on once to a Domino server, then access any other Domino server in the same domain without logging on again. This is accomplished with a new "multi-server" option in the Server record for session-based authentication, along with a new configuration document in the Domino Directory called the Web SSO document. Note that all Domino servers participating in multi-server session authentication must be at the Domino R5.0.5 level or above, and users' Web browsers must have cookies enabled. For more details about deploying this feature, see the Release Note entitled "Enabling Single Sign-on for Domino and WebSphere servers".
Single sign-on with WebSphere Application Server 3.5
A Web user can now log on once to a Domino server, then access any WebSphere Application Server 3.5 without logging on again. This is accomplished by setting up the new "multi-server" option for session-based authentication and importing the secret key from a WebSphere server rather than generating it in Domino. The WebSphere server(s) must be configured in secure mode and use WebSphere's LTPA (Lightweight Third-Party Authentication) protocols. The WebSphere server(s) may use the Domino Directory as the repository for user definitions and passwords or certificates, via Domino's LDAP service. Note that all servers participating in a single sign-on domain must be at the Domino 5.0.5 and/or WebSphere Application Server 3.5 level. For more details about deploying this feature, see the Release Note entitled "Enabling Single Sign-on for Domino and WebSphere servers".
New Java API options for authenticated invocation
New options in the Notes APIs for Java allow sessions between Domino servers, or calls between Domino and WebSphere 3.5 Java code, to carry a user's authenticated identity. The servers must be set up to utilize the "single sign-on" features introduced in Domino R5.0.5 and WebSphere 3.5. For more details about these API changes, see the Release Note entitled "Enabling Java API options for authenticated invocation".