BPM_Setup
59
0
0
Full text
(2) Business Process Monitoring Configuration Roadmap Configure SAP Solution Manager & Connect and configure monitored systems. Creation of Monitoring Solution. Configure Monitoring Objects. © 2012 SAP AG. All rights reserved.. Setup basic functions in SAP Solution Manager Needs to be performed usually once (and after support package installations if update is needed) Connect monitored system to Solution Manager Include systems into logical components Needs to be performed for every system to be included in BPMon Performed by Solution Manager system administrator in SolMan_Setup. Create solution for monitoring (include logical components and processes) Needs to be performed once as a prerequisite for the configuration Performed by BPMon expert together with Business Process Owners. . Select and configure of actual monitors for BPMon Depending on business process information in SAP Solution Manager Needs to be performed for every business process to be monitored Performed by BPMon expert in the BPMon Setup tool based on input from Business Process Owners RKT. 2.
(3) Business Process Monitoring Configuration Roadmap Configure SAP Solution Manager & Connect and configure monitored systems. Creation of Monitoring Solution. Configure Monitoring Objects. © 2012 SAP AG. All rights reserved.. Setup basic functions in SAP Solution Manager Needs to be performed usually once (and after support package installations if update is needed) Connect monitored system to Solution Manager Include systems into logical components Needs to be performed for every system to be included in BPMon Performed by Solution Manager system administrator in SolMan_Setup. Create solution for monitoring (include logical components and processes) Needs to be performed once as a prerequisite for the configuration Performed by BPMon expert together with Business Process Owners. . Select and configure of actual monitors for BPMon Depending on business process information in SAP Solution Manager Needs to be performed for every business process to be monitored Performed by BPMon expert in the BPMon Setup tool based on input from Business Process Owners RKT. 3.
(4) The BMon Scenario in SolMan_Setup. Addresses business process independent prerequisites and setup for Business Process Monitoring in SAP Solution Manager: • • • • •. Software and plug-in prerequisites BI content activation Setup of the BPMon infrastructure Migration of previous BPMon setup into the new BPMon setup tool Template users in Solution Manager. and the managed systems • • • •. RFC destinations to the managed system Registration of the managed system in the monitoring infrastructure Initial load of the monitor definitions from the managed system Communication users in the managed system. © 2012 SAP AG. All rights reserved.. RKT. 4.
(5) The BPMon Setup via SolMan_Setup. First the SAP Solution Manager itself has to be prepared and the managed (monitored) systems have to be connected and configured. © 2012 SAP AG. All rights reserved.. RKT. 5.
(6) The BPMon Setup via SolMan_Setup. Then the BPMon specific technical prerequisites have to be done.. © 2012 SAP AG. All rights reserved.. RKT. 6.
(7) The BPMon Setup Scenario in SolMan_Setup Configure Automatically. Check and activate the BW cubes for BP Analytics and BPMon Trend Analysis Check the Service Preparation Check is performed completely.. Make sure you include BPM checks, if you run RTCCTOOL manually. © 2012 SAP AG. All rights reserved.. Schedule the new extractors to load alert data from the BPMon alert table. If SAP Solution Manager already contained BPMon setup from before Solution Manager 7.1 SP 05 you will see an additional activity called “Migrate Monitoring Customizing”. This activity automatically migrates the prior SP 05 BPMon setup to the new BPMon Setup tool. RKT. 7.
(8) Configure Solution Manager Create Local BPMon Connection. In this step you will create a local RFC destination called BPM_LOCAL_<client> •. The RFC destination point from client 000 to the productive client in SAP Solution Manager. •. BPMon data collection is triggered by every 5 minutes by the AUTOABAP running in client 000 with the user SAPSYS. •. If a data collection is due for a monitoring object the task is transferred via local RFC using destination BPM_LOCAL_<client> to user SM_BPMO in the productive due to authorization limitations for user SAPSYS.. © 2012 SAP AG. All rights reserved.. RKT. 8.
(9) Configure Solution Manager Create Template Users. Different users take part in the process of business process monitoring, in this step you create template users for different tasks in the BPMon process •. Template users for different tasks are equipped with reasonable authorizations for their specific task. •. Customers can reuse these users as template for their own role concept. User for BPO administration (setup and configuration) User for BPMon operations (monitoring and alerting). User for CrossDatabase Comparison functionality Display user for business processes and monitoring. User for BPMon reporting functionality. © 2012 SAP AG. All rights reserved.. RKT. 9.
(10) Select Monitored System and Select Client. In the steps 2 and 3 of the setup you select the managed system you want to setup Business Process Monitoring for: •. The following setup steps have to be performed for every single managed system. •. Business Process Monitoring also collects client-depended business-transactional data: •. BPMon setup need to be performed for the productive client of the managed system, to make sure data collectors run in the right client. © 2012 SAP AG. All rights reserved.. RKT. 10.
(11) Configure Monitored Systems (1/2). In the first three steps of the monitored system configuration the connectivity is checked and the system is placed in the monitoring infrastructure of SAP Solution Manager:. Check RFCs needed for BPMon exist for the managed system to the selected client. Insert the system in the monitoring infrastructure in transaction RZ21 in Solution Manager, to enable the integration of local CCMS MTEs into BPMon. Check the user used in the READ RFC has the required authorizations. For some BP monitoring functionality additional authorizations are needed. See SAP Note 784752 for details.. © 2012 SAP AG. All rights reserved.. RKT. 11.
(12) Configure Monitored Systems (2/2). In the second three steps the status of the plug-ins ST-PI and ST-A/PI are checked and the monitoring definitions are load to SAP Solution Manager. Check that the plugins ST-PI and STA/PI have the recommended release and SP level. Check the service preparation check ran successfully in the managed system and all recommendations are implemented. © 2012 SAP AG. All rights reserved.. Load the monitoring definitions from the managed system to SAP Solution Manager. Monitors and data collectors for Business Process Monitoring are shipped with the ABAP add-on STA/PI and are depending on the version and release of ST-A/PI installed on the managed system. Hence these monitoring definitions need to be loaded to SAP Solution Manager.. RKT. 12.
(13) Create Template Users. In this step the template users needed for BPMon in the managed system are created •. During the detailed analysis of an alert or the analysis of trend data, the user can jump from Business Process Operations in SAP Solution Manager to detailed screens showing the objects causing the alert (e.g. all erroneous IDocs causing an alert) Trusted RFC destinations and hence the authorization S_RFCACL is needed at least. •. Further authorizations depend on the scope of BPO in the managed system and need to be assigned according to the customers authorization concept and the BPO scope. User for BPO administration in the managed system User for BPO analytics in the managed system. © 2012 SAP AG. All rights reserved.. RKT. 13.
(14) Complete. The “Complete” step gives you an overview over the performed configuration and offers a jump-in to the Business Process Operations workcenter. © 2012 SAP AG. All rights reserved.. RKT. 14.
(15) Business Process Monitoring Configuration Roadmap Configure SAP Solution Manager & Connect and configure monitored systems. Creation of Monitoring Solution. Configure Monitoring Objects. © 2012 SAP AG. All rights reserved.. Setup basic functions in SAP Solution Manager Needs to be performed usually once (and after support package installations if update is needed) Connect monitored system to Solution Manager Include systems into logical components Needs to be performed for every system to be included in BPMon Performed by Solution Manager system administrator in SolMan_Setup. Create solution for monitoring (include logical components and processes) Needs to be performed once as a prerequisite for the configuration Performed by BPMon expert together with Business Process Owners. . Select and configure of actual monitors for BPMon Depending on business process information in SAP Solution Manager Needs to be performed for every business process to be monitored Performed by BPMon expert in the BPMon Setup tool based on input from Business Process Owners RKT. 15.
(16) Creation of Monitoring Solution WoC Solution Manager Administration. Create new solution.. Save… Business Process Monitoring Solution. … and then press button Solution Directory to add logical components and business processes. Alternatively you can access the Solution Directory via the BPO work center Common Tasks Maintain Solution Business Process Monitoring Solution (see next slide).. © 2012 SAP AG. All rights reserved.. RKT. 16.
(17) Accessing Solution Directory WoC Business Process Operations. Access to Solution Directory. © 2012 SAP AG. All rights reserved.. RKT. 17.
(18) Adding of Logical Components Solution Directory. © 2012 SAP AG. All rights reserved.. RKT. 18.
(19) Creation of Business Processes Solution Directory. © 2012 SAP AG. All rights reserved.. RKT. 19.
(20) Business Process Monitoring Configuration Roadmap Configure SAP Solution Manager & Connect and configure monitored systems. Creation of Monitoring Solution. Configure Monitoring Objects. © 2012 SAP AG. All rights reserved.. Setup basic functions in SAP Solution Manager Needs to be performed usually once (and after support package installations if update is needed) Connect monitored system to Solution Manager Include systems into logical components Needs to be performed for every system to be included in BPMon Performed by Solution Manager system administrator in SolMan_Setup. Create solution for monitoring (include logical components and processes) Needs to be performed once as a prerequisite for the configuration Performed by BPMon expert together with Business Process Owners. . Select and configure of actual monitors for BPMon Depending on business process information in SAP Solution Manager Needs to be performed for every business process to be monitored Performed by BPMon expert in the BPMon Setup tool based on input from Business Process Owners RKT. 20.
(21) Configure Monitoring Objects – BPMon Setup With SP05. Access Business Process Monitoring Setup Load Monitor Definitions Create Monitoring Object on Logical Component Level Create Monitoring Object on Step Level. Configure Monitoring Object Generate and Activate Utility Functions – NEW . Monitoring Object List Maintenance. . Cross Functions. © 2012 SAP AG. All rights reserved.. RKT. 21.
(22) Business Process Monitoring Setup Access BPMon Setup Tool. Access to BPMon Setup. © 2012 SAP AG. All rights reserved.. RKT. 22.
(23) Business Process Monitoring Setup Access BPMon Setup for Solution. Locate your solution.. © 2012 SAP AG. All rights reserved.. RKT. 23.
(24) Configure Monitoring Objects – BPMon Setup With SP05. Access Business Process Monitoring Setup Load Monitor Definitions Create Monitoring Object on Logical Component Level Create Monitoring Object on Step Level. Configure Monitoring Object Generate and Activate Utility Functions – NEW . Monitoring Object List Maintenance. . Cross Functions. © 2012 SAP AG. All rights reserved.. RKT. 24.
(25) Business Process Monitoring Setup Load Monitor Definitions. Check if the monitor definitions from your monitored system have been loaded. If not, load them.. © 2012 SAP AG. All rights reserved.. RKT. 25.
(26) Configure Monitoring Objects – BPMon Setup With SP05. Access Business Process Monitoring Setup Load Monitor Definitions Create Monitoring Object on Logical Component Level Create Monitoring Object on Step Level. Configure Monitoring Object Generate and Activate Utility Functions – NEW . Monitoring Object List Maintenance. . Cross Functions. © 2012 SAP AG. All rights reserved.. RKT. 26.
(27) Business Process Monitoring Setup Create Monitoring Object on Logical Component Level. Create monitoring objects for data collection.. © 2012 SAP AG. All rights reserved.. Note: Monitoring objects for alerting can not be created on logical component level, but only on step level. However, all monitoring objects for the system are listed and can be maintained, generated and activated. RKT 27.
(28) Configure Monitoring Objects – BPMon Setup With SP05. Access Business Process Monitoring Setup Load Monitor Definitions Create Monitoring Object on Logical Component Level Create Monitoring Object on Step Level. Configure Monitoring Object Generate and Activate Utility Functions – NEW . Monitoring Object List Maintenance. . Cross Functions. © 2012 SAP AG. All rights reserved.. RKT. 28.
(29) Business Process Monitoring Setup Create Monitoring Object on Step Level. Create monitoring objects for data collection and alerting.. Note: The monitoring object creation dialog is similar on step, interface and on logical component level.. © 2012 SAP AG. All rights reserved.. In order to create an alerting monitoring object as reference (i.e. alerting based on BI data), you have to follow the creation dialog (there is no separate button any more). RKT 29.
(30) Business Process Monitoring Setup Create Monitoring Object. Select the monitor and name it. (F4 is filled depending on your filter criteria). Press o.k.. © 2012 SAP AG. All rights reserved.. RKT. 30.
(31) Business Process Monitoring Setup Create Monitoring Object. Done. Now you need to configure it.. © 2012 SAP AG. All rights reserved.. RKT. 31.
(32) Configure Monitoring Objects – BPMon Setup With SP05. Access Business Process Monitoring Setup Load Monitor Definitions Create Monitoring Object on Logical Component Level Create Monitoring Object on Step Level. Configure Monitoring Object Generate and Activate Utility Functions – NEW . Monitoring Object List Maintenance. . Cross Functions. © 2012 SAP AG. All rights reserved.. RKT. 32.
(33) Business Process Monitoring Setup Configure Monitoring Object. After the creation of a monitoring object you can access its customizing by clicking on the monitoring object (e.g. monitoring object “Sales Documents”).. © 2012 SAP AG. All rights reserved.. RKT. 33.
(34) Business Process Monitoring Setup Configure Monitoring Object. Here you can get some information on the monitor (in case of application monitoring).. Select key figures …. © 2012 SAP AG. All rights reserved.. RKT. 34.
(35) Business Process Monitoring Setup Configure Monitoring Object. Maintain thresholds and …. … parameters.. © 2012 SAP AG. All rights reserved.. Note: There is a mass maintenance for parameters and thresholds in node “Monitoring Object List”. RKT 35.
(36) Business Process Monitoring Setup Configure Monitoring Object. Maintain when the monitoring object shall be executed …. … and if data collection shall be done via sRFC or via background job (which makes sense for long runners and monitoring objects, where a delayed execution is not a problem).. © 2012 SAP AG. All rights reserved.. RKT. 36.
(37) Business Process Monitoring Setup Configure Monitoring Object. Assign a notification template and / or maintain notification configuration on object level. Save and then activate it. Note: The configuration on object level dominates the configuration of the template.. © 2012 SAP AG. All rights reserved.. Note: “Notification Templates” can be defined in the “Cross Functions” section. RKT. 37.
(38) Business Process Monitoring Setup Configure Monitoring Object. Assign an analysis tool set and / or add additional analysis tools.. © 2012 SAP AG. All rights reserved.. Note: “Analysis Tool Sets” can be defined in the “Cross Functions” section. RKT 38.
(39) Business Process Monitoring Setup Configure Monitoring Object. Assign a monitoring team.. © 2012 SAP AG. All rights reserved.. Note: Monitoring teams can be defined in the “Cross Functions” section. RKT. 39.
(40) Business Process Monitoring Setup Configure Monitoring Object. Assign a monitoring activity template and / or maintain a monitoring activity.. © 2012 SAP AG. All rights reserved.. Note: Monitoring activity templates can be defined in the “Cross Functions” section. RKT 40.
(41) Business Process Monitoring Setup Configure Monitoring Object. Assign an alert parameter set.. Access the monitoring object to assign the suitable Parameter Set to it.. © 2012 SAP AG. All rights reserved.. Note: Alert parameter sets can be defined in the “Cross Functions” section. RKT 41.
(42) Configure Monitoring Objects – BPMon Setup With SP05. Access Business Process Monitoring Setup Load Monitor Definitions Create Monitoring Object on Logical Component Level Create Monitoring Object on Step Level. Configure Monitoring Object Generate and Activate Utility Functions – NEW . Monitoring Object List Maintenance. . Cross Functions. © 2012 SAP AG. All rights reserved.. RKT. 42.
(43) Business Process Monitoring Setup Generate and Activate for an Individual Monitoring Object. After finishing the customizing you have to generate and activate in order to start the monitoring and alerting.. © 2012 SAP AG. All rights reserved.. Note: In contrast to the past BPMon setup, you can not only activate all monitoring objects for a process, but also individual monitoring objects … RKT 43.
(44) Business Process Monitoring Setup Generate and Activate for a List of Monitoring Objects. After finishing the customizing you have to generate and activate in order to start the monitoring and alerting.. © 2012 SAP AG. All rights reserved.. … as well as a complete list of them (e.g. for a step or process), i.e. you will find in several places in the setup the possibility to activate. RKT 44.
(45) Configure Monitoring Objects – BPMon Setup With SP05. Access Business Process Monitoring Setup Load Monitor Definitions Create Monitoring Object on Logical Component Level Create Monitoring Object on Step Level. Configure Monitoring Object Generate and Activate Utility Functions – NEW . Monitoring Object List Maintenance. . Cross Functions. © 2012 SAP AG. All rights reserved.. RKT. 45.
(46) Business Process Monitoring Setup Maintain Monitoring Objects in a List. Access to the list maintenance.. © 2012 SAP AG. All rights reserved.. RKT. 46.
(47) Business Process Monitoring Setup Maintain Monitoring Objects in a List You can filter the monitoring objects of the current solution to your needs.. In the “Monitoring Objects” tab you can maintain the assignments of. © 2012 SAP AG. All rights reserved.. a). Notification Templates. b). Analysis Tool Sets. c). Monitoring Activities Sets. d). Monitoring Teams. e). Alert Parameter Sets RKT. 47.
(48) Business Process Monitoring Setup Maintain Monitoring Objects in a List. In the “Monitoring Schedules” tab you can maintain the data collection schedules and if the data collection shall be in background or not.. © 2012 SAP AG. All rights reserved.. RKT. 48.
(49) Business Process Monitoring Setup Maintain Monitoring Objects in a List. In the “Parameter Values” tab you can maintain the parameter values of application monitors.. © 2012 SAP AG. All rights reserved.. RKT. 49.
(50) Business Process Monitoring Setup Maintain Monitoring Objects in a List. In the “Thresholds” tab you can maintain the alert thresholds for of application monitors, i.e. for every individual parameter set. © 2012 SAP AG. All rights reserved.. RKT. 50.
(51) Configure Monitoring Objects – BPMon Setup With SP05. Access Business Process Monitoring Setup Load Monitor Definitions Create Monitoring Object on Logical Component Level Create Monitoring Object on Step Level. Configure Monitoring Object Generate and Activate Utility Functions – NEW . Monitoring Object List Maintenance. . Cross Functions. © 2012 SAP AG. All rights reserved.. RKT. 51.
(52) Business Process Monitoring Setup Cross Functions. Access to the maintenance of customizing, that can be linked to monitoring objects (Note that except for the notifications, changes to those linked objects are active after save, i.e. no explicit activation is necessary):. © 2012 SAP AG. All rights reserved.. a). Notification Templates. b). Analysis Tool Sets. c). Monitoring Teams. d). Monitoring Activities Templates. e). Alert Parameter Sets RKT. 52.
(53) Business Process Monitoring Setup Maintain Notification Templates. Create notification template …. … and maintain the configuration.. © 2012 SAP AG. All rights reserved.. RKT. 53.
(54) Business Process Monitoring Setup Analysis Tool Sets. Create tool set … … and maintain the configuration. (“Executable Unit”, is what will be executed.). © 2012 SAP AG. All rights reserved.. RKT. 54.
(55) Business Process Monitoring Setup Monitoring Teams. Create monitoring team …. … and add the members. (The input help of column “Name” is filled from the “Contacts” that can be maintained for the corresponding solution in the Solution Directory (see next slide).. © 2012 SAP AG. All rights reserved.. RKT. 55.
(56) Business Process Monitoring Setup Monitoring Teams – Access to Solution Directory: Contacts. Access to the contacts maintenance.. Access to Solution Directory.. © 2012 SAP AG. All rights reserved.. RKT. 56.
(57) Maintenance Functions Monitoring Activities Templates. Create monitoring activity template, maintain the frequency …. … and maintain the texts. © 2012 SAP AG. All rights reserved.. RKT. 57.
(58) Maintenance Functions Alert Parameter Sets. Create an “Alert Parameter Set” and maintain the configuration.. © 2012 SAP AG. All rights reserved.. RKT. 58.
(59) © 2012 SAP AG. All rights reserved.. No 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, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.. Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.. © 2012 SAP AG. All rights reserved.. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.. RKT. 59.
(60)
Related documents