Sunday, September 13, 2009

OBIEE security integration with Oracle E-Business Suite

 

Architecture
This article is to discuss the integration of the Oracle E-Business Suite with Oracle BI EE in an Oracle BI Applications environment.  BI Applications for EBS integration solution consists of an application integration from a user interface perspective: single sign on, integrated user interface, action links (Action link screens enable to drill back into the transactional application screen from an Oracle BI request or dashboard) from a data source perspective. The following section discusses how to integrate OBIEE user interface with EBS, leveraging the EBS security framework.

Assumptions
It is assumed the following pre-requisites are fulfilled:
1. Oracle E-Business Suite (11.x) is installed
2. Daily Business Intelligence is installed and is configured
3. All necessary EBS patches (5556799, 5473858) have been applied by the EBS application DBA
3. Client Browser accepts cookies
4. Oracle Business Intelligence Platform (10.1.3.x) is installed in the same network domain

Integration of the User Interface
A user will be able to access the OBIEE environment if this user is administered as an EBS user with the right responsibilities.
The integration of Oracle e-Business Suite (EBS) to Oracle Business Intelligence (OBIEE) consists of the following steps:
1. Specification of OBIEE base URL in EBS
2. Specify the authentication part of the integration in the instanceconfig.xml
3. Modify the connection pools in the repository
4. Specify Static Repository variables

OBIEE URL in EBS
The EBS administration screen for managing profile options (System Administrator > Profile > System) allows to specify the hostname and location of the web application to integrate with.  The URL will be interpreted by the OBIEE Presentation Server. Set the value of the following Profile Option Name,

"FND: Oracle Business Intelligence Suite EE base URL" = http://[hostname.domain_name]:[port_number] (No slash is required at the end of this URL)


Authentication Integration

The authentication integration for OBIEE is via http cookies combined with a URL. The cookie is also used for the action link integration (drill back to EBS screen from an OBIEE request). This integration is specified in the instanceconfig.xml. The integration and authentication steps are:
1. Login into EBS
2. When clicking on an OBIEE link in the EBS client browser, EBS builds up an URL starting with the OBIEE base URL specified in the previous step. This base URL is extended with:
[base_url]/analytics/saw.dll?[module_invoked]&acf=
Here [module_invoked] is for example Dashboard or Answers and [acf_id] is a 10 digit number generated by EBS. This number is used to retrieve other authentication and authorization information from the EBS session by the Oracle BI Server
3. EBS sends a cookie to the browser, most likely the cookie file name is equal to the ICX base domain.
Tip: Using Mozilla Firefox browser allows you to find the cookie named value pair you are looking for.
This cookie named value pair which indicates the user ICX session id. The name of this value pair is very important and needs to be captured for the instanceconfig.xml, i.e. the configuration file of the Presentation Server. The value is used for the actual authentication in OBIEE.
4. By the instanceconfig.xml for OBIEE, the OBIEE presentation server is programmed for external authentication (ExternalLogon enabled=true in the [Auth] tag area).
In order to complete the authentication the OBIEE session will try to resolve two parameters:
- NQ_SESSION.ICX_SESSION_COOKIE
- NQ_SESSION.ACF
The first is resolved from a cookie with the name specified in the instanceconfig.xml configuration file by the nameInSource attribute of the [Param] tag. The attribute value is the name of the cookie. The value of the cookie is the ICX session cookie ID stored in the OBIEE Server parameter NQ_SESSION.ICX_SESSION_COOKIE and is passed to the OBIEE Server. The second parameter is resolved from the URL by [acf_id].
The correct specification of the instanceconfig.xml [Auth] tag is as follows (after the ParamList tag):
Param name="NQ_SESSION.ICX_SESSION_COOKIE"
source="cookie"
nameInSource="[cookie name]"
and
Param name="NQ_SESSION.ACF"
source="url"
nameInSource="acf"
After the changes have been applied, the OBIEE Presentation Server needs to be rebooted.


Repository Configurations
Two authentication initialization blocks populating repository session variables are most important for the integration of EBS with OBIEE. Assume the name for these initialization blocks are:
1. EBS Security Context (old version- FndGetSecContext )
2. FndGetResp (Authorization)


The first initialization block, “EBS Security Context”, populates the following variables:
RESP_ID, RESP_APPL_ID, RESP_APPL_ID, RESP_APPL_ID, USER_ID, EMPLOYEE_ID, USER
using a database query:
SELECT FND_GLOBAL.RESP_ID
, FND_GLOBAL.RESP_APPL_ID
, FND_GLOBAL.SECURITY_GROUP_ID
, FND_GLOBAL.RESP_NAME
, FND_GLOBAL.USER_ID
, FND_GLOBAL.EMPLOYEE_ID
, FND_GLOBAL.USER_NAME
FROM DUAL
within a connection pool, dedicated for the authentication purpose:
EBS_Authentication_Pool
Of course this initialization block can be extended to populate other variables than the ones mentioned in this example. The connection pool uses a static user name and password to connect to the EBS OLTP database, referenced by the static repository variables, e.g.:
- Static_USER_ID
- Static_DSN_OLTP
When connection is established, the first thing the OBIEE Server will invoke is the following package (stored procedure) call:
call /* valueof(NQ_SESSION.ACF) */
APP_SESSION.validate_icx_session('valueof(NQ_SESSION.ICX_SESSION_COOKIE)')
The value of the parameter NQ_SESSION.ICX_SESSION_COOKIE is passed through by the presentation server, obtained from the EBS session cookie.
If this package call fails the authentication fails. When the call is successful, the authentication session variables are populated, after which the next init block is executed for Authorization.

