To check out the project, which begins the development process, perform the following steps: 1. Click File --> Multiuser --> Checkout.
2 . In the "Extract from SharedMaster.rpd" dialog box, enter the repository password (for example, Admin123) an click OK.
3 . The Browse dialog box appears. Select the checkbox for Sample Apps Presentation and click OK.
4 . The "Create new subset repository" dialog box appears.
In the "Create new subset repository" dialog box, change the default file name, Metadatan.rpd (where nrepresents a variable number), to abell.rpd. There are several items to note at this point: 1. The file name (abell.rpd, representing Adam Bell) is arbitrary. 2. The repository file is being saved to the default repository directory (<ORACLE_INSTANCE>bifoundationOracleBIServerComponentcoreappplication_obips1reposito y) not the RPD directory. 3. A copy of the shared repository (SharedMaster.rpd) has been copied to the default repository directory
5 . Click Save. 6 . Adam Bell's repository appears with the subset of data from the Sample Apps Presentation project. The other subject areas and business models from SharedMaster do not appear. Note that Adam's repository name appea in the title bar at the top of the Administration Tool.
Leave the repository and the Administration Tool open. Minimize the Administration Tool. 7. Navigate to <drive>:RPD by using Windows Explorer. Two new files appear: SharedMaster.000 and SharedMaster.mhl. The SharedMaster.000 file is an automatic backup file for SharedMaster.rpd, where the SharedMaster.mhl file tracks the checkout status and parameters, including project, computer, and user.
8 . Navigate to the default repository directory ( <ORACLE_INSTANCE>bifoundationOracleBIServerComponentcoreappplication_obips1repository Three new files appear: original bell.rpd, abell.rpd.Log, and abell.rpd. The abell.rpd file is a subset of the SharedMaster repository that you modify. The original bell.rpd file contains the original repository file, which the Administration Tool uses to track your changes or revert to the original. Finally, the abell.rpd.Log file is your local log file.
9 . Check out the repository as Helen Mayes. Open up a new instance of the Administration Tool, and then click File > Multiuser > Checkout.
10 . In the "Extract from SharedMaster.rpd" dialog box, enter the repository password (for example, Admin123) an click OK.
11 . The Browse dialog box appears. Select the checkbox for Sample Apps Presentation and click OK.
Note that you are not given any indication that another developer currently has the project out for updates. This is an intentional feature of the product. Multiple developers can work on a single project. All changes are merged during the checkin process. 12 . In the "Create new subset repository" dialog box, change the default file name, Metadatan.rpd (where n represents a variable number), to hmayes.rpd.
13 . Click Save.
14 . Helen Mayes' repository appears.
Leave the repository and the Administration Tool open. Minimize the Administration Tool. 15. Navigate to the default repository directory ( <ORACLE_INSTANCE>bifoundationOracleBIServerComponentcoreappplication_obips1repository Three new files appear for Helen Mayes, just as they appeared for Adam Bell: originalhmayes.rpd, hmayes.rpd.Log, and hmayes.rpd.
The most significant difference between Oracle Business Intelligence 10g and 11g is:
The administration is done using:
Middleware Control (non-Java components)
Many configuration settings that affect repository development, including the default published repository, are now centrally managed in Fusion Middleware Control. You can no longer manually change these configuration settings such as the default ODBC DSN for the Oracle BI Server.
In Oracle Business Intelligence release 10g users and groups could be defined within a repository file using Oracle BI Administration Tool. In Oracle Business Intelligence release 11g users and groups can no longer be defined within a repository. Oracle Business Intelligence authenticates users and get groups using an Oracle WebLogic Server authentication provider against user information held in an identity store. In 11g any named user can be granted administrative permissions if desired. This compares to 10g where there was a single user with administrative permissions who was named Administrator.
In Presentation Catalog, the Everyone group has been replaced with the authenticated user role
Oracle BI Delivers now accesses information about users, their groups, and email addresses directly from the configured identity store. In many cases, this completely removes the need to extract this information from your corporate directory into a database and configure SA Subject System Area to enable all Delivers functionality. SA System Subject Area is still supported for backward compatibility.
The new BI Systems Management API Java programming interface includes a rich set of standards-based JMX MBeans to enable developers to automate administrative operations using Java and scripting technologies such as WLST (WebLogic Scripting Tool) and JPython. You can also use the BI Systems Management API to programmatically start and stop Oracle Business Intelligence. This feature is especially helpful for automating the rolling restart of Oracle BI Servers in a cluster, to enable repository upgrade with zero end-user downtime.
This release introduces several enhancements for localizing your system, including:
language to enable users to view member names in their own language. Typically, you define a session variable to dynamically select the appropriate alias upon user login.
You can now define presentation hierarchies and presentation levels in the Presentation layer. These objects provide an explicit way to expose the multidimensional model in Oracle BI Answers and enables users to create hierarchy-based queries.
Presentation hierarchies expose analytic functions such as:
Support for Unbalanced (Ragged) and Skip-Level Hierarchies
Oracle Business Intelligence now supports:
leaves (members with no children) do not necessarily have the same depth.)
do not have a value for a particular ancestor level. )
members that all have the same type. For example, an organizational chart has a distinct parent-child hierarchy, but all members are employees. hierarchies.
Creating Subject Areas for Logical Stars and Snowflakes
You can automatically create one subject area (formerly called presentation catalog) for each logical star or logical snowflake in your business model.
You can configure logical columns so that Oracle Business Intelligence users can select the currency in which they prefer to view currency columns in analyses and dashboards.
Generating and Applying XML Patch Files
You can now generate an XML patch file that contains only the changes made to a repository. This patch can be then applied to the old (original) version of the repository to create the new version. This is very useful for development-to-production scenarios, and can also be used for Oracle BI Applications customers to upgrade their repository. You can also use the Oracle BI Server XML utilities to create a generic, XML-based representation of the Oracle Business Intelligence repository metadata, on any supported Oracle BI Server operating system.
Enhancements for Multiuser Development and Repository Lifecycle
The following list summarizes improvements and new features for multiuser development and repository lifecycle management:
Object security permissions no longer affect which presentation objects are included in a checked‐out repository.
automatically check consistency and equalize during merges.
no longer have to select repositories one by one and wait for them to load.
of separate repositories.
Repositories now have a repository password that encrypts the repository contents using a strong encryption algorithm. This feature ensures that repository metadata is secure, including data source credentials in connection pool objects. Repositories now have repository-specific passwords that are used to encrypt the repository contents. The repository password is stored in an external credential store when you publish a repository in Fusion Middleware Control so that the Oracle BI Server can retrieve the password to load the repository. Note that a blank repository password is not allowed.
To reduce storage needs, repositories are now stored in a compressed format. Because of this, you may notice that the size of an RPD file opened and saved in this release is significantly smaller than the size of RPD files from previous releases.
The following new and revised SQL functions enable users to create time-series calculations and level-based measures:
starting x units of time and ending y units of time from the current time.
time back to a specified time period. In this release, the time_level argument is optional, and there are additional syntax changes. This function was called PERIODAGO in a previous release.
beginning of a specified time period to the currently displayed time. The syntax for this function has changed in this release. This function was called PERIODTODATE in a previous release.
SELECT_PHYSICAL statements provide the functionality to directly query objects in the Physical layer of the metadata repository and to nest such a statement within a query against the Business Model and Mapping layer or the Presentation layer.
Calculated members are user-defined dimension members whose measure values are calculated at run time. You can define a calculated member within a dimension through a formula that references other members of the same dimension.
Oracle Business Intelligence now supports:
application that is built on top of the ADF Framework.
You can now drag and drop XMLA objects (whole XMLA database or cube tables, at the same time or one by one) into the logical layer to automatically create a consistent business model.
You can now use a standby database with Oracle Business Intelligence. A standby database is used mainly for its high availability and failover functions as a backup for the primary database.
Aggregate Persistence Auto-Indexing
For greater performance, Oracle Business Intelligence now creates indexes and statistics on relational tables when aggregates are persisted.
Pruning Utility to Delete Unwanted Repository Objects
Oracle Business Intelligence now includes a pruning utility to remove unwanted objects from your repository. This utility is especially useful for Oracle BI Applications customers who only need to use a subset of the objects included in the shipped Oracle BI Applications repository.
Ability to Defer Execution of Session Variable Initialization Blocks
To improve session logon time and save resources, administrators can defer execution of selected session variable initialization blocks until the associated session variables are actually used within the session.
Key Terminology Changes
In this release, the following terminology changes have been made:
Major User Interface Improvements
The user interface has undergone major improvements in several areas, including a new Home page and redesigned editors and panes. These improvements are intended to make working with Oracle BI EE easier and more consistent. This guide provides detailed information on working with the various pieces of the user interface. The interface has been enhanced to better serve the needs of users with disabilities. Accessibility Features You can create Analysis from Simple SQL dialog box.
New Column Type: hierarchical column
In previous releases, you included presentation columns and measure columns in analyses. With this release, presentation columns have been renamed to attribute columns and a new column type, hierarchical column, is introduced.
Along with the new column type comes new ways to do the following:
Enhancements to Views
Several of the view types have been enhanced, including those in the following list:
Calculated Items and Groups
You can continue to create calculated items to perform mathematical operations on members. In previous releases, you could create a calculated item for an attribute column. In this release, you can create a calculated item for the members of an attribute column or of a hierarchical column. In this release, you can create a “group” of members to display in a view. The group inherits the aggregation function of the measure column with which it is displayed.
Multiple Subject Areas
In this release, you can work with multiple subject areas. In addition to the primary subject area that you select when you create a new analysis, filter, or dashboard prompt, you can include additional subject areas that are related to the primary subject area with which to work. In addition, you can view metadata information for subject areas, folders, columns, and hierarchy levels.
Enhancements to Formatting
This release includes enhancements to the way that default formatting is handled. Conditional formatting has been enhanced to work with pivot tables and with hierarchical columns.
Enhancements to the Oracle BI Presentation Catalog
The Oracle BI Presentation Catalog is a powerful, underlying storage directory-based system that contains the objects (dashboards, scorecards, prompts, and KPIs for example) that you create. If you use BI Publisher, then the catalog also contains BI Publisher data and objects (data models and schedules, for example). Using the catalog, you can:
In addition to these tasks, administrators can:
Full-Text Search Capability
This release provides a mechanism for searching for objects in the Oracle BI PresentationCatalog that is similar to a full-text search. You can search for objects by various attributes, such as name and description.
In this release, you can create actions that navigate to related content or that invoke operations, functions, or processes in external systems.
In this release, you can create new objects called conditions. Conditions return a single Boolean value that is based on the evaluation of an analysis or of a key performance indicator (KPI).
Enhancements to Agents
In this release, the functionality of agents (previously called iBots) has been enhanced to incorporate support for conditions and for actions.
Key Performance Indicators (KPIs)
In this release, you can create KPIs to represent business measures or metrics (Units Shipped, Manufacturing Costs for example) that you want to monitor, improve, and use to evaluate the performance of the objectives and initiatives that comprise levels of organizational strategy. Use KPIs to perform these tasks:
To proactively respond to changes in KPI performance, you can create the following:
Agents that notify you when a KPI assesses a specific performance state, such as warning.
Oracle Scorecard and Strategy Management
In this release, you can use Oracle Scorecard and Strategy Management to articulate, evaluate (scorecard), and evolve the performance of your organization or key business areas. You can use Oracle Scorecard and Strategy Management to define, depict, and monitor the progress of the strategic goals and requirements (objectives) key to corporate functions, and the tasks and projects (initiatives) that are required to achieve those goals.
Oracle BI Publisher fully integrated
Oracle BI Publisher is a fully integrated member of the Oracle BIEE suite by default. All of the BI Publisher functionality appears seamlessly within the Oracle BIEE application, and all of the reports and related objects are created within Oracle BI EE and saved to the Oracle BI Presentation Catalog. Single sign-on capability is provided. The Release 11g security model has been extended to include additional BI Publisher-specific permissions, such as xmlp_template_designer.
Report-Based Totals Created in Previous Releases Be Upgraded
In previous releases, you had the ability to create report-based totals in table views. Because report-based totals are handled slightly differently in this release, you might notice a difference in totals as follows:
Interactions Created in Views in Previous Releases Be Upgraded
In previous releases of Oracle BI EE, you could set up interactions at the view level, which allowed you to override the interactions that had been set up at the criteria level. In this release, you create all interactions at the criteria level. If you upgrade from a previous release, then all interactions will be moved to the measures at the criteria level and will take effect for all views. For example, suppose that you had created an analysis in a previous release whose criteria was defined as Region, District, Dollars, and Units. In addition, you had created an interaction for a graph view. To upgrade the interaction for this release, the interaction will be moved to both Dollars and Units at the criteria level.
For an in-depth understanding of OBIEE click on:
You liked the article?
Like : 0
Vote for difficulty
Current difficulty (Avg): Medium
TekSlate is the best online training provider in delivering world-class IT skills to individuals and corporates from all parts of the globe. We are proven experts in accumulating every need of an IT skills upgrade aspirant and have delivered excellent services. We aim to bring you all the essentials to learn and master new technologies in the market with our articles, blogs, and videos. Build your career success with us, enhancing most in-demand skills in the market.
Get stories of change makers and innovators from the startup ecosystem in your inbox