Oracle Integration Cloud on its own is a tool with nothing to connect. Integration work is moving data between places, so practising it needs the places as well as the tool - somewhere files arrive, somewhere data lands, and something with a screen on it. That is why our OIC plan is not OIC alone.
What comes with it
- Oracle Integration Cloud itself, for building the integrations
- VBCS - Visual Builder, for the application front end
- An ATP database, for data to read from and write to
- FTP access, for file-based flows
Why the ATP database matters
Most real integration work ends in a database. Without one you can build a flow and never see the other end of it, which teaches you the tool and not the job. With ATP you can write a record, query it back, and find out whether your mapping was actually right rather than whether it merely ran.
Why FTP matters
File-based integration is still how a great deal of enterprise data moves - a file lands on a server overnight and something has to pick it up, read it, and do something with it. Practising a scheduled flow that reads a file, transforms it and loads it is only possible if there is somewhere for the file to be.
Why VBCS matters
VBCS is where an integration becomes something a person can use. If you are learning the full path from screen to database rather than the middle of it, you need the screen.
If you need Fusion as well
Integration work against Fusion needs Fusion. The combo plan carries an Oracle Fusion instance - refresh or non-refresh - alongside the OIC instance, so both ends of the integration are yours rather than one end being imagined.
How long to take it for
Terms are 1, 3 and 6 months, and the longer ones cost less per month. Integration practice tends to accumulate - a flow you built last week is the thing you extend this week - so if you are working towards something rather than trying the tool out, the longer terms usually fit better.