FndGetResp. This initialization block will query the responsibilities from the EBS OLTP database:
SELECT RESPONSIBILITY_KEY
FROM FND_RESPONSIBILITY
WHERE RESPONSIBILITY_ID = 'valueof(NQ_SESSION.RESP_ID)'
This query will populate the (single valued) GROUP repository variable and assign the user to one of the preconfigured repository groups and web catalog WEBGROUPS. Based on these groups the user will have access to role-specific content.

Because of the tight and enforced EBS security integration, the OBIEE repository is only accessible using EBS: an EBS session ID must exist in the EBS database in order to be authenticated. Each database query to the EBS database will check whether the session ID still exists. If not Authentication, Authorization or the Query fails.

Wednesday, July 15, 2009

Using Oracle BI Office in OBIEE for Microsoft Excel and Powerpoint

Installing the BI Office Client

To install the BI Office Client:

  1. Log in to Oracle BI Answers or Oracle BI Interactive Dashboards with your Oracle BI EE user credentials.

  2. Select the More Products link and then select Download Oracle BI for Microsoft Office.

    This image is described in the surrounding text.

  3. A dialog box prompts you to save or run OracleBIOffice.exe. Save the file to your local directory.

4.Close the Excel or PowerPoint applications on your system, if open. Navigate to the saved location and double-click OracleBIOffice.exe.

InstallShield Wizard appears.
Note: Microsoft .Net Framework 2.0 is required for the BI Office client. If it is not installed on your computer, you are prompted to exit and install Microsoft .Net Framework 2.0 from the Microsoft Web site.

When the Welcome page appears, click Next.

5. Select the installation type. Typical performs an installation for both Excel and PowerPoint Add-Ins to C:\Program Files\Oracle\BIOffice. Custom enables you to select the install directory and choose the components to install. Select Typical as the installation type, and click Next.

6. Review the setup information and then click Next.

7.When the InstallShield Wizard completes, click Finish.

When Oracle BI EE was installed on your computer, the BI Office Server was installed automatically. The installer performs other configuration tasks such as the following:

Deploying the bioffice.ear file

Updating the instanceconfig.xml file with the location of the OracleBIOffice.exe client

Copying the OracleBIOffice.exe file to the location where Presentation Services is running, which makes the client installation available for download from the More Products menu (as performed in step 1)

Initializing values in the BI Office configuration file (bioffice.xml file)

The following image depicts a sample bioffice.xml file, which contains critical information used by the client to connect to Presentation Services. (Observe the highlighted line in the file, which defines the URL for the Presentation Services.) You create the connection in the BI Office client in the next step.

Note: If any of the above configuration tasks were not performed due to some reason, you can look up the documentation available here to perform these installation and configuration tasks manually.

9. Configure the BI Office client to associate the BI Office Add-Ins with Presentation Services:

Enter the following information in the Connection Detail dialog box:

Server Name: This is the name that you give to the BI Office Server connection. Enter localhost as the name.

BI Office Server: This is the BI Office Server URL. You can enter localhost because the BI Office Server is installed on your local machine.

Port: For a Java 2, Enterprise Edition (J2EE) deployment, the BI Office Server port is 9704. The default value is 80; change it to 9704.

Application Name: The default value is bioffice. When you deploy the BI Office Server application file to OC4J or to your supported J2EE container, you can provide any name for the application. In this case, the default value of bioffice was accepted.

Click Test Connection.

Note: If you have given a different name for the application than the default value of bioffice, enter the name of the application accordingly while creating the connection. You can also edit the connection details after it is created, select the connection from Oracle BI > Preferences, and then click Edit.

Using BI Office with Excel and PowerPoint

Now that you have successfully installed the BI Office client and configured the connections, you are ready to start using the BI Office Add-Ins. In this topic, you are guided to use the features in the BI Office Add-Ins that enable you to analyze and deploy Business Intelligence reports easily in Microsoft Office applications, Excel and PowerPoint.

Some key features provided by BI Office are listed here:

You can copy views from Answers and Interactive Dashboard pages and paste them into Excel and PowerPoint documents by using the Paste feature of BI Office Add-Ins. Copied views are pasted as Office documents (Excel or PowerPoint tables and charts). This functionality also extends to copying compound views from Answers and Dashboards. Compound views copied from Answers or Dashboards are pasted into Microsoft Office documents as native Microsoft Office tables and charts.

For every request, the flat data view provides the entire data set for the original request in a simple tabular format. This view is more suitable for use when users want to obtain only the data and then use the Excel functionality to perform further analysis on that data.

The table view displays results in a tabular format. Users can navigate through the results, add totals, customize headings, and change the formula or aggregation rule for a column.

The pivot table view, available in the BI Office Excel Add-In, presents data from BI Requests with page items as well as a section-based layout if these sections were defined in the BI pivot table view for the request in Answers.

A BI Presentation Catalog browser is provided in Excel and PowerPoint to browse requests (both user created and shared).

Support is provided for prompts defined in the BI request.

