Automic Workload Automation Initial Setup

Vinit Choudahry
Technical Consultant at a tech services company with 10,001+ employees
I haven't done the initial setup, but I think it's pretty straightforward from what I have seen in the documents. My feeling is it should not take more than an hour or two to get it up and running. If everything is ready, your database is there, and you have the right amount of resources on the server, it shouldn't take more than an hour or two hours. In terms of an implementation strategy: * You should have a database. * You need to figure out what components you're going to go for. * You need an estimation of the number of jobs you are looking for to plan out the resources on the server. * Finally, you need to think about how you will roll out access to the users: a thick client or a web console. Those are the things that need to be factored in before beginning the installation. The accessibility part can be dealt with later, but the resourcing of the database on the server and the management server have to be spec'd out before. View full review »
Sr Production Control Analyst at a logistics company with 10,001+ employees
I believe it's pretty straightforward. It's a complex thing by nature so it's not going to be super simple, but it's not like you can't do it either. I believe experience helps. And in our case, we had a lot of help from the vendor, so while we, per se, didn't have the experience, there were people helping to get us going that did have the experience. So maybe I'm underestimating how much that was important, because it was available, even though it wasn't coming from me or one of my team members, but somebody else was providing it. View full review »
Irvin Carney
DevOps Engineer at 84.51
I was heavily involved in the initial setup. It was December 2015 that we had to migrate our entire workload automation suite of 1000s of jobs. We are publishing petabytes worth of data into this big relational data warehouse, publishings, all these different applications. We probably received 2000 files per week, and probably had 5000 jobs per week. Therefore, we had to migrate all that from one solution to another solution in 60 days. It was a contract thing that was going on, so we had to do it and I was heavily involved. We had some professional services people come down and we found out about it in mid-December and we were done by the first week of February. So, it was a heroic effort, but we did it. View full review »
Find out what your peers are saying about CA Technologies, BMC, IBM and others in Workload Automation. Updated: August 2019.
365,423 professionals have used our research since 2012.
Marc Massie
Data Operations Lead at 84.51
We changed out from Chronicle to Automic in 90 days, without a single outage to our business. That has never been done with Automic. The Automic people were even saying, "How the heck did y'all do that?" But we had some people from Automic, this was before CA bought them out. Some guys from Automic came over to our site, stayed in Cincinnati for a couple weeks, to help us with this initial setup, because it was such a time crunch. We had 90 days to get it in, and we had to pull the switch on Chronicle, or else it was going to cost us $1.5 million. It was a big time crunch, and they helped us get it in, get it working. We did not have any outage, we did not miss any Loyal Customer campaigns. Nobody missed the coupons because of our switch to Automic. View full review »
Ruairi Brennan
IT Manager at ESB
I was not involved in the initial setup. View full review »
Christine Bauder
Assistant Director of Production Services
The initial setup of Automic is simple and easy. As long as it can talk to what it needs to talk to, there are no issues with the installation. View full review »
Technical Architect at a financial services firm with 1,001-5,000 employees
I was not involved in the initial setup, but I have been involved in the current upgrade process. The current upgrade process is straightforward. They have made the process much simpler. After we get to version 12 and any subsequent versions going forward, it should not require any downtime at all. It should not require any system reboots for the upgrade of other components outside of the engine itself, such as the agents. View full review »
Eric Felker
Software Engineer at a media company with 10,001+ employees
Initially, is it hard to set up? I don't really think so. I've been working with it for a while now. Once you understand how something works, it becomes pretty easy. I'll say this, support team there have been really great, very enthusiastic. Will answer your questions, and that helps a lot. A lot of it is, you don't know what you don't know. Once you do, you've got it figured out. In terms of upgrading, it's very database-driven. You have to upgrade the database, and then just replace binaries, new software. View full review »
IT Specialist Automation Service Coordinator at a financial services firm with 1,001-5,000 employees
I was responsible to design and build the system. The project was an agile project, which was a pilot, because our company was not very agile. While we are a public institution, we are very old school. This was a first attempt at doing new things. I was the only technical resource that had the proper knowledge and skills. Therefore, I was the one who designed the system and build it. The initial setup was complex, because of our specific requirements. View full review »
Mohamed Elazzouzi
Production Systems Engineer at Sofrecom
The initial setup required us to do an analysis of the Dollar U environment for conversion to ONE Automation. We have special tools for converting the session and the UPROCs from Dollar U to jobs and workflow in ONE Automation. We have developed macros with VBA to convert all the information in Dollar U to ONE Automation. When we start an integration for the first time, we create the client and we attach the agent for the application, because every application is a "client" for us. We use Red Hat Servers for this. Of course, we use Windows servers, but 80 percent are Red Hat as well as iX and HPE servers. Each application takes a different amount of time. For example, there are applications for factoring or financial applications. We need one year for their implementation. Smaller applications take a few months. We start with the small applications and then move to the more difficult applications. We have a team working on this and every person has ten or 15 applications to do. View full review »
Jared Kessans
Lead Systems Administrator at Great American Insurance
I wasn't involved in the initial setup. I actually used it from an operator's standpoint. I did not start maintaining the system until about a year and a half after we brought this system in. View full review »
Axel Lambrecht
Systems Engineer at Merck KGaA
The people involved in the initial setup were convinced that they had the right product and absolutely satisfied with the setup in 2001. View full review »
Systems Engineer at a tech services company
The initial setup was very complex. This company and the one that I worked at before found the very first migration from whole systems, like TWS, to the Automic product challenging. They were not used to all the features that it had. Though, I did not hear a lot of complaints about it. View full review »
VInce Sola
Manager, Application Administration at a leisure / travel company with 1,001-5,000 employees
The initial setup was very straightforward. The consulting team for implementation was great to work with and taught us the system very well. View full review »
Aicke Sandrock
Engineering Job Scheduling at IT S Care
I did it 13 years ago at different companies. In the past, we did not use the wizard. We set up the components standalone, then combined them in configuration. It was easy and well documented. Presently, there is a problem with the translation. It is some type of hybrid. We have some parts in German and some in English. It should be completely in German and completely in English. It should be better in the future. View full review »
If I work with a customer (as a consultant), they do not want a straightforward setup. Therefore, I have not seen an out-of-the-box setup, because I have not seen a normal implementation. View full review »
Ali Imran
Head of Branchless Banking at a financial services firm with 5,001-10,000 employees
The implementation was not straightforward, though it is not that complex. During installation, some database elective issues popped up. These took some time to fix, but after some back and forth communication, these issues were resolved. View full review »
UC4 Administrator at a financial services firm
The complexity of the initial setup depends on the person who is performing it. It was okay for me, but I have some colleagues who have had some problems with it. View full review »
Martin Mertens
Manager of Global Process Automation at Adidas Group
During our PoC, I was the guy who was implementing and installing the product. I thought with the help of a consultant that it was an easy installation. View full review »
Eric Gauthier
Senior System Engineer at BECU
I was involved in the initial setup. The software itself was pretty straightforward. We converted from the Application Manager Platform to the One Automation Platform, and it was a little complex to get our jobs migrated over. Once they were migrated over, it was pretty straightforward. The software itself was pretty straightforward to install and get going. View full review »
Mladen Stankovic
Systems engineer at a comms service provider with 5,001-10,000 employees
The initial setup was straightforward. The installation took two days. We did not have any difficulties. You just click, click, and click. View full review »
Unix Administrator at a manufacturing company with 1,001-5,000 employees
I was initial in the initial setup. It was complex. We had a person come in from CA and assist us with the setup. It went smoothly. It took us about a week to get it up and running. However, it has been up and running, and we have not had any real issues with it since. We still actually have not implemented this version as it is in its test phase. View full review »
Alain Feyereisen
Application Operating Service Manager at a financial services firm with 201-500 employees
Implementing the solution in 2009, the setup was easy (straightforward). Other parts, meaning implementation of all the processes, this was very complex. We had to think about steps, like name conventions, standards to introduce, common objects the users should use, and the training that users should receive about how to use the product. View full review »
Adrian Northage
Automic Admin at IT Service Solutions Service Delivery
The initial setup is relatively straightforward. There is an awful lot of planning because it is such a critical application for us. We have to test everything before we go ahead. It could take us up to three months doing all of the testing, maybe putting the infrastructure in place for an upgrade. The actual day when we upgrade only takes about an hour or so. It is very fast, and we have never had an issues. View full review »
Automation Admin
We have using Automic for long time. From the first step, you need to have time to install it. When you want to use the entirety of Automic, it is heavy. In the beginning, our administration chief told us to use 10 percent of your time for Automic administration. Now, we are using 100 percent (our entire job); it is a full-time job. Our systems are not that big. When we have trouble or have updates, it is a full-time job. We must talk with other teams. We must see that the hotfixes are updated. This cannot be done in ten minutes as some modules and add-ons come together, and we must see how to orchestrate it within our company. We must look at these things, which are part of the company, see how they can be used. We spend a lot of time of this. View full review »
Lead Production Control Specialist at SAIF Corporation
It was good. We had customer support who came onsite to install it and to train everybody and I was right there. It's mainly a product for our department, and then, as an administrator, we assign everybody, all the users and train them. View full review »
Archive And Research And Development Lead at a manufacturing company with 10,001+ employees
I'd say complex from the side that I don't know, where they have to set up, from our operations group, the servers and all that. That's beyond me. View full review »
Systems Analyst at a tech services company
The initial setup was complicated and difficult. View full review »
Rolf-Peter Langer
Admin Developer And SAP Admin at a wholesaler/distributor
The initial setup is easy and straightforward. I did it over 20 years ago. View full review »
Matthias Wanke
Automation Engineer at Ing-Diba Ag
The initial setup was 10 years ago, so it was easy at the time. With each upgrade, it will probably have more complexity, but it has been a little hidden because it is a step-by-step process. Though, the complexity is okay with the setup. View full review »
Enzo Fusco
Systems Engineer at Consoft Systemi
The initial setup was quite simple because they have a manual which tells you in a simple way of how to install it step-by-step. Therefore, I didn't have any problems. You do need to have a background in operating systems, then it is not so difficult to install. View full review »
Senior Programmer at a manufacturing company with 1,001-5,000 employees
It was straightforward. We made it difficult on ourselves at the time. We have recently changed and made it simpler. As regards to a mixed environment, it was fine. View full review »
Bartlomiej Stawecki
Consultant at Project Management.Pl
The application is straightforward to setup. What is sometimes challenging is making the application fit into the customers' environment. They may have some restrictions and restraints that we need to consider and also need to understand how to prepare. Therefore, it is rather an organizational challenge rather than a technical one. View full review »
Associate Director at Pbb Deutsche
The initial setup was straightforward. With outsourcing, it made it simple. View full review »
Ryan Bryers
UK CTO with 5,001-10,000 employees
We spun it up during a weekend. View full review »
Senior Systems Engineer at a non-tech company with 11-50 employees
Sometimes it was simple, and other times, it was very difficult. However, we had good technical support from Automic designing our system. View full review »
Erwin Antona
User at Aci
Straightforward. View full review »
Yalin Yuksel
System Specialist at Türkiye İş Bankası
In the beginning, it is hard. We did not know how to deal with things. However, when the process is ongoing, it is very easy to set up and build infrastructure on Automic. View full review »
I was not involved with the initial setup. View full review »
Hesham ElSheikha
Workload Automation Expert at a financial services firm with 5,001-10,000 employees
If the environment is straightforward, then the initial setup will be straightforward. View full review »
Wolfgang Tappert
Consultant at a tech vendor with 201-500 employees
It is straightforward for me. Those new to this business find the initial setup complex. It is a complex product, so you can't do the setup with a click. View full review »
Achim Henkman
Service Management at Siemens Industry
The initial setup was easy. We have used it for 20 years, so we set it up in a special way. We were installation number 30 for this product. We have been working with it for a long time. View full review »
Systems Administrator at Athene Deutschland Service Gmbh
Our migration from a previous system was not easy. However, when we did a new implementation that was easy. View full review »
Norbert Bollinger
Production Services at a government with 1,001-5,000 employees
I was not involved in the initial setup. View full review »
Roman Rauchwarter
Systems Analyst at a tech services company with 1-10 employees
The initial setup was straightforward. View full review »
Find out what your peers are saying about CA Technologies, BMC, IBM and others in Workload Automation. Updated: August 2019.
365,423 professionals have used our research since 2012.
Sign Up with Email