Functional Differences Between the Delegated Administrator Console and Utility

The Delegated Administrator Console and the Delegated Administrator Utility (commadmin) have some differences in functionality. This section covers those differences and includes the following topics:

• Functions in Utility but not in Console

• Functions in Console but not in Utility

Functions in Utility but not in Console

The following functions can be done in the Utility, but not in the Console:

• The purge command, commadmin domain purge, permanently removes a user, group, or calendar resource from the LDAP directory. The console can only mark the LDAP entries for deletion, but the purge utility actually deletes them.

  This restriction is purposefully set up to protect the LDAP from an administrator inadvertently permanently removing entries.

• The debug command, commadmin debug log, creates a debug log; it cannot be done in the console.

Functions in Console but not in Utility

The following functions can be done in the Console but not in the Utility:

• Create and manage service packages.

  With the utility, you can use the -S mail,cal option to add mail and calendar services to a resource, but this does not let you assign a set of service attributes with specific values, as you can do with service packages.

• Manage Service Provider Administrators (SPAs) and provider organizations.

  To create a Service Provider Administrator and provider organization, you must use LDIF files and directly write to LDAP using LDAP tools. Also, the Top Level Administrator (TLA) does not have administrative control over provider organizations; they appear as regular organizations to the TLA. And a TLA cannot create an SPA. Once they are created, you can modify and delete them in the Console.

• Create and manage shared organizations and full organizations subordinate to a provider organization.

For more information on the Delegated Administrator Console and Utility, see Sun Java System Delegated Administrator 6.4 Administration Guide.