Per user:
•Fill out the field RDBMS User in the screen Persons.
•Create a scheme for personal use. All reports executed under this scheme have access to the same amount of information under the filter that is set. The Oracle schema name must be identical to the RDBMS User Prefix plus the value of the field RDBMS User (option ‘E’ when calling log_on_through_oracle) or the schema name has to be equal to the value of the field RDBMS User minus the RDBMS User Prefix (option ‘O’ when calling log_on_through_oracle). For example this can be done with (assuming the user RDBMS prefix ‘P_’ option and ‘E’):
create user p_scotty
identified by p_scotty
default tablespace pbubs
temporary tablespace temp
/
•It is not recommended to use a shared central Oracle schema for all users unless it is not a problem when all reports can contain data of all projects and users do not affect each other with the changes in the filter.
•Assign to this scheme the application specific role for read and write access. This is standard ‘BUBS_USER’. This can be done by:
grant pbubs_user to p_scotty
/
•Alternatively you can make use of the application specific role for read access only. This is standard ‘BUBS_READER’.
The connection can be based on JDBC, ODBC, OLEDB, native Oracle SQL * Net or other connection methods.
The connection can be tested by signing in as the new Oracle user and then check the contents of the column gbr_naam of the view bubs_mijn_rechten_r.