In this post, we will apply the finishing touches to our integration. You can find the earlier parts here and here. One of the things you also need to set up on your integration, is a tracking parameter. This is a mandatory step, and can be done from the Tracking page.
I just used the start time, as the tracking variable.
Now, we should be done dealing with all the errors and warnings. In order to run this package, we need to activate it. Conversely, if you need to edit the integration again, you need to de-activate it.
This takes a few seconds. The same menu also gives you the option to run the job.
You can check the status of the run from the link that pops up. The start time that we set up as the tracking variable is displayed from the run status. This tells you that you can add more information, as needed.
Finally, if we check our FTP directory, we can see our variables file.
And if we open it up, we can see our list of variables.
One of the other cool things with OIC, is the ready availability for external executions, using OIC’s REST API. Each job has its own execution URL. We can grab this from OIC:
You can now go to your favorite REST client (I am using Boomerang in this case) and plop it on there.
Make sure to add the “NOW” parameter in the body, as shown in the documentation. We also need to add the authentication credentials.
And if you submit this “POST” action, the job should execute on OIC.
All things considered, I am very impressed with OIC. I think Oracle has done an excellent job with this tool. If you like ODI (like I do), I think you will be really impressed with OIC. It has some similar concepts, but the ease of use for cloud applications is superior, in my humble opinion.