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
← Controlling SAP Adaptive ComputingConfiguration Details for Integrating SAP Monitors →

Integrating SAP Monitors

note

SAP XAL support has been deprecated.

With Redwood Server, multiple monitors from different SAP Systems can be watched from one central location. Any monitor or monitor set available in transaction RZ20 can be imported with the process definition SAP_ImportCcmsMonitors. The XAL tab of the SAP System needs connection credentials of an RFC user with sufficient privileges to use the XAL interface of the given SAP System. The required privileges are outlined in Reference SAP RFC User Privileges.

When you submit the process definition SAP_ImportCcmsMonitors, choose a value for the SAP instance parameter and the available Monitor sets and Monitors are available in the respective parameter fields. These fields auto-complete, a character sequence of the name can be entered to reduce the list.

note

This functionality is only available when the XAL tab of the SAP System repository object has been filled.

The following process definitions are available for handling monitors:

  • SAP_ImportCcmsMonitors
  • SAP_DeleteCcmsMonitors

The SAP monitoring data can be seen in "Monitoring > Monitors", alongside Redwood Server monitoring data.

You may set a maximum setting for the number of RFC connections, please see the tuning for more information.

note

XBP 3.0 requires a logical system for the client, see Setting Up Logical Systems for more information on creating logical systems for clients.

Prerequisites

  • The JCo libraries must be available, see the Installing the JCO Libraries topic for more information.
  • Client / username and password of the RFC user.
  • The SAP System must have a default client configured, please refer to the SAP documentation.

Procedure

To set up the interface to import and delete SAP Monitors:

  1. Choose "Environment > SAP" in the Navigation bar.
  2. Choose New SAP System from the context-menu.
  3. On the SAP System tab, fill the Name, Connect String and the Time zone fields.
  4. On the XBP tab, fill in Client Number, Username, Password, and check Default Client, if no default client has been previously specified.
  5. On the XAL tab, fill in Client Number, Username, Password.
  6. Choose Save & Close to save the changes and close the edit window.
  7. Choose "Environment > Process Servers" in the Navigation bar.
  8. Choose Start from the context-menu of the process server belonging to the relevant SAP System.

To import a CCMS Monitor

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of the process definition named SAP_ImportCcmsMonitors.
  3. In the submit wizard, fill in the details for Monitor set and Monitor.
  4. Choose Next and choose the queue of the SAP System.
  5. Choose Submit to submit the process.
  6. Navigate to "Monitoring > Monitors" to check the status of the database.

Values

Information about the required configuration data that needs to be specified for integrating SAP monitoring data can be found in the Configuration Details for Integrating SAP Monitors section of the documentation.

Example

You need to be able to monitor the Oracle database of your production NetWeaver AS ABAP+JAVA system.

The following information is known to you:

  • The Client is 200, username is example and password is example.
  • The SAP R/3 connect string is: ASHOST=169.254.10.12 SYSNR=52 TRACE=0
  • XBP version supported is XBP 2.0 (INITXBP2 has run).
  • The default client of the SAP System is client 200.
  • The monitor set and monitor that you use to monitor the Oracle database in RZ20.

First you need to set up or modify the connection to the SAP System; it requires XAL settings.

TabFieldValue
SAP SystemNamesapbw_prd
SAP SystemConnect StringASHOST=169.254.10.12 SYSNR=52 TRACE=0
SAP SystemJob HandlingDisabled
SAP SystemTime zoneEurope/Berlin
SAP SystemApplicationSAPBW
SAP SystemdescriptionProduction SAP BW system in Berlin
XALClient Number200
XALUsernameexample
XALPassword******* (example in this example)
XALAudit Level0 - Change actions
XALSAP LanguageEN
XALDescription

XALMax RFC Connections

XALInterface Versionautomatic

Once the SAP System has been set up, you need to import the SAP Monitors into Redwood Server, you do this with the process definition SAP_ImportCcmsMonitors.

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of the process definition named SAP_ImportCcmsMonitors.
  3. In the submit wizard, fill in the details for Monitor set and Monitor.
  4. Choose Next and choose the queue of the SAP System.
  5. Choose Submit to submit the process.
  6. Navigate to "Monitoring > Monitors" to check the status of the database.

See Also

  • SAP Systems
  • Configuration Details for Integrating SAP Monitors
← Controlling SAP Adaptive ComputingConfiguration Details for Integrating SAP Monitors →
  • Prerequisites
  • Procedure
  • Values
  • Example
  • 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 |