Oracle HCM Cloud Connector Integration with IdentityIQ – Request for Insights

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Hi All,

I’m currently working on the integration of the Oracle HCM Cloud connector. As per the documentation, it recommends creating an export file first for Active, Termination, and Rehire feeds.

I’d appreciate it if anyone who has already integrated this connector could share some insights, particularly on the following:

  1. How can this be replaced or aligned with the Fusion HCM connector?
  2. How will the export file be maintained or updated in the future?

Thanks in advance for your support!

2

@All,
is there anyone who already implemented Oracle HCM Cloud connector?
IdentityIQ (IIQ) #OracleHCMCloud

Regards,
Manish S

3

hi @manish4sailpoint

Few considerations:

  1. The export file method works well for Active, Termination, and Rehire feeds, especially when automated through BI Publisher or HCM Extracts.
  2. If you’re considering the Fusion HCM connector, it’s API-based and much more dynamic. We found it easier to maintain and better for real-time updates.
  3. During our transition, we ran both methods in parallel to validate data and ensure consistency.
4

thanks @haideralishaik for the the reply.

I have the following queries:

  1. In the case of a full aggregation, is it mandatory to configure the mapping for all feed files?

  2. What is the recommended approach to automate the HCM export so that it is readily available whenever an aggregation is executed?

  3. Aside from the recent updates, does the connector function in the same manner as it did in Fusion HCM?

Regards:

Manish S.

5

hi @manish4sailpoint

:one: Full Aggregation & Feed Mapping Yes, for a full aggregation, it’s best to configure mappings for all feed files involved (Active, Termination, Rehire). This ensures IdentityIQ can correctly interpret and correlate identities across feeds.

:two: Automating HCM Export We automated the export using Oracle HCM Extracts scheduled via BI Publisher. The files are pushed to a secure location (like SFTP), and IdentityIQ picks them up during scheduled aggregation tasks. This setup keeps things smooth and hands-off.

:three: Fusion HCM Connector Behavior Aside from recent updates, the Fusion connector still follows the same core logic just with improved API support and better performance. If you’re using REST APIs, you’ll notice more flexibility compared to the older file based approach.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.