If a view selected for insertion has multiple levels from one or more dimensions, you can choose to limit the data for each dimension by deselecting the levels from a level-selection dialog box. You can also edit the prompts and levels after the view is inserted .

You can insert table and chart views into PowerPoint presentations as PowerPoint tables and charts (subject to the limitations of PowerPoint).

You can insert chart views as images in Excel spreadsheets and PowerPoint presentations that can be refreshed.

You can insert chart views as high-quality Flash objects in PowerPoint presentations that can be refreshed.

For BI chart views inserted as native Excel or PowerPoint charts, you can change the chart type and apply other formatting changes by using Excel and PowerPoint charting capabilities. These changes are preserved during refreshes.

You can define Excel-specific conditional formats to data from BI views. These conditional formats can be preserved during data refreshes.

You can add gauge and funnel views in Excel and PowerPoint for better analysis of the reports.

You can secure a slide or worksheet, or you can secure the entire presentation or workbook. When you secure a particular object in Excel or Powerpoint, all BI views on that object—that is, slide, worksheet, presentation, or workbook are secured. Users must authenticate themselves before they can refresh and view this secured BI data. Secure communication is handled through SSL.

Using BI Office with Excel

In this topic, you work with basic views such as table, chart, and pivot table. This topic shows you how to log in to BI Office in Excel, locate a table and insert the data as a list (flat data) into Excel (so that you can manipulate the data by using Excel capabilities), copy a chart from the Presentation Catalog, switch between Excel and Answers to modify the chart, and copy and paste this chart into Excel. You also insert the pivot table view into Excel.

1. To use BI Office Add-Ins, you must log in. Select Start > All Programs> Microsoft Office > Microsoft Excel 2007 to launch Excel.

From the Oracle BI menu on the Ribbon, select Login. (Observe the Oracle BI–specific options added in the toolbar. Note that these menu options are added in Excel during the installation of BI Office Add-Ins.)

2. The Login dialog box appears. Ensure that the connection you created before (localhost) is selected from the Connection drop-down box. Enter Administrator in both the User ID and Password fields, accept the default for the remaining fields, and click Login.

You are now connected to Presentation Services.

3. The Presentation Catalog appears in Oracle B I Task Pane on the right.

To view catalog details, click the plus sign to expand the Shared and Paint Demo folders.

Also note that the Presentation Catalog can be hidden or displayed by clicking the Oracle BI Catalog icon on the toolbar.

4.Click the plus sign () to expand Brand Analysis.

Click the plus sign () to expand the Sales by Brand for Current Year Trends request. (Observe the listed views available for this request.)

The following table identifies the types of request views that are supported, and can be inserted (or copied and pasted) into Excel from the Presentation Catalog:

Table view

Enables you to select levels before insertion into Excel, allowing you to limit the data. You can add Excel formatting to the inserted view. Use this view to see data in the grouped format defined in the Answers request.

Pivot table view

Offers the features of the table view and maintains features defined in Answers (such as page item lists and group sectioning)

Chart view

Inserts charts as defined in Answers

List view (Insert as List)

Available for all table views. This inserts the entire data set for the original request. Use this view when you want to perform filtering, pivoting, charting, and other manipulations in Excel. (In the previous version of BI Office, this was available as flat data view).

Funnel View
Displays results as a three-dimensional chart that represents target and actual values by using volume, level, and color. It is useful for depicting target values that decline over time, such as a sales pipeline.

Gauge View
Shows results as gauges, such as dial, bar, and bulb-style gauges. (Funnel and gauge are two new views, which are introduced in BI Office 10.1.3.4.0.)

Compound view
Provides an assembly of different views on a dashboard. This view must be composed of supported view types (those listed above) to be fully inserted. If the compound view includes unsupported views, only those from this list of views will be pasted into Excel or PowerPoint.

Right-click Table and select Insert as List from the shortcut menu. The Edit Prompts and Levels dialog box appears. Accept the default options and click Insert.

Note: The Edit View option launches Answers in your browser, which in turn enables you to modify the request.

The entire data set for the original request appears in the worksheet area. (Note that the worksheet is named tableView). All Excel capabilities are available for use with this data.

5. Click any cell in the data area. Pivot icons () are added to each column heading. These pivot icons allow you to sort the data, or filter unwanted data (as shown in the screenshots below).

7. In the Presentation Catalog that is already open in the right pane, right-click Chart under the Sales by Brand for Current Year Trends request, and select Insert from the shortcut menu.

Note: The "Insert as Image" option enables you to add the chart as a static image to Excel.

The 3D Line chart from the request appears in the newly added worksheet.

8. Double-click the chart to view data associated with the chart values.

Setting Properties in the bioffice.xml Configuration File

This section describes the properties that you can configure in the bioffice.xml file.

Following is a sample bioffice.xml file:

