In Endeca 3.0(2.4) we have a feature to integrate Oracle Business Intelligence data (RPD) to Endeca MDEX engine this post will look cover below topics
1. Configuring Data domains
2. Integrating BI with Endeca Integrator
3. Creating Sample reports out of MDEX data
1.Configuring Data domains
Once you installed Endeca 3.0 start the Endeca Server (weblogic/tomcat) open integrator
File --> New -->Project -->(Import the GettingStarted project) or create new project
![]()
![]()
2. Integrating BI with Endeca Integrator
Open integrator File --> New -->Project --> Endeca Information Discovery -- Load Data from OBI Server
![]()
Next and enter OBI-Server make sure it is up and running (including weblogic and bi services) when you click on Connect to OBI Server it should show Connected as highlighted in below screen
![]()
Once it is connected successfully it will show you the BI Server RPD with available Subject Areas Select (All) the table(s) you want to import to report on
![]()
Next,edit the object (Display Name) in the Attribute Configuration screen then group the objects(Group Name) once the renaming is done click on Edit Finished then only finish button enables if you don't have anything to edit just click on Edit Finished --> Finish
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
1. Configuring Data domains
2. Integrating BI with Endeca Integrator
3. Creating Sample reports out of MDEX data
1.Configuring Data domains
Once you installed Endeca 3.0 start the Endeca Server (weblogic/tomcat) open integrator
File --> New -->Project -->(Import the GettingStarted project) or create new project
How to import and run Getting Started:
Once it is completed you should run the InitDataDomain.grf file and it has to complete successfully without any errors.
2. Integrating BI with Endeca Integrator
Open integrator File --> New -->Project --> Endeca Information Discovery -- Load Data from OBI Server
Click on Next and enter your Endeca-Server Details
Endeca-server host : localhost
Endeca-server port : 7001 (default weblogic)
Endeca domain : GettingStarted( your custom one ) configured in step 1
Next and enter OBI-Server make sure it is up and running (including weblogic and bi services) when you click on Connect to OBI Server it should show Connected as highlighted in below screen
Next,edit the object (Display Name) in the Attribute Configuration screen then group the objects(Group Name) once the renaming is done click on Edit Finished then only finish button enables if you don't have anything to edit just click on Edit Finished --> Finish
Our Project(BI) is ready click on workspace.prm and verify the data_domain_name configured should be same as Data Source configured in Studio(as shown below)
Things to Note : Endeca Server uses our SELECT_BUSINESS_MODEL clause to query the statements (QueryStatement.sql)
QueryStatement.sql :SELECT_BUSINESS_MODEL
"SampleApp Lite"."F0 Revenue Base Measures"."Billed Quantity" F0_Revenue_Base_Measures_Billed_Quantity,
"SampleApp Lite"."F0 Revenue Base Measures"."Discount Amount" F0_Revenue_Base_Measures_Discount_Amount,
"SampleApp Lite"."F0 Revenue Base Measures"."Revenue" F0_Revenue_Base_Measures_Revenue,
"SampleApp Lite"."F1 Targets Base Measures"."Target Quantity" F1_Targets_Base_Measures_Target_Quantity,
"SampleApp Lite"."F1 Targets Base Measures"."Target Revenue" F1_Targets_Base_Measures_Target_Revenue,
"SampleApp Lite"."F0 Revenue Base Measures"."# of Offices with Orders" F0_Revenue_Base_Measures___of_Offices_with_Orders,
"SampleApp Lite"."F0 Revenue Base Measures"."# of Orders" F0_Revenue_Base_Measures___of_Orders,
"SampleApp Lite"."F0 Revenue Base Measures"."# of Products with Orders" F0_Revenue_Base_Measures___of_Products_with_Orders,
"SampleApp Lite"."D2 Offices"."Company Key" D2_Offices_Company_Key,
"SampleApp Lite"."D2 Offices"."Dept Key" D2_Offices_Dept_Key,
"SampleApp Lite"."D2 Offices"."Office Key" D2_Offices_Office_Key,
"SampleApp Lite"."D2 Offices"."Office Sequence" D2_Offices_Office_Sequence,
"SampleApp Lite"."D2 Offices"."Org Key" D2_Offices_Org_Key,
"SampleApp Lite"."D1 Products"."Brand Key" D1_Products_Brand_Key,
"SampleApp Lite"."D1 Products"."LOB Key" D1_Products_LOB_Key,
"SampleApp Lite"."D1 Products"."Product Sequence" D1_Products_Product_Sequence,
"SampleApp Lite"."D1 Products"."Product Type Key" D1_Products_Product_Type_Key,
"SampleApp Lite"."D0 Time"."Day Of Month" D0_Time_Day_Of_Month,
"SampleApp Lite"."D0 Time"."Day Of Week" D0_Time_Day_Of_Week,
"SampleApp Lite"."D0 Time"."Day Of Year" D0_Time_Day_Of_Year,
"SampleApp Lite"."D0 Time"."Julian Day Num" D0_Time_Julian_Day_Num,
"SampleApp Lite"."D0 Time"."Julian Month Num" D0_Time_Julian_Month_Num,
"SampleApp Lite"."D0 Time"."Julian Qtr Num" D0_Time_Julian_Qtr_Num,
"SampleApp Lite"."D0 Time"."Julian Week Num" D0_Time_Julian_Week_Num,
"SampleApp Lite"."D2 Offices"."Company" D2_Offices_Company,
"SampleApp Lite"."D2 Offices"."Department" D2_Offices_Department,
"SampleApp Lite"."D2 Offices"."Office" D2_Offices_Office,
"SampleApp Lite"."D2 Offices"."Organization" D2_Offices_Organization,
"SampleApp Lite"."D3 Orders (Facts Attributes)"."Billed Date" D3_Orders__Facts_Attributes__Billed_Date,
"SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Date" D3_Orders__Facts_Attributes__Order_Date,
"SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Month" D3_Orders__Facts_Attributes__Order_Month,
"SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Number" D3_Orders__Facts_Attributes__Order_Number,
"SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Size Bin" D3_Orders__Facts_Attributes__Order_Size_Bin,
"SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Status" D3_Orders__Facts_Attributes__Order_Status,
"SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Type" D3_Orders__Facts_Attributes__Order_Type,
"SampleApp Lite"."D1 Products"."Brand" D1_Products_Brand,
"SampleApp Lite"."D1 Products"."LOB" D1_Products_LOB,
"SampleApp Lite"."D1 Products"."Product" D1_Products_Product,
"SampleApp Lite"."D1 Products"."Product Number" D1_Products_Product_Number,
"SampleApp Lite"."D1 Products"."Product Type" D1_Products_Product_Type,
"SampleApp Lite"."D0 Time"."Calendar Date" D0_Time_Calendar_Date,
"SampleApp Lite"."D0 Time"."Per Name Half" D0_Time_Per_Name_Half,
"SampleApp Lite"."D0 Time"."Per Name Month" D0_Time_Per_Name_Month,
"SampleApp Lite"."D0 Time"."Per Name Qtr" D0_Time_Per_Name_Qtr,
"SampleApp Lite"."D0 Time"."Per Name Week" D0_Time_Per_Name_Week,
"SampleApp Lite"."D0 Time"."Per Name Year" D0_Time_Per_Name_Year
FROM "SampleApp Lite"
In Outline window edit the Metadata directory(Workspace) to check the records you are going to load in Endeca MDEX server
Load Data.grf is important where it takes data from Metadata(DataRecord.fmt) file and pumpsto MDEX engine using ENDECA_BULK_ADD_OR_REPLACE_RECORDS component
Execute the graph by right clicking on Canvas Run-->Clover ETL Graph
3. Creating Sample reports out of MDEX data
Below are sample Pivot , Chart's where you can enable the sorting order by Column and conditional formatting
Report creation using studio : http://www.varanasisaichand.com/2012/10/oracle-endeca-studio.html
We will see how to enable sorting , conditional formats and other number format's like OBI in another post