| User category | Estimates |
|---|---|
| Configured users | 12,000 |
| Logged-on users | 6,000 (50% of configured users) |
| Active users | 3,000 (25% of configured users) |
Logical divisions of users
Once you have enumerated your user base, the next step is to group these users according to location and function. Here it is important to identify not only geographic divisions, but also functional or other administrative divisions within your organization. Both geographic and administrative divisions are used in the next step, where the users are grouped to create nodes.
Acme Co.
example
Thus, in our Acme Co. example, the total user population of 12,000 is distributed in the following manner:
Grouping users to create nodes
With the logical divisions among your user base clearly delineated, you are now ready to group your users into nodes. Before making these decisions, however, a number of factors must be considered:
A node is a Calendar database containing all user and resource information and calendars
See Appendix B, "Sizing Guidelines" for any additional node size restrictions related to particular hardware or an operating system.
unimvuser utility, see Appendix G "Calendar Utilities".
A further consideration in terms of the investment of time required to administer your Calendar Server network is the repetition of some tasks. Certain features -- holidays, designates and members-only groups -- are specific to each node. The tasks associated with these features, such as adding holidays or assigning designates, must be done separately on each node.
/users/unison/misc/unison.ini file. For more information on setting and modifying parameters, see Chapter 7, "Server Configuration."
lck_users determines the maximum number of logged-on users. The default value is 100. Although setting this number too high will waste system resources, it must be set relative to the size and expected usage of each node.
mail enables or disables mail notification for all event or task creation. The default value enables this feature.
resourceconflicts permits double-bookings.
allowattachments enables or disables the attachment of files to events or tasks created by clients. The default value disables this feature. If attachments are allowed, they may be limited in size using the parameter maxattachmentsize.