<bioffice>
<!-- log -->
<!-- LogDir. Default is [O4CJ dir]\j2ee\home\applications\bioffice\bioffice\WEB-INF\log -->
<!-- <property name="LogDir">D:\BIOffice\Server\log\</property> -->
<!-- LogLevel Never = 1; Error = 2; Warning = 3; Msg = 4; Debug = 5; -->
<property name="LogLevel" type="int">3</property>
<!-- saw -->
<property name="SawBaseURL">http://localhost/analytics/saw.dll</property>
<!-- Does SAW use SSO (Single Sign-On): yes = 1; no = 0; -->
<property name="SawUseSSO" type="int">0</property>
<!-- Specifies the maximum number of rows to be returned by SAW executeXMLQuery or fetchNext method. -->
<property name="SawMaxRowsPerPage" type="int">5000</property>
<!-- Parse hyperlink column: turn on = 1; turn off = 0; -->
<property name="SawParseHyperLink" type="int">1</property>
<!-- Parse percentage column: turn on = 1; turn off = 0; -->
<property name="SawParsePercentageColumn" type="int">1</property>
<!-- Fetch fresh data: turn on = 1; turn off = 0; -->
<!-- Turn on will make SAW re-submits the query to refresh data, in stead of reading data from cache. -->
<property name="SawFetchFreshData" type="int">0</property>
</bioffice>

Setting Up an SSO-Enabled Oracle BI Presentation Server for BI Office

Oracle BI Office currently cannot be fully integrated with SSO. If your Oracle BI Enterprise Edition implementation is SSO-enabled, users can use their SSO credentials from the Microsoft Excel or PowerPoint add-in to log in to the Oracle BI Office system. However, the following options from the client add-in insert menu are not supported:
  • Edit View

  • Insert as Image
  • Insert as Flash

To enable the integration of BI Office with SSO-enabled Oracle BI, you must deploy a separate SAW bridge application (analytics.ear) and grant trusted IP address (where BI Office is installed) access privilege to the new SAW bridge without going through SSO authentication. You must configure the BI Office server to send Web service requests to this SAW bridge that bypasses SSO. Depending on the SSO server type, the configuration may differ. Following is an example of how to integrate BI Office with Oracle SSO-enabled Oracle BI:

  1. On the same machine where BI Presentation Services Plug-in has been deployed, deploy another Presentation Services Plug-in using the file analytics.ear:

    Locate analytics.ear in the directory OracleBI_HOME/web.
  2. Name the new Plug-in "analyticsSOAP". Make the same modifications to the web.xml file for this analyticsSOAP servlet that were made to the web.xml file for the default "analytics" servlet.

  3. Make the following modification to the file mod_osso.conf to open analyticsSOAP to requests from the BI Office server:

    (The mod_osso.conf is located in the directory Oracle_HOME/Apache/Apache/conf.)
    <Location /analyticsSOAP>
    Require valid-user
    AuthType Basic
    Allow from <IP address of BI Office server>
    Satisfy Any
    </Location>
    where

    <IP address of BI Office Server> is the IP address of the BI Office server, for example: 10.155.324.7

  4. Locate the Office Server configuration file (bioffice.xml). The configuration file bioffice.xml can be found in the directory:

    OAS_HOME\j2ee\home\applications\bioffice\bioffice\WEB-INF

  5. Update the following properties:

    • "SawBaseURL" to point to the new analyticsSOAP deployed in the previous steps
    • "SawUseSSO" to indicate that you have enabled SSO for BI Office and Presentation Services. Set the value to "1". This setting suppresses the unsupported options from the client add-in insert menu.

    Example:

    <property name="SawBaseURL">http://localhost:port/analyticsSOAP/saw.dll</property>
    <!-- Does SAW use SSO (Single Sign-On): yes = 1; no = 0; -->
    <property name="SawUseSSO" type="int">1</property>


Monday, June 15, 2009

Security for hierarchical dimensions

Using IndexCol Function to Handle hierarchy Level security

IndexCol can use external information to return the appropriate column for the logged-in user to see. The Oracle BI Server handles this function in the following ways:

  • ODBC Procedures. NQSGetLevelDrillability and NQSGenerateDrillDownQuery return the context-specific drill-down information based on the expression translated from IndexCol. This applies to both IndexCol expressions specified in the logical SQL query and IndexCol expressions specified in a derived logical column.
  • Query Log and cache. The logical SQL with IndexCol function appears in the SQL string in the query log. But the logical request will not show the IndexCol function because Oracle BI Server will translate IndexCol to one of the expressions in its expression list in the logical request generator.

    NOTE: The query cache will use the resulting translated expression for cache hit detection.

  • Usage Tracking. Usage tracking will insert the logical SQL query string with the IndexCol function.
  • Security. As long as the user has the privileges to access the column(s) in the expression translated from IndexCol, then the query will execute.

    When the first argument to IndexCol is a session variable and if a default expression is expected to be returned even if the init block fails, then the Oracle BI Administrator should set a default value for the session variable. Otherwise, the query will fail because the session variable has no value definition.

Syntax

IndexCol( INTEGER literal, expr1, expr2, ... )

The IndexCol function takes in an integer literal value as its first argument, followed by a variable length expression list and translates to a single expression from the expression list. The literal value is the 0-based index of the expression in the expression list to translate to.

Consider the following expression:

IndexCol( INTEGER literal, expr1, expr2, ... )

If the literal value is 0, the above expression is the same as expr1. If the literal value is 1, then the value is the same as expr2, and so on.

NOTE: The primary use case for IndexCol is for the first argument to contain a session variable. Specifying a constant literal would result in IndexCol always choosing the same expression.

Example With Hierarchy Levels

Company ABC has a geography dimension with the hierarchy Country of State, City. The CEO can access the Country level down to the City level, and the sales manager can access the State and City levels, and the sales people can only access the City level. Create the table

