Troubleshoot Oracle Fusion Connections

Issues that may be encountered when connecting Intelligent Advisor to Oracle Fusion are listed in the following table.

Table 1. Oracle Fusion connection issues
Issue	Resolution
Hub connection issues
Intelligent Advisor Hub shows Oracle Fusion connection as failing (circular red stop icon)	Try refreshing the Fusion connection. For more information, see Repair an Oracle Fusion Connection. Check that you have the correct connection configuration details. Ensure that the username/password used to generate the jwt token has access to the base Oracle Fusion objects and their services. For more information, see View Oracle Fusion connection details.
Intelligent Advisor Hub shows "Accessing topology manager was forbidden" message on the Connections page	To use the Oracle Fusion connection type in Intelligent Advisor Hub, you must have a user login with permissions to write to topology manager in Oracle Fusion.
"Bad Request - IAM Client id and secret not authorized" error	Displayed when creating an Oracle Fusion connection if the client id and secret are not correct, or the confidential client does not have access to the correct scope an error will result. Check the settings in your confidential application.
"Bad Request - User or client with name 'linkedApiClient' already exists" error	Displayed when creating an Oracle Fusion connection if the client already exists in the Intelligent Advisor site. Make sure you are using a new confidential client. Follow the steps in Create a Confidential Application for Fusion Connections to Access the Hub API to create one before creating your Oracle Fusion connection.
Policy Modeling connection issues
Policy Modeling shows error when you choose the Oracle Fusion connection	Check that the connection in Intelligent Advisor Hub is successful (green tick icon) For more information, see View Oracle Fusion connection details.
Policy Modeling shows an error "Hub could not parse the response" for the selected connection in the Choose Connection dialog	Change the wsc_req_timeout_for_metadata configuration setting for Intelligent Advisor Hub to 180 (seconds). For more information, see Intelligent Advisor Hub Configuration Properties.