1 2 Previous Next 17 Replies Latest reply on Sep 18, 2019 2:58 PM by Robert Stinnett Go to original post
      • 15. Re: Jobs as code
        Robert Stinnett



        We were in the same boat for a long time with WCM.  Now that the web client is being fully developed out, we are starting to get more people looking at it.  We found that one of the best ways to show value was with promotion rules.  Even if you still have folks using the traditional client you can put promotion rules into place and that really goes a long way to help enforce those standards, etc.



        1 of 1 people found this helpful
        • 16. Re: Jobs as code
          Mike Landis

          Everyone this has been very helpful. Each response I read helps me think of new questions.

          Was your developers asking for the ability to create their own jobs? or was it mandated by management?

          Does it allow your Schedulers/Operators more time to focus on production control?  Or did you trade building jobs with verifying developers work and configuring of standards and security?

          • 17. Re: Jobs as code
            Robert Stinnett

            Mike ,


            When we started down this road a few years ago (back when they introduced the pre-1.0 release of Automation API!) nobody was asking for it, it was more seeing the writing on the wall.  Applications were getting more and more open via APIs and interfaces, and one of the things that I personally believed for many years is that Control-M had the potential to be a powerful engine that could drive many applications.  I knew that if I could present our developers a way to easily utilize the "automation services" then they would consume it like crazy -- and I was right!


            It really started out by working with developer allies and showing them a few things, and constantly promoting the possibilities.  Over time, I found that the developers started to want to work more 1:1 (aka, DevOps!) and actually learn and listen.  I was very good at listening to what they needed at a high level and then helped them discover how to use Automation API to make that happen.


            The biggest thing, and I cannot stress this enough, is to be able to provide an environment where your devs and other folks can tinker with it without running into security roadblocks.  This might be the Workbench for some, or (and my recommendation) spinning up a training environment for them.


            Long story short, I did not want to spend the rest of my life building jobs -- something I'd spent years getting away from -- and I knew that even with all the constant IT change and technology shifts going on around us, products like Control-M not only have a place in modern IT, but can play a crucial role.  So I decided it was up to me to be the person who could lead our company forward in making this happen.  Better to ask forgiveness than permission!


            If you are at the New York Exchange conference, I'd be glad to talk more about this with anyone!  Just drop me a line.



            2 of 2 people found this helpful
            1 2 Previous Next