With integration projects, one of the biggest drains on time and resource is the unplanned activities, caused by unforeseen issues. The root cause of many of these unforeseen issues is an incorrectly installed and configured middleware platform.
Enterprise scalable middleware platforms are inherently complex; when we consider that an enterprise ready deployment of the Oracle SOA platform requires several hundred steps, then it should not be surprising that when performed manually, it is nearly impossible to get right in one go, and especially difficult to get right consistently across all environments.
Once deployed, we need to manage the requirement to make on-going configuration changes to the Oracle Middleware platform. With each change, we risk making an error that can result in us breaking the platform. We also have the risk that change is not applied consistently, resulting in configuration drift. Which can result in code not behaving as expected in some environments, and time wasted in troubleshooting these issues.
All these issues very quickly have an impact on overall project time frames; with the development or testing team left in a holding pattern waiting for a working environment to be provided or being forced to work with an unstable environment and the suffer the corresponding impact on productivity. As a result, milestones are missed, with the inevitable project delays and cost blowouts.
This paper examines best practice, such as DevOps for the installation, configuration, build and deployment of Oracle Middleware projects, enabling organizations to rapidly, reliably and repeatedly deliver projects faster, with less risk and less cost.