Automic Workload Automation Pros and Cons
Automic Workload Automation Pros
The most valuable feature is the one for SAP batch processing... There are certain other mid-level workload automation tools which can handle the OS level, but SAP is something which is really very critical. Automic stands out from the ordinary tools because handling SAP processes is absolutely easy with it.View full review »
It's easy to use. When you schedule jobs, if you can speak English you can schedule them easily and correctly. Also, there's a lot of flexibility because the product allows you to do many tasks, in multiple ways, so you can choose the way that works best for your environment.View full review »
It works. It does not fail. If something fails, it is not Automic.
It has greatly increased our efficiencies and productivity, and reduced the amount of human interaction required.View full review »
An important feature is the ability to modify PeopleSoft Run Controls at run-time.View full review »
The very special feature that we use is the connection to ServiceNow.View full review »
We automate very manual, robust tasks, which are very time consuming and not error-free.
We impose some standards for backup and restore operations.View full review »
I have found new methods for converting scripts from Dollar U to ONE Automation. For example, I take the dynamic library from Dollar U and put it in the dynamic binary library in ONE Automation. This enables us to use Dollar U scripts in ONE Automation.View full review »
Stability has been great. My team, we call ourselves "the invisibles" because things run so well that sometimes you almost feel like you have to try to break something to actually get acknowledged.View full review »
We have seen improvements in time efficiency and cost resources, because we are mainly focused on the SAP area, and its automation in that part.
We do not have to use a broad variety of agents to connect to different types of systems.View full review »
You can create very fine, granular workflows with a lot of possibilities. It gives you the possibility to do things in many ways.View full review »
Automic Workload Automation Cons
There are certain jobs that are triggered one after another. It would be helpful to have a more user-friendly way of seeing how these jobs are connecting from one server to another.View full review »
They need to handle cross datacenter failover. They have a really good High Availability solution that works well within a single sysplex, but in our environment, since we have two main datacenter locations, we have two separate sysplex.View full review »
It has a very complicated interface, which could be made to be more user-friendly.View full review »
There are some scripting elements that could be added.
Some of the things we don't do are mainly because we don't know how to do them. Hands-on training can be expensive, so we find other ways to work around things to forgo the hands-on training. It is also an issue because we are a Linux shop and most trainers are Windows-based.View full review »
The scalability is limited by the SQL in the background, and that is a problem.
ServiceNow creates problems with the Automic entry of the connector, so the stability could be a little bit better with this product.View full review »
There could be a better user interface for end users. They should make it more intuitive, not based on Java.
With every new version, things that would previously work, Automic breaks them. So, we have to report the new bugs. Therefore, every time when we patch the system, there is usually a new bug or a feature that was working, then it stops working.View full review »
There were many bugs in the last version. For example, we could only use capital letters for searching for agent names. Also, we had a problem with ONE Automation where we couldn't use the PGA and SGA in Oracle Databases for resolving RAM because the last version didn't have this capability.View full review »
We would like to have some features with the AWI with the founding technique, which cannot currently be delivered.
We would like some advantages, which we had with the Java UI, with the automation engine.View full review »
I am heading up the AWI. I desperately miss the possibility to show my read-only users on the Explorer side only their folders, not all the folders.View full review »
The direction in which the UI is going is concerning to me. It does not offer the security context we would need to implement future versions. While I see benefit in the Web UI, the security it would lack in separating a user's experience from an administrator's experience is an issue for us. MFA functionality is required since we're dealing with connectivity to the POS and for PCI/SOX compliance.
An area for improvement would be SQL performance. While tracing SQL traffic, we noticed a lot of commands that cause contention/locks as well as forced waits. The efficiency of the SQL could be greatly improved (in some cases by simply replacing nested Selects and using NOLOCK hints).
I should be able to grant a user access to execute a job without having to directly list every include, prompt set, output scan, script, login, etc. An inherited read for execution purposes would accomplish the same results without making the admin list every single object every time, as well as deny the user the ability to edit.View full review »