Within an on-premise scenario, the OBIEE development life-cycle was quite simple:
- connect to a data warehouse and import the warehouse tables (metadata import to physical layer)
- build OBIEE metadata model (RPD)
- upload the RPD into Weblogic using the Deployment screen
Within a cloud scenario the BICS development life-cycle is quite the same, but requires some additional steps and some decisions on the development model: either using web-based BICS developer or upload of full RPD file developed using OBIEE Admin Tool.
While it’s possible to develop the complete metadata model within the cloud using the BICS web-based Modeller, like below:
the capabilities of this web-based Modeller are more limited. Due to this there is no option to edit or change the uploaded RPD file within the web-based BICS modeller afterwards. The process to upload a locally developed (OBIEE) metadata model (.rpd file) to the BICS Cloud is called “lift&shift”.
The required setup for this OBIEE to BICS development life-cycle using lift & shift is described in below diagram:
For the BICS development life-cycle setup the data of the Fusion Cloud e.g. HCM or ERP is assumed to be already present within a Oracle Database Cloud (DBaaS/DBCS). For this setup all components (formally probably referred to as “server” components) are provisioned on the Oracle Public Cloud behind a firewall and only the IT Development Tools (IDE) are installed on a developer machine like a desktop or laptop.
The following integrations need to be setup:
To create Backup as part of the development life-cycle refer to the following article:
BIAPPS on PAAS – Backup and Restore – Introduction
To connect between DBaaS and the Fusion Application Cloud (SaaS):
BIAPPS on PAAS – Source Connectivity
The above scenario uses the Oracle Database Cloud for storing the data. If the Data is not stored in the Oracle Database Cloud, but the Oracle Schema Cloud Service which is bundled for-free with BICS then the data must be loaded into BICS using the BICS Data Sync tool:
Within the all above scenario the (“server”) components are provisioned on the Oracle Public Cloud. For a scenario where some components like the Database still reside on-premise the following tool needs to be installed on the server hosting the Oracle Database:
as described in this article from Oracle.