AppWorx Workload Automation Reviews

The primary use case for AppWorx Workload Automation for us is as a distributed platform job scheduler. We use it to set up complex job streams, reporting, and it is cloud-aware, allowing it to operate in a cloud environment. We use the tool to manage workload efficiently.

AppWorx Workload Automation's simplicity and powerful functionality are its most valuable features for us. It allows for efficient workload management and reports on the status of processes, which was a unique feature when it was first introduced. 

The tool now supports complex job streams and is relatively easy for operators and developers to learn. It has great error-handling capabilities and can perform actions like opening tickets for support teams. 

Despite being easy to use, the tool offers high availability and redundancy features, which we have not utilized in our organization but add to the product's capabilities.

AppWorx Workload Automation does not support mainframe environments, which limits its use for larger and older organizations like ours that still rely on mainframes.

We started using AppWorx Workload Automation under its original name, SQLoper, which we adopted back in 1994.

The stability has been very good for us. We have not faced any real issues, and it’s the main reason why we haven't enabled a lot of the redundancy features.

For us, scalability has been good, as we have not experienced any performance issues.

Initially, customer service from Broadcom was problematic for us, however, they have improved significantly. Their current support level is really good, although we have only needed their assistance once.

Positive

Our corporation uses ESP in our mainframe space, but we do not use it in our part of the organization. We have explored other options, but alternatives could not meet our needs.

The initial setup was super straightforward for us. It's a Java-based tool requiring a platform and a database like Oracle or SQL Server.

When we deployed it back in 1994, I was part of a team of four people who were responsible for bringing it in and learning how to set it up.

The return on investment has been very good for us. The product manages workloads efficiently, allowing our operators to learn and operate it quickly, which underscores its value to our business.

The licensing is fair and reasonable for what the product offers. We will soon need to redo our licensing due to changes in our department.

We evaluated another similar product to ESP developed by the originator of ESP. However, the alternative could not match what AppWorx Workload Automation does for us.

I rate AppWorx Workload Automation a nine out of ten. 

There's always room for improvement.

In general, I use Atomic Applications Manager to manage our unique servers in our cloud infrastructure, specifically for support in our manufacturing industry. We are an enterprise and utilize many B2B business units.

Atomic Applications Manager is user-friendly and accommodates around 100 users who can monitor and run their jobs effectively. This transition from manual tasks to automation has significantly improved the efficiency of our processes. 

The UI versions 21.03 and 21.04 are commendable for being completely user-friendly, allowing effortless web-based login, which is a notable improvement from the previous Java-based version.

Currently, I have switched to negotiating through third-party vendors for licensing, which has made it more expensive. Broadcom should address this by dealing directly with customers again. 

Licensing fees have increased as they charge based on executions rather than user agents, causing higher costs. Technical support also involves third-party interactions, complicating direct assistance from Broadcom.

I have had almost six years of experience with this product.

I have had no issues with stability; it has been good.

Technical support is managed by third parties now, which complicates direct customer assistance from Broadcom. Previously, it was handled directly by Broadcom, which was preferable.

Neutral

I previously used a different tool and switched to Atomic Applications Manager for better performance and efficiency.

I was not present during the initial setup, so I am not sure about the experience.

The automation in Atomic Applications Manager has provided a solid return on investment as it has significantly reduced the time required for tasks that were previously manual, such as running batch and online jobs and report submissions.

Compared to other tools, it is now expensive. Licensing now depends on execution counts as opposed to agent counts, leading to increased costs.

I would recommend the product to others in my industry due to its efficiency and advancements. 

Overall, I would rate the product an eight out of ten.

AppWorx is basically a scheduling tool. Users use this as an automation tool. It’s a scheduler where jobs and changes run automatically for the user. Things get automated at their end. We are sort of the AppWorx admins here. We manage the AppWorx setup and everything while the users create, develop, and plan their jobs. They deploy their jobs and handle all the settings, but we are the admins. That's how it goes.

AppWorx is an automation tool. It eases the work of users. For example, in a plant, manual tasks can take a lot of time. Automating these tasks with AppWorx simplifies the work. 

It's a scheduling tool, so job changes and user loads on the AppWorx environment automatically get triggered. Users don't have to manually check again and again. They just schedule their jobs and changes for a particular time, say 12:00 PM tonight, and it will automatically trigger; there is no manual intervention.

