SAP AG 2005

BPM
Condensed Set up Gui de
SAP AG 2005
Generate
Set up Pr oc edur e BPMon ST320 ST-SER2005_1_620
Set up Interface Monitoring
in Satellite System
Create Logical Component
Create Business Process
Set up Monitoring
Customizing
Activate
Use the Monitoring
Create Product, Server, Database and System
Create RFC Destinations and Maintain SAP Server Names
Create Logical Component
Assign Logical Components to Solution
Create Contact Persons
Choose Business Scenario
Create Business Process and Business Process Steps
Arrange Process Graphic and Create Process Flows
Define Solution Support Organization
Choose Business Process and Process Steps to be monitored
Define Monitoring Objects per Step
Per Monitoring Object:
Provide technical Details and Threshold Values for the Alerts.
Assign Monitoring Transactions and Set up Monitoring Tasks.
Set up Automatic Emails and Service Desk Messages
Observe Alerts Relative to the Business Process
Check Detailed Alert Information and Check for Open Alerts
Review Historic Alerts
Analyze Problem in the Satellite System
Create Service Desk Message
Confirm Alerts for Solved Problems
Where
Details
Solution Manager:
System Maintenance
Solution Manager:
Entrance Screen
Solution Manager:
Solution Directory
Solution Manager:
BPMon Setup Session
Solution Manager:
Monitoring Graphic
BPMon Session
Generate Monitoring Customizing
Generate Local RFC Destination and set Data Collector Frequencies
Activate Monitoring
Set up Interface Monitoring
in the Solution Manager
Satellite System
Solution Manager:
BPMon Setup Session
Set up qRFC and IDOC Monitoring in the Satellite Systems
Solution Manager:
BPMon Session
Specify Interface Details
Assign Monitoring Objects to the Interface
Assign Analysis & Monitoring Tools and Set up Monitoring Tasks.
Set up Automatic Emails and Service Desk Messages
Create Solution
Create Solution
SAP AG 2005
WHERE: Sol ut i on Manager Ent r anc e Sc r een
You can always go to the Entrance Screen via
Solution Overviewin the Main Screen of the
SAP Solution Manager.
The first execution of transaction DSWP takes
you automatically to the Entrance Screen of the
SAP Solution Manager.
SAP AG 2005
WHERE: Syst em Mai nt enanc e
The System Landscape Maintenance can be accessed via
Operations Setup ->Solution Landscape ->System Maintenance
in the Main Screen of the Solution Manager. Alternatively, you can use transaction SMSY.
SAP AG 2005
WHERE: Sol ut i on Di r ec t or y
In the Solution Directory you can assign logical components to the solution and create business processes.
You can access the Solution Directory via
Operations Setup -> Solution Landscape -> Solution Landscape.
SAP AG 2005
WHERE: Busi ness Pr oc ess Moni t or i ng Set up Sessi on
The Business Process Monitoring Setup session
is available only after a business process has
been created. You find this session in the area
Operations Setup ->Solution Monitoring ->
Business Process Monitoring.
There is one Business Process Monitoring Setup
session per solution landscape.
In this session, you can maintain the monitoring
customizing for all business processes and
interfaces contained in the solution landscape.
SAP AG 2005
WHERE: Sat el l i t e Syst em
To set up interface monitoring there are a number of activities that have to be carried out in the systems that
are supposed to be monitored. These systems are called Satellite Systems.
SAP AG 2005
WHERE: Busi ness Pr oc ess Moni t or i ng Sessi on
To access the Business Process Monitoring session choose
Operations ->Solution Monitoring ->Business Process Monitoring.
You can access the session via the left icon in the process graphic (either process alert if monitoring is
active or match if monitoring is not active).
SAP AG 2005
WHERE: Moni t or i ng Gr aphi c
To access the monitoring graphic choose
Operations ->Solution Monitoring ->Business Process Monitoring.
SAP AG 2005
Cr eat e Sol ut i on
Via Newyou create a new solution landscape.
In the next screen, specify a name for the solution and the language that you want to use.
Choose to create
new solution.
Enter the solution name and
your customer number.
SAP AG 2005
Cr eat e Pr oduc t
You can either use an existing product or create a new product. It is also possible to create non-SAP
products or to use the predelivered products.
Right mouse click on
any product.
Fill in the
information.
Product has
to be active.
SAP AG 2005
Cr eat e Ser ver
Servers are created in area Landscape Components.
Right mouse click
on Server.
SAP AG 2005
Cr eat e Dat abase
Databases are created in area Landscape Components.
Right mouse click on
Databases.
SAP AG 2005
Cr eat e Syst em
Create the new system and assign it to the corresponding product.
In order to completely document a business process all concerned systems (also non-SAP) should be
available in the Solution Manager.
Right mouse click on Systems to
create a new system.
Area Landscape
Components.
continued on next slide
System that are supposed
to be monitored have to be
in status Production
SAP AG 2005
Pr ovi de Syst em Det ai l s
You can maintain systems manually or import the information from LIS (Landscape Infrastructure Server)
or SLD (System Landscape Repository).
In the tab Header Data, the system number, the message server and the installation number for the
respective system have to be specified. You can also specify the database for the system.
In tab Clients the client of the satellite system that you want to monitor has to be specified as well.
Provide system
information.
Enter the client of the
system that is to be
monitored.
SAP AG 2005
Cr eat e RFC Dest i nat i ons
To create the RFC destinations mark the line with
the client the destinations are supposed to point to.
Then choose Generate RFC Destinations.
Mark the line with the client and
choose Generate RFC.
In the popup select and deselect the fields as
shown in the screenshot (example).
SAP AG 2005
Spec i f y SAP Ser ver Names
For setting up performance monitoring for dialog transactions you need the SAP Server names in tab
Instances. You can either enter this information manually or read the data from the system via
Read System Data Remote.
Choose to read the system data or
enter instances manually.
SAP AG 2005
Cr eat e Logi c al Component
A logical component represents a logical unit of systems, usually representing a transport layer consisting of
a development system -> test system -> production system with the respective client. You can create your
own logical component and assign your systems.
Right mouse click on Logical
Components to create a new
component.
Go to area System Groups and
Logical Components.
Specify Information.
The status of the
logical component
has to be active.
Assign system:client to the
logical component in role
Production System.
SAP AG 2005
Assi gn Logi c al Component s t o Sol ut i on
Assign the logical components to the solution in tab System Group of node <solution name>via the value
help. Observe that the leading role for the solution determines which of the systems contained in the logical
component will be relevant for monitoring.
Assign logical
component via
value help.
Leading Role
SAP AG 2005
Cr eat e Cont ac t Per sons
Tab Contacts in node <solution name>is the only place where you can create or change contact persons.
These persons can later on be assign to the various monitoring tasks.
Create or change
contact persons.
SAP AG 2005
Choose Busi ness Sc enar i o
Business Scenarios are created via entries in the tab Structure in node Business Scenarios. You have to
set the business scenario to Production if you want to set up Business Process Monitoring for the
processes within this business scenario.
Specify Scenario (free
text or value help).
Set status to
Production.
SAP AG 2005
Cr eat e Busi ness Pr oc ess
Business processes are created via entries in the tab Structure in node Business Processes. You have to
set the business process to Production here if you want to set up monitoring for the process.
Define Business
process (free text or
value help).
Set status to
Production.
SAP AG 2005
Cr eat e Busi ness Pr oc ess St eps
Business process steps are created via entries in the tab Structure in node <process name>. To each step
you have to assign the logical component where it is executed.
Define Business
Process Step (free text
or value help).
Assign logical component
via value help.
SAP AG 2005
Ar r ange Pr oc ess Gr aphi c
In node <process name>there is also a tab Graphic available. This is the only place where you can change
the layout of the process graphic.
Mark the box. Change size and
position via drag and drop.
SAP AG 2005
Cr eat e Pr oc ess Fl ow s
Process Flows (logical flows and interfaces) are created in the process graphic in node <process name>in
tab Graphic. The arrows in the graphic are created via right mouse click. Asynchronous lines leave or enter
the step boxes at the top or bottom, synchronous lines at the sides.
There is no cross relevance to the interface technique. The interface might still be assigned any interface
technique, independent of its status in the graphic.
Right mouse click on
the sender step.
Right mouse click on
the receiver step.
SAP AG 2005
Def i ne Sol ut i on Suppor t Or gani zat i on
The Solution Support Organization is created in node Solution Support Organization and its sub-nodes.
You have to define teams and assign member to the teams as well as specify monitoring roles.
Add new team.
Enter team members and
define monitoring roles.
SAP AG 2005
Choose Busi ness Pr oc ess t o be Moni t or ed
In node Business Processes choose which business processes are supposed to be monitored. By saving
your selection the respective sub-nodes for the business processes are created in the session.
Choose Business
Process.
SAP AG 2005
Choose Busi ness Pr oc ess St eps t o be Moni t or ed
In node BPMon <process name>choose which business process steps are supposed to be monitored. By
saving your selection, the respective sub-nodes for the business process steps are created in the session.
Choose Business
Process Steps.
SAP AG 2005
Per St ep: Def i ne Moni t or i ng Obj ec t s
Choose which objects should be monitored in node Step <No.><Step name>(<SID>). When saving, a sub-
node is created in the session for each of the selected monitoring objects.
Choose Monitoring Types.
SAP AG 2005
Per Moni t or i ng Obj ec t : Pr ovi de Tec hni c al Det ai l s
Provide technical details for the monitoring object in node <monitoring type>. Technical details include
names and start procedures for background jobs, application logs, names of dialog transactions etc.
Provide technical details.
SAP AG 2005
Per Moni t or i ng Obj ec t : Pr ovi de Thr eshol d Val ues
Provide threshold values for the monitoring objects. The nodes in which the thresholds can be specified
depend on the monitoring object.
Provide threshold values.
SAP AG 2005
Per Moni t or i ng Obj ec t :
Assi gn Anal ysi s & Moni t or i ng Tool s
In node Analysis & Monitoring Tools it is possible to assign analysis transactions as direct links from the
solution manager into the satellite system. You can also define URLs as links for the monitoring employee to
access further documentation about the monitoring object.
Define Analysis
Transactions.
SAP AG 2005
Per Moni t or i ng Obj ec t : Set up Moni t or i ng Task s
Monitoring Tasks to the various members of the Solution Support Organization are assigned in node
Monitoring Activities. For each process step and monitoring type define a person responsible for the
monitoring (via value help). In the same table define the monitoring frequency, problem indicator, error
handling procedure, and escalation path.
People who are assigned in this check must have been defined as belonging to that particular team in the
Solution Support Organization earlier in this session in node Solution Support Organization.
Set up Monitoring Tasks.
SAP AG 2005
Per Moni t or i ng Obj ec t :
Set up Aut omat i c Emai l s and Ser vi c e Desk Messages
In node Notifications you can set up emails to be
sent automatically for alerts. Prerequisite is that
transaction SCOT has been set up in client 000 ion
the Solution Manager system and there is a user in
client 000 available that has a valid email address
assigned in its user data in SU01.
Set up Emails to be sent.
In table Support Notifications you can set up
Service Desk messages to be created
automatically for alerts or provide templates for the
manual creation of Service Desk message. For the
automatic creation, all fields except Text Template
must be filled.
Set up automatic
Service Desk messages.
SAP AG 2005
Set up qRFC Moni t or i ng i n t he Sat el l i t e Syst em
The qRFC Monitoring in the satellite system is set up via transaction RZ21. For the detailed procedure
please check SAP Note 441269. Since the monitoring objects created on the satellite system are
considered as customizing, they have to be created on the development system first and from there
transported to the productive system. To navigate in transaction RZ21 always mark the respective line in the
table on the right hand side and then choose the next sub-node in the check tree on the left hand side.
Choose
Technical Infrastructure
->Configure qRFC-Monitoring Groups.
Create an owner via New entries.
There can be only one activate owner
per satellite system.
continue on next slide
SAP AG 2005
Set up qRFC Moni t or i ng i n t he Sat el l i t e Syst em
During the setup of the monitoring objects there are a number of free text fields to be filled. Only at the very
end of the setup you have to define whether the queues are inbound or outbound and specify the name of
the queue thats actually supposed to be monitored.
Fill the free text field.
Specify whether the
queues are outbound
or inbound.
Enter the queue name and
the client here. Generic
entries for queue names are
possible (using * at the end
of the name).
SAP AG 2005
Set up I Doc Moni t or i ng i n t he Sat el l i t e Syst em
continue on next slide
You can create IDoc monitoring objects on the satellite system via transaction BDMO. These objects are
considered as customizing. Therefore, they have to be set up in the development system and from there
transported via the quality assurance system to the productive system.
To create a monitoring object choose
Create/Activate Monitoring Object.
Create a new
monitoring object
via New entries.
Set the monitoring
object to active.
SAP AG 2005
Now assign one or more message types to the monitoring object via Change monitoring object. If the
same interface should be monitored on the sending system as well as on the receiving system, you have to
create the respective monitoring objects on both these systems.
To actually activate the monitoring objects then choose Monitoring Object / Start all in the entrance screen
of transaction BDMO.
Set up I Doc Moni t or i ng i n t he Sat el l i t e Syst em
Choose
Change monitoring object
to assign message types to
the monitoring object.
Specify which
IDoc types should
be monitored.
Specify which system
the messages are sent
to or received from.
Specify how long
alerts should be
stored on the
satellite system.
SAP AG 2005
Spec i f y I nt er f ac e Det ai l s
In node Interface Monitoring specify the interface technique and interface name, and mark the interface for
monitoring. When saving, the respective sub-nodes for the interface are created in the session.
Specify interface name and
technique and flag for monitoring.
SAP AG 2005
Assi gn Moni t or i ng Obj ec t s t o t he I nt er f ac e
Load the monitoring objects from the satellite system into the value help in node Interface <interface name>
and afterwards assign the monitoring objects to the interface via the value help.
You can assign several monitoring objects to the same interface. If you want to monitor an interface on the
outbound side and the inbound side you have to assign the respective monitoring objects from the sending
system and the receiving system to the same interface.
Load existing monitoring
objects from the satellite
system.
Assign objects via
value help.
continue on next slide
SAP AG 2005
Ac t i vat e I nt er f ac e Al er t s and Pr ovi de Thr eshol d
Val ues
Activate the interface alerts in node Alert Monitors. You can change the threshold values for the
monitoring objects or use the thresholds that already have been maintained on the satellite systems.
Activate alerts and
provide thresholds.
Reload alerts and
thresholds from the
satellite system.
SAP AG 2005
Gener at e Cust omi zi ng
Monitoring Customizing is generated in node Generate Monitoring Customizing, individually for each
business process.
Choose to generate.
SAP AG 2005
Gener at e Loc al RFC Dest i nat i on and Set Dat a
Col l ec t or Fr equenc i es
In node Data Collector Frequencies choose the
frequencies with which alert information for your
monitoring objects should be collected. These
settings are valid for the whole solution, not just for
individual business processes!
Choose
frequencies.
Green icon means no action
is required in this node.
For the functioning of Business Process Monitoring
you need a local RFC destination on the Solution
Manager system. You can check the existence in
node Local RFC Destination for Data Collection.
If Availability in this node is rated red, you need to
create this RFC destination here.
SAP AG 2005
Ac t i vat e Moni t or i ng
To activate, choose Activate Monitoring in node Activation. With the activation of the monitoring the sub-
nodes for the business process are created.
Choose to
activate.
SAP AG 2005
Use t he Moni t or i ng
To get a demonstration how to use the monitoring (navigate in the active solution, display alerts, analyze
errors, confirm solved problems etc.) we recommend the Tutorial Alert Handling within SAP Business
Process Monitoring available in the media library of SAP Service Marketplace , quicklink /BPM.
Tutorial
SAP AG 2005
Quest i ons or Pr obl ems
For questions, problems and error messages,
please refer to the Business Process Monitoring
Setup Guide. You can find the current version in
the SAP Service Marketplace in the media library
of quicklink /BPM.
Please open an OSS message on queue
SV-SMG-MON-BPM
for Business Process Monitoring related problems
you cannot solve with the BPMon Setup Guide or
SAP Note 558643.
Setup Guide
SAP AG 2005
Copyr i ght 2005 SAP AG. Al l Ri ght s Reser ved
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, 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 IBM Corporation in the United States and/or other
countries.
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 Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of 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 their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. 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.
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.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP

product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed 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 the information, 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 may result 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 access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.