Pros and Cons of using ODI in data integration requirements

Batch data integrations can be designed with mapping and Business rules and the solution works seamless with the defined mapping and conversion schedules.

Pros:

• ODI is  for batch data integrations (ETL transactions)
• Appropriate for bulk data integrations and Batch integrations can be scheduled
• Out-of-box integration with databases, ERPs, CRMs, Flat Files
• Lesser cost compared to SOA products as App server is not needed for this only ODI licenses required.
• Good error monitoring systems
• License costs are relatively low (Compared to OSB or SOA)

Cons:

• This is not meant for real-time data integrations

Best to Use When:

• The Applications involved such as Oracle JDE, EBS, Hyperion which have Out of Box Integration features
• Budget is restricted but Flat File Integration is not going to help
• Bulk data integrations are required but need not be real time integrated
• Error monitoring required unlike Flat File Integrations which wont have good error Monitoring
• Inhouse expertize of ODI available
• Complementary Products like Hyperion are already in place with ODI licenses included
• Real-Time data integration is not critical