Issue: A 404 Not Found error occurs when dynamically calling a local integration within a project in OIC.
Error details:
CloudInvocationException (Fault Details:
<n30:type/>
<n30:APIInvocationError xmlns:n30="http://xmlns.oracle.com/cloud/generic/rest/fault/collocatedics/LocalIntegration CallNextIntegration">
<n30:title/>
<n30:detail/>
<n30:errorCode/>
<na:errorDetails>>
<n30:type>http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5</ns0:type>
<n30:title>Not Found</ns0:title>
<ns:errorCode>404</ns):errorCode>
<nao:errorPath><! [CDATA[Inbound JaxrsResponse(context=ClientResponse(method=POST, uri=http://rest-adapter:8080/ic/api/integration/vi/flows/rest/INT324_HCM_CCS_NEWHIR MAIN/1.0/NewHireEmpElecAllow/main, status=404, reason Not Found)}]] ></n30:errorPath>
<n30:instance><! [CDATA[Please check the URL and try again. There are no currently active integrations serving /ic/api/integration/vi/flows/rest/INT324_HCM_CCS_NEWHIRMAIN/1.0/NewHireEmpElecAllow/main. The HTTP 404, 404 Not Found, and 404 error message is a Hypertext Transfer Protocol (HTTP) standard response code, in computer network communications, to indicate that the client was able to communicate with a given server, but the server could not find the resource that was requested. Carefully re-examine the target endpoint that is being called. )></n30:instance></nao:errorDetails></n50: APIInvocationError> ]
Solution:
Ensure that the Project Code, Integration Code, and Version are correctly mapped in the invoke action using a Lookup.
Steps:
- Open the integration where the local call is being made.
- Use a Lookup to dynamically fetch the Project Code, Integration Code, and Version.
- Ensure the endpoint URL is correctly formed using these values.
- Verify that the lookup values match the actual integration details in the project.
- Save, activate, and test the integration again.
This ensures dynamic mapping and avoids hardcoded values, resolving the 404 error.
No comments:
Post a Comment