What is our primary use case?
We use AutoSys to run our scheduled jobs. In terms of the version, I am probably using version 14.
How has it helped my organization?
This type of tool is essential for a data group in terms of how we pick up data from different things and vendors, and how we set up the workflows to do all the jobs. Without it, we can't imagine how we would run all the jobs. If we need something to run on a daily basis, we can use AutoSys to fully automate it. We don't need to have a dedicated resource to look at a job and ensure that it is completed. AutoSys simplifies our life.
What is most valuable?
It is very valuable for us when we are trying to arrange or orchestrate jobs into a system. It is helpful for triggering jobs for a scheduled task.
What needs improvement?
We are trying to see if we can use this from a cloud perspective with AWS, Azure, and other clouds, but it seems that there is no cloud integration in this product. We would like to see cloud integration. We are very pleased with this solution, but we are moving our application to the cloud, and we found out that it doesn't support any cloud features. So, we are trying to find a replacement.
For how long have I used the solution?
I've been using this solution for more than 10 years.
What do I think about the stability of the solution?
It is quite mature. It is pretty good.
What do I think about the scalability of the solution?
We are using AutoSys for very large-scale deployment, and it is very scalable. It is capable of handling 10,000 jobs on a daily basis. It is very good.
We have more than a hundred users, and it is being used at the corporate level. We are trying to use something like this in the cloud. I don't think we are going to expand the usage of AutoSys because we are thinking of moving to the cloud. We are trying to see which solutions provide similar functionality but support the cloud environment.
How are customer service and support?
Their support is very standardized. The application has been out there for quite a long time, and the skillset is generally available in the market.
It is a very mature product, and we require very little support. I don't remember ever contacting their customer support or client support team for any major issues or downtimes.
Which solution did I use previously and why did I switch?
I have been using this solution from day one in this organization.
How was the initial setup?
It depends on the experience. For me, it is very straightforward. In a simple setup, you set up a server, a database, and an agent, and you are ready to go. In a complicated setup, you have to set up high availability, virtual machines clusters, etc.
We have a dedicated group to handle all top-level applications. This is relatively straightforward for them. From planning to implementation and getting it into the production environment, it takes a month or two.
What about the implementation team?
We did it ourselves. To get it rolling and to maintain it, we have a very small team with less than five people. They are just regular developers.
What other advice do I have?
This product has been bought by Broadcom, and Broadcom does not have enough dedicated resources to further develop this product. I don't see any major features, versions, or functions being added to this product in the future. I don't think the vendors would be willing to spend resources on top of it.
I would rate it a nine out of 10. We really like the product and its functions. It works, and we like its stability, scalability, and robustness. It is a very reliable product, but it lacks future enhancements. We haven't heard of any cloud initiative for this product.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
A somewhat surprising review...
CA WAAE will easily scale up to 50,000 jobs a day per single instance and more if the jobs starts are relatively evenly distributed in time. The vendor claim and a quarter of a million with the recent service pack3 improvements (not verified) which introduce new threads for handling agent communications.
The UI (WCC) is relatively poor but will scale up to tens of concurrent users and hundreds of defined views (we have over 300 defined users and over 100 jobflow views per instance). A lot of development effort has been spent by the vendor to improve the UI and this is still on-going. The UI is 24/7, the issues are elsewhere.
Bear in mind that the strength of of CA WAAE (Autosys) is its relative simplicity, which enables both administrators and end users to get up to speed with it quickly and start getting value from it in a matter of days. Therefore it is logical the that UI is always going to be somewhat less rich than some more complex and feature rich products.
As far as stability, yes there are some issues: not so with the UI though but with the application server. Also the security module (EEM) cluster failover seems somewhat unreliable and prone to corruption (for instance if you run out of disk space the settings will get corrupt as some xml settings file get clobbered).
The built-in application cluster is old fashion and a bit slow to fail over. More modern technologies should be considered for resilience.
Re. SLA and deadline monitoring, the base product does lack functionality although the reviewer suggests otherwise. Some useful improvements are in the road map but more importantly this aspect if very well covered by complementary products such as iDash or JAWS.
Lastly on the licencing aspect, this is obviously a matter between the vendor and one's organisation but be informed that there is nothing in the product that will block or preempt any functionality based on licence (expiration or limit etc.), except for some of the advanced agents plugins which do not come out of the box and need to be purchased separately.
I hope this helps