No configuration found for 'Account Aggregation' despite having created one

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

I am creating a Web Services SaaS connector from ISC to Oracle HCM to gather account information from the Oracle Workers API. The full api path is baseURL/hcmRestApi/resources/latest/workers

Base config and Connection Settings area all fine, and under HTTP Operations, my Test Connection works when I run the Review & Test in the Source Setup.

I have left Aggregation Settings for Delta and Partial disabled right now because I want to run full imports at this stage of our POC.

In Test Connection, the context URL is set to /hcmRestApi/resources/latest

I then create under HTTP Operations a second Operation for Account Aggregation. Operation Type is set to Account Aggregation. Context URL on this screen I am setting to /workers and set the Parent Endpoint to Test Connection. I have tried playing with the context URL fields to mix and match full vs partial paths, I get the same error in the end regardless but some clarity on this would be appreciated!

My only header value is Accept : application/json. (This is the only value that seems required in Postman) Under Response Information, Root Path is set to $.items[*] and Success Codes is set to 200.

My Response Mapping table is very basic at this point:

displayName : $.items[].names[].DisplayName

id : $.items[*].PersonId

personNumber : $.items[*].PersonNumber

image
image747×332 4.87 KB

image
image1025×434 12.1 KB

image
image1003×435 17.7 KB

image
image598×332 14.9 KB

So if there are any thoughts here, I would love some insight as to why the Aggregation process when I run it, or even Account Correlation tests, all fail to recognize the Account Aggregation HTTPS operation that has been added of if I have done something incorrect in my set up. Thanks.

2

I think you may be misunderstanding the purpose of Parent Endpoint. That is for chaining requests. Try entering the full context URL and remove the Parent Endpoint.

3

Hi Justin. Welcome to the dev forum!

I have a couple of thoughts on your overall configuration, but first, why does it not recognize the Account Aggregation operation when you have defined it? If you set the parent endpoint to Test Connection, then there is no account aggregation step to start. Leave the parent endpoint blank. The test connection runs on its own as part of the hourly status check.

Other than that, in your response information, root path, use $.items - you don’t need to include the [*] - it will iterate over the array on its own.

In your response mapping, exclude the $.items[], you already defined that in the root path. Start with $.names[].DisplayName or $.PersonNumber

Your context path is built on top of the base URL in the main configuration. Each operation needs to have the context path begin where the base URL leaves off.

4

Jeremy, thanks so much for helping me understand better that config. Things are working now!

5

Matt, thanks for helping me understand better the inner-workings of the configuration. Between your and Jeremy’s expertise, I’ve been able to get this all working as intended now. Thanks so much!