Redwood Documentation

Product Documentation

 

›Automation Concepts

RunMyJobsAutomation Concepts

Automation Concepts

  • Central Scheduling Concepts
  • Automating Processes Across the System Landscape
  • Processes, Chains, and History
  • Queues and Process Servers
  • Workload
  • SAP Systems
  • Events and Event Definitions
  • Scheduling
  • Applications
  • Editing Objects in XML

Locks and Events

  • Prevent Simultaneous Execution of Processes
  • Creating Locks
  • Creating Event-Driven Schedules with Events

Documents

  • Documenting Code, Procedures, and Messages with Documents

Applications

  • Organizing Processes in Applications
  • Creating Applications

End User Overviews

  • End User Interfaces
  • Process Monitors Overview
  • Process Monitors Overview Columns
  • User Message Monitor
  • Designing User Message Forms
  • User Message Monitor Columns
  • Interacting with User Messages
  • Feeds

Managing Output Formats

  • Managing Output Formats

Regular Activities

  • Regular Activities for Redwood Server

Promoting Objects

  • Migrating Objects with the Promotion Module
  • Exporting Redwood Server Objects
  • Export Rule Sets
  • Creating Export Rule Sets
  • Importing Objects
  • Importing Redwood Server Objects with Imports
  • Using Import Rule Sets to Customize Imports
  • Importing Objects with Import Rule Sets
  • Creating Remote Systems
  • Promotion Reaction Processes
  • Integrating Redwood Server Promotion into SAP CTS+
  • Pusher Process Definitions for SAP CTS+ Integration

Backup and Recovery

  • Backup and Recovery of Redwood Server
  • Database Backup
  • Restore Data from Backup

Reference

  • Managing Output Formats
← Queues and Process ServersSAP Systems →

Workload

Queues distribute work across a larger system. If one or more machines can perform a task, then queues can be used to distribute work among these machines by attaching a process server to each machine, and a queue to these process servers. Processes are automatically distributed to all the process servers as they start.

The following figure shows a queue and two process servers working normally.

This scenario also provides for fail over in both planned and unplanned scenarios.

In a planned scenario (for example, an upgrade of the operating system is required), the process server is first shut down gracefully: all running processes are allowed to complete, but no new processes start. Processes now automatically start on one of the other process servers until the planned work is completed and the process server restarted. The following figure illustrates a planned down-time scenario.

In an unplanned scenario, the process server is unreachable. This can be due to network failure, or a hardware failure.

The following figure illustrates an unplanned, network-related down-time scenario.

In the case of a network failure, processes continue to execute, and complete on the machine. The process server attempts to notify the central system that the processes has completed. It continues to retry this operation if it fails.

The following figure illustrates an unplanned, system-related down-time scenario.

In the case of a machine failure, processes on the machine are set to the UNKNOWN status to indicate that their results may not be reliable (since the machine failed).

See Also

  • Using Queues
  • Using Process Servers
  • Using Resources to Distribute the Load
  • Balancing the Load on SAP Systems
  • Balancing the Load on Platform Agents
← Queues and Process ServersSAP Systems →
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |