Redwood Workload Automation

Formerly RunMyJobs

The system lets you run tasks in parallel to reduce overall runtime, unlike the built-in scheduler in SAP. You can also set your multi-step job so that if a step fails, follow-on steps will still run...again unlike the SAP scheduler. It's also very easy to set up calendar-based jobs, for example, those that should only run during a month-end week. There are many other scheduling options available.

Things we don't run via Redwood are tasks that need to run VERY often...for example, every minute or so. We decided to run those directly in SAP.

Redwood Business Process Automation is very well suited for Finance & Accounting processes.

Since we are not an SAP shop, which I know the RunMyJobs company has, it seems like it's hit and miss, where I think maybe an SAP shop might have less issues. AS400/iSeries is touch and go. We have a lot of SSIS package runs and some complicated chains, file watchers that kick off events, and even are able to kick off scheduled jobs in ServiceNow.

It seems many pressing issues have to be escalated to their dev team, which I believe is mostly overseas. The response time isn't always the greatest. I go back to the documentation as well, if that was better there would be less need of support from myself. There are also times when they figure out the resolution, it has to be included with a fix in which you have to wait for the next release, however long that may be. Update - the support response time and quality of answers has greatly increased in the past 6 months or more.

Multiple system[s] can be configured in Redwood Business Process Automation so in a single Redwood tool we can monitor all the jobs for all the different systems[.] It was not possible in [the] SAP system, in SAP GUI we have to login individual system to check individual job, and setting [an] alert and monitoring is very quick in Redwood Business Process Automation.

Can't find any less appropriate areas [seen] from my end. But the ability to automate the entire [batch flow] - both the simple executions, but also the highly complex chains with several dependencies, be it dates, times, other jobs[,] etc. - in a very simplistic way, what is not to like.

As our ERP adoption across business units has grown, so have the number of jobs, and Redwood Business Process Automation has worked very well in removing non-value-added activities and a bottleneck from the administration of these jobs. It is also providing role-based access to functional leads, which has improved the time to resolution as well as providing numerous continual improvement opportunities. Redwood Business Process Automation product has changed our organization's thought process around job scheduling.

I think that any company that is running SAP should be triggering their jobs with Redwood. The scheduling features and options in Redwood give you so much more flexibility than the options provided by SAP. As more and more security mandates come down from the ivory towers, it seems the best idea for companies is to restrict individual access to the production SAP environments and run it all through a scheduling tool, my preference obviously being Redwood. It also enable[s] you to keep longer history for your jobs than SAP traditionally prefers. It gives you a centralized location where you can track all of the jobs you have been running, if you are doing file transfers you can track the success or failure of those transfers much easier using Redwood than you could if you just sent them off to some file transfer service. In my humble opinion, if you are running SAP, you shouldn't be doing it without Redwood. It's not just an SAP tool of course, but all of my experience has revolved around SAP being the central data processing system which is why I've focused so much of my review of Redwood around that.

It is well-suited to our environment where we run SAP but also have multiple middle-ware applications.

RunMyJobs is flexible enough to be able to invoke and orchestrate jobs originating in any of those environments, tying them together

Our admins rely on their informational dashboards to ensure data flow in and out of our company is running smoothly as our cashflow depends on it.

It is a well-rounded product that offers excellent integration with many, many applications.

I've always had great support from the sales and support team, too.

Well suited in an SAP environment where I can import jobs from SAP. Another good thing is you can move jobs from one system to another. Less flexible when it comes to scheduling based on multiple selection criteria. There is room to import with reporting and monitoring.

RunMyJobs is easy to manage.

RunMyJobs is well suited in organizations where there are multiple department requiring jobs and job information to be shared.

Poor documentation, outdated documentation. Slow turnaround. Lack of knowledge - not much is handled by 1-level support, inability to handle basic questions, problems have to be forwarded to 2-level support.