ShowTable of Contents
Table of Contents |
Previous Page |
Next Page
For those administrators who want to get a brief overview on what is new in Domino 8.5 and 8.5.1, this page provides a list of new functions and features of the Domino server.
Console Log Mirroring
Console log mirroring causes a new server thread to be created which monitors all messages written to the Console Log file and duplicates these messages into another file. When this new file is filled, the thread closes the mirrored file and creates a new file into which subsequent messages are written.
Interoperability for non Notes calendar users
You can now configure compatibility mode and MIME simplification on the server to improve the experience for users of Microsoft® Exchange, Microsoft Outlook, and other non-Notes calendars.
Domino Server Commands
The following sections describe new and changed commands for Lotus Domino Server. For more detail refer to the New Server Administration Commands section of the Administration pages.
Show ID Vaults
This command displays configuration information about the ID vaults on a server and indicates if any documents required for proper vault operation are missing.
Show Stat Mail
You can view new messaging statistics in the server console window when you enter the command show stat mail.
DAOS Manager Tell commands
These commands include status and re-synchronization commands for the Domino Attachment and Object Service (DAOS). A listnlo command helps identify missing attachment files, and a prune command helps clean up unused ones.
Enhancement to Show Tasks
The Show Tasks server command now includes task status from additional mail router threads and generates detail regarding router activity.
Enhancements to Show Server and Show Directory
These commands now report whether the Domino Attachment and Object Service (DAOS) is enabled, and provide a list of which databases are included in DAOS with details for each.
Administration Process
The Administration Process records statistics to help you monitor the request processing activity of the administration process tasks. All administration process requests scheduled for processing originate from the Administration Requests database (ADMIN4.NSF). Requests are regularly retrieved from ADMIN4.NSF and temporarily stored in various ID tables, depending on the type and schedule of the request. They remain in the ID table until it is time to process specific requests based on schedule. Statistics are maintained for each of these ID tables to provide feedback on the ID table's usage as well as an indication of the Administration Process workload. All of the ID tables referred to by these statistics contain the NoteID of the administration process request that is to be processed.
Once the administration requests have been properly categorized into the appropriate ID tables, they are available for processing. At the appropriate scheduled time they will be placed onto one of a number of available message queues. Similar to statistics maintained for ID tables, statistics are maintained for each message queue to provide feedback on message queue usage.
A third group of statistics is also provided to provide feedback on request processing times for Administration Process batched requests.
These statistics are separated into the following three areas:
Statistics for Administration Process task
|
Corresponding statistic heading
|
Request ID Table Monitoring
|
|
|
|
|
|
|
ADMINP.BatchReqProcessing
|
These statistics are provided to represent an indication of Administration Process activity. The statistics do not really provide a method to monitor progress. For example, reviewing the statistics and noticing that there are a large number of "Waiting" statistics in any one of the message queues would indicate that all of the request processing threads are busy running long-running requests, and some reconfiguration of the Administration Process may be necessary. For example, you may need to add additional processing threads or configure dedicated threads.
For more details, see the topic "Statistics generated during administration request processing" in the Lotus Domino and Notes Information Center.
Database Features
Lotus Notes/Domino introduces a new on-disk structure called ODS51.
ODS 51 Advantages
You have to use ODS 51 to enable DAOS. To have the databases converted to ODS 51 you will have to add Create_R85_Databases=1 to the Notes.ini of the server (or workstation).
You can set this parameter by one of the following methods
- Edit the Notes.ini directly and restarting the server
- Enter the command at the server console:
> set config Create_R85_Databases=1
- Add the command through the Notes.ini section on the server configuration document.
Now every new database you create and every database you compact will be using the new ODS51.
Having to manually add this parameter lets administrators decouple the ODS upgrade from the server upgrade, and to control when and how the new ODS will be implemented on servers and clients. It’s always a good thing to be in control during an upgrade. Pre-Domino 8 servers will ignore this parameter, so you can add it prior to upgrading the server. The ODS version does not replicate from server to server. You have to add the parameter to every Domino 8.5.x server where you want to use the new ODS.
Now use the copy style compact command at the console to upgrade existing databases to the new ODS. Running the compact while the server is down will allow most system databases that are in use while the server is up, to be converted also.
>Load compact -c
To enable the new ODS and to reduce the size of dbs on your server use:
Load Compact -c -ZU -n -V
The parameters indicate:
-c Copy style compact, used to put db in new ods format.
-ZU Converts document attachments using compression type Huffman to LZ1 if db property is set.
-n Compress data
-V Compress views
NOTE: This also works on the workstation, you will need to run compact from the command prompt to update the local databases.
Domino Attachment and Object Service DAOS
This feature is explained in more details in on the
DAOS page.
Auto Populate Groups
Now you can have groups automatically built based on the user's home server. The auto-populated groups can be updated through out the day based on the time period you enter. Once populated, you can use the group anywhere you currently use groups, such as mail, policies, ACL and even as a member of other groups.
The auto-populated groups feature uses predefined criteria to automatically determine and update group membership. Use the auto-populated groups feature to apply policies to users and groups based on their home servers. Use the Group document to create a home server group whose group members use the specified server as their home mail server. Assign a policy to that group. That policy applies to everyone in the home server group. Any updates to the home server's group membership automatically impacts which users the policy is applied to. Use this feature to greatly reduce the work required to keep groups updated.
This features requires that the Domino Administration Server has the LDAP task running. The auto-populate group look-up is through an LDAP search query.
For IBM Lotus Domino 8.5, the use of home servers is the only auto-populate method available.
When you are creating a group and specifying group members in the Members field, if large numbers of names are retrieved from the Domino Directory, you may reach a limit as to how many names can be retrieved. If you reach the name look-up limit, you will see the following Domino Domain Monitor (DDM) event when viewing DDM events:
Search for auto-populated group members failed for group Server1MBUsers.: NAMELookups are limited on this server to a size smaller than what would be returned. See your Domino Administrator for more information.
To prevent this from happening, use the following server NOTES.INI setting to increase the limit from 1MB to a value greater than one.
Namelookup_max_mb=1
Start by increasing the value to 2MB and continue increasing the value until you do not reach a limit as to the number of names that can be retrieved.
Auto-populated groups can have subgroups. When an auto-populated group becomes large, subgroups are automatically created for the auto-populated group to hold all of the members of the group. The subgroup names have a specific format.
For example, if the auto-populated group name is Home Mail Server, the first automatically created subgroup for that group has the following name:
Home Mail Server-AP00001
Note: You cannot manually create an auto-populated subgroup and you cannot modify or edit the Members field.
The Domino update task runs on the Domino administration server and processes group documents by locating changes to those documents or to users and groups in the Domino Directory. The group document is searched for predefined criteria according to the auto-populated method you specify in the field "Auto-Populate Method" on the Group document. The entries in the fields "Additional Members" and "Excluded Members" are also used to determine the final group membership. If the final group membership list differs with the membership specified in the group document, the group document is updated. You specify how often the update task runs by specifying an update interval in the field "Auto-populated group Members update interval" in the Domino Directory Profile document.
Note: Auto-populated groups that contain subgroups should not be copied and pasted in the Domino Directory because they contain references to their subgroups; therefore, a copied and pasted auto-populated group refers to the same subgroups as the original group.
Auto-populated groups are available from the Domino Administrator, not from the Domino Web Administrator.
Setting up auto populated home server groups
Complete these steps to set up an auto-populated home server group.
- Make sure LDAP is configured and running on the server.
- Set up a Home Server auto-populated group in a Group document.
- Specify the update interval for auto-populated groups in the Domino Directory Profile document. This interval is read by the update process when it starts up. If you change the update interval setting, you need to restart the update process to make the change take effect.
Auto populated group statistics
Auto-populated group statistics are generated when the updated thread runs, according to the interval you specified in the field "Auto-populated group members update interval" on the Directory Profile document. If the Update task has problems processing the auto-populated groups, it will be indicated in the statistics and in the Domino Domain Monitoring (DDM), The normal cause of failure is due to failed LDAP search, because of an LDAP configuration issue.
The following statistics are generated under Update / APGroups:
|
|
|
Update.APGroups.Processed
|
Number of distinct auto-populated groups processed this iteration
|
|
|
Number of distinct auto-populated groups updated this iteration
|
Update.APGroups.MembersProcessed
|
Total number of members processed this iteration
|
Update.APGroups.TotalProcessingTime
|
Total processing time for this iteration
|
Update.APGroups.TotalFailed
|
Number of auto-populated groups that were not fully processed due to errors
|
Table of Contents |
Previous Page |
Next Page