Redwood RunMyJobs Reviews

It's used for all of our SAP applications. We have ERP, CRM, and data warehousing. It's used for our PeopleSoft, and it's used for some of the other corporate internal applications. Informatica Data Warehousing uses it.

I don't build jobs. I'm part of the team that did the version and the infrastructure part of it. Our teams go through the process definition and the chain definition for the most part, and I believe they do not use the visual process editor.

In terms of deployment, the core of it is SaaS, and you still have some internal servers. It's never 100% SaaS.

Going to a SaaS solution has eliminated some of the down times that we needed to install some of our patches. For our agent servers, we're able to create redundant servers so that we can take one down at a time and not involve any downtime. So far, the various upgrades that we received had extremely short outage durations of one or two minutes. The ability to stay up-to-date and current, both from a security standpoint and from an application enhancement standpoint or bug fixes, has been fabulous as compared to an on-prem solution, which would take a long project to upgrade. That's probably been the biggest benefit. Moving to a SaaS solution has a lot of advantages. When you're running factories and projects 24 hours a day and seven days a week, uptime is very important, and you try to minimize any downtime, even planned downtime.

It has dramatically reduced the time and effort that our organization spends on deployment, updates, and maintenance. With our other application, it would be a six-month project to do a major upgrade. So far, with the upgrades that have been done by Redwood, the downtime is only for a few minutes. There is a gigantic difference.

We're pretty heavy into SAP. They have a good SAP interface where we're able to create and utilize jobs even from SAP, which gives us some additional features. It's about the same on the other applications that are simply running command-type batch jobs, but the SAP interface gives us a lot of flexibility. Some of it's similar to what we already had, but it has a positive impact on us.

It's a very powerful tool. It has a lot of flexibility for how you can define jobs and build them. There are different ways in which you can construct jobs depending on your specific needs and requirements. It has a lot of features for different ways that you can build jobs, which is great for power users but a bit confusing for newcomers because there are a lot of different options. 

It lacks some of the common reporting features. I'm a bit surprised that there aren't some standard reports to be able to extract any data on usage. They've described to us that customers have different reporting needs, so they let them develop those, but reporting is a common need. It would be helpful to have it as part of the solution.

One of our business groups has used Redwood SAP BPA for at least 10 years before I started working with it, and then the rest of our teams moved over from AutoSys to Redwood over the last year and a half.

It has been pretty stable. Performance-wise, we've had to work on it a bit simply because of our volume. That's more with database performance. We haven't had any problems with any jobs because of any bandwidth performance.

So far, it's been good. It scales. As we did the conversion, we did probably eight different deployments or eight different sub-projects to bring various applications live. That part of it scaled very well, with the exception of some of the performance of the database tuning, which took some time, but part of it had to do with the high volume of jobs that we run.

It's deployed across a broad list of applications, across multiple data centers. Its users include business people, developers, and schedulers for jobs. There are hundreds of people who use it.

I have contacted them. I would rate them an eight out of ten at this point.

Positive

Over the last year and a half, we've migrated from AutoSys to Redwood. We switched because of their roadmap and their commitment to keeping the product fresh by patching on a regular basis and providing regular updates. Looking at other competitors, there was also the cost-benefit.

The future of AutoSys was unclear. It was a product that we had used for almost 25 years, but the roadmap was unclear on whether that was going to be a viable product going forward. It put us onto a SaaS product that is definitely more stable and gives us a roadmap into the future for enterprise-wide job scheduling.

Redwood is a little more complex than the AutoSys application we used before. It creates some challenges from the standpoint that there's a two-step process. You build a job and then you schedule the process to run. You build a process definition or a chain definition, whereas, in AutoSys, you do it basically in one step. That part has been a little bit more difficult, but it has given us a lot more flexibility, specifically in terms of the ability to write some very complex calendaring that we couldn't quite do before for the scheduling portion of it.

It was complex. We had a high number of jobs, and we had a percentage of jobs that were very complex in terms of how they were built. Also, we were moving from a system that had been in place for over 20 years. So, you don't always have experts around who understood why it was done that way, but the conversion pretty much brought everything over the way it was executed before.

We spent a year. Part of that was the volume of jobs that we have and the number of teams involved. We've got multiple job scheduling teams by application. We don't have one central team, which made it more difficult from a conversion standpoint. There were a lot of people to train.

