Monitoring sap banking parallel processing jobs with solution manager business process monitoring
Upcoming SlideShare
Loading in...5
×
 

Monitoring sap banking parallel processing jobs with solution manager business process monitoring

on

  • 1,464 views

 

Statistics

Views

Total Views
1,464
Views on SlideShare
1,464
Embed Views
0

Actions

Likes
1
Downloads
38
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Monitoring sap banking parallel processing jobs with solution manager business process monitoring Monitoring sap banking parallel processing jobs with solution manager business process monitoring Document Transcript

  • Best Practice Monitoring SAP Banking Parallel Processing Jobs with SolutionManager Business Process Monitoring Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS internal in progress DATE VERSION Apr-06 2010 1.0Solution Management Phase SAP Solution Topic Area Solution Manager AreaOperations & Optimizations mySAP Banking Business Process Operations Business Process and Interface Monitoring
  • Date Alteration Reason Version08.02.2010 Creation 0.127.04.2010 Correction after review 1.0© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 2/38
  • Table of Contents1 Management Summary 4 1.1 Goal of Using this Service 4 1.2 Staff and Skills Requirements 4 1.3 System Requirements 5 1.4 Duration and Timing 5 1.5 Case Study or Sample Scenario 52 Best Practice 6 2.1 Preliminary Tasks 6 2.2 Design 6 2.3 Procedure – Setup 10 2.3.1 Setup Procedure in Satellite system 10 2.3.2 Setup Procedure in Solution Manager 11 2.4 Procedure – Operation and Handling 27 2.4.1 MASSMAN in Satellite System and Central System 27 2.4.2 Monitoring in Solution Manager BPM 323 Further Information 37 3.1 Background Information and References 37© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 3/38
  • 1 Management Summary1.1 Goal of Using this ServiceThe optimized performance of core business processes is the key requirement for any successful operation ina banking environment.The IT department of a bank is usually faces different challenges: - Complex solution landscape, including modifications, own developments, third-party software - Legal requirements (limited time window to process data for reporting) - Mass data processing - Workload is not equally distributed between days/Peak times (for example, end of month) - Huge requirements on system stability and data security - Difficulties to make exceptions visible and to provide sufficient tools for Root Cause AnalysisIn a typical Banking Services project, the system scenario consists of various SAP solutions like; XI to handlethe communication between different SAP systems; CRM to store customer information; Banking Services tohandle loans, deposits, and run bank specific mass run; FI-CAX (ERP) to manage open items; BW to storethe results; and analytical solutions like Bank Analyzer. The hardware consumption is not distributed equallybetween different systems, due to fluctuating data from legacy systems. Normally, the end-of-day, month-end, quarter-end, and year-end processes are the peak time of a banking system, where high data volumeshave to be processed in a limited time frame. For example, large banks may need to run settlementfunctionality on millions of accounts during the quarter-end processing and still have to fulfill their dailybusiness like money transfer from and to the ATM. The requirement on the hardware is to process increasingworkload during peak time within given time frame.To help the IT department of a bank to monitor their critical jobs and the whole process chain, SAP SolutionManager offers a wide range of tools for performance monitoring. These performance monitoring tools aregrouped in the Business Process Monitoring (BPM) functionalities in SAP Solution Manager.The purpose of this document is to enable the customer to setup, and configure and operate the businessperformance monitoring for their core business processes. The performance monitoring can help bankcustomers to control and maintain their critical processes better, and reduce the risk and TCO.1.2 Staff and Skills RequirementsTo implement the job monitoring for parallel processing, specific skills and roles are required from the variousdepartments at banks. The following tasks should be assigned to the mentioned teams. Maintain system landscape within Solution Manager (Responsible: SAP Basis Team). Setup a monitoring solution and configure the monitor for each critical batch job (Responsible: Solution Manager Expert / Technical Support Team)© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 4/38
  • Monitor the solution and handle the exceptions (Responsible: Solution Manager Expert / Technical Support Team) Based on the collected job statistics, analyze the information and create automatically generated report (Responsible: Technical Support Team)1.3 System RequirementsThe following system requirements are required in SAP Solution Manager and the relevant satellite systems.Solution Manager Solution Manager 7.0 EHP1 (Enhanced Package 1).Satellite systems ST-A/PI Release M (latest Support Package release) Latest ST-PI Release If the satellite system has SAP Product Banking Services in place, its release should be at least FSAPPL 100. If the satellite system has SAP Product Transactional Banking in place, its release should be at least TRBK 3.0. If the satellite system has SAP Product Bank Analyzer in place, its release should be at least BANK- ALYZE 5.01.4 Duration and TimingFor an initial implementation of BPMon for monitoring Banking batch jobs, the following duration and effortestimation can be given as general guidelines:. 2 days setup and configuration for two or three critical jobs. 2 days fine tuning, BI-Reporting, knowledge transfer, training.Note: Depending on the complexity of the customer requirements, the implementation might take more orless time.1.5 Case Study or Sample ScenarioDuring the End-of-Day processing, it is a very important task for the bank production support team to monitortheir critical batch jobs and collect the statistics for the jobs after the processing. Based on the collectedstatistics, the support team can analyze and compare the runtime of the jobs and report to management. It isa time consuming task without an appropriate tool to collect the statistics (job name, start time, status,duration ...) and maintain the reporting sheet.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 5/38
  • 2 Best Practice2.1 Preliminary TasksEnsure that you perform the following preliminary tasks or checks in the system before you start theimplementation: Check the software requirements in the Solution Manager Check the software requirements in the satellite systemsSolution Manager - Solution Manager 7.0 with BPMon should be implemented. - Check SAP Note 521820 “Availability of Business Process Monitoring” for software requirements. - Check SAP Note 784752 “BPMon in SAP Solution Manager – Prerequisites” for technical details. - Implement ST-A/PI Release M and Run Report RTCCTOOL in SE38 to activate the data collector and clear all the red alerts.2.2 DesignIn a typical monitoring architecture, SAP Solution Manager should be linked to various satellite systems. ThenSAP Solution Manager is the central system where all relevant monitoring information should be stored anddisplayed. The Solution Manager should become the central tool to monitor all satellite systems where criticalbusiness processes or jobs are running, for example, SAP Deposit Management. Multiple satellite systemscan be connected to Solution Manager. For different monitoring purposes, there are different data collectorsrunning in satellite systems. They collect information periodically and send it back to the Solution Manager.This architecture brings a clear overview of the whole solution landscape, the monitoring team can easilymonitor their solution which spreads in different monitored systems and the results (monitoring key figures,alerts) are stored centrally in Solution Manager for trend analysis, for example, in Microsoft Excel. In additionto the already mentioned functionality, the monitoring on SAP Solution Manager also allows you to use thecentral BPM framework to create alerts or incidents, if certain threshold for key figures is reached.Figure 2-1 is the overview of functionalities of Business Process Monitoring in Solution Manager.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 6/38
  • Figure 2-1 Overview – Business Process Monitoring in Solution ManagerIn SAP banking solutions, it is common to use parallel processing for jobs which are part of the critical path,for example, End-of-Day processing. Through parallel processing, large amounts of data can be split intodifferent work packages and work packages can be assigned to different work processes. The parallelizedjobs are called mass runs.The business performance monitor is one of the BPM application monitors. It is designed to monitor theperformance of the parallel jobs (mass runs) started by the SAP parallel processing framework (for example,PP Framework). The performance monitor has its own data collector running in the satellite system to collectthe performance information of mass runs. The data collector running in the satellite system is calledMassMan. The MassMann data collector is delivered with the SAP ST-A/PI package (available since releaseK). The collected data is sent back to SAP Solution Manager for display and to trigger further actions likenotification and analysis.Since ST-A/PI release M, we offer a new Banking Mass Activity Monitor (technical name: BOMASSBK) inSolution Manager BPM to monitor the banking jobs using Parallel Processing Framework. The new monitor isa revised product of the previous Mass Activity Monitor (BOMASSBS for Banking Services, BOMASSDM forTransactional Banking, BOMASSBA for Bank Analyzer). It unified different monitors for different bankingproducts into one unified monitor. It can select jobs and collect statistics, not only based on technicalparameters (for example, job name, user, variant...) but also on banking specific functional parameters (forexample, bank posting area, legal entities). With the new monitor, statistics and KPIs (Key PerformanceIndicator) can be exposed more precisely than previous tools. Of course, even with the implementation of thenewest ST-A/PI release M, it is ensured that monitoring scenarios based on previous monitors(BOMASSBS/BOMASSDM/BOMASSBA) will continue working.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 7/38
  • Figure 2-2 shows the landscape of performance monitoring for SAP Bank Solution, Banking Services andBank Analyzer.Figure 2-2 Architecture of Exception Handling with Solution ManagerTable 2-1 is a summary of the available KPIs in the revised Mass Activity Monitor. They are grouped intodifferent categories.Category Key figures / KPIsCounter Selected Objects Successful Objects Exceptions Custom Counter Custom Counter Custom CounterJob information Duration (Batch) Duration (PP) No. Canceled Jobs (Batch/PP) PPF Return CodePerformance information Throughput (per hour) Throughput (per child job/hour) Estimated DurationHardware utilization CPU Utilization Paging (per hour) Memory Consumption (per Server) Memory Consumption (per Mass Activity) Batch Workprocesses Job Statistics (per Mass Activity)Others Comparison of Counters© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 8/38
  • Remote Counter ComparisonTable 2-1 Category of KPIsTable 2-2 describes the meaning of each KPI / key figure.Index Key figure /KPIs Description1 Selected Objects Counter can be assigned to this key figure to show the number of selected / due objects that need to be processed.2 Successful Objects Counter can be assigned to this key figure to show the number of successfully processed objects.3 Exceptions Counter can be assigned to this key figure to show the number of failed objects.4 Custom Counter Additional counter of the belonging application type can be assigned.5 Custom Counter Additional counter of the belonging application type can be assigned.6 Custom Counter Additional counter of the belonging application type can be assigned.7 Duration (Batch) Duration of the job or step from SM378 Duration (PP) Duration of the job or step in Parallel Processing Framework. (in simple case it is the duration of the longest parallel job)9 No. Canceled Jobs (Batch/PP) Number of job or parallel job that has status cancelled10 PPF Return Code The application return code of the Parallel Processing Framework11 Throughput (per hour) Number of the reference counter can be processed per hour12 Throughput (per child job/hour) Number of the reference counter can be processed per hour and per parallel job.13 Estimated Duration The estimated time that the process is supposed to run. It is based on the data volume to be processed and current throughput.14 CPU Utilization CPU utilization from SAPOSCOL.15 Paging (per hour) Paging rate (page in, page out) per hour from SAPOSCOL.16 Memory Consumption (per Server) Memory consumption per server from SAPOSCOL.17 Memory Consumption (per Mass Memory consumed by the parallel process application Activity)18 Batch Workprocesses Number of batch work process used by the PP application19 Job Statistics (per Mass Activity) CPU time, DB time and extended memory used by the PP application© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 9/38
  • 20 Comparison of Counters Compare the difference between two counters of this application21 Remote Counter Comparison Compare one counter from this PP application with another counter from a remote PP application. Compare counter from different applications.Table 2-2 Description of KPIsIn the Banking environment, a mass activity job can be planned / scheduled differently. Typically there arethree types: 1. Single job with only one report kicked off by external job scheduler 2. Single job containing multiple steps, each step can be a mass processing report 3. Mass processing can be planned in a job chain, which is triggered by event.By using the mass activity monitor, all three types of processing can be specified and the statistic informationcan be assigned to the related processing.2.3 Procedure – SetupThis section describes the setup procedures in satellite system and Solution Manager.2.3.1 Setup Procedure in Satellite systemIn this section, the setup procedures required in the satellite system will be described. It should be donebefore the configuration in Solution Manager. The procedure 2.3.1.1 should be done in all monitored systems.2.3.1.1 Finalize ST-A/PI in Satellite SystemIn each satellite system, after installing the ST-A/PI package, the program RTCCTOOL should be started inSE38 to finalize the installation process. All the red alerts displayed in the tool should be fixed manuallyaccording to the instruction. Figure 2-3 shows the correct result from RTCCTOOL. Please also follow the SAPNote 69455.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 10/38
  • Figure 2-3 Successful result of RTCCTOOL2.3.2 Setup Procedure in Solution ManagerIn this section, the setup procedure Solution Manager will be explained. Please follow the steps in the samesequence as described below.2.3.2.1 Required User and RFC Connection in Solution ManagerUser CSMREG should be created in Solution Manager and configured according to SAP note 455356.Local RFC connection BPM_LOCAL_<Client> in Solution Manager should be created, with communicationuser CSMREG.Please check the other preconditions according to SAP Note 784752.2.3.2.2 Create a New Solution in Solution ManagerFirst of all in Solution Manager, a new solution should be created by starting transaction DSWP. In thesolution overview window (Figure 2-4), select the “Create” button to create a new solution.Figure 2-4 Solution overview2.3.2.3 Maintain Solution Landscape in Solution ManagerThe solution landscape should be maintained in the newly created solution. The path is “Solution Landscape Solution Landscape Maintenance”First different logical components need to be assigned to this solution. A logical component is a group of SAPinstances represent same product in the transport landscape. The logical component can be created andmaintained in transaction SMSY or in path “Solution Landscape System Landscape Maintenance”.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 11/38
  • Figure 2-5 Maintain Solution LandscapeAfter assigning the logical components, the leading role of the solution should be decided. The leading roledecides which SAP systems in the transport landscape should be monitored. In Figure 2-5, the leading role isset to “Production System”, so the systems specified under the “Production System” column are to bemonitored. The leading role can be modified only at the initial time, when the solution is saved, it cannot bemodified anymore.2.3.2.4 Maintain ContactsIn Figure 2-6, click the button.Figure 2-6 Solution Landscape MaintenanceIn Figure 2-7, please click button or to create a new entry. The added user should be already definedin transaction SU01. Double-click the “User” field to select the user from SU01. The user maintained here willbe assigned later to different monitoring organizations. The user that is used later as alert sender must havea valid e-mail address.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 12/38
  • Figure 2-7 Maintain Contacts in Solution2.3.2.5 Create ScenarioA scenario or business process can be created newly or import from SAP repository or existing solutions.Figure 2-8 Maintain ScenarioAs shown in Figure 2-8, two scenarios are created. After configuring, switch the Status from “Planned” to“Production”, otherwise we cannot activate the scenario later if it is in status “Planned”.2.3.2.6 Create Business ProcessesAfter creating the business scenario, business processes can be created under business scenario. In Figure2-9, the scenario has one business process “EOD”. Its status is set to “Production” and the availability is 7days a week and 24 hours per day.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 13/38
  • Figure 2-9 Create Business ProcessThe possible process availability is -5x16 h -5x8 h -5x24 h -7x24 hIt should also be chosen according the business requirements.2.3.2.7 Create Business Process StepsAfter creating an empty business process, we can define different business process steps inside the businessprocess. To create a new step, a logical component and processing type need to be specified.Figure 2-10 Create Business Processes StepsIn Figure 2-10, it shows the business process steps within business process “EOD”. They are maintainedunder the tab “Structure”. Column “Step Name” specifies the name of the process step. It is a text thatdescribes the business step. Column “Logical Component” specifies the logical component that this step isrunning. It can be chosen from the logical components that assigned to this solution. Column “Process Type”specifies the run type of this business step in the logical component. It can be Dialog, Background andDialog/Background.The process steps can be sorted by clicking the “Up” and “Down” button .© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 14/38
  • 2.3.2.8 Start Business Process Monitoring SetupAfter creating the business process steps and maintaining the contacts, go back to the solution screen asFigure 2-11 shows and use the path “Operations Setup -> Solution Monitoring -> Business ProcessMonitoring” -> “Setup Business Process Monitoring” to start configuring monitoring objects in businessprocess steps.Figure 2-11 Setup Business Process Monitoring2.3.2.9 Maintain Solution Support OrganizationFigure 2-12 Create Support TeamsIn the “Name” column, choose the user that you want to add to the team. The user is defined in transactioncode SU01.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 15/38
  • Figure 2-13 Assign User to Support OrganizationIn the second tab, “Monitoring Roles”, assign the role of the team.Figure 2-14 Select Monitoring Roles2.3.2.10 Activate Business ProcessesAfter having configured the support organization, the business processes and steps should be activated, sothat different monitor can be assigned to process step.As shown in Figure 2-15, select the check box and click the save button . Then, the selectedbusiness processes or steps will be displayed on the left side, within the Business Processes tree.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 16/38
  • Figure 2-15 Activate Business Process Steps2.3.2.11 Configure Mass Activity Monitor for Banking ProductsIn this section, it will describe how to configure the Mass Activity Monitor for Banking in Solution Manager.2.3.2.11.1 Choose CollectorThe first step is to choose the data collector. In the selected business process step, activate the ApplicationMonitor. As shown in Figure 2-16, if the ST-A/PI package in the monitored system has been modified, pleasefirst click button to load the current data collectors from monitored system, in our examplethe monitored satellite system is BPP. Afterwards, click to add a new monitoring entry.Figure 2-16 Collector - Create New Monitoring ObjectIn field Monitor Name, press F4, Figure 2-17 will be displayed. It shows a list of available Application Monitorsin satellite system. From the list, choose “Exception Handling for Banking”. After selection of the collector,click the button to configure the detail information of the collector.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 17/38
  • Figure 2-17 Collector - List of Available Monitors2.3.2.11.2 Activate Key FiguresIn this step, under the “Key Figure” tab, choose the key figures that you want to activate. Then, click thesecond tab “Detail Information”. The alerts are raised based on the configuration of each key figure.Figure 2-18 Collector - Activate Key FiguresBefore you can activate the key figure of the data collector, the parameters in “Detail Information” tab must beconfigured first.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 18/38
  • 2.3.2.11.3 Configure Detail InformationIn “Detail Information” tab, double click Counter “001”, a popup screen is shown as in Figure 2-19. In thepopup screen 10 parameters can be maintained for selecting the target runs. The description of the 10parameter can be found in Table 2-3. To ease your configuration, the F4 help is available for parameterLogical Unit, Application Type, Parallel Phase, Assign Posting Date.Figure 2-19 Collector - Configure Detail InformationIndex Parameter Description1 Job Name Name of the batch job in SM372 Job User User that starts the batch job3 Trigger Parameter The trigger event parameter of that job4 Step Count The step number of the batch job. If you want to select one step from the batch job, specify the correct step count.5 Program Name The ABAP report name that are executed6 Program Variant The variant of the report that is used for execution7 Logical Unit It is a banking specific parameter. It means Bank Posting Area in Banking Services or TRBK. It means Legal Entity in Bank Analyzer.8 Application Type Type of the PP application (for example, BCA_SETTLE, R205 … )9 Parallel Phase Inside the PP Framework, some application type can have multiple phases during the processing. (for example, in application type R205, two phases are defined, BUNDLING and CALCULATION)10 Assign Posting Date Link the posting date to the job. It is used for End-of-Day processing in the Banking Services and TRBK. It gives the possibility to group the job according to posting date of payment cutoff.Table 2-3 Collector - Job Selection ParameterBelow are some typical examples showing how to maintain the parameters.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 19/38
  • Example: To define a monitor to monitor the batch job 010_LOAD_ARREAS started by user BATCH. Thecollector parameter can be maintained as in Table 2-4Index Parameter Value1 Job Name 010_LOAD_ARREAS2 Job User BATCHTable 2-4 Collector – Example Parameter for Batch Job SelectionExample: To define a monitor for a PP-Enabled account settlement Job 020_EXECUTE_ACCOUNT_SETTLMENT for Bank Posting Area 0001, started by user BATCH. The collector parameter can bemaintained as Table 2-5 showsIndex Parameter Value1 Job Name 020_EXECUTE_ACCOUNT_SETTLMENT2 Job User BATCH5 Program Name RBCA_SETTLE_RUN_PP7 Logical Unit 00018 Application Type BCA_SETTLETable 2-5 Collector – Example Parameter for PP Job SelectionExample: In batch job 030_POSTING_EXTERNAL_BUSINESS_TRANSACTION, two steps are defined. Firststep is for legal entity 020 and second step is for legal entity 050. Two collectors can be defined for each stepas Table 2-6 and Table 2-7 shows.Index Parameter Value1 Job Name 030_POSTING_EXTERNAL_BUSINESS_TRANSACTION4 Step Count 15 Program Name /BA1/RB1_PBTP_POST_FDB7 Logical Unit 0208 Application Type BBP1Table 2-6 Collector – Example Parameter for Job Step and PP Selection 1Index Parameter Value1 Job Name 030_POSTING_EXTERNAL_BUSINESS_TRANSACTION4 Step Count 25 Program Name /BA1/RB1_PBTP_POST_FDB7 Logical Unit 050© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 20/38
  • 8 Application Type BBP1Table 2-7 Collector - Example Parameter for Job Step and PP Selection 22.3.2.11.4 Configure Monitoring ScheduleAfter having done the above steps, choose the “Monitoring Schedule” tab to define when the data collectorshould be started.Figure 2-20 Collector - Monitoring ScheduleIn our example, the data selection is on a weekly basis, each working day, every 60 minutes.2.3.2.11.5 Configure Key Figure: Selected ObjectsFigure 2-21 shows the selection screen of key figure “Selected Objects”.Figure 2-21 Key figure: Selected Objects2 parameters from the selection screen need to be maintainedParameter “Count ID” you can choose F4 Help to select the available counter for that application type.Parameter “Comparison Operator” you can choose F4 Help to select the operator. The operator decideshow to compare the measured counter value with predefined threshold and when the alert should be raised. If“GT” is chosen, then when the measured counter value exceeds (greater than) the yellow threshold, a yellowalert will be raised. If the measured counter value exceeds the red threshold, a red alert is raised.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 21/38
  • Figure 2-22 Key Figure: List of Available CounterFigure 2-23 shows the threshold settings. Normally for Counters like Selected Objects or Successful Objects,the support team does not want to trigger alert for them, they are activated only to record the value forstatistic reason. Normally, we set the threshold to a large number (for example, 99999999) that will not bereached to prevent alert creation.Figure 2-23 Key Figure: Selected Objects - Threshold2.3.2.11.6 Configure Key Figure: Duration (Batch) / Duration (PP)Figure 2-24 shows the selection screen of key figure “Duration (Batch)”. The same logic is applied here asabove key figure. The parameter “Comparison Operator” needs to be maintained and the threshold needs tobe maintained.Figure 2-24 Key figure: Duration (Batch) - Selection ScreenKey figure “Duration (PP)” is configured in the same way as “Duration (Batch)”. But the key figure “Duration(PP) should only be activated if the job is based on Parallel Processing Framework with predefined counterfrom development; otherwise no result will be returned.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 22/38
  • 2.3.2.11.7 Configure Key Figure: No. Cancelled Jobs (Batch/PP)For key figure “No. Cancelled Jobs (Batch/PP)”, no parameter needs to be maintained; only the thresholdshould be maintained. Figure 2-25 shows an example setting of the threshold. If 1 job is cancelled, a red alertwill be raised. Here the only comparison operator is greater or equal.Figure 2-25 Key Figure: No. of Cancelled Jobs2.3.2.11.8 Configure Key Figure: PPF Return CodeFigure 2-26 shows the parameter selection screen of key figure “PPF Return Code”.Figure 2-26 Key Figure: Nr. of Payments in CpD with critical residence time - Selection ScreenFor the parameter “PPF Return Code” F4 Help is available. You can select one or a list of return code asshown in Table 2-8.Value Description0 Successfully Completed2 Completed with Warning Messages4 Completed with Individual Error8 Terminated16 Asynchronous Processing Still Active99 UndefinedTable 2-8 F4 Help for PPF Return Code© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 23/38
  • The threshold is normally set to 1, so that the alert can be raised when one job with the specified return codeoccurs.Figure 2-27 Key Figure: PPF Return Code - Threshold2.3.2.11.9 Configure Key Figure: Throughput (per hour)During mass processing, the throughput is a central indicator to measure the performance. In the key figure“Throughput (per hour)”, normally, the alert will be triggered when the throughput is lower than expectedvalues. Figure 2-28 shows the selection screen of key figure “Throughput (per hour)”. As throughput iscalculated for a specific counter, in the parameter “Reference Counter”, please use F4 Help to choose anavailable counter. In parameter “Comparison Operator”, use F4 Help to choose an operator that you wantto use for comparison between calculated throughput and threshold. Normally, we want to get notificationwhen the throughput is lower than the minimum expectation, in this case the operator “LT” (lower than)should be chosen.Figure 2-28 Key Figure: Throughput per hour - Selection ScreenFigure 2-29 shows the threshold setting. Together with Figure 2-28, it will trigger a red alert when the speedof successfully processed accounts less than 20,000 accounts per hour.Figure 2-29 Key Figure: Throughput per hour - Threshold© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 24/38
  • 2.3.2.11.10 Configure Key Figure: Estimated DurationAs we know, the data volume to be processed and the speed of processing (throughput), we can giveforecast of the expected run-time.Figure 2-30 shows the parameter selection screen of key figure Estimated Duration. In Parameter“Comparison Operator”, please use F4 to select an operator. Normally, we want to be notified when theestimated duration exceeds our limit. In this case, we will choose “GT” (greater than).Figure 2-30 Key Figure: Estimated Duration – Selection ScreenFigure 2-31 shows the threshold setting of key figure “Estimated Duration”.Figure 2-31 Key Figure: Estimated Duration – ThresholdBased on the configuration in Figure 2-30 and Figure 2-31, red alert will be triggered when the estimatedduration exceeds 3,600 seconds.2.3.2.11.11 Configure Key Figure: Comparison of CountersWithin the same application type, the counter for the number of due objects and counter for number ofsuccessfully processed objects are provided. The difference between due objects and successfully processedobjects is the number of failed objects. It could be useful to trigger alert when the number of failed objectsexceeds the threshold, for example, to detect malfunction in the processed business transactions.Figure 2-32 shows the parameter selection screen of key figure “Comparison of Counters”. For parameter“Reference Counter 1” and “Reference Counter 2”, use F4 help to choose a counter.The difference between two counters is represented by percentage. It is calculated with below form:Percentage = ( REF_COUNT2 / REF_COUNT1 ) * 100© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 25/38
  • Figure 2-32 Key Figure: Comparison of Counters – Selection ScreenFigure 2-33 shows the threshold setting of key figure “Comparison of Counters”.Figure 2-33 Key Figure: Comparison of Counters - ThresholdBased on the configuration in Figure 2-32 and Figure 2-33, if the successful objects lower than 80% of dueobjects, a yellow alert will be raised. If the successful objects lower than 60% of due objects, a red alert willbe raised.2.3.2.12 Alert NotificationWhen an alert is triggered, it should be sent to the responsible person to solve it. In the alert notificationcheck, you can configure sender and receiver and when the notification should be sent. If the number ofyellow or red alerts exceeds the threshold, alerts will be sent to the recipient address.Notifications can be set up for the whole business process or for each business process step individually.There are two types of notifications: Workflow notifications and Support notifications. Workflow notificationsallow sending messages in case of alerts to a specified Recipient. This could be an e-mail or SAPOffice mail.Support notifications allow setting up a service desk message in case of an alert. The information entered forthe service desk message serves as a template. The service desk message can be created manually orautomatically.On business process level, it is possible to define notifications for the whole business process, that is, assoon as the business process gets an alert status, notifications will be triggered. Alternative notifications canbe defined for every Monitoring Type individually, for example, all alerts related to all background jobs of thebusiness process are forwarded to a defined e-mail address.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 26/38
  • Notifications defined on business process step level will override the configuration made on business processlevel for this particular step.Figure 2-34 Configure Alert Notification for each Monitoring ObjectFigure 2-35 shows the notification methods. 5 different methods are available.Figure 2-35 Recipient Type2.4 Procedure – Operation and HandlingIn the previous section, we have discussed how to setup business process monitoring and configure bankspecific mass activity monitor to monitor background jobs. In this section we will explain how to interpret andanalyze the monitoring results. The data collector running in the monitored system is called MassMan. Wewill first explain the results in MassMan, and then explain the results in operation mode from SolutionManager BPM session.2.4.1 MASSMAN in Satellite System and Central SystemIn the satellite system and the central Solution Manager system, MassMan can be started in transaction codeST13. MassMan is an online monitoring tool, which provides very useful information about the currentprocess status. It can either be used for active online monitoring or it will also help to identify the root cause ofperformance problems during mass processing.ST13 is a collection of different SAP analysis and service tools. From the list of available tools, choose“MASS_MAN_MONITORING” and execute. MassMan can use preconfigured RFC connections to load massruns from remote systems. This makes MassMan very flexible and increases the scalability of the solutionlandscape to be monitored.2.4.1.1 MASSMAN - Start ScreenFigure 2-36 shows the start screen. On top of the screen are command buttons, lower part is selectionconditions. Different conditions can be used to choose the proper mass runs. MassMan is not designed toselect every job from SM37, but only the banking specific mass run jobs. The mass run jobs are those jobsthat use the PP Framework. MassMan can store selected runs to its own history table, so that data can be© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 27/38
  • stored permanently, in comparison to report RBANK_PP_MONITOR. The mass run can be selected by startand end time, status, historic run or not historic run and application type.Figure 2-36 MassMan - Start screen for selection criteria2.4.1.2 MassMan – Maintain counterFor most of the mass runs, application-specific counters are available to count the objects that are processedby the application. From the MassMan start screen, choose the button , a new screen asFigure 2-37 will be displayed. In this screen, the relationship between application type and counter ID aremaintained. Entry can be inserted and deleted. The column “Throughput” and “Show” can be marked, whichmean the throughput for the marked Counter ID should be calculated and displayed in MassMan.Figure 2-37 MassMan - Maintain Counter© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 28/38
  • 2.4.1.3 MassMan – CustomizingOn the MassMan start screen, by clicking on button , the customizing screen will bedisplayed as Figure 2-38. On the panel “Main Screen Options”, the GUI of the main screen can beconfigured. In panel “RFC Settings”, different pre-configured RFC connections can be selected. The mass runfrom the different RFC destinations can be loaded through the RFC connections. As configured in Figure2-38, mass runs started from system BPP client 010 and MM1 client 300 can be displayed.In panel “Central Customizing” different MassMan functionality can be activated by choosing the check-box“active?”. We recommend that the rest setting should be left as default.Figure 2-38 MassMan - Customizing© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 29/38
  • 2.4.1.4 MassMan – Job listChoose the button “Execute” from the MassMan start screen. All the mass runs that satisfy the selectionconditions are listed.Figure 2-39 MassMan – Mass run detail viewFigure 2-39 the upper part is a list of function buttons, the lower part is a list of job with detail information.The Button is a refresh button. It refreshes only the runs that are already displayed. New one will not bedisplayed.The Button is a refresh button. It checks the mass run log and displays all the mass run thatsatisfy the selection conditions.The Button shows all child jobs that started by the selected job. The mass run uses the PPFramework. It can start child jobs in parallel. During the processing additional information like memoryutilization on work process level is available.The button jumps to the SAP standard job log in the target system/client.The button jumps to the SAP global work process overview.The button jumps to the Post Processing Office where failed objects can be reprocessed.The button jumps to the PP Framework.The button jumps to the standard SAP application log (SLG1) in the target system/client where theapplication error can be analyzed.The button shows the server statistics of memory usage, paging rate for each server. Theinformation is coming from SAPOSCOL.Below the function buttons, the selected mass runs are listed. The meaning of different columns areexplained as followsColumns DescriptionSys/Clt The system ID and client where the mass run is executedHist If selected, the mass run is stored in MASSMAN history table, otherwise from PP Framework table.Jobname If field is empty, it is started in dialog mode, otherwise as background job.Application SAP predefined application type for the mass run.Description Job descriptionExt. Runid External run ID, can be specified by the customer to identify different mass runsStatus Different status of the mass run (R: Running, F: Finished, A: Aborted, P: Postprocessing)© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 30/38
  • Startdate, These three fields are the time-stamp to specify when the mass run is started and finished. It isStarttime, the time window that the parallelization framework is called. It is a subset of job start time andEndtime finish time from SM37.%ready It is the percentage of the progress.est. rem It is the estimated remaining time that the mass run still needs to run before it finishes.Durationest. Durat. It is the estimated total run time for the mass run. It is used only during the processing. When the mass run is finished, it is set to 0.Duration The real run time that the mass run needs.Counter If the number of selected objects is available for the mass run, it will be displayed in Counter.Throughput Throughput is the estimated number of processed objects per hour.Jobs Total number of started jobs for the mass run (parent job + child jobs)Act Number of currently active jobsCompl. Number of currently completed jobsCan. Number of canceled jobsAPPL Average CPU usage (per hour) from the time the mass run is runningDB Average DB usage (per hour) from the time the mass run is runningTable 2-9 MassMan – Job detail view (description of column)The information collected by the MASSMAN is sent back to the solution manager for display and triggeralerts.2.4.1.5 MassMan - Forecast ActivationThe forecast process estimates the number of objects to be processed for a specific mass run type before themass run starts. In this part, we will describe how to activate Forecast functionality in MassMan.First in MassMan “Maintain Customizing” screen, select check box “Enable Forecast” and in “CentralCustomizing” panel, select “C_FORECAST” check box, then save.From MassMan start screen, select “Forecast Customizing” button as Figure 2-40.Figure 2-40 MassMan – Forecast PanelFigure 2-41 shows the customizing screen of the forecast. The Forecast functionality is currently onlyavailable for selected process steps from Transactional Banking and Banking Services. The form routinespecified in “Method” column return the forecast value. The customer can extend the forecast functionality bydeveloping their own methods. If the checkbox in column “Counter for MassMan” is selected, then theforecast functionality for the specified application is activated.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 31/38
  • Figure 2-41 MassMan – Forecast CustomizingTo start the forecast process, in Figure 2-40 select the “Jump to Forecast” button, the forecast start screen isdisplayed as Figure 2-42. Please configure the parameter in selection screen as displayed in Figure 2-42,only the parameter Selection date should be set to current posting date. After execution, the forecast resultwill be displayed.Figure 2-42 Forecast – Start screen2.4.2 Monitoring in Solution Manager BPMBPM from Solution Manager is a central monitoring tool. It calls different data collectors in satellite systemslike MassMan and manages the alerts centrally. In the next part, we will explain how to monitor massactivities for Banking in BPM.2.4.2.1 Monitoring OverviewThe operation view can be accessed by transaction code SOLMAN_WORKCENTER.Figure 2-43 is the overview of the available solutions and the number of alert messages for each solution.The usage of the various SOLMAN_WORKCENTER requires specific roles/authorization described in note834534.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 32/38
  • Figure 2-43 Operation – OverviewFrom the Alert mode, you can choose between “Current” and “Open”. If “Current” is chosen, it shows thenumber of messages created from the latest data collection run. If “Open” is chosen, it shows the number ofmessages that is not confirmed yet.Table 2-10 describes the meaning of different icons used to rate the business processes and steps.Icon Description The business process is not activated. The business process is activated, but no message is received from the monitored system The business process is activated and only green messages are received from the monitored system. The business process is activated and yellow message is received from the monitored system The business process is activated and has received red alerts.Table 2-10 Operation – Icon Description2.4.2.2 Business ProcessFrom the solution overview, select the business process; the business process view is displayed. In thebusiness process view, each process step is displayed with alert rating as Figure 2-44.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 33/38
  • Figure 2-44 Operation - Business Process View2.4.2.3 Alert detailClick the step “Execute Account Settlement” from Figure 2-44 , the configured KPIs (alert type) for that step isdisplayed as Figure 2-45. It gives the information about rating and status of each KPI.Figure 2-45 Operation – Process Steps ViewSelect one line of KPI, the threshold setting of that KPI (alert type) will be displayed below as shown in Figure2-46.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 34/38
  • Figure 2-46 Operation - Alert of monitoring key figures2.4.2.4 Alert Message Detail ViewFrom Figure 2-46 click the link under Alert Type, you will jump into the alert detail view as Figure 2-47 shows.In the alert detail view (operation mode), under each monitoring key figure, the alert messages belonging tothat key figure are displayed. After each data collector run, if new mass run is detected, a new entry is addedto the alert list. The alert message is rated according to the threshold configuration. The rating can be red,yellow or green.To view the detail of the alert message in the satellite system, you first need to select the alert message byclicking the check box, and then click the button in the tool bar.When a red alert is solved in the monitored system, first select the alert check box; click the button to confirm the red message.Figure 2-47 Operation - Alert List© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 35/38
  • Table 2-11 describes the meaning of the important columns from alert list.Columns DescriptionRating Symbol of rating, it can be green, yellow and red.Date, Time These two fields is the time that data collector is executed in monitored systemStart Date, Start Time This is the time that the mass run is executed in monitored systemJob Name The name of the job in SM37.Step The step number the monitored mass run is executed.Logical Unit The Bank Posting Area or legal entity of the monitored mass run.Measured Value The value of the KPI at time point the collector is executed.Table 2-11 Operation – Alert Message Column Description© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 36/38
  • 3 Further Information3.1 Background Information and ReferencesBelow is a list of useful information regarding Solution Manager and Business Process Monitoring http://service.sap.com/bpm -> Media Library -> Technical Information http://service.sap.com/solutionmanager http://service.sap.com/solutionmanagerbp List of Best Practice Documents SAP Note 521820 SAP Note 784752© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 37/38
  • © Copyright 2010 SAP AG. All Rights ReservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of CitrixSystems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Instituteof Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form orfor any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document containsonly intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to anyparticular course of business, product strategy, and/or development. Please note that this document is subject to change and may bechanged by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that mayresult from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may accessthrough the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warrantywhatsoever relating to third-party Web pages.© 2010 SAP AG - Best Practice Monitoring SAP Banking Parallel Processing Jobs page 38/38