You initially log in as an administrator, review roles and privileges in Oracle WebLogic Server, and then create a project in the Administration Tool. Projects consist of Presentation layer subject areas and their associated business model logical facts, dimensions, groups, users, variables, and initialization blocks. Administrators create projects so that developers and groups of developers can work on projects in their area of responsibility. The primary reason to create
projects is to support multiuser development.
You perform additional tasks as two different BI Developers, Adam Bell and Helen Mayes. Adam and Helen are working on the same development project and need access to the same repository. Adam will check out the repository, and make required modifications. Helen will also make modifications. Adam will commit the changes, merge the master repository with all changes, and publish the updated repository. Helen will then try and publish her repository and
will make issue-resolution decisions.
Preparing the Environment – Initial Administrative Tasks
The Oracle BI Repository development process is conceptually identical to the classic Software Configuration Management (SCM) three-way merge, in that changes are managed by merge and reconciliation. The Oracle BI Repository is stored as an .rpd file. Changes are managed by using the Administration Tool. Developers check out the file and make changes locally. Then, these changes are reconciled and merged into the master repository. To read a more detailed description and view an image of the merge process, click this link.
In this topic, you review user roles and privileges in Oracle WebLogic Server, set up the MUDE directory, and create a project.
Verifying User Roles and Privileges by Using WebLogic
In previous releases of Oracle BI, users were stored in the repository. These users are now stored in the WebLogic LDAP or whatever identity store with which your system is configured.
To review user roles and privileges in Oracle WebLogic Server, perform the following steps:
1 . Open the WebLogic Administration Console. Open a browser window and in the address bar,
enter http:\\<hostname>:port\console (for example, http:\\localhost:7001\console). Note that
7001 is the default port assignment for the Oracle WebLogic Server Administration Console.
2 . The Oracle WebLogic Server Login window appears. Enter your username and password (for example, weblogic/welcome1).
Note: During installation, you are prompted for a username and password to use as an Oracle BI Administrator. This user (weblogic, for example) has administrative privileges across the Oracle Business Intelligence (BI) stack. This includes the Oracle BI Repository, the Oracle BI Presentation Catalog, Oracle BI Publisher, the identity store in WebLogic, and so on.
3 . Click Login. The Oracle WebLogic Server Administration Console appears.
4 . Select Security Realms from the Domain Structure pane on the left.
5 . The “Summary of Security Realms” pane appears on the right. Select myrealm from the Realms table.
6 . The “Settings for myrealm” pane appears on the right. Click the Users and Groups tab.
7 . All users who are configured in this security realm appear in the Users table. In the Name column, click abell.
8 . The “Settings for abell” pane appears. From this pane, you can change Adam’s name, password, attributes, and the groups to which he belongs. Click the Groups tab.
9 . Review the detail for Adam Bell on the Groups tab and note the two selection areas: Available and Chosen. You select a group and then use the arrow buttons ( ) to toggle a parent group membership on or off for the specific user.
There are three default groups specific to Oracle BI: BIAdministrators (in the Available grouping in the image), BIAuthors, and BIConsumers (both in the Chosen grouping in the image). These default groups are provided as a convenience during installation, so that you can use the Oracle BI software immediately. Groups are nested in a hierarchy.
• Members of the BIAdministrators group have permissions equivalent to those of the Administrator user of earlier releases. Members of the BIAdministrators group are by default members of both other groups.
• Members of the BIAuthors group have permissions necessary to create content for others to consume. Members of BIAuthors are members of BIConsumers.
Aspired to become an OBIEE 11g? Explore the post to discover the know-hows on OBIEE 11g Training Online.
• Members of the BIConsumers group have permissions necessary to consume content created by others.
Now that you’ve reviewed Adam’s privileges, click the breadcrumb trail for “Users and Groups” (highlighted in the image below, just above the “Settings for abell” pane) to review the privileges for Helen Mayes. The breadcrumb trail provides a means for you to quickly navigate back to pages that you have previously viewed.
10. The “Settings for myrealm” pane reappears. Click hmayes.
11.Once again click the Groups tab. Note that Helen is also a member of the BIAuthors and BIConsumers groups.
12 . Click Log Out and then close your browser.
For indepth understanding of OBIEE click on