As a job scheduling tool, Redwood has reduced the footprint for what's needed. There are still process servers that are required to be inside in order to communicate with SAP and keep the communication inside, which is good from a security standpoint, but the core application is in the cloud. So, we're not responsible for patching the database or patching the core components of the application. This means our upgrades have become very simple because it's a small agent that gets updated during any software release. So, the actual upgrade process is just a few minutes of downtime, which has been a huge benefit. Server-wise, we probably have the same number of internal servers because there are some gateway servers that are utilized, and we've duplicated them and made them redundant so that we can take down and patch them one at a time to minimize any downtime and failover capabilities. Our net is probably similar, but the planned downtime is significantly or exponentially less.

Being hosted on SaaS has reduced the patching requirements that are needed. Any of the connectivity and vulnerability requirements are pretty much handled by the application now, so we don't have to deal with that internally. When you move to a SaaS solution, you're at the wind of the internet, if you will, for final connectivity, but it's not quite as important in job scheduling because your jobs, once they fire off and run, continue to run on the application servers if there is any outage. So, it's not like other applications that are more chatty or require a persistent connection.

We used the Redwood migration team. Our experience with them was good. They are sharp people, and they know their product very well. Alex Borders was the most helpful. He was our lead for the conversion. He had a huge wealth of knowledge.

From our side, there were two of us who worked on it from a standpoint. I worked on it from the technical side, and the other person worked on it from the governance side in terms of whatever we had to change internally process-wise, but each application had its own teams involved in it. So, there were hundreds of people involved in it. Most of it was from the testing and training standpoint for the job support and job processing teams, basically our developers and schedulers.

We're not even a full year into running it yet, so it's a little hard to provide any input about the ROI.

It initially surprised me because we went from an application that was priced by connection to agents/the number of agents to an application that was priced based on the number of job executions. At that time, many of the products we looked at were also priced on job execution. That seems to be more common in the business or in the vendors that provide solutions out there, but that was probably our biggest difference.

An evaluation of other products was done, but we had already used the SAP version of Redwood. So, we were already familiar with its capability. The fact that we already had people who were familiar with supporting it weighed pretty heavily into it.

It's important to do a PoC, take some of your complicated processes, and ensure that your expectations are met.

For the people I work with, the time freed up from using this solution is about the same because we were already using an Enterprise job scheduler. It's probably the same workload. Similarly, the reduction in service interruptions and process failures is the same, but we've drastically cut down our planned downtime. 

I would rate it a nine out of ten.

It provides cloud advantages. 

RunMyJobs is very useful in our case. I'm from an ERP background. We had a hard time running jobs to keep our business alive. This was due to the complex structure and nature of the jobs which tend to move to different systems at each point in time. This was difficult to achieve with traditional SAP software.

We can achieve anything that we would like to do using this solution. In SAP, it's not generally possible with just with SAP. So we have solution manager as an option, but run by job. 

Price-wise, it is not affordable. When we compare with other industry-leading software and even the same scale, there are certain software that can compete with Redwood, but Redwood is very highly paced. 

It is more SAP-friendly, at this point. Since it was owned by SAP for a very long time, they have made it SAP-friendly. But if you look at the tool as an enterprise tool, it is not really that great. You can have better options when you couple it with SAP.

I have been using Redwood RunMyJobs for seven years. 

The solution is highly stable.

It is not a very scalable solution. I would rate the scalability a seven out of ten. 

The technical support does not provide support over the weekend. 

Neutral

The initial setup is straightforward. 

The return on investment is good. 

Even though it is highly-priced, it is a go to SAP product. I rate the overall solution an eight out of ten. 

Redwood provides an advanced form of scheduler that supports multiple applications and workflows by automating the process. This makes room for innovation that helps users to innovate rather than perform a repeated process. 

This being a SaaS automation tool, we benefit from integrating with other technologies across the enterprise and consolidating workflows across different environments. 

It helps us overcome limitations and gaps in complex processes that function between various resources. Process flows can be created and managed well. 

The cloud, data, and file management capabilities are remarkable.

The file transfer, cloud, and data can now be managed well.

Jobs can be scheduled, integrated, and automated without much effort.

There is an opportunity for innovation.

This product is simple and easy to use.

Redwood unifies the process by being user-friendly which makes work simple and easy to navigate across. It patches the gap in complex processes that function between resources. The solution scales and integrates with different technologies. It helps people overcome monotonous and repeated processes by providing the opportunity to innovate and think out of the box. 

It is uniquely designed for maximum benefit and scalability.

Redwood unifies the process by being user-friendly which makes work simple and easy to navigate across.

The product helps people overcome monotonous and repeated processes of work by providing the opportunity to innovate and think out of the box.

I like the following features:

