Source Control for the RPD and WebCatalog Objects

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.

RPD

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.

WebCatalog

To source control WebCatalog objects there are two main practices that must be followed:

  1. Objects stored in source control must maintain the directory structure of the OBI 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 OBI.

  2. 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 CodeObject Type NameFile Extension in Source Control
    RPD
    .rpd
    FOLDERFolder.fldr
    ANALYSISAnalysis.anlys
    DASHBOARDDashboard.db
    DASHBOARD_PROMPTDashboardPrompt.dbp
    REPORTReport.rprt
    DATAMODELDatamodel.dm
    STYLE_TEMPLATEStyleTemplate.st
    METADATAMetadata.md
    KPIKPI.kpi
    FILTERFilter.fltr