File Library

The case for Groovy-based automation of Essbase administration tasks has been excellently made (see “System Automation the Groovy Way” in the well known publication “Developing Essbase Applications”). Unfortunately, a well constructed argument, even good step-by-step proof-of-concept instructions, do not as if by magic make automation a reality for some of us who have been “converted” and have now been “sent out into world” where the “rubber meets the road” and the going is not easy. This is not the fault of anyone nor of Groovy itself. Even with all its champions, and with all its elegance and simplicity, adopting Groovy still requires confronting and overcoming numerous difficulties. A good strategy is of the essence if one does not want Groovy’s promises of a “better world” to quickly vanish in the air, blown away by frustration and peer indifference.
The strategy consists of finding a way to prioritize a list of existing and/or wish-list automation tasks in such a way that Groovy can start being used immediately, creating momentum and a quick sense that old ways of doing things are not as irreplaceable as once thought. One Groovy script, quickly promoted to production, can be a solid foundation from which to add sophistication and functionality. This is the core strategy followed by the presenter. The presentation demonstrates how simplicity led, by means of gradual steps, to a complete solution without disrupting functionality already in place.