Author name: makeiteasy

Why using scripts and script automation tools (i.e. Jenkins, IBM UrbanCode, CA Automic, etc) are the wrong approach to DevOps and managing the SDLC for enterprise applications (both SaaS and on-premise). Scripts are (literally) stupid. Frankly, it is somewhat amusing watching all of the hoopla over simple script automation tools as they apply to DevOps.

Reducing Informatica PowerCenter deployment time from 6 1/2 hours to under an hour (almost 90% reduction) means no more need for weekend deployments… …if using Scriptless DevOps. So, we were working with this customer…  we’ll just say they’re a European Financial Services company that is also part of the Fortune 500.  Hopefully we’ll get a chance

Continuous Integration can be a powerful tool in custom software development. It can also be very effective on enterprise applications like SoftwareAG’s webMethods.  However, Continuous Integration should be a tool in your toolbox… but it is not a one-size fits all solution. Before everyone starts piling on saying how crazy we are, let’s talk definitions.

Managing change within the SDLC for enterprise applications like webMethods is actually a very complex challenge which requires it’s own specialized solution.  Deployment is just one step in the overall process.  However, folks are still trying to use scripts to manage the end-to-end process.  Scripts have their place.  They are great for simple, easily repeatable processes.

We currently work with several large enterprises that make heavy use of Informatica PowerCenter.  One of the universal complaints we hear from virtually every customer is that “deployments take a long time.”  Many of the companies that are the heaviest users of PowerCenter are large financial institutions with rigid deployment windows.  For example, if your corporate