CREATE TABLE HIERARCHY_LEVEL
(
USER_NAME VARCHAR2(30 BYTE),
TITLE VARCHAR2(30 BYTE),
GEO_LEVEL NUMBER(1) DEFAULT 5
)

GEO LEVEL on Oracle must be NUMBER(1) as data type to become a INT in OBIEE. Samples values are given below.

Table Example With Hierarchy Level






























USER_NAME


TITLE


GEO LEVEL

BillCEO0
BruceVP1
MikeManager2
KaleManager2


The following steps illustrate one way to create a single query where each user sees the top level to which they have access:

Create the OBIEE user

Create the OBIEE users with the same user names.

The Oracle BI Administrator creates a new session variable GEOGRAPHY_LEVEL that is populated by the initialization block: SELECT GEO_LEVEL from T where USER_NAME = ':USER'.

Create the session variable
SELECT GEO_LEVEL FROM HIERARCHY_LEVEL WHERE USER_NAME = ':USER'

This assume that the Oracle BI Server instance has the same user names.

Create a column formula
IndexCol( VALUEOF( NQ_SESSION.GEOGRAPHY_LEVEL ), Country, State, City )

With the amount sold.

Using SELECT IndexCol( VALUEOF( NQ_SESSION.GEOGRAPHY_LEVEL ), Country, State, City ), Revenue from Sales, the following occurs:

  • Bill logs in and IndexCol translates to the Country column because the GEOGRAPHY_LEVEL session variable is 0. He will get the same result and be able to drill down on Country to State as if he had used SELECT Country, Revenue from Sale.
  • Bruce logs in and IndexCol translates to the State column because the GEOGRAPHY_LEVEL session variable for Jackson is 1. He will get the same result and be able to drill down on State to City as if he had used SELECT State, Revenue from Sales.
  • Mike logs in and IndexCol translates to the City column because the GEOGRAPHY_LEVEL session variable for Mike is 2. He will get the same result and won't be able to drill down on City as if he had used SELECT City, Revenue from Sales.

Reference

Oracle Documentation

Tuesday, June 9, 2009

Calendars in Oracle BI Applications 7.9.6

Overview of Calendars in Oracle BI Applications

Oracle Business Intelligence Applications Version 7.9.6 supports different calendar formats:

  • Enterprise (Global) - cross functional reporting calendar, which can be fiscal or gregorian.

  • Fiscal - accounting or financial calendar.

  • Gregorian - regular calendar that starts on January 1st and ends on December 31st.

  • 13 Period - a calendar is which each year is comprised of 13 periods.

  • 4-4-5 - each year is composed of twelve periods of either four weeks of 28 days or five weeks of 35 days.

 

Calendar Categories

Calendars are categorized into two types:

OLTP sourced (also known as Source Calendars) - OLTP sourced calendars are calendars that are defined in ERP sources and brought into the warehouse via ETL maps and standard DAC loads.

Warehouse generated (also known as Generated Calendars) - Generated calendars are fiscal calendars generated in the warehouse based on configuration files.

Both source calendars and generated calendars are stored in the Multiple Fiscal Calendar (known as MCAL) tables. MCAL tables have the prefix W_MCAL.

 

Calendar Tables in Oracle Business Analytics Warehouse

The tables used for Time Dimension calendars can be categorized based on the calendar types as below -

Gregorian Calendar Tables

  • W_WEEK_D

  • W_MONTH_D

  • W_QTR_D

  • W_YEAR_D

  • W_DAY_D

Fiscal Calendar Tables

  • W_MCAL_WEEK_D

  • W_MCAL_PERIOD_D

  • W_MCAL_QTR_D

  • W_MCAL_YEAR_D

Enterprise Calendar Tables

  • W_ENT_WEEK_D

  • W_ENT_PERIOD_D

  • W_ENT_QTR_D

  • W_ENT_YEAR_D

 

W_DAY_D is the base table that represents the time dimension in the Oracle Business Analytics Warehouse. This table needs to be populated as a prerequisite for the multiple fiscal calendar tables. If W_DAY_D is not populated, then the fiscal calendar tables will not be populated.

There are two parameters $$START_DATE and $$END_DATE for the task SIL_DayDimension that need to be setup to load the calendar data in W_DAY_D. The SIL mappings use standard time functions to create records for each calendar day falling within the boundary defined by these two parameters. Once the records are created in W_DAY_D, the aggregate calendar tables are loaded by their respective SIL mapping. Then the fiscal calendar tables (known as MCAL tables) are populated.

 

Configuring Enterprise Calendars

An Enterprise calendar (or reporting calendar) enables cross subject area analysis. Enterprise calendar tables have W_ENT prefix. Enterprise calendars can be set to one of the OLTP sourced fiscal calendars or to one of the warehouse generated calendars. This can be done by setting the following source system parameters at the DAC container level:

  • $$GBL_CALENDAR_ID

  • $$GBL_DATSOURCE_NUM_ID

Scenario 1 Using an Oracle EBS fiscal calendar as the Enterprise calendar

