SAP Landscape Transformation Replication Server (SLT)

SAP Landscape Transformation Replication Server integrates with software such as SAP HANA, SAP Data Hub, SAP S/4HANA for central finance foundation, and SAP BW/4HANA, to allow you to move data in real time between different systems within the same network, wide-area networks, and in the cloud. 

 

Technical Prerequisites

To be able to monitor SAP SLT replications you need:

  • FRUN 2.0 Feature Pack 01 
 

Advanced Integration Monitoring Setup

Please, select...

To be able to monitor interfaces of an on-premise system you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Technical Systems' tray and click on the pen icon in the upper right corner. This will open the 'Integration and Cloud Monitoring - Systems' view. 
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of the system. 

In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.

Select the monitoring categories in scope.

Available Monitoring Categories

The available monitoring categories are:

  • SLT: SLT replications between two systems (Monitoring transaction LTRO)

 

 

Please, select...

After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. You can create more than one filter for a monitoring category.

Available Filter Options

SLT

For SAP SLT monitoring you can monitor all SLT replications or use the following filter parameters to restrict the data collection:

  • Source System: Source system of the replication (Field Source System in transaction LTRS)
  • Target System: Target system of the replication (Field Target System in transaction LTRS)
  • SLT Schema: SLT configuration name (Field Configuration Name in transaction LTRS)
  • Status Group: Status group of the replication, choose ERROR or SUCCESS 
 

Please, select...

The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. If you didn't use specific filters in the setup before, but rather opted to collect all data, you have to create filters for the alerts.

  1. Click on the 'New Alert' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  2. Select the monitoring category
  3. Select the metric name. The available metrics depend on the monitoring category.
  4. Enter a name for the alert
  5. Enter a name for the filter

In the next sub-step, you have to maintain the filter. The filter values are the same as described above. For some metrics, you have to maintain metric parameters. Find details below in the overview of the available metrics.

In the last sub-step you have to activate the alert:

  1. Check the checkbox next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.

Available Metrics

For SLT replications the following metrics are collected:

SLT

  • Number of SLT replication with error: Number of SLT replications with errors
  • Status of metric "Load Jobs Config Not Run" is error: Number of configured but not running load jobs
  • Status of metric "Load Jobs Status" is error: Status of Data Load Job(s)
  • Status of metric "Load Jobs Terminated" is error: Number of terminated load jobs runs since the last refresh
  • Status of metric "Master Jobs Status" is error: Status of SLT Master Job
  • Status of metric "Source Status" is error: Monitors the connection status to Source System
  • Status of metric "Target Status" is error: Monitors the connection status to Target System
  • Status of metric "Trigger Active Status" is error: Checks whether the triggers are active for all tables of a configuration.
  • Status of metric "Trigger Status" is error: Checks whether a triggers is in error status
  • Violation of limit of metric "Avg Latency 1h":  This metric shows the median time taken for data replication over the last hour.
  • Violation of limit of metric "Avg Latency 24h": This metric shows the median time taken for data replication over the last 24 hours.
  • Violation of limit of metric "Load Jobs Nb Config": Number of configured load jobs
  • Violation of limit of metric "Master Jobs Terminated": Number of terminated master jobs runs since the last refresh
  • Violation of limit of metric "Max Entr To Repl For Sngl Tbl": Maximal number of table entries that are still to be replicated of a single table
  • Violation of limit of metric "Max Latency 1h": This metric shows the maximal time taken for a data replication over the last hour.
  • Violation of limit of metric "Max Latency 24h": This metric shows the maximal time taken for a data replication over the last 24 hours.
  • Violation of limit of metric "Nb Tables Not Fully Repl": Number of tables that are not fully replicated
  • Violation of limit of metric "Oldest Age Table Rep": Age of the oldest time stamp of a table entry that should be replicated
  • Violation of limit of metric "Schema Latency": This metric shows the median time taken for data replication over the last 24 hours per schema
  • Violation of limit of metric "Sum Table Entries to Repl": Sum of all table entries that are still to be replicated (for all tables)
  • Violation of limit of metric "Table Nb Error": Number of Tables in Error State
  • Violation of limit of metric "Table Nb To Repl": Number of tables to be replicated
  • Violation of limit of metric "Youngest Timestamp": Timestamp of the most recent replication of the a data record.