manage all of a tenant's databases.
The administrator roles described in the following are defined via various privileges at the server and database level. Depending on the roles assigned to the administrators they can carry out specific functions.
superuser
The user superuser is created automatically. By default, this user is assigned the User management, License management, and Configuration administrator function privileges. This user can also enable this function privilege for other users. Users of the superuser type do not use up a license. They manage the system administration, but cannot use ARIS products due to license restrictions. The default password is superuser. You should change the default password to prevent unauthorized access. The password of the superuser is very important, as it is the only user who cannot be deleted. You can change all user data except for the user name. The superuser can recreate the other default users (system, arisservice, guest) if they were deleted.
system
The system user system assumes the of the system administrator and has all function and access privileges in all databases of a tenant. Authorized persons can use this emergency user to log in to any database, even if you are using an external system, such as LDAP, for authentication.
The name system cannot be changed. The System user check box for this user (Function privileges properties page in ARIS Architect) cannot be disabled either. You should immediately change the password manager to prevent unauthorized access.
To avoid problems, you should create additional system users. Having more than one system user can avoid problems, for example, if one system user has forgotten his password. If you forgot the passwords of all your system users, the full range of functions is no longer available and full data access is no longer possible.
The following administrator roles are defined:
Database administrators
Database administrators require the Database administrator function privilege in ARIS Administration. Users with this role have all function and access privileges and can edit data of all databases of the client.
Database administrators perform the following tasks at the server level:
Create databases
Delete databases
Backup databases
Restore databases using backups
Reorganize databases
Users with defined function privileges can perform additional actions at the database level.
Configuration administrators
A Configuration administrator requires the Configuration administrator function privilege in ARIS Administration.
They perform the following tasks:
Define the modeling conventions and adapt the appearance to match the corporate design of the company.
Define the contents of ARIS Method that are available in the database.
Script administrators
Script administrators require the Script administrator function privilege in ARIS Administration.
Script administrators perform the following tasks:
Write report scripts
Delete scripts
Transfer custom or modified scripts of previous ARIS versions
Analysis publisher
Analysis publishers require the function privilege of the same name in ARIS Administration.
Analysis publishers perform the following actions:
Analysis administrators
Analysis administrators require the function privilege of the same name in ARIS Administration.
Analysis administrators perform the following actions:
Please note:
Database administrators and database users can take certain measures to ensure that the
are optimized.If you observe basic factors from the start, you can optimize a database's size in terms of content. This results in faster database operations, such as backup and restore. Furthermore, administrative tasks become significantly easier. Consider this example: If you assign or change access privileges through the user groups, you do this only once for all users of the user group, instead of repeating the procedure for each user.
Just create the required user groups and delete user groups that you no longer need.
Delete database languages that are no longer in use from the database and the configuration. If a language comes back in use, you can create it again.
Create only those font formats that you use and delete the ones you do not require.
Create only the filters and templates that you use, and delete the ones you do not require. The Filters are not stored in the databases but will users to work only with the items they require.
Assign users access privileges to users through the user groups.
Reduce the size and resolution of images and embedded objects. For example, you can insert large logos in models and reduce their display size later, but they still take up the space required for their original size. If models with logos are versioned, the logos even take up this space in the database multiple times.
Distribute objects in different groups. For example, this makes sense because the group structure of a database reflects organizational structures of an environment. In this case, it makes no sense to save all object in the main group, for example. Database operations are faster if each group contains up to 1000 objects.
Therefore, it is recommended that you keep only objects that you really need in the database. If objects that no longer have any occurrences in any model have piled up, create a database backup and reorganize. During the reorganization, all objects that no longer have occurrences in any model are deleted.
Use suitable model sizes. The large size of a model that contains many objects affects both the model legibility and performance.
Modeling
Use occurrence copies if you want to use the same object in different models.
Use variants only for models and objects that differ. When creating model variants, you can decide which objects are to be created as a new variant, for which objects existing variants are to be used, and for which objects occurrence copies are to be created.
Versioning
Version only models that must be versioned. If you version the entire database every time, it becomes very large.
Do not create versions to save intermediate results. For this, we recommend database backups.
Delete versions you no longer need.