Merge Your External Applications
If you’ve an external semantic model such as an Oracle Analytics Cloud instance other than the Oracle Analytics Cloud instance associated with your Oracle Fusion Data Intelligence instance, then you can merge it with the semantic model of Oracle Fusion Data Intelligence only in your non-production instance.
You can also merge your existing catalogs in the external Oracle Analytics Cloud with those in the Oracle Analytics Cloud instance associated with your Oracle Fusion Data Intelligence instance. Both external semantic model and semantic model extensions can co exist and you can include the external semantic model in your semantic model extensions. On the Publish Model page, select "Yes" if you want the external semantic model to be included.
If the external semantic model references application roles and groups, then you must create them manually. The merge capability imports only the mappings and doesn't import the roles and groups definitions. Create the applicable groups in your identity provider, see Create Groups or Create a Group as applicable. Create application roles using the Security page in Oracle Fusion Data Intelligence, see Create an Application Role.
Merging external semantic models may require you to scale up your Oracle Analytics Cloud compute resources to ensure better performance. In particular, if you're merging a semantic model that was in use on a live Oracle Analytics Cloud instance, then Oracle recommends scaling up Oracle Fusion Data Intelligence's Oracle Analytics Cloud compute resources by the same number of CPUs as the instance the semantic model is merged from.
- Data types of the conforming columns are matching, else you can't merge.
- Data for the mapped columns match, else queries don't fetch correct results.
- Level of details at which data is stored in the dimensions match, else queries return incorrect results.
- External semantic model is up to 25 MB in size.
- Catalog objects are in folder names that don't conflict with the prebuilt folders
of Oracle Fusion Data Intelligence and in
/Shared/Custom/folder. - New logical table source that you add has a higher priority group than the prebuilt logical table source. For example, if the logical table source of the prebuilt object is 2, then you must specify a priority group of 3 or higher.
- Additional hierarchy has its own total level.
The external semantic model connects only to the Oracle Autonomous Data Warehouse associated with Oracle Fusion Data Intelligence. After enabling the external application merge functionality, if you make semantic model changes with data augmentation, then it'll result in unexpected errors. If such changes exist, then you must update the data augmentations to remove the semantic model changes. Ensure that you make the semantic model changes in the external semantic model and that you don't use system variables in your extensions.You must also ensure that the functional areas enabled in the target environment and the development environment from where the template semantic model was extracted are the same to avoid failure of the external application merge.
- Import or migrate your external warehouse data to the Oracle Autonomous Data Warehouse associated with Oracle Fusion Data Intelligence using the Oracle database utilities or any ETL tool.
- While importing the objects, create a new physical schema for the custom schema such as X_FAW_MERGE_POC and import the objects into this physical schema. Though the objects are under the schema called X_FAW_MERGE_POC, because read access is provided, the SQL is formed as X_FAW_MERGE_POC.custom table.
- Download and save a copy of the external semantic model on your local machine using the Download Imported Semantic Model option in Actions on the External Application page, if you have imported it earlier.
- Download the template semantic model using the Export Semantic Model Template option in Actions on the External Application page.
- Use the Model Administration Tool that's a part of the Oracle Analytics Client Tools
to:
- Merge the template semantic model with your external semantic model
- Update connections to the custom schema to which you migrated your warehouse data. See Set up Metadata Import in the Repository File and Set Up Table Import in the Repository File.
- Update joins with conformed dimensions as appropriate, keeping in mind the mentioned constraints. See Conformed Dimensions to Merge External Applications.
- Make the external semantic model consistent and free of errors and warnings. Ensure that the column mapping is fully qualified in the external semantic model to avoid any application upgrade failures. You can download the latest semantic model from the user interface, make the necessary changes using the Model Administration Tool, and reupload it. See Download and Install Oracle Analytics ClientTools.
To move the merged semantic model from your non-production instance to your production instance, the recommendation is to perform the test to production process using the Bundles functionality. See Bundle Your Application Artifacts.