• File transfers, cloud, and data can be managed well
• Jobs can be scheduled, integrated, and automated without much effort
• There is always an opportunity for innovation 
• Simple and easy to use

There is nothing much that the product should improve on except for adding new features. They should provide an easy-to-go-through document for beginners to understand and use the solution hassle-free. 

The product can improve customer service. 

Apart from these, it has impactful and unique features that stand out from any other application used. They are helpful in bringing people out of their comfort zone as they have room for innovation. 

Redwood is primarily used for DevOps automation in our business for agile, functional application delivery. 

It helps in creating logical workflows from the data center to the cloud with automation. Redwood easily manages and coordinates complex processes and automates their interdependencies without manual intervention which is an impressive feature. 

Every step is fully logged and auditable at a process level, without manual intervention. It can visually combine workflow steps into the process chains.

Redwood has helped in automating the scheduled tasks and jobs. 

We can create and test micro-workflows to find defects sooner. Redwood helps in eliminating repetitive and time-consuming manual steps for better productivity. 

The tool is very compatible with multiple CI/CD tools. Every step is fully logged and auditable at a process level, without manual intervention. It can visually combine workflow steps into the process chains. 

It enforces consistent business and IT service standards across the enterprise without extra manual effort.

Redwood Software has many excellent features, including, automating any number of tasks without lagging, and provides multi-tier environments like development, test, and production. 

It has an event-driven automation feature for accurate, complete data and faster results. 

Built-in SLA monitoring allows you to meet your SLA targets and get early warnings for deadline breaches. 

We can create and test micro-workflows to find defects sooner. 

Redwood helps in eliminating repetitive and time-consuming manual steps for better productivity. The tool is very compatible with multiple CI/CD tools.

Redwood Software has a high price tag, especially for small and medium-sized businesses that might not have the funds to engage in a complete automation system. 

The initial setup of the software is quite challenging. There are some difficulties faced during dependencies set up under jobs. 

The customer support and documentation part can be improved for much better response and understanding. A course could be provided on the tool in the market about the importance and usage. 

Apart from the above, Redwood is doing great at its automation and is highly recommended

 I've used the solution for two years.

We did not previously use a different solution.

We did not previously evaluate other options.

We use Redwood Workload Automation for scheduling jobs and for automatic alert generation in case of long-running and failed jobs. 

It provides easy access to managing jobs and controlling the flow of automation. Alerts generated keep us up to date on the long-running jobs as well as failed jobs. 

Configuring the jobs is easy, and scheduling them through redwood makes it very effective for 24-hour monitoring. 

The Redwood support team is very helpful and gives a prompt response and fast resolution when needed.

Scheduling jobs from the Redwood end is a breeze. 

The automated alert response is very useful for long-running and failed jobs during off-business hours. 

A detailed summary of the job and its predecessors can be tracked very effectively using the redwood workload automation tool. Using the tool in day-to-day activities makes the tool very easy to handle work efficiently.

Some of the pros that we received after using the tool were:

• Easier administration of jobs
• Easier job search and error analysis
• Automated alerts help during off-business hours

Some improvements would be:

1. Having a graphical user interface for the dashboard.

2. Better Compatibility with other platforms for logging into the system.

I have been using it for more than a year.

The tool is stable and easy to use.

This is a very scalable, useful tool.

We have always received good support from the Redwood support team.

Positive

The first time using this technology/tool in the industry. I had no prior use of the tool.

I was not a part of the purchasing team.

I was not a part of the purchasing team.

The ROI we have witnessed is based on faster job scheduling and alerts.

I was not part of the purchasing team.

Redwood is very easy for functional users to learn and use. The steps are useful and therefore end user training is easy to deliver.

It is a high-performance, secure, stable, and scalable platform.

Redwood is a great solution to complement and enhance our SAP instance. 

Redwood has good flexibility in automating our own processes using the plug-and-play components from their big library store. One of the most beneficial parts of RunMyJobs is we don't have to support and maintain the infrastructure for the scheduler; it's all in the cloud, so Redwood takes care of that maintenance and upkeep.

Redwood automation helps us to rely on the software to get our core business processes run on time with almost no expected errors. This is time effective, which helps us to meet the client's requirements

A whole lot of jobs can be controlled with just one click, which is time effective. We can control a complex workflow with simple events, which makes life easier

Redwood is of value to our organization due to of its ease of use and the ability to automate and orchestrate any platform that we utilize today. 

Redwood has pre-defined process definitions, a data transformer, a chain diagram of the process, and error handlers.

When something obstructs the job flow, instead of scheduling and running a new job, we can set up tasks in a logical flow that runs automatically during job failures. 