Source System DAC Parameters for Oracle EBS Enterprise Calendars:

  • GBL_CALENDAR_ID: This parameter is used to select the Enterprise Calendar. It should be the MCAL_CAL_NAME~MCAL_PERIOD_TYPE for Non-Generated Calendars. For example GBL_CALENDAR_ID will be 'Accounting~41', if the Enterprise Calendar id='Accounting' and the calendar period_type='41'.

  • GBL_DATASOURCE_NUM_ID: If Enterprise Calendar is not a Generated Calendar: It should be the DATASOURCE_NUM_ID of the source system from where the Calendar definition is taken. For example, if you have two data sources as PeopleSoft and Oracle, and the Global Calendar is from an Oracle data source, then this parameter value should specify an Oracle data source.

Scenario 2 Using a warehouse generated calendar as the Enterprise calendar

Source System DAC Parameters for Generated Enterprise Calendars:

  • GBL_CALENDAR_ID: Should be the CALENDAR_ID of the Generated Calendar (4-4-5 or 13 period type of Calendars). By default the 4-4-5 calendar has a CALENDAR_ID of '10000' and the 13-period calendar has a CALENDAR_ID of '10001'.

  • GBL_DATASOURCE_NUM_ID: If Global Calendar is Generated Calendar: It should be the DATASOURCE_NUM_ID value of the OLAP (Data warehouse)

Scenario 3 Using a fiscal calendar loaded via the Universal Adapter as the Enterprise calendar

Source System DAC Parameters for Universal Enterprise Calendars:

  • GBL_CALENDAR_ID: Should be the INTEGRATION_ID from the file_mcal_cal_d.csv file of the particular calendar which is defined as the Global Calendar.

  • GBL_DATASOURCE_NUM_ID: If Global Calendar is not a Generated Calendars, then it should be the DATASOURCE_NUM_ID of the source system from where the Calendar definition is taken. If it is defined in the file_mcal_period_ds.csv file, then that value should be taken, or else as defined in the DAC for Universal adapter.

 

Generated Calendars

