Table of Contents
Objective
Many unforeseen bottlenecks can arise post deployment of your Oracle Integration Cloud Project to Production. One of the most serious issues is data streaming performance, when data is not available to the target in time it can affect the business synchronization functions.
As there are many components that compose the integration flow, in this high level plan, we shall refer to the ‘Stress Testing’ approach by getting the ‘Typical Processing Times’ as a baseline and have them compared to running the next integrations for a scheduled integration.
The Plan
Important Note
This plan is dedicated for testing of ‘Scheduled Integrations’
Step-by-Step Process
- Determine an Integration’s Typical Processing Times
- Perform ‘Stress Testing’ to your integration project.
- As not all applications support testing automation, you may use scripts to log more data in the source application, and your integration pattern should be pre-set to ‘Schedule’
- Work with your application architect on this so that you can automate an Insert script in a batch / massive way to increase the load to the source application.
- Increase the Test gradually by inserting more number of records / messages until the Integration systems gets blocked. This is the point that shall tell you how the runtime shall go
- Investigate the integration logs to get the reason behind the delay / block
- Find the bottleneck(s) before deployment to Production
- Determine Whether an Integration’s Performance Is Consistent Over Time using the integration cloud dashboard monitoring.
- Find Integration Instances with Increased Processing Times
- Check the Number of Incoming Messages
“When an integration receives a large number of messages to process, Oracle Integration adds the messages to a queue and processes them until it clears the queue. A long queue can impact the overall performance of your system. For example, a retailer might experience higher message volume during a promotion.”
Notes
- During design phase, always try to utilize the Vendor’s API ‘out of the box’.
- Typically a slow target application is the most common cause of slow-running integrations.
References
Oracle® Cloud Using Integrations in Oracle Integration 3
G36915-13
