To many old fashion JDeveloper developers using Maven is a new and obscure thing as JDeveloper has his own build system and does not require ANT or Maven as a build or deployment tool. However if it goes to continuous integration with many small integration automatic builds done daily than using ANT or Maven is inevitable, of which Maven is newer and more popular. Unfortunately for SOA/OSB 12c developers, other popular IDEs, like NetBeans, Eclipse or IntelliJ have much better Maven support than JDeveloper. Still relaying on his old build and deploy system, and using somewhat hybrid approach on integrating Maven, JDeveloper has a lot of issues when it comes to creating new Maven based projects and build them. Moreover Maven problem does not ends with JDeveloper when it comes to proper working of Maven with OSB architecture but it spans whole Middleware architecture.

Oracle Fusion Middleware provisiong is always a critical prerequisite which will substantially influence the success or failure of our development projects. Those of us who have spent many years working with this toolset in its many versions, should know for sure what a distressful experience it is to work with sloppily or incorrectly provisioned environments.

Using Queues with Delivery Failure

Some days ago I realized that when a message is created through the Admin Console the Queue parameters set to use an Error Destination do not override the message’s parameters, it made me lose time because I thought that my application had a problem. However, the problem was caused because the “Redelivery Limit” set on the message by the Admin Console was no overwritten by the “Redelivery Limit” set in the Queue.

OSB Patching

We have some customers which only use OSB - and not SOA Suite. When you want to patch - should you look only at WLS and OSB-patches? The answer is no.

Ansible is an automation tool that is recognized for be simple and powerful at the same time. From my experience, I can say this is mainly because of its scripting language: YAML, and its agentless architecture.