Workload automation simplifies things in a much better way. With AppWorx, we can give confidence to the customer/user that we can handle their workload in a secure and private environment. They shouldn't have to worry about their production being impacted or losing money. 

AppWorx gives us a sort of surety that their plant and their loads are safe with us. It's a very secure environment.

AppWorx has simplified things, making them easy not just for the AppWorx admin, but also for those who are new to it. For instance, if people request jobs and chains, and they encounter difficulties or issues, we have a team call to explain how things are done and how to understand AppWorx. This is how we manage it.

First of all, AppWorx isn't limited to Unix or Linux. We can set it up in Windows, AWS, or Azure environments. It's not dependent on any one particular environment.

There are many internal features in AppWorx. For example, there are agents on different servers. Users can have multiple applications and teams, like 10 to 20 applications teams, to run their jobs and chains running on the same master.

Previously, this wasn't possible, but now many users can deploy the App Engine jobs simultaneously. It can run thousands of jobs in a day. Users can choose to share the master or use it independently, which makes handling it very easy. In short, it's easy to handle.

AppWorx leverages AI to improve automation:

We have SOAP agents, also known as AI tools. We create jobs and chains and link them to an AI tool. The triggers happen on our end, but the automation, the workload for which those tools were created, is reflected at the application site. 

For example, if they want to move a shipment from plant 'A' to plant 'B', it's done systematically and automatically with the help of AI linked with AppWorx, without manual intervention. It's done securely, with no manual intervention that could breach the privacy of the application or its users.

Currently, we download a client file from a URL and set up the master. I'd like to see a return to the previous functionality where we could just enter the URL in the browser, and the entire master setup would appear.

The current setup process can be a bit much for users, especially since they have to create a new setup for each master. This can make them hesitant and uneasy.

Other than that, I don't find any issues with AppWorx. It's a good tool.

I still work with it and have about three years of experience.

In general, it's stable. But because it's technology, we also have issues on our side sometimes. 

Sometimes, there are connectivity issues, which aren't the fault of AppWorx but rather server-related. It takes about five to ten minutes to reboot and get things flowing again. So it's good, but at times, we feel things could be improved.

It is a scalable product. 

In AppWorx, we have around 13 to 14 people. In our workload, we are the only AppWorx admin team. However, there are many other application teams across the world for whom we are the AppWorx admin.

Broadcom's technical support has been really good. Whenever we've had an issue and raised a case, they've come to our support, whether it's day or night, 24/7.

Deployment is not complex, but it requires knowledge to ensure you're on the right path. It comes with experience, and Broadcom provides helpful manuals that are easy to understand.

The documents provided by Broadcom are very useful. If we have any doubts, we can go through those documents. If we encounter an error, we can often find that Broadcom has resolved it in the past for other teams.

While technology can be complex in every sense, once you get used to it, it becomes easier.

Deployment model:

We have a variety of sources. Some are on the FTDC (data center), and some are on the workload. We have a mix of everything, and we don't experience any problems with this setup.

Deployment time:

The deployment time depends. Sometimes, different teams want to go through each process with a deadline, so it might take a week or even three weeks. But at our end, if something comes up, it usually doesn't take more than a day or two.

Deployment resources:

One or two people are more than sufficient to deploy, if it's within their shift or timeframe.

In our environment, we have databases running on AppWorx, along with other Unix/Linux features. We also establish AppWorx connectivity with other applications. It's easy to use in combination with Splunk services, Dynatrace, or other AI tools.

Maintenance:

Every server and tool requires monthly maintenance, if not weekly, to maintain uptime and ensure things run smoothly and efficiently. AppWorx is no exception and requires maintenance.

There's the migration feature. We have a lower environment (testing) and a production environment. Users don't need to recreate what they create in the lower environment in production. 

The automation of jobs and chains saves a lot of time for users during development, testing, and production. This migration feature simplifies work and is very time-efficient, safe, and secure.

It saves a lot of time. Without it, users might have to create their jobs in the lower environment for a week and then test it out for another week. It sort of easifies and simplifies things and makes them more time-efficient so everything can be done in a day or two, rather than taking a month.

