This option requires that developers commit required files to choice of SCM. Customers can choose option that works well for them, use of SCM is preferred practice in general.
Source controlling the RPD is as simple as checking the RPD into your Source Control System with the extension of rpd. The plugin will now recognize the artifact and build it accordingly.
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 OBI WebCatalog.
For example, notice the WebCatalog path for the report below:Objects stored in source control should be named with the following extensions corresponding to the object type in order to show up in the right bucket.
Object Type Code | Object Type Name | File Extension in Source Control |
---|---|---|
RPD | .rpd | |
FOLDER | Folder | .fldr |
ANALYSIS | Analysis | .anlys |
DASHBOARD | Dashboard | .db |
DASHBOARD_PROMPT | DashboardPrompt | .dbp |
REPORT | Report | .rprt |
DATAMODEL | Datamodel | .dm |
STYLE_TEMPLATE | StyleTemplate | .st |
METADATA | Metadata | .md |
KPI | KPI | .kpi |
FILTER | Filter | .fltr |