OBIEE Security - Default BI/Application Roles

Default BI Role:

Authenticate User : BI Administrative/Administration User

Default Application Roles

An application role defines a set of permissions granted to a user or group.Default application roles have corresponding default system user groups used in assigning catalog permissions and system privileges.

The Following are the Default Application Roles:

• The BIAdministrator role grants administrative permissions necessary to configure and manage the Oracle Business Intelligence installation. Any member of the BIAdministrators group is explicitly granted this role and implicitly granted the BIAuthor and BIConsumer roles.

• The BIAuthor role grants permissions necessary to create and edit content for other users to use, or to consume. Any member of the BIAuthors group is explicitly granted this role and implicitly granted the BIConsumer role.

• The BIConsumer role grants permissions necessary to use, or to consume, content created by other users. By default, every Oracle Business Intelligence authenticated user is part of the BIConsumers group and does not need to be explicitly added to the group or role

Sharing Schemas Required by Oracle Business Intelligence

The Repository Creation Utility (RCU) creates the BIPLATFORM and MDS schemas that are used when you install OBIEE 11g.

Now if you run a multi-node system what do you do, can you use the same RCU created schemas, or do you have to create parallel ones?

This extract from the Oracle OBIEE documentation (http://docs.oracle.com/cd/E23943_01/bi.1111/e10539/c3_requrmnts.htm#BABBICDA) provides the answer, which states that:

If you scale out a system from a primary node, the new nodes share the same RCU schemas as the primary.
A new OBIEE system needs separate RCU schemas.

------------------- extract ---------------------
If your organization has an MDS schema installed in a supported database, you do not need to install the MDS schema again with the RCU. You can use the existing MDS schema for your Oracle Business Intelligence installation. For this option, deselect the Metadata Services schema in the Select Components screen of the RCU. Then, when you install Oracle Business Intelligence, specify the details for the existing MDS schema in the MDS Schema screen.

However, each Oracle Business Intelligence system (BI domain) requires its own BIPLATFORM schema. Two or more systems cannot share the same BIPLATFORM schema, although they can share the same database. Therefore, you must run the RCU and install the BIPLATFORM schema and the MDS schema (if no MDS schema exists) before installing each distinct Oracle Business Intelligence system (BI domain). For example, if you plan to install two Oracle Business Intelligence systems, you must run the RCU and install the required schemas twice, or once for each system.

This requirement does not apply when you scale out an Oracle Business Intelligence system. In a scaled-out (clustered) system, you only run the RCU and install the database schemas once, before installing the primary node of the Oracle Business Intelligence cluster (the BI domain for the cluster is created at that time). Additional Oracle Business Intelligence nodes that you install during the scale-out process become members of that domain and, therefore, use the same set of schemas.

OBIEE: Handy hint - Pagination using RCOUNT

Pagination.

How many rows are returned by my query.

Add a column already in the query and edit the Formula max(rcount(1))

Now assuming each 'page' of output is 25 lines, how many pages of output are there: once again
Add a column already in the query and edit the Formula CEILING(max(rcount(1))/25)

We are busy paging through our report and want to know how many pages in we are:
Add a column already in the query and edit the Formula CEILING((rcount(1)-1)/25)+1

Remember you can cast the output as INTEGER and that will ensure that the output is integer and not double (doesn't show the .00).

OBIEE 11.1.1 - How to turn off EM centralized control

Note: This is not for the faint hearted and is not recommended, but is available in emergencies.

There is a flag in the central config file which can be used to turn off all of the EM central configuration. Edit the biee-domain.xml file from location ORACLE_HOME\user_projects\domains\bifoundation_domain\config\fmwconfig.  The flag is near the top; it says: centralConfigurationEnabled="true" . If you change this to "false", then none of the config files will be modified centrally.

(You will need to restart the managed server and BI System Components)

So what happens: In OBIEE 11G, The instanceconfig.xml file stores the OBI Presentation Server configuration settings. Many configuration settings are available in Enterprise Manager and those should be set within EM only. If any particular setting is not available in EM then we make changes directly in the instanceconfig.xml file. Like changing the default value of the maximum number of rows in a pivot table.

If you change any of the settings directly under EM control, as soon as you restart the BI components you will find the original values returned and your settings overridden. Setting centralConfigurationEnabled="false" will disable the EM settings overwriting any new values.

Important Note: Turning off EM centralized control for managing BI config files is NOT recommended.