Steps requires to perform in FDI instances when there is a scheduled or ongoing patch in ERP/SCM

User_7AIAG

What is the best practice for managing FDI instances while the linked Fusion ERP/SCM instance undergoes patching?

RVohra

@User_7AIAG , Welcome to the Oracle Analytics Community!

Before scheduled patching to your Fusion ERP/SCM environment, plan and communicate the maintenance schedule with the team that owns your FDI pipelines.

• Notify analytics users and pipeline owners of planned maintenance windows.
• Schedule full or incremental loads to run before the patch begins to ensure recent data is captured.
• Pause/monitor FDI job runs that would normally execute during the ERP/SCM outage.

RVohra

Also, as a best practice, after patching, validate credentials/connectivity. Hope it helps!

User_7AIAG

@RVohra will the linked FDI instance and relerelevant analytics URL be available during patch activity in ERP/

Bhaskar Konar

https://community.oracle.com/products/oracleanalytics/discussion/comment/74059#Comment_74059

Hi @User_7AIAG,

Please take a look into the following post which might be useful for the understanding.

Production to Test environment refresh impact on FDI — Oracle

Hope this help.

Thank you.

Silvio Garber-Oracle

FDI instances are independent from the Fusion instances they copy data from. There should be no impact on FDI and OAC availability due to Fusion patching and no precautions are documented for before or after the patch.

RVohra

Hi @User_7AIAG , there are a few different ways to create an FDI instance. It depends on what approach was used for a particular implementation. Oracle recommends integrating FDI directly with the Fusion Applications instance, as it results in a much smoother and more tightly connected setup. With this approach, the FDI instance is automatically linked to Fusion Applications, key application details are prefilled during instance creation, and users can sign in using the same credentials they already use for Fusion. In addition, an integrated FDI setup also allows users, roles, and security groups to be shared between Fusion Applications and FDI, while OAuth is used for authentication across both platforms.

If your deployment is Integrated FDI then it is better to follow the best practice that I had posted before. Thanks

Silvio Garber-Oracle

@RVohra Integrated deployment indeed includes SSO, but we can configure SSO even with a detached deployment. The main difference from a user perspective is the use of OAuth for data extraction, which eliminates the need to manage connection credentials. No other functional differences would be experienced.

RVohra

@Silvio Garber-Oracle , Thanks for providing this information, appreciate it!