Redwood Documentation

Product Documentation

 

›SAP Monitoring

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
← Configuration Details for Sending Monitoring Data to SAP SystemsActive XMB Monitoring →

Monitoring Redwood Server Availability in CEN

You can use the Generic Request and Message Generator (GRMG) to monitor the availability of technical components and entire business processes. GRMG is suitable both for technical monitoring and for application monitoring. The following Redwood Server components can be monitored with GRMG:

  • Dispatcher - the process that distributes the load of processes across the central Redwood Server
  • Queues - load-distribution component of Redwood Server
  • Process servers - component that executes processes
  • Services of process servers - component of a process server that run processes, each process server has a service per definition type
  • SAP system process servers - component that sends jobs to SAP systems for processing

The following syntax is used in transaction GRMG to monitor the components, the host and port parameters refer to the host name and connection port of the central Redwood Server.

Examples

  • http://<host>:<port>/redwood/monitoring Dispatcher
  • http://<host>:<port>/redwood/monitoring?object=processserver&name=CRM_ProcessServer Process server CRM_ProcessServer
  • http://<host>:<port>/redwood/monitoring?object=queue&name=CRM_Queue Queue CRM_Queue
  • http://<host>:<port>/redwood/monitoring?parent=CRM_ProcessServer&object=psservice&name=SAPR3Service SAPR3 service of the process server CRM_ProcessServer
  • http://server:port/redwood/monitoring?object=sapsystem&name=T5U

Prerequisites

  • A functional Central Monitoring System (CEN) has been configured
  • GRMG must have been previously set up and functioning on the Central Monitoring System (CEN)
  • Login credentials to the CEN with sufficient privileges to set up a GRMG-lite scenario are required
  • The full URL to the central Redwood Server must be known
  • on-site-related topic Connectivity from the central Redwood server to SAP on its port
  • cloud-related topic Connectivity from the secure gateway to SAP on its port

Procedure

Create a scenario

  1. Open transaction GRMG on the CEN.
  2. Choose Edit/Delete and then Create GRMG-Lite Scenario, choose Yes to Create a technical ping to test a URL.
  3. Fill in a Scenario name and Description for the scenario, as well as a Component name and Description for the Component.
  4. Choose Create.
  5. In the URL/Destination fill in one of the above URL's, depending on the component you would like to monitor.
  6. Fill in Connect Settings.
  7. Select the scenario and choose Start Scenario from the Start Button.
  8. Make sure the scenario is listed as running.

Result

In transaction RZ20 under the GRMG Monitor set, you should see your Redwood Server-specific monitors you created.

See Also

SAP Systems

← Configuration Details for Sending Monitoring Data to SAP SystemsActive XMB Monitoring →
  • Examples
  • Prerequisites
  • Procedure
  • Result
  • 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 |