Is there any way to check if the item is properly integrated to Downstream systems from Agile ?
We have integration from Agile to EBS through SOA. We are facing issues on integration. Is there any way to see from Agile to check whether the data is integrated to EBS or not ? Like sending data from EBS and updating some status in Agile ? Please help.
The PIP will update a status in Agile indicating the processing completed or not, but only to the extent of what the PIP, or any other integration for that matter, is designed to accomplish. If something is not working per the business rules then the PIP would need to be updated to correct the issue and the Agile update will occur the same as it does now.
Sorry, I assumed when you mentioned the SOA integration that the Oracle PIP (Process Integration Pack) was in use. Is this a home grown SOA integration then? Either way, the issue is the same. If the integration did what it’s supposed to do and it has been fully tested then you can rely upon the integration keeping the data in sync. If that’s not happening, or there are concerns about not trusting the integration, then the integration needs to be further tested or modified to ensure it’s trustworthy.
I don’t know your integration architecture but I am assuming that user action in A9 triggers some code (event based PX ?) which calls REST/SOAP endpoint to send data to external service end point.
If you wish to allow A9 users “check” with one liner showing up in the Web UI, one suggestion is to create action based PX to trigger another service call into the external end point “asking” “hey do you have this valid data?” If you need to display more than a one liner, then write a URL_PX ( basically an external web application) to do the same and display more meaningful data.
I am sorry, I don’t know your level of experience with integration methodology, but the suggested best practice is to at least have one “hub/wrapper” layer that manages the two way verification for you with the external system.
High level example only:
1)A9 has a custom “status” field dedicated to showing integration status.
2) User action or something triggers A9 data to be shared with external system, while the status field get updated
3) The “external system” in our case will be a hub/wrapper that handles the actual interaction with the external system, such that A9 will only have to “talk” to the hub/wrapper
4) the hub does the conversion necessary to interact with the external system, handle request/response and send update back to A9. Depending on the implementation, the hub may call a custom end point in A9 or just update the data field in A9
5) user can later come and check the status.