Administrator User Interface

The Administrator UI allows the following aspects of the Carapace Hub to be configured:

audit The Carapace audit records information about the activities done on or by the system. All aspects of the audit are configured using the Administrator's UI.

authentication database The Carapace authentication database holds information about users -- names, addresses, passwords etc. -- as well as information about the roles they can perform and the resources they can access.

messaging The Carapace Hub can store and send messages for users. The messaging configuration is performed using the Administrator's UI.

scheduler The Carapace Hub incorporates a scheduler which is used to defined the times a job needs to be run along with what the particular is. The scheduler configuration is performed using the Administrator's UI.

audit	The Carapace audit records information about the activities done on or by the system. All aspects of the audit are configured using the Administrator's UI.
authentication database	The Carapace authentication database holds information about users -- names, addresses, passwords etc. -- as well as information about the roles they can perform and the resources they can access.
messaging	The Carapace Hub can store and send messages for users. The messaging configuration is performed using the Administrator's UI.
scheduler	The Carapace Hub incorporates a scheduler which is used to defined the times a job needs to be run along with what the particular is. The scheduler configuration is performed using the Administrator's UI.

Audit Configuration

The Carapace Audit records information about the activities done on or by the system. The following aspects of the audit are configured using the Administrator's UI.

activities The Carapace Audit records information about the activities done on or by the system. Carapace comes configured with certain activities, but custom activities can be configured using this UI.

content Audited information is held within a database. This information may be held for as long as required. Eventually, the data will need to be removed -- to free up disk space etc. The content of the audit can be purged using the Administrator's UI.

objects The Audit can be extended to record arbitrary objects. Such objects require custom handlers to store and retrieve the objects. The configuration for the storage of objects within the Audit is done using the Administrator's UI.

types On delivery, the Carapace Audit is configured to hold information about actions done by users and actions done to messages -- i.e. there are two audit types configured. Further audit types are added programmatically using the Admin interface. The Administrator's UI can be used to see which types are configured within the Audit.

types It is particularly important to record when actions fail. The types of error which can be held within the Carapace Audit is maintained using the Administrator's UI.

activities	The Carapace Audit records information about the activities done on or by the system. Carapace comes configured with certain activities, but custom activities can be configured using this UI.
content	Audited information is held within a database. This information may be held for as long as required. Eventually, the data will need to be removed -- to free up disk space etc. The content of the audit can be purged using the Administrator's UI.
objects	The Audit can be extended to record arbitrary objects. Such objects require custom handlers to store and retrieve the objects. The configuration for the storage of objects within the Audit is done using the Administrator's UI.
types	On delivery, the Carapace Audit is configured to hold information about actions done by users and actions done to messages -- i.e. there are two audit types configured. Further audit types are added programmatically using the `Admin` interface. The Administrator's UI can be used to see which types are configured within the Audit.
types	It is particularly important to record when actions fail. The types of error which can be held within the Carapace Audit is maintained using the Administrator's UI.

Authentication Database Configuration

The Carapace authentication database holds information about users -- names, addresses, passwords etc. -- as well as information about the roles they can perform and the resources they can access. The following information is configured using the Administrator's UI:

addresses A person can have multiple addresses which are used for identification. For example, a person may have multiple Internet email addresses, several X.400 mail addresses. In addition, the person can be identified by their National Insurance number -- this too can be seen as a form of address. In the same way, computer systems can have multiple addresses.
This UI allows further address types to be configured as well as addresses for users/computer systems to be setup.

resources A person or computer system may access multiple resources. Access to some resources may be unrestricted while other resources may only be accessible to a very limited number of users. The set of resources controlled by the Carapace authentication database is configured using the Administrator's UI.

roles Access to a resource is defined by a role -- a user may be allowed multiple roles, but can adopt only one role at a time. Once in a given role, it is the role which defines the resources which are accessible. The set of roles and the resources they control is configured using the Administrator's UI.

users The authentication database holds information about users -- these users may be people, or they may be other computer systems. In whichever case, details are recorded about them within the authentication database. This information is configured using the Administrator's UI.

addresses	A person can have multiple addresses which are used for identification. For example, a person may have multiple Internet email addresses, several X.400 mail addresses. In addition, the person can be identified by their National Insurance number -- this too can be seen as a form of address. In the same way, computer systems can have multiple addresses. This UI allows further address types to be configured as well as addresses for users/computer systems to be setup.
resources	A person or computer system may access multiple resources. Access to some resources may be unrestricted while other resources may only be accessible to a very limited number of users. The set of resources controlled by the Carapace authentication database is configured using the Administrator's UI.
roles	Access to a resource is defined by a role -- a user may be allowed multiple roles, but can adopt only one role at a time. Once in a given role, it is the role which defines the resources which are accessible. The set of roles and the resources they control is configured using the Administrator's UI.
users	The authentication database holds information about users -- these users may be people, or they may be other computer systems. In whichever case, details are recorded about them within the authentication database. This information is configured using the Administrator's UI.

Messaging Configuration

The Carapace Hub can store and send messages for users. The following messaging configuration is performed using the Administrator's UI:

mail domains In most mail systems -- e.g. Internet email of X.400 etc. -- the full mail system is partitioned into domains. A user has a mail address within a domain, and some domains contain other smaller domains. The Carapace Hub holds message stores for users. The list of domains served by Carapace is configured using the Administrator's UI.

message stores Carapace holds messages for users within message stores. These message stores are configured using the Administrator's UI.

MTA queues Within mail systems, messages are transferred between Message Transfer Agents (MTAs) until finally a message is delivered to its recipient(s). If one MTA finds that another MTA is unreachable, typically the messages will be stored until a connection can be established. Carapace messaging works in this way. Different queues are setup to hold messages which require transfer to different MTAs. The configuration of these MTA queues is done within the Administrator UI.

mail domains	In most mail systems -- e.g. Internet email of X.400 etc. -- the full mail system is partitioned into domains. A user has a mail address within a domain, and some domains contain other smaller domains. The Carapace Hub holds message stores for users. The list of domains served by Carapace is configured using the Administrator's UI.
message stores	Carapace holds messages for users within message stores. These message stores are configured using the Administrator's UI.
MTA queues	Within mail systems, messages are transferred between Message Transfer Agents (MTAs) until finally a message is delivered to its recipient(s). If one MTA finds that another MTA is unreachable, typically the messages will be stored until a connection can be established. Carapace messaging works in this way. Different queues are setup to hold messages which require transfer to different MTAs. The configuration of these MTA queues is done within the Administrator UI.

Contents Index Current topic: Carapace Hub Related topics: audit