Utilizing Batch Processing for OIC Integration
Question
One of your downstream applications is becoming overwhelmed with too many individual synchronous invocations from your newly-implemented OIC orchestration-style integration.
It has been recommended that you redesign the integration to take advantage of the batch processing capabilities of the application.
Which OIC approach is appropriate to implement this OIC design best practice? (Choose the best answer.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D.
The best approach to implement the recommended OIC design best practice for this scenario is D. Create a custom batch call with JavaScript, register the library and invoke a Function call.
When an OIC integration makes individual synchronous invocations to a downstream application, it can lead to performance issues, particularly when there are a large number of requests. Batch processing is a way to process multiple requests as a group, which can improve performance by reducing the number of individual invocations.
To implement batch processing in OIC, we can create a custom batch call with JavaScript. This involves creating a JavaScript library that can handle the batching of requests and then invoking a function call to that library within the integration flow. The JavaScript library can be registered within OIC and used in the integration flow.
Using the Append operation of the Stage File action (Option A) is not appropriate for implementing batch processing. The Stage File action is used for reading and writing files, and the Append operation is used to append data to an existing file. This is not related to batch processing.
Defining an Ad-Hoc mapping within a while loop action (Option B) is also not appropriate for implementing batch processing. Ad-Hoc mappings are used to transform data within an integration flow, and while loops are used for iterative processing. While this approach may be useful in some scenarios, it is not directly related to batch processing.
Disabling tracing and message tracking for each invocation (Option C) may improve performance slightly but will not address the underlying issue of individual synchronous invocations. Disabling tracing and message tracking can reduce the overhead of the integration flow, but it will not provide the benefits of batch processing.
Therefore, option D is the best answer as it describes the recommended approach to implementing batch processing in OIC.