It's good. I haven't heard any complaints. It's a very cost-efficient tool with high availability, so no issues there.

AppWorx is a good option if you want to: 

• automate your workload, 
• make things more time-efficient, 
• make things to be more secure, and with minimal manual intervention,
• want things to be done at varied times. For example, if you have a sort of shipment which has to go at twelve o'clock, and because of this, some of the reason it's going at one o'clock. So, AppWorx maintains that if something has to be triggered at twelve, then it will get triggered at twelve.

So, I would suggest anyone to give AppWorx a try. It's very efficient and time-efficient.

Overall, I would rate it a ten out of ten, with one being worst and ten being best. 

I use the solution in my company for monitoring, scheduling, and creating jobs as per our requirements. The product's daily load is the same, so it is used for monitoring because all the jobs are on a revenue basis, meaning they generate revenue or returns.

Though it has been over nine months that I have been working with the product, I don't know much about the tool's features. It is usually used for scheduling notifications, specifically email notifications. Whenever a new job is created in the tool, its users get notifications via email.

If there is a time out that happens at the tool's end, then we, as users of the product, are not able to login to the GUI. Recently, my company faced an issue where we were not able to log into the product's GUI, and the reason was that the database session got logged out at the DB's end. After AppWorx released the aforementioned session, the users in my company were able to log in to the product. With the tool, I did not face any major issues which required escalations.

I have experience with AppWorx Workload Automation for the last nine months. My company uses the tool.

My teammates have connected with the product's support team, but since our company does not have a certain agreement or license, AppWorx did not provide us with any support when we needed it. This became one of the major reasons why my company decided to move to another product. I rate the technical support a ten out of ten.

Positive

I have worked with integration tools like Dell Boomi, MuleSoft, and TIBCO. For the last nine to ten months, I have been working with AppWorx Workload Automation.

The product's initial setup phase was easy. When I started to use the product, I saw that the configuration part was very easy to manage, and it did not take much time either. The VDI access is an area that is difficult to manage in the product, but AppWorx's configuration and deployment areas are easy.

The solution can be deployed in an hour.

The benefits from the use of the product revolve around the fact that it helps with monitoring and sending out notifications. My company created the jobs, and we only took care of the automation and provided the schedules. In short, my company has only created jobs. On a daily basis, we use the product to do patching of our company's backup servers. My company applies Java patches from Oracle to the tool on a monthly basis.

My company does not want to renew the license for AppWorx Workload Automation. My company plans to move to a new tool. For the past seven to eight years, I know that my company has been using AppWorx Workload Automation.

I have been searching for a tool, which can fulfill my current requirements with its functionalities and offers a competitively good solution. Actually, my company does not want to renew our license with Broadcom for automation tools. Yeah. My company and managers decided to change the tool, and upgrade to another product.

My company is satisfied with the functionalities offered by AppWorx Workload Automation. My company and my manager decided to switch from AppWorx Workload Automation to another product, so it is a decision coming from upper management, and I have been assigned the task of creating an analysis report of the tools available in the market.

My company did not do any process automations with the tool. My company is just monitoring whatever existing jobs are there in our environment. If we are getting any requirements from our company's IT team, we create those jobs in the tool.

The product does support our industry's standard compliances.

My company does not currently have any requirements for using AI. We just want to migrate our existing infrastructure into a new tool. The tool's scope is very limited for our company.

I would definitely recommend the product to others since it is a stable solution. The issue that I faced in my company with the product is one of the major drawbacks of the product that AppWorx needs to look into because if you are not able to log in, then it could escalate as a big issue in the organization. GUI-wise, there are no such issues with the product, and the configuration is visible.

Considering that the product needs to work on the graphical representation area, I rate the tool a seven out of ten.

Our company uses the solution for electronic automations. We have 300 users, a few use cases on-premises, and a few use cases on the cloud. 

The solution is very user friendly so anyone can use it. 

The user finance module is a key feature.

The scheduling tool is very valuable. 

The graphical interface is pretty cool but not the best so it could use some improvement.  

I have been using the solution for five years. 

The solution is stable but comparatively could be improved. Stability is rated a seven out of ten. 

The solution is scalable but could be even better. Scalability is rated a seven out of ten. 

Technical support is good so is rated a ten out of ten.

