07-30-2007 04:36 PM
We need to propose a scheduler software to our client.We are thinking of either Autosys or Control-M. Do Someone have evaluation/comparison document of these softwares. Advantgaes and disadvantages between two of them etc..
Which one to use and why ---this is the kind of presentation we need to show to our client.
07-31-2007 01:40 AM
First one (even though its blocked here) states:
Whither Autosys?They put me on a team to evaluate AutoSys vs. Maestro, having heard that AutoSys might ... Can anyone tell me the difference between Control-M and Autosys. ...
I'm guessing if you pick through some of those links from the search you can find some information.
07-31-2007 01:53 AM
If the customer is also a user of HP Openview Operations (OVO), you might also want to look at Dollar Universe from ORSYP, as this is integrated with OVO.
07-31-2007 11:44 AM
The only thing I can suggest you do first is enquire not only about features but about the pricing, especially long-term. Try to squeeze your reseller or vendor into getting a contract that will last a while, or whatever can be done to prevent being chewed off once you're locked in with thousands of jobs and can't switch to another product.
08-01-2007 01:55 AM
That being said, I've heard they changed the way they price it out to make it more appealing I guess.
I guess the pros:
Just from working with Autosys the last few places I've worked. It's easy to configure the server once the shell of a database is created.
Installation of the client is just as easy.
If for some reason your dialed in on a lowspeed connection, the commands are easy to use and easy to manipulate jobs.
Oracle adapter is easy to use, nothing special needs to be added other then one binary.
AS400 adapter is easy to configure from the unix side (if that is where your going to run it). I'm not sure how easy the client is to install since I've never worked on an AS400.
Cons for us were:
Grainularity of security. We wish you could do more, without having to install their E-Trust package. I believe at one time was SeOS. Which seems like overkill considering the original software package was to secure OS commands. When the only small piece we wanted to use was to secure who can do what with which jobs.