Traditional SAP job scheduling often assumed that customers controlled the servers, agents, and scripts behind their background processes. Moving workloads into RISE with SAP changes that operating model. SAP Enterprise Cloud Services (SAP ECS) manages the environment, so scheduling tools, file transfers, and operating-system scripts built around direct server access cannot be assumed to move unchanged. RunMyJobs by Redwood gives customers a documented path through that boundary. In an SAP Community post, Darryl Gray, SAP’s senior vice president of ISV partner management, described the SAP Endorsed App as part of the RISE with SAP reference architecture, with SAP ECS providing managed services for the connectivity and execution components required inside the controlled environment.

RISE with SAP Puts Legacy Scheduling Behind a Managed Boundary

In many on-premises SAP ECC environments, background processing grew around direct server access. Operations teams could place agents on application servers, watch for incoming files, and use shell scripts or cron jobs to start the next step in a process. Because much of that logic lives outside SAP itself, migration teams can overlook it when planning which workloads and dependencies must move. RISE changes who controls that execution environment. Customers cannot assume they can independently reinstall existing agents or reproduce operating-system processes. The work may still be possible, but it needs an approved path inside the landscape. Migration teams should identify these dependencies and decide which to keep, replace, or retire.

SAP ECS Creates a Managed Path for RunMyJobs

SAP ECS supports two RunMyJobs components for the RISE environment: the Secure Gateway and the OS-Platform Agent. The Secure Gateway connects the customer’s RunMyJobs tenant to the managed SAP landscape. When a job needs to run a script or move files on a RISE server, the OS-Platform Agent performs that work. SAP ECS installs and monitors the agent, so the customer does not need direct access to the server. The two components provide a controlled path for automation inside RISE. Redwood describes RunMyJobs as the only workload automation platform included in the RISE with SAP reference architecture. Separately scoped SAP ECS services can also monitor agreed jobs and perform technical root-cause analysis when errors occur. The scheduling engine remains outside the ERP core, while SAP manages the components operating inside the controlled environment. Customers can continue running necessary jobs, scripts, and file transfers without recreating their former server-access model.

Customers Still Own the Automation Design

SAP ECS manages the connection and execution components, but it does not take over the customer’s scheduling strategy. Teams decide which jobs should run, when they should start, how processes depend on one another, and what should happen when a job fails. This division of responsibility should be defined before migration. SAP can keep the technical path available and provide additional monitoring or remediation services, but customers remain accountable for the workflows moving through it. Reviewing those boundaries early can prevent gaps between what the managed service covers and what internal operations teams still need to design, maintain, and support.

What This Means for SAPinsiders

• Scheduling becomes a defined migration workstream. RISE gives teams a reason to review scheduling dependencies alongside applications and infrastructure. Addressing them early creates a clearer path for redesign, support, and cutover planning.
• Managed access strengthens the operating model. RunMyJobs gains value from the SAP ECS-managed path into RISE. That gives customers a documented architecture for connecting automation to the controlled environment.
• Shared responsibility supports clearer governance. SAP manages specified technical components while customers retain control of job design and sequencing. Defining those boundaries early helps align support, maintenance, and escalation responsibilities.