The FlexDeploy OTBI solution allows developers to either source the WebCatalog objects from a development OTBI instance or from a source control system.
To source control WebCatalog objects there are two main practices that must be followed:
Objects stored in source control must maintain the directory structure of the OTBI WebCatalog.
For example, notice the WebCatalog path for the report below:
The path above must match the path in the source control system as we see below.
For above example, FlexDeploy project source configuration will be configured with BusinessIntelligence/12c as sparse folder. This would ensure that all objects under that folder will be discovered as WebCatalog objects and file path starts with /shared which matches the WebCatalog path in OTBI.Objects stored in source control should be named with the following extensions corresponding to the object type in order. The extensions are important to both ensure the deployment operation is handled correctly, and it makes it easier to identify and search for these objects in FlexDeploy.
OTBI Type Name OTBI Signature / Composite Signature* Source Control Extension Action action Action Agent coibot1 Agent Analysis queryitem1 Analysis Column cosavedcolumn1 Column Condition condition1 Condition Dashboard dashboardfolder1 Dashboard Data Model .xdm * Data Model Dashboard Prompt globalfilteritem1 Dashboard Prompt Filter filteritem1 Filter Group customgroup1 Group KPI kpi1 KPI KPI Watchlist scorecardkpiwatchlist1 KPI Watchlist Report .xdo * Report Scorecard scorecard1 Scorecard Style Template .xss * Style Template Visual Analyzer Projects projectfolder1 Visual Analyzer Projects The OTBI signature can be viewed by hovering over the
icon on the OTBI WebCatalog Manager's properties for a catalog object (see image above).