Oracle Communities

Oracle Analytics and AI

Child Item

Fusion Data Intelligence: Migrating from SME to Sandbox Framework-Upgrade Guidelines and Schedule

Please Note Customers who are using SME Branch Framework will have an option/banner as per following schedule for migrating from SME to Sandbox Framework.

Migrate to the Sandbox Framework for Semantic Model Extensions
Prior to switching over to the Sandbox framework for semantic model extensions please note the following tasks and ensure to take appropriate action where required in the suggested sequence. Begin by migrating the non-production instances to the Sandbox framework before migrating the production instance.

Pre-requisite Summary:
If possible use a FDI-ATE(additional test environment) for this Upgrade
1. Pre-Migration Tasks - Validation/Cleanup/Merge to Main Branch
2. Migration Validation - Validate there are no Error/Customization Warnings
3. Schedule Migration to SME Sandbox
4. Rollback to SME Branch Option - if needed within 60 days SME Sandbox can be Rolled backed to SME
5. Plan migration of SME-Sandbox Bundle to PROD

Following is Tentative/ETA Schedule for Sandbox SME Upgrade Rollout :

Please DO NOT Schdule Upgrade without Completing all Prerequisites/Validation -

DataCenter/Region	Upgrade Banner Availability/ETA
APAC/EMEA	Starting March-03 thru APR-07-25
Americas	Starting March-17 thru APR-07-25

The above schedule is only for enabling the migration flag for all FDI Instances where customers will be given an option/upgrade-banner - Customers should carefully choose the actual date to migrate.

High Level Guidelines: About Migrating to the Enhanced Semantic Model Extension Framework
Prior to switching over to the new semantic model extensions framework, do note following and take appropriate action where required:
• Delete or merge all unpublished branches because these won’t be migrated.
• Ensure that you schedule or apply all the release updates prior to the migration to avoid not being able to rollback.
• Create a Semantic Model Extensions bundle prior to making any semantic model extension changes.
• Delete or enable disabled steps as needed in the branch to be migrated because the migration process migrates only the enabled steps.
• Before migration, merge the published branch with the main branch and confirm that all the subject areas operate as expected.
• After merging all your changes to the main branch, validate it to ensure that the branch and its steps are error free. You can run the validation report, review it, and resolve all errors. The migration process converts this single main branch to a single Semantic Model Extensions Sandbox.
• Schedule the migration during a low usage period to avoid reporting impact.
• Upgrade all non-production and production instances to the new framework before attempting any migration of semantic extensions from non-production to production instances using the Bundles functionality.

Documentation Links: Please review following documentation which has detailed steps - please validate each step as stated in documentation:
About Migrating to the Enhanced Semantic Model Extension Framework
FDI : https://docs.oracle.com/en/cloud/saas/analytics/24r4/fawag/migrate-semantic-model-extensions-sandbox-framework.html#GUID-3325B397-6E0C-447E-A81A-50D27D9ACB42

Using the Enhanced Semantic Model Extension Capabilities: https://docs.oracle.com/en/cloud/saas/analytics/24r4/fawag/extend-semantic-model-using-sandbox-framework.html

Find more posts tagged with

FDI

Fusion Data Intelligence

Fusion Data Intelligence FDI

Comments

Bhaskar Konar

Very helpful information.

Thank you very much @Rajesh L-Oracle!

RMJ-kpmg

Hi Rajesh - Is the upgrade to the enhanced framework required by Feb 24? If so, will the system auto upgrade on this date?

Rajesh L-Oracle

@RMJ-kpmg Feb-24 is last batch processig date based on region for upgrade Banner enablement - you can schedule actual upgrade to a future date by clicking Schedule Now - please only schedule after you have gone through the validations.

user1565808

Hi, I have a few questions around these Semantic Extension Releases (see below), I was hoping you could please help with:

Is the banner the only notification we will get to inform of an Semantic Extension upgrade, or will we get a notification email too for each environment?
Is there a predefined auto-update target date, or does the clock only start ticking once you've manually selected a date via schedule now on the banner?
Once you've chosen a date via schedule now, can it be cancelled or changed?
Are these Semantic Extension updates going to be a regulary reoccurance, if so what is the planned release schedule?
Could you elaborate on the potential business impact during the implementation of the change, for example do all reports and dashboards remain accessible during the upgrade, no service downtime? How much testing is required?

Rajesh L-Oracle

Hi @user1565808

please find answers in-line

Is the banner the only notification we will get to inform of an Semantic Extension upgrade, or will we get a notification email too for each environment? > Banner will be visible in your Instance SME console once you environment is enabled/available for migration per above schedule
Is there a predefined auto-update target date, or does the clock only start ticking once you've manually selected a date via schedule now on the banner? > You have a choice to pick and schedule Migration date
Once you've chosen a date via schedule now, can it be cancelled or changed? > We suggest that migration date should only be picked once you have completed all validation and there are no errors
Are these Semantic Extension updates going to be a regulary reoccurance, if so what is the planned release schedule? > this is a one time migration from Branch framework to Sandbox framework
Could you elaborate on the potential business impact during the implementation of the change, for example do all reports and dashboards remain accessible during the upgrade, no service downtime? How much testing is required? > Please use this process in a ATE/DEV environment first as suggested - we suggest all the customization should be tested after migration