Repointing FDI to a different IAM/IDCS

Victor H

When you change the Fusion source instance for FDI, the IDCS and IAM remain pointed to the original IAM/IDCS. Is there a way to repoint these?

Lets say for example we have an FDI_TEST that was originally pointing to a Fusion ERP instance ERP_TEST1

If we change the source to another Fusion instance ERP_TEST2, the pipelines will point to that instance but the users/group assignments wil still be synced to ERP_TEST1. Is there a way to redirect the FDI security to use ERP_TEST2 users/group assignments?

In the past we have had to destroy the FDI instance and recreate it on ERP TEST2 but we want to avoid that; The ADW is also destroyed and this impacts other tools (e.g. ODI)

What are the IAM best practices/alternatives for dealing with FDI data source changes?

RajeshPolavarapu-Oracle

Hi @Victor H

This is an expected behavior, and only option you have is - create a new FDI instance under IAM domain where your ERP_TEST2 exists.

Mallikarjuna Kuppauru-Oracle

Hi @Victor H

Are you using same IDCS instance for fusion and FDI ? or using different IDCS for both Applications.

Regards,

Arjun

Victor H

Same IDCS

Mallikarjuna Kuppauru-Oracle

Hi @Victor H

Got it. If you have 2 separate instances then its an easy to sync . Refer below -

https://docs.oracle.com/en/cloud/paas/identity-cloud/tutorial-scim-template-sync-idcs/

Regards,

Arjun

Victor H

we do not want to sync 2 different IDCS instances, we need to repoint FDI to a different one.

IN the example I provided, ERP_TEST1 and ERP_TEST2 may have different user/role assignments.

When we repoint FDI to ERP_TEST2 only the data source is repointed but users/roles are still coming from ERP_TEST1.

We are not looking for a way to sync ERP_TEST1 and ERP_TEST2.

PRATHEEK

@Victor H

Just a quick refresher I’ve been following this thread, and I wanted to check if any solutions or best practices have been shared so far.

Hi All @Abhishek Bajpai - CEAL Team-Oracle @Mallikarjuna Kuppauru-Oracle @Dayne-Oracle @John Hung-Oracle

I have a similar use case with a few customers who have implemented Fusion Data Intelligence (FDI) for both Prod and Non-Prod environments by creating two new, separate compartments within their OCI tenancy.

During my review, I noticed that FDI Non-Prod was installed in a new compartment, rather than being configured within the Pre-Prod (Fusion ERP Non-Prod) domain. From my understanding, FDI should ideally be deployed within the same domain/compartment as the corresponding Fusion ERP environment.

Can anyone confirm if this is the recommended approach? Also, what are the potential implications—if any—of deploying FDI in a separate compartment from Fusion ERP (e.g., integration, data access, pipeline refresh issues)?

Appreciate any insights or experiences you can share.

PRATHEEK

Just a quick refresher I’ve been following this thread, and I wanted to check if any solutions or best practices have been shared so far.

Hi All @Abhishek Bajpai - CEAL Team-Oracle @Mallikarjuna Kuppauru-Oracle @Dayne-Oracle @John Hung-Oracle

I have a similar use case with a few customers who have implemented Fusion Data Intelligence (FDI) for both Prod and Non-Prod environments by creating two new, separate compartments within their OCI tenancy.

During my review, I noticed that FDI Non-Prod was installed in a new compartment, rather than being configured within the Pre-Prod (Fusion ERP Non-Prod) domain. From my understanding, FDI should ideally be deployed within the same domain/compartment as the corresponding Fusion ERP environment.

Can anyone confirm if this is the recommended approach? Also, what are the potential implications—if any—of deploying FDI in a separate compartment from Fusion ERP (e.g., integration, data access, pipeline refresh issues)?

Appreciate any insights or experiences you can share.