Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Oracle BI WebCatalog objects are deployed in specified structure. Additionally, there are few different types of objects available in Oracle BI WebCatalog. When sourcing from source code repository, FlexDeploy Oracle BI plugin requires that developers download and commit files in matching folder structure and with appropriate extension.


Oracle BI (Oracle Business Intelligence in pre-5.5.0.1) project type:

Objects stored in source code repository should be named with the following extensions.:

Object Type CodeObject Type NameFile Extension in Source Control
FOLDERFolder.fldr
ANALYSISAnalysis.anlys
DASHBOARDDashboard.db
DASHBOARD_PROMPTDashboardPrompt.dbp
REPORTReport.rprt
DATAMODELDatamodel.dm
STYLE_TEMPLATEStyleTemplate.st
METADATAMetadata.md
KPIKPI.kpi
FILTERFilter.flt

Oracle BI 2.0 project type. @Since 5.5.0.1

Objects stored in source code repository should be named with the following extensions:

OBIEE Type Name
OBIEE Signature / Composite Signature*
Source Control Extension
ActionactionAction
Agentcoibot1Agent
Analysisqueryitem1Analysis
Columncosavedcolumn1Column
Conditioncondition1Condition
Dashboarddashboardfolder1Dashboard
Dashboard Promptglobalfilteritem1Dashboard Prompt
Data Model.xdm *Data Model
Filterfilteritem1Filter
Groupcustomgroup1Group
KPIkpi1KPI
KPI Watchlistscorecardkpiwatchlist1KPI Watchlist
Mobile App.xmaMobile App
Report.xdo *Report
Scorecardscorecard1Scorecard
ShortcutN/AShortcut
Style Template.xss *Style Template
Visual Analyzer Projectsprojectfolder1Visual Analyzer Projects


For example, let's see following Balance Letter report in /shared/Sample Lite/Published Reporting/Reports Location.  Images below are shown for Oracle BI project type, but similar structure is required for Oracle BI 2.0 using the extensions from the table above.

If you Archive this report, it will be downloaded as Balance Letter.xdo.catalog, but in order to work with FlexDeploy you should rename it to Balance Letter.rprt and place it in /shared/Sample Lite/Published Reporting/Reports folder of your code repository.

This can be a bit cumbersome, but it can be further automated, . See Automate check-in of development catalog items to SCM.