Pros and Cons of ODI in Data Integration

ODI:

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