SuccessFactors Webservices connector - Aggregation taking more than 12 hours

IdentityIQ (IIQ) IIQ Discussion and Questions
, , ,
1

Which IIQ version are you inquiring about?

8.4P1

Hi SailPoint Community,
We have implemented SuccessFactors Webservices connector utilizing ODATA API, we are facing issue in aggregation as it is taking more than 12 hours for aggregating data, we are also unable to Refresh Identity as identity getting locked in aggregation process. This issue is from long time please suggest any option or procedure to reduce this aggregation time
To overcome this issue now we are thinking to migrate to SuccessFactors native connector but we are not getting all the attributes which are used in SF webservice connector and these attributes are used in Rules, Workflow and in other task, even though if we get attributes navigation path from SFAPI Dictionary or ODATA API dictionary it will be big task to make changes in all the rules and other areas it may get effect in onboarding process.
I have searched in the community it is given we need to use both SF native connector and webservice connector to get all custom attributes, but I am not sure of the integration process . Can anyone please suggest or provide some procedure to overcome this issue.

Thanks,
Lavanya Kulkarni

2

Hi @lavanyakulkarni,

the best way is using the partinioning, static or dynamic. I dont know the odati api of SF, but you can review the documentation and check if you can set a filter on the call, so you can make more call at the same time.
An other way, if you can use a filter on the call, is limit the accounts that you are reading, maybe you are aggreating accounts that dont you need. Also, you can use a customization rule to dont create accounts.
The last way is increase the resource of server(or add servers) but before of this step you must analyze where is the problem, if the response of SF is slow or the elaboration on IIQ or if you some rule that slows down the process, ect…