Database roles, users, and logins
During the deployment, administration, and use of i2 Analyze, a number of different actions are completed against the Information Store database. These actions can be separated into different categories that are usually completed by users with differing permissions.
The database roles described below are high-level concepts. In the example deployment, a number of different roles and users are used to demonstrate the types of roles that might complete each action. The way these users and roles are implements depends on the database dialect that is used.
Database roles
In the example, the following roles are used:
| Role | Description |
|---|---|
| DBA_Role | The DBA_Role is used to perform database administrative tasks. |
| External_ETL_Role | The External_ETL_Role is used to move data from an external system into the staging tables in the Information Store database. |
| i2_ETL_Role | The i2_ETL_Role is used to read data from the staging tables and ingest it into - and delete it from - the Information Store database. |
| i2analyze_Role | The i2analyze_Role is used to complete actions required by the Liberty application. For example, returning results for Visual Queries. |
| i2_Public_Role | The i2_Public_Role is used to complete actions against database objects in the Information Store public schema. |
| Deletion_By_Rule | The Deletion_By_Rule is used to access and run all of the views and procedures in the Information Store public schema. |
To understand how these roles are implemented in each database dialect, see: