Technology Overview

allows business-based requesters to use a simple end-user interface to perform actions:

See the "Features" page for a more comprehensive overview, or download our Administration manual from the downloads page.

User Create? But I want Load-Balancing, and I have clusters!

When we create a user, we:

  • Check the name for duplicates in all Domino directories - and optionally add unique numbers to ensure uniqueness. Optionally check name elements against an external database (such as a global shortname directory)
  • Add the user to relevant groups based on profile information
  • use profile-based information to query the directory in order to work out the least loaded server
  • Create the user's mailfile using a profile-specified template name and user access level.
  • If that server is part of a cluster, and the configuration variable "Add mailfile to all clusters" is set on, then replica mailfiles are created on all cluster mates.

What happens when I start to create large groups?

The group management tool has been designed from the ground up to accommodate "large" groups - groups containing more than 200+ names. Domino limits group size to less than 16k of information. Once a group approaches this size, the group manager "spawns" subgroups automatically. So if group "Mail Users" gets close to the limit, the group management tool will move the existing members to a new group called "Mail Users_01", and add "Mail Users_01" as a member to "Mail Users". There are no practical limits to the number of spawned subgroups that the group manager can cope with.

We built the group management product for a 110,000 user, six domain European based corporate. We know about large groups.

What makes better than other Domino Administration Systems?

  • It's profile based. You create profiles to dictate how the requesters and authorisers will use the product.
    For instance, that business user in the Marketing department can only create marketing users on the marketing server. And the user is automatically added to the correct marketing groups. All we need is the new users' name.
  • It has a "Dynamic" field feature, where you as the Administrator can specify in the profile mechanism "What's the users new office telephone number", and write it to a particular person document field. All without programming.
  • It's based on LotusScript, meaning that you do NOT have to run dedicated server-add-in tasks which may crash your server
  • It can run on multiple servers with failover capability, giving you 24x7 operation.
  • It can run Domino agents in YOUR database for particular requests at particular stages of the request. For instance, you can "trap" all User Create transactions, and should they succeed - will run your agent in your database, passing it the request document with all information.
  • You can interface with using our object-orientated LotusScript classes. Should you wish to add group-management functionality to your applications, this can be achieved by writing less than 20 lines of LotusScript code. So if you wish to add a web-user management portal to your existing intranet - its very, very easy.
  • It supports a Domino multi-domain environment.

Profile-based? What does that mean?

A profile is a collection of "rule" information that dictates:

  • What the name of this profile is - what will be displayed to the requester. So the requester sees "New marketing user in London" instead of "AppSev01Mar/Lon/Business/IBM"
  • Who can request things with this profile. So the requester only sees what they're supposed to see.
  • Who can authorise things with this profile. If a requester is listed as both a requester and an authoriser, it's automatically authorised.
  • What static fields should be filled in on the person document when using this profile.
  • What dynamic fields (fields where the requester is prompted for information at run-time) when using this profile
  • Which groups should the person automatically be added to during creation
  • And for User Create, additional sub-profiles can be specified. Each sub-profile also includes static field, dynamic field, and group information:
    • ID Type profile. So you can choose between "Temporary" and "Staff", and therefore have different certificate expiration periods, ID file encryption strengths, etc.
    • Certifier profile. You can specify which certification hierarchy should be used for this particular user.
    • Location profile. So you can decide which server(s) a particular "location" uses. If you specify more than one server, will choose the server with fewest users (load balancing). If that server is a member of a cluster, and the configuration profile has been set, then replicas of the user mailfile will be created on all cluster mates.
    • Country Profile. Should you choose to, you can have different groups, static fields and dynamic fields based on country.
    • Company Profile. Should you have multiple companies, you can specify different groups, static fields, and dynamic fields
    • Business Group Profile.

This means that the administrators can make different business rules for different business groups, enforce control, and yet retain complete flexibility.

Does it work with Domino 5? 6? 7? 8?

It is of course tested and certified on Domino v5, v6 and v7.0

Currently, we require that your infrastructure has Domino 5.0.8 or better, and that the requesters use Notes 5.0.8 or better. We test it on a cross-platform, cross-domain infrastructure that includes Domino 5.0.11 and Domino 6.x and 7.0 Servers, without difficulty.

  • Is a standard suite of Domino applications - no server add-in tasks, no difficult deployment.
  • Supports Domino v5, v6, v7
  • Supports all Domino platforms
  • Supports Notes clients on Windows and Macintosh
  • Installs within 60 minutes - and requires no end-user training
  • Is an enterprise-level Identity and Resource management tool, supporting multiple domains, multiple clusters, load balancing, failover, etc.