Positive

The setup is pretty straightforward so is rated an eight out of ten. 

We implement the solution in-house. Four staff members can deploy the solution in one business day. 

The price for annual licenses is a bit expensive so pricing is rated a two out of ten. 

The solution is a good product so I rate it a nine out of ten. 

I would describe myself as a manager who focuses on the big picture. I am aware that we possess a technology that we use to perform tasks, but my knowledge of its functionality is limited. This technology was implemented as a resolution when we acquired our ERP system.

My knowledge about it is limited and I lack specific details about the topic.

As a high-level individual, I am interested in understanding the upgrade process of Atomic from AppWorx, including the differences between the two and their respective features.

We were looking at a demo of Autonomy from Broadcom.

We have a lot of nightly jobs that need to be run. Therefore, we perform a lot of calculations and processes during nighttime hours.

We are looking for additional features that would allow us to call APIs and integrate the product with other tools more effectively.

We are currently using AppWorx Workload Automation.

AppWorx Workload Automation is quite stable.

There were no issues with the scalability of AppWorx Workload Automation.

Because I am in a high-level position, I cannot provide a detailed assessment of technical support. However, based on my personal experience, I thought the technical support was good.

I would rate the technical support a seven out of ten.

The initial setup may have appeared complex from an outsider's perspective.

The deployment likely took several months to complete.

We had a team of three administrators involved in completing the deployment.

I would rate AppWorx Workload Automation an eight out of ten.

AppWorx Workload Automation is used for allowing passwords and fund management systems. It is mostly used in retail and higher education.

The most valuable features of AppWorx Workload Automation are simplicity and reliability. Additionally, they recently transformed the UI which is better.

The scalability could improve.

I have used AppWorx Workload Automation for approximately five years.

The solution is highly stable.

I rate the stability of AppWorx Workload Automation a ten out of ten.

The scalability could improve because they do not have Kubernetes options.

We have 10 customers in the middle east and more globally.

I rate the scalability of AppWorx Workload Automation an eight out of ten.

The support from the vendor is brilliant.

The initial setup of AppWorx Workload Automation is simple. It can be done on Linux or Microsoft Windows.

All of these tools require some administrator's access to complex the deployment. For example, deploying them with databases.

We use one or two people for the deployment and maintenance of the solution.

The cost model is based on the number of orchestrated systems used.

I would recommend to others they update the solution for more functionality.

I rate AppWorx Workload Automation an eight out of ten.

Our primary use case for this solution is to schedule our batch, applications and data warehouse batches automatically. I'm an enterprise application architect and we're a customer of AppWorx. 

The most valuable feature for me is the scheduling. 

This solution could be improved in the areas of reporting, forecasting, and intelligence. In addition, the portability and deployment, artificial intelligence and machine learning, whether it's integrated or embedded, could also be improved. These things would help me to know the SLAs for when a job will end. 

I've been using this solution for close to 10 years. 

I would rate this solution as six out of 10. 

We use this solution for compliance purposes.

The interface is good.

The compliance-related features are very good.

The compliance features are limited to the server and not the entire infrastructure.

I have been using CA Automic Applications Manager for between two and four years.

We have approximately ten people who are using this solution in our company. We do not yet have plans to increase our usage.

We have not had to contact technical support.

We are satisfied with the pricing.

The primary use case is process automation and orchestration.

It has improved my organization through automation of back office and infrastructure procedures, and by integrating and orchestrating key business applications spanning multiple technology stacks.

It is an object-based approach to task and process design in conjunction with conditional logic and event-based scheduling actions, which enables a build once/use often design methodology to be employed, producing automated processes capable of dynamically adapting task flow according to events occurring before/during process execution.

• The user interface (UI) could be modernised. 
• The internal security model can be complex when configuring multiple user groups. 
• It is difficult to integrate with the Active Directory (AD).

Earlier versions of the product suffered some stability issues. The more recent versions of this product are stable.

We have encountered no scalability issues with the product.

We have not needed to use technical support services for some time.

Our previous solution was not scalable.

It has a straightforward initial setup.

Licensing options are fairly straightforward.

I can't recall the products which were evaluated.

It is a good product. As a general process automation and integration tool, it has been superseded by other offerings, notably the Workload Automation suite.