Business Process Monitoring for non-ABAP/non-SAP

56 Pages·2010·1.89 MB·English

Business Process Monitoring for
non-ABAP/non-SAP
Application Monitoring
SAP AG
Global CoE Business Process Integration
Active Global Support
© SAP 2010 / BPMon via Web Service / Page 1
Agenda
1. Introduction
2. Application Monitoring with generic access paths
3. Application Monitoring with specific access paths
4. Appendix
© SAP 2010 / BPMon via Web Service / Page 2
Overview - Business Process Monitoring in the
SAP Solution Manager (present situation)
Solution Manager
Continuous Online Alert Monitoring
Solution Landscape Presently:
ERP SCM BI CRM
Strong focus on
SAP ABAP-based
Products
© SAP 2010 / BPMon via Web Service / Page 3
Overview - Business Process Monitoring in the
SAP Solution Manager (new extensions)
Solution Manager
Reporting Notifications
Continuous Online Alert Monitoring
Solution Landscape
ERP SCM BI CRM
Future:
External External Log File &
New / extended
External
API call: Alert push: Data File
Database
RFC or HTTP-Post Monitoring BPMon connectivity
Access
Webservice or XML-file
features to include
monitoring of non-ABAP
and non-SAP Products
Partner / non-SAP / Legacy
Software Products
© SAP 2010 / BPMon via Web Service / Page 4
BPMon Data Collectors for non-ABAP/non-SAP
New features for Business Process Monitoring
to monitor non-ABAP/non-SAP systems
Application Monitoring on Remote Databases
(cid:132)
(cid:132) With generic monitoring object
(cid:132) With specific monitoring object ( available for TriplePoint CSL)
Application Monitoring using Web services
(cid:132)
(cid:132) Push-mechanism
(cid:132) Pull-mechanism
Application monitoring based on data extracted to SAP BW
(cid:132)
Reusable framework for customer-specific implementations
(cid:132)
© SAP 2010 / BPMon via Web Service / Page 5
Data Collection via Remote Database Access
External Application Data Collector
(cid:132) ABAP coding (in ST-A/PI) using BPMon Infrastructure
(cid:132) Collector runs on Solution Manager as „ABAP Bridge“
Database of non-ABAP between BPMon and non-ABAP system
/ non-SAP application (cid:132) Uses remote DB connectivity via ADBC
(cid:132) Supports counting (=measured value) and detail display
Requirements & Prerequisites
(cid:132) Available for any SAP supported DBMS
DBSL + (cid:132) DBSL + DB Client installed on SAP Solution Manager
DB Client
(cid:132) Remote DB Connection maintained in SAP DBA Cockpit
ADBC
Potential Concerns & Restrictions
ABAP Data
(cid:132) Secure Access to remote DB
Collector
(cid:132) Authorization checks via SAP ABAP Stack
(cid:132) Own DB Logon User with limited authorization, e.g.
Periodic Calls
read access to specific schema / data only
BPMon Infrastructure (cid:132) Performance
(cid:132) Balance between frequency of data collection and
SAP Solution Manager
size of database table
Data Collection via external API calls
External Application Requirements & Prerequisites
(cid:132) External application
Web Web Service
Service Consumer (cid:132) provides a remote-enabled function module
or Web Service
(cid:132) or can call a Web Service or remote-enabled
function module
(cid:132) Solution Manager BPMon Framework needs to
provide capabilities to attach Monitoring Object to
external component but execute it in Solution
Web Service Web
Manager
Consumer Service
Requirements & Prerequisites
(cid:132) Web Services can be called from many
ABAP Data
environments and are language independent
Collectors
Potential Concerns & Restrictions
Periodic
(cid:132) RFC enabled FM or Web Service needed
Calls
(cid:132) Collector needed (low effort)
BPMon Infrastructure
SAP Solution Manager
© SAP 2010 / BPMon via Web Service / Page 7
Data Collection based on data extracted to
SAP BW
External Application
Data Collector
(cid:132) ABAP coding (in ST-A/PI) using BPMon Infrastructure
External BW extractor
(cid:132) Collector runs on Solution Manager as „ABAP Bridge“
/ SMD agelet between BPMon and non-ABAP system
(cid:132) Uses BW connectivity via RSDRI
(cid:132) Supports counting (=measured value) and detail display
Requirements & Prerequisites
(cid:132) BW activated and external application stores data in BW
BW Info Object (cid:132) Remote RFC Connection to BW maintained
(cid:132) Desired: SMD activated
RSDRI
Potential Concerns & Restrictions
ABAP Data (cid:132) Secure Access to BW
Collector
(cid:132) Authorization checks via SAP ABAP Stack
(cid:132) Performance
Periodic Calls
(cid:132) Balance between frequency of data collection and
BPMon Infrastructure size of BW Info Cubes
SAP Solution Manager
Possible Use-cases for Remote DB Access
within BPMon Application Monitors
Use-case 1: Fully generic data collector similar to generic table
counter „BOTABCNT“ for ABAP database
(cid:132) User needs to know the data model in order to enter table and field names
(cid:132) Complete SELECT statement is generated at runtime
(cid:132) As substitute/workaround only, if there is no standard collector available
Use-case 2: Predefined SELECT statement for known non-ABAP /
Partner product („half generic“)
(cid:132) Only predefined user parameters with descriptions are shown in BPMon setup
(dynamically)
(cid:132) The entered user parameters are converted into a where-clause and are added
to the delivered statement template during runtime
(cid:132) Complexity and technical details are hidden
Use-case 3: Complex data collector (for known non-ABAP / Partner
product) including application logic
(cid:132) Hard-coded in ST-A/PI like a normal application monitor and called from
BPMon as individual collector, using ADBC for remote database access
(cid:132) User parameters are statically defined at design time by SAP
Agenda
1. Introduction
2. Application Monitoring with generic access paths
1. On Remote DB
2. Using Web services
3. Using BW data
3. Application Monitoring with specific access paths
4. Appendix
© SAP 2010 / BPMon via Web Service / Page 10