The best thing about the Redwood software's RunMyJobs is it has automated jobs running smoothly with no issues, and automated upgrades are completed in less than five minutes. This makes maintenance very easy.

Redwood software helps to integrate complex processes in a heterogeneous landscape that combines SaaS and on-premise solutions.

Currently, our developers aren't able to access their own objects in the user acceptance testing server and production system server as they are assigned the developer access role, which is kind of a solid role, and no changes or additions can be made to it. In the next release, I would suggest that the access can be limited but accessible by developers

Also, in terms of an outage, this becomes critical since it tasks some time to identify and restore our services with which we fail to reach our Service level agreements.

We highly recommend the product overall.

Redwood Software’s RunMyJobs workload automation solution IT teams can create and run essential scheduled and event-driven processes, manage file and data transfers, and orchestrate automation across applications and other tools like RPA.

Enterprises in every industry, from manufacturing, utility, retail, and biotech to hospitality, banking, and aerospace, rely on Redwood. 

Our low-code automation platform is at the core of critical business operations such as forecasting, replenishment, reconciliation, financial close, order-to-cash, billing, reporting, and more.

Redwood manages the workload of ERP platforms like SAP, Oracle, etc. It also has an additional feature of load balancing through nodes and can restrict the number of jobs running in parallel by entering the execution size limit in the ECC queue.

Redwood manages all complex job workflow processes.

Whenever we are experiencing issues with the Redwood system, we can send log files to the Redwood support team by selecting get support files at the top right corner of the redwood window. Redwood software is supported in almost all web browsers, unlike other software that doesn't support it.

Before, we were using the SAP CPS chronicle tool to schedule batch jobs which doesn't have a user-friendly interface and were not flexible enough to use. Later, when we shifted to Redwood Software everything was hassle-free and we could import hundreds of jobs just using a script. That made our life much easier.

Having multiple options to restrict the use and authority to use Redwood Software to users (user only, scheduler admin, etc) was great. It solved many problems. We can now take reports on how many jobs are running daily, mail alerts for job failures, platform agents connected, and dashboards.

In Redwood, all job-related information can be accessed and downloaded, including job spool lists, job statistics, application logs, etc., which is actually an added advantage for the user to check and analyze the job-related issue.

However, when I check operator messages, there are a lot of messages stuck in the queue. For example, "couldn't send alert" mail to a few recipients. 

The job log has a size limit. 

These are very minor things to look into. If these issues are fixed Redwood, will be in a great position.

The primary use case of Redwood Software in my working environment is that my project includes 24+ applications that are migrated to the cloud as well. We have very complex application flows and integrations. Redwood Workload Automation Edition has helped with application integration. It can integrate with a wide range of applications, including ERP systems, databases, and middleware, which allows organizations to automate end-to-end business processes. 

Also, Redwood has helped in file transfers. It can automate the movement of files between systems, ensuring that data is transferred securely and efficiently. Since our project is also dependent on the cloud, Redwood provides cloud automation which automates the workflows that span across on-premises and cloud environments.

Redwood Workload Automation Edition has helped in improving my organization in numerous ways. 

Our project has complicated workflows and huge tasks to be scheduled. Redwood's features of job scheduling and automation allowed us to schedule and automate batch jobs across multiple platforms and systems, which reduces the manual workload for the employees, saving a lot of time. 

Redwood provides full security while transferring files to different systems. Since ours is a middleware project, the work involves a lot of file movement between different vendors and organizations. By using Redwood, file transfer for the work has been easier and more efficient.

Since my project is a monitoring project, we need to keep an eye on all the applications all the time. The best feature I love about Redwood is the real-time event monitoring and alerting. Redwood can monitor critical business events in real time and can send alerts as well when the predefined thresholds are exceeded. This saves a lot of accountable time for employees and can accurately detect errors with the highest priority, which helps in recognizing and solving the issue within a short span of time. 

Redwood also supports cloud automation to automate workflows between on-premises and the cloud, which is a really cool feature.

The user interface of Redwood can be improved a bit to make it more user-friendly and interesting. Since everything is now updated, it would be better if Redwood's next version release included features involving machine learning and artificial intelligence. 

Since more organizations are migrating to the cloud, it would be beneficial if Redwoood incorporates more cloud-native features such as serverless computing, integration with cloud-native services, and containerization. It would be of added advantage if Redwood could display the workload with visualizations such as flowcharts, bar charts, and process maps which makes the user easy to understand.

I have been using Redwood Software for a period of more than one year.