-by Joe Goldberg, Solutions Marketing Manager, Control-M Solutions Marketing, BMC Software Inc.
You’re implementing a new application and you have either downloaded a new Application Integrator job type from the Application Hub or built a job type for it. How is your life better than if you had not done that?
You can build a Connection Profile which contains all the general information about your application such as which server it’s on, which ports or libraries it uses and any credentials that may be required to run its jobs.
This means none of your jobs have to specify this detailed information and if it ever changes, you just update the connection profile instead of tons of jobs or scripts.
Your auditors and ultimately your management love you because you don’t fail audits and you don’t expose potentially sensitive and thus dangerous information.
When you build jobs, it’s IDENTICAL to the way you build jobs today. Grab the job type from the job palette and drop it into the flow wherever you need it. The forms ensure you specify correct application characteristics because you can select from a list that is retrieved from the application in real time. And if you ever need help with a particular application, the information as to which person or group for you to contact for support is part of the job type. If you use Control-M Workload Change Manager, you can even specify site standards so that these application jobs are built correctly and in adherence to your operational requirements.
When you are running these jobs and someone in the business tells you to hold all jobs for “application x”? NO SWEAT! Find, filter or create a viewpoint (your choice) that shows you all the jobs in the active environment for that application and hold them or delete them or whatever you need to do. Because Application Integrator created a new “job type” you can search for it easily. And if that same person in the business told you to change something in a bunch of those jobs? You can use Find and Update to do that quickly.
What about looking at output when something fails? Well, if your developers wrote their own scripts, they probably put the output somewhere where they can get it. The problem is the person analyzing the current problem may not know where that is or worse not have access to it. And each script could be different and your developers spent a lot of time writing that code. Tell them they don’t have to bother because Control-M will take care of it for them when flows are built using Control-M job types instead of scripts that run as “black boxes”.
Finally, considering you are probably seeing more and more new applications and they’re coming at a faster and faster rate, all the above benefits may sound better and better.
So why not visit the Application Hub today and grab a new job type for a new application you are implementing. If there isn’t one there, perhaps you can build it and help the next person who may need that very same job type. Remember, you have the technology!
The postings in this blog are my own and do not necessarily represent the opinions or positions of BMC