The following Task Level DAC Parameters are needed for Generated Calendars.

  • $$13P_CALENDAR_ID  - Task: SIL_TimeDimension_MCalWeek13Period. Required if you want to populate the 13 period type of calendar in your Data Warehouse. The value should be the CALENDAR_ID as defined in the W_MCAL_CONFIG_G table for the 13 period type of calendar.

    $$445P_CALENDAR_ID  -  Task: SIL_TimeDimension_MCalWeek445. Required if you want to populate the 445 period type of calendar in your Data Warehouse. The value should be the CALENDAR_ID as defined in the W_MCAL_CONFIG_G table for the 445 period type of calendar.

  • If there is a week (starting on a Sunday and ending on a Saturday) that falls across two calendar years, the week is counted in both years. For example, the week that starts on 12/30/2007 will be counted in both 2007 and 2008. In 2007, the week start date will 12/30/2007 and the end date will be 12/31/2007. In 2008, this will be the first week with start date as 01/01/2008 and end date as 01/05/2008.

  • W_DAY_D stores 31 records for each month regardless of whether the month actually has 31 days. If the month has a fewer number of days, there will be records with null values in the Calendar Date and Day Date columns. These extra records are loaded for the calculation of Period Ago metrics in the Oracle BI Repository and will not affect the ETL or reporting.

  • There are some attributes on the W_DAY_D table that are not mapped in the Physical layer of the Oracle BI Repository. Therefore, before creating any new attribute in the repository, check whether the attribute is already available in the Physical layer and if it can be mapped directly.

  • If your fiscal calendar contains more than 12 months, the extra months will be assigned a value of 0 for the fiscal quarter. The same holds for the fiscal trimester and fiscal half values.

     

    How to Include and Exclude Multiple Calendar Support for Subject Areas in DAC

    The Multi-Calendar tasks are included in the TASK_GROUP_Load_DayDimension in the DAC.

    When the TASK_GROUP_Load_DayDimension task group is added to any Subject Area, the Multi-Calendar tasks are not extracted by default. You need to add a Configuration tag to the Subject area before you run the ETL process to pull these tasks into the ETL process, as described in the following steps.

    To include and exclude Multiple Calendar support for Subject Areas:

    1. In DAC, display the Design view, and select the appropriate container.

    2. Display the Subject Area tab in the upper pane and select the Subject Area to which you want to add Multi-calendar tasks.

    3. Display the Configuration Tags tab in the lower pane.

    4. Click Add/Remove to display the Choose Subject Area Configuration Tags dialog.

    5. Select the configuration tag named 'Multiple Calendar Support' in the left pane and click Add, then OK.

    6. In the upper pane, click Assemble.

    7. Display the Execute view.

    8. Display the Execution Plans tab.

    9. Select the Execution Plan that includes the Subject Area to which you added the configuration tag named 'Multiple Calendar Support'.

    10. Run this Execution Plan.

     

    How to set up a 13 Period calendar

    To set up a 13 Period calendar:

    1. In the DAC, display the Design tab, and select an appropriate adapter.

    2. Display the Source System Parameters tab.

    3. Set the value of $$GBL_CALENDAR_ID and $$GBL_DATSOURCE_NUM_ID as follows:

      • GBL_CALENDAR_ID: Should be the CALENDAR_ID of the Generated Calendar (4-4-5 or 13 period type of Calendars). By default the 4-4-5 calendar has a CALENDAR_ID of '10000' and the 13-period calendar has a CALENDAR_ID of '10001'.

      • GBL_DATASOURCE_NUM_ID: If Global Calendar is Generated Calendar: Should be the DATASOURCE_NUM_ID value of the OLAP (Data warehouse).

    4. Using a text editor, edit the values in file_mmcal_config_g.csv.

    5. In DAC, set the value of 13P_CALENDAR_ID to 10001.

      Note: The task SIL_TimeDImension_McalWeek13Period will run as part of the execution plan for your subject area. Please note that is no separate subject are for common dimensions. They are included in the core subject areas.

     

    How to set up a 4-4-5 calendar

    To set up a 4-4-5 calendar:

    1. In the DAC, display the Design tab, and select an appropriate adapter.

    2. Display the Source System Parameters tab.

    3. Set the value of $$GBL_CALENDAR_ID and $$GBL_DATSOURCE_NUM_ID as follows:

      • GBL_CALENDAR_ID: Should be the CALENDAR_ID of the Generated Calendar (4-4-5 or 13 period type of Calendars). By default the 4-4-5 calendar has a CALENDAR_ID of '10000' and the 13-period calendar has a CALENDAR_ID of '10001'.

      • GBL_DATASOURCE_NUM_ID: If Global Calendar is Generated Calendar: Should be the DATASOURCE_NUM_ID value of the OLAP (Data warehouse)

    4. Using a text editor, edit the values in file_mcal_config_g.csv.

    5. In DAC, set the value of 445P_CALENDAR_ID to 10000.

      Note: The task SIL_TimeDimension_McalWeek445 will run as part of the execution plan for your subject area. Please note that is no separate subject are for common dimensions. They are included in the core subject areas.

  • Sunday, May 10, 2009

    BI Publisher Overview

    Oracle Business Intelligence Publisher is a reporting and publishing application that
    enables you to extract data from multiple data sources, create a template to lay out the
    data in a report, and publish the report to numerous output formats. BI Publisher also
    enables you to schedule reports and deliver the reports to any delivery channel
    required by your business.

    Administering BI Publisher requires setting up and maintaining the following system
    components:
    • BI Publisher security
    • Data source connections
    • Integrations with other Oracle products
    • Report delivery options
    • Runtime configuration settings
    • BI Publisher Scheduler configurations
    • System maintenance options

    Integration

    Oracle BI Publisher enables you to integrate with the following products:

    • Oracle BI Presentation Services - This integration enables you to use Oracle BI Answers requests as data sources for your reports.

    • Oracle BI Discoverer - This integration enables you to use Oracle BI Discoverer Worksheets as data sources for your reports.

    • Hyperion Workspace and Shared Services - This integration enables you to access BI Publisher from within the Oracle Enterprise Performance Management Workspace.

    • Oracle Smart Space Client - This integration enables you to set up a link to the Oracle Smart Space download page. This will enable all BI Publisher users to easily access the Oracle Smart Space client download page from their BI Publisher session.

    • Oracle E-Business Suite – This integration can be done by uploading a DBC file to recognize your Oracle E-Business Suite users.

    • Oracle BI Server – This can be integrated by setting up the BI Publisher roles in your BI Server Administration tool then configure BI Publisher to integrate with it.


    Technorati Tags: Oracle E-Business Suite,BI Publisher

    Integrating with Oracle E-Business Suite

    1. In the Oracle E-Business Suite, log in as a System Administrator and create the
    following responsibilities to correspond to the BI Publisher functional roles:
    • XMLP_ADMIN – this is the administrator role for the BI Publisher server.
    • XMLP_DEVELOPER – allows users to build reports in the system.

    • XMLP_SCHEDULER – allows users to schedule reports.
    • XMLP_ANALYZER_EXCEL – allows users to use the Excel analysis feature.
    • XMLP_ANALYZER_ONLINE – allows users to use the online analysis feature.
    • XMLP_TEMPLATE_DESIGNER - allows users to connect to the BI Publisher
    server from the Template Builder and to upload and download templates.
    2. Add the new BI Publisher responsibilities to the appropriate Users.

    3. Log in to BI Publisher Enterprise. From the Admin tab, select Security Configuration.
    4. In the Security Model section of the page, select Oracle E-Business Suite from the list.
    5. Load your dbc file from the E-Business Suite instance. This is typically located
    under the $FND_SECURE directory. If you do not have access to this file, contact
    your E-Business Suite system administrator. This file specifies how BI Publisher
    should access the E-Business Suite instance.
    6. It is recommended that you create a local super user for the system to allow you to
    access the Administrator pages once the changes take effect. Select the Enable Local
    Superuser check box and enter a username and password for the user under the
    Local Superuser section of the Security Configuration tab.
    7. Restart the BI Publisher server for the security changes to take effect.
    Once you restart the system, all your E-Business Suite responsibilities will be visible as
    roles in the BI Publisher security center. Add folders to the E-Business Suite roles.

    Integrating with Oracle BI Server Security

    This is done by defining BI Publisher functional roles within the Oracle BI Server
    Administration tool, assign users to these groups, and then specify Oracle BI Security as
    your security model in the BI Publisher Admin interface.

    1. In the BI Server Administration tool, create the following groups to correspond to
    the BI Publisher functional roles:
    • XMLP_ADMIN – this is the administrator role for the BI Publisher server.
    • XMLP_DEVELOPER – allows users to build reports in the system.
    • XMLP_SCHEDULER – allows users to schedule reports.
    • XMLP_ANALYZER_EXCEL – allows users to use the Excel analysis feature.
    • XMLP_ANALYZER_ONLINE – allows users to use the online analysis feature.
    • XMLP_TEMPLATE_DESIGNER - allows users to connect to the BI Publisher
    server from the Template Builder and to upload and download templates.
    2. Add the appropriate users to the BI Publisher groups in the BI Server Administration tool.
    3. In the BI Publisher Enterprise application, log in with Administration privileges. From the Admin tab select Security Configuration.
    4. In the Security Model section of the page, select Oracle BI Server from the list. Provide the following connection information for the BI Server:
    • JDBC Connection String - example: jdbc:oraclebi://host:port/

    • Administrator Username and Administrator Password
    • Database Driver Class - example: oracle.bi.jdbc.AnaJdbcDriver
    5. It is recommended that you create a local super user for the system to allow you to
    access the Administrator pages once the changes take effect. Select the Enable Local
    Superuser check box and enter a username and password for the user under the
    Local Superuser section of the Security Configuration tab.
    6. Restart the BI Publisher server for the security changes to take effect.


    Logging into Business Intelligence Publisher

    1. Navigate to the URL provided by your system administrator. The URL is of the format http://hostname:port/xmlpserver/
    2. Select the language you prefer for the user interface.
    3. Enter your credentials to log in to BI Publisher.
    4. Select Accessibility Mode if you wish to render the Reports home page in an
    accessible tree structure.
    5. Select Sign In.

    image

    Saturday, May 2, 2009

    Oracle BI Applications 7.9.6 release


    Oracle BI Applications 7.9.6
    :

    Oracle Business Intelligence Applications are built on Oracle Business Intelligence Suite Enterprise Edition, a comprehensive next-generation BI and analytics platform.

    Oracle Business Intelligence Applications includes the following:

    • Oracle Financial Analytics
    • Oracle Human Resources Analytics
    • Oracle Supply Chain and Order Management Analytics
    • Oracle Procurement and Spend Analytics
    • Oracle Project Analytics
    • Oracle Sales Analytics
    • Oracle Service Analytics
    • Oracle Contact Center Telephony Analytics
    • Oracle Marketing Analytics
    • Oracle Loyalty Analytics
    • Oracle Price Analytics
    • Oracle Pharma Marketing Analytics
    • Oracle Pharma Sales Analytics

    Oracle BI DAC (Data Warehouse Administration Console)

    In this release DAC is a stand alone application and can reside in a separate home and doesn't need to be setup within OraceBI. The functionality and UI is similar as with earlier release, but the authentication has been changed. The login page now needs an authentication file that needs to be setup and stored for the datawarehouse instance.

    Wednesday, April 15, 2009

    Authentication In OBIEE

    The Oracle BI Enterprise Edition (OBIEE) supports the following authentication types:

    Built in BI Server authentication

    BI Server authentication stores credentials and other attributes in the repository file
    • Good for testing and small installations but if users change often, might be a problem
    • Users can not be shared across multiple repositories
    • If a user exists here no other logon procedures will be used
    • Users can be imported from an LDAP server and refreshed periodically
    • Maintaining your passwords in many applications is also a difficult.

    image

    Database users Authentication

    • Create named database users in the repository matching exactly users in the database
    • Assign these users to groups if needed and grant permissions
    • Specify that database authentication will be used, in the NQSConfig.ini file
    • Set up a connection pool in the physical layer of the repository without shared login

    image

    NQSConfig.ini configuration changes
    #----- 1 -----
    #AUTHENTICATION_TYPE = NQS; // optional and default
    #
    #----- 2 -----
    AUTHENTICATION_TYPE = DATABASE;
    [ DATABASE ]
    DATABASE = "asdb";
    #
    #----- 3 -----
    #AUTHENTICATION_TYPE = BYPASS_NQS;


    LDAP Authentication

    • Create a new LDAP server entry in the Security Manager
    • Create an Initialization Block to populate the security session variable USER
    • Assign the LDAP unique username attribute to the USER variable
    • Log in and see the with LDAP credentials

    Setup LDAP server in repository

    image

    Configure Hostname and port for LDAP

    image

    Defined the unique identifier

    image

    Create a new initialization block

    image

    Assign data source to the block

    image

    image

    Assign the data source to the target

    image

    Create new variable for user name

    image

    Map LDAP attribute to the USER variable

    image

    Enable required for authentication

    image


    ‣ External tables Lookup

    • Initialization block fires to authenticate the user based on a table lookup.
    • The session variables USER and PASSWORD used to query an existing security table
    • Other attributes can be picked up at the same time like email and groups.

    The following table can be imported into the physical layer and used for authentication.

    Select
    username,
    groups,
    fullname,
    From
    obiee_users
    Where username=‘:USER’
    and password=‘:PASSWORD’

    image

    Enter the SQL in the initialization block as below.

    image


    ‣ Custom Authenticators


    • An API is defined in the administration guide
    • A developer implements and delivers a library that exposes the API
    • The BI Administrator defines a new Custom Authenticator using the custom library
    • Then define an init block to execute the custom authentication and map to session variables
    • Log in with the required credentials

    • The BI server Hashes the supplied password and compares with the hash in the password file
    • Initialization block populates the USER and GROUP variables

    Create a new custom authenticator

    image

    Specify plug in and configuration password file.

    image

    Map to USER and GROUP variables

    image