Redwood Documentation

Product Documentation

 

›Process Chains

RunMyJobsSAP Connector

Introduction

  • The SAP Connector
  • HANA Platforms

Configuration

  • Configuring the Central and Satellite Systems
  • Installing SAP JCo
  • Configuring an SAP System for Process Automation
  • SAP RFC User Privileges
  • Assigning SAP Authorizations to the RFC User
  • Connecting to SAP Systems
  • Connecting to SAP Systems with the Wizard
  • Connection Details for the ABAP Stack
  • Intercepting SAP Jobs
  • SAP Job Interception Configuration
  • Interacting with SAP Events
  • Configuration Details on Interacting with SAP Events
  • Parsing Log Files to set Status of SAP Jobs
  • Understanding the Different XBP Interface Releases

Importing SAP Objects

  • Importing Objects from SAP Systems
  • Importing ABAP Programs
  • Importing ABAP Program Parameter Definitions
  • Importing Archive Objects
  • Importing Batch Events
  • Importing SAP BusinessObjects Processes
  • Importing SAP Calendars
  • Importing SAP CCMS Jobs
  • Importing Communication Channels via PI/XI
  • Importing External Commands
  • Importing and Running Mass Activities
  • Importing Output Devices
  • Importing Process Chains
  • Importing Process Chain Definitions
  • Importing Recipients
  • Importing Variants
  • Importing Variant Definitions

SAP ABAP

  • Handling ABAP Programs
  • Controlling Batch Input Sessions
  • Handling Variants
  • Creating and Modifying Variants in Redwood Server
  • Maintaining Variants Manually
  • Maintaining Variants Automatically
  • Maintaining Variants Automatically (Advanced)
  • Using Temporary Variants
  • Default SAP Process Definitions

Business Objects

  • Main
  • Interface Configuration
  • Crystal Reports
  • Web Intelligence
  • Data Services
  • Triggering Events
  • Crystal Reports REST
  • Web Intelligence REST

Process Chains

  • Handling Process Chains
  • Running Process Chains
  • Monitoring Process Chains
  • Restarting Process Chains

SAP PI/XI

  • SAP Communication Channels with PI/XI
  • Controlling Communication Channels with Redwood Server via PI/XI

Adaptive Computing

  • SAP Adaptive Computing
  • Controlling SAP Adaptive Computing

SAP Monitoring

  • Integrating SAP Monitors
  • Configuration Details for Integrating SAP Monitors
  • Sending Monitoring Data to SAP Systems
  • Configuration Details for Sending Monitoring Data to SAP Systems
  • Monitoring Redwood Server Availability in CEN
  • Active XMB Monitoring
  • Active IDoc Monitoring

Advanced Configuration

  • Connect to an ABAP System via SAProuter
  • SNC connection to an SAP System
  • The SAP Cryptographic Library
  • Tuning Redwood Server

Legacy Systems Support

  • Enable XBP 2.0 or 3.0 Functionality
  • Enhanced SAP Interfaces with Redwood Transports
← Running Process ChainsRestarting Process Chains →

Monitoring Process Chains

You can monitor process chains started from within SAP with Redwood Server, this functionality offers the following advantages:

  • Allows you to migrate to full use of Redwood Server in phases
  • The process chains are displayed in a hierarchy, just like Redwood Server chains
  • You have a central point of control
  • Email/SMS Alerting of failures if you have the Active Monitoring Module

The jobs are monitored via the XBP interface job control rules. You need to create new job control rules for jobs with the name BI_PROCESS_TRIGGER.

note

It is not possible to use Redwood Server to balance the load of process chains across SAP application servers. As far as scheduling is concerned, you can only influence the parent job. You can, however, restart certain child jobs.

Prerequisites

  • SAP Note 1080558 describes the SP levels for the BW/BI releases
  • XBP 2.0 or higher
  • Redwood transport files must be loaded

ProcessServerService.SAP.XBPVariant license key

Procedure

Create the job control rule

  1. Navigate to "Environment > SAP".
  2. Choose Edit from the context-menu of the SAP System where the process chains run.
  3. On the Job Control Rules tab, fill in details of the jobs you want to monitor:
  4. The action must be set to Monitor, job name must be set to BI_PROCESS_TRIGGER and statuses Finished and Error must be checked,.
  5. A second rule needs to be created with a higher processing order to ignore stray BW jobs; The action must be Ignore and the job name must be BI_PROCESS*. No other fields need to be checked. See Job Interception Configuration for information on the fields.
  6. Choose Save & Close.

See Also

  • Running Process Chains
  • Restarting Process Chains
  • Importing Process Chains
  • Importing Process Chain Definitions
  • Handling Process Chains
← Running Process ChainsRestarting Process Chains →
  • Prerequisites
  • Procedure
  • 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 |