JSM HC SetupGuide

Job Scheduling Management
Health Check -
Setup and User Guideline
SAP Job Scheduling

Management Health
Check
with SAP Solution

Manager
June 2012
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com
© Copyright 2011 SAP AG. All rights JAVA® is a registered trademark of Sun Microsystems, Inc.
reserved.
J2EE™ is a registered trademark of Sun Microsystems, Inc.
No part of this publication may be reproduced or transmitted in any JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,
form or for any purpose without the express permission of SAP AG. used under license for technology invented and implemented by
The information contained herein may be changed without prior Netscape.
notice.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business
Some software products marketed by SAP AG and its distributors Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,
contain proprietary software components of other software vendors. Management Cockpit, mySAP, mySAP.com, and other SAP products
and services mentioned herein as well as their respective logos are
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and trademarks or registered trademarks of SAP AG in Germany and in
SQL Server® are registered trademarks of Microsoft Corporation. several other countries all over the world. MarketSet and Enterprise
Buyer are jointly owned trademarks of SAP Markets and Commerce
IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, One. All other product and service names mentioned are the
MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, trademarks of their respective owners.
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,
TM
Netfinity®, Tivoli®, Informix and Informix® Dynamic Server are
trademarks of IBM Corp. in USA and/or other countries. Disclaimer
Some components of this product are based on Java™. Any code
ORACLE® is a registered trademark of ORACLE Corporation. change in these components may cause unpredictable and severe
malfunctions and is therefore expressively prohibited, as is any
UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of decompilation of these components.
the Open Group.
Any Java™ Source Code delivered with this product is only to be used
Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®, by SAP’s Support Services and may not be modified or altered in any
WinFrame®, VideoFrame®, MultiWin® and other Citrix product names way.
referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered

Documentation in the SAP Service Marketplace
trademarks of W3C®, World Wide Web Consortium, Massachusetts You can find this documentation at the following address:
Institute of Technology. http://service.sap.com//bpm
Job Scheduling Management Health Check with SAP Solution Manager
TABLE OF CONTENTS
1 INTRODUCTION .................................................................................................................................. 5
1.1 CONCEPT OF JOB SCHEDULING MANAGEMENT HEALTH CHECK................................................ 5
1.2 BENEFITS OF JOB SCHEDULING MANAGEMENT HEALTH CHECK ............................................... 7
1.2.1 JSM Health Check on Jobs ...................................................................................................... 7
1.2.2 JSM Health Check for Business Process Monitoring Job and BW Process Chain ............... 9
2 SETUP ................................................................................................................................................11
2.1 PREREQUISITES ................................................................................................................................11
2.1.1 SAP Solution Manager System ...............................................................................................11
2.1.2 Relevant SAP Notes ................................................................................................................12
2.1.3 Check of Repository changeability and cross-client customizing ........................................12
2.1.4 Check System Changeability ..................................................................................................13

2.1.5 Users and authorizations ........................................................................................................14
2.1.6 Set up Business Process Monitoring Job and BW Process Chain .......................................17
2.2 ACTIVATION WITH SAP SOLUTION MANAGER 7.0 .........................................................................17

2.2.1 Activate SAP Business Information Warehouse objects .......................................................17
2.2.2 Check if the Extractor Framework (EFWK) and housekeeping job are working...................19
2.2.3 Check E2E Resources used by the Extractor Framework .....................................................20
2.2.4 Maintain table for active worklist items in Extractor Framework (EFWK).............................20
2.2.4.1 JSM Health Check on Jobs (Daily/Weekly/Monthly view) .......................................................................20
2.2.4.2 JSM Health Check for Business Process Monitoring Job and BW Process Chain...................................22
2.2.5 Maintain table for target-source mapping for aggregation ....................................................23
2.2.6 Maintain table for definition of data reorganization ...............................................................24
2.2.7 Web Service Activation ...........................................................................................................25
2.2.8 Create and store URL for specific Web Templates ................................................................25
2.2.9 Check Job Scheduling Management Health Check Report ...................................................27
2.3 ACTIVATION WITH SAP SOLUTION MANAGER 7.1 .........................................................................28

2.3.1 Activate SAP Business Information Warehouse objects .......................................................28
2.3.2 Check if the Extractor Framework (EFWK) and housekeeping job are working...................30
2.3.3 Check E2E Resources used by the Extractor Framework .....................................................31
2.3.4 Activate data extraction process in Extractor Framework (EFWK) .......................................32

2.3.5 Maintain table for target-source mapping for aggregation and data reorganization ............33
2.3.6 Web Service Activation ...........................................................................................................35
2.3.7 Check Job Scheduling Management Health Check Report ...................................................35
3 TROUBLESHOOTING.........................................................................................................................38
3.1 PROBLEMS DURING ACTIVATION PROCESS..................................................................................38
October 2011 3
3.1.1 Error during activation of BW objects (step in section 2.2.1 and 2.3.1) ................................38
3.1.2 Problem with EFWK Administration Work Center (step in section 2.3.4) .............................39
3.1.3 JSM extractors are missing in the list of available extractors (step in section 2.3.4) ..........39
3.2 PROBLEMS AFTER ACTIVATION PROCESS....................................................................................40

3.2.1 No data available for the JSM Health Check Report ..............................................................40
4 October 2011
1 Introduction
The Job Scheduling Management (JSM) Health Check is an analytical functionality within SAP Solution
Manager. It provides reporting dashboards based on key performance indicators (KPI) related to job
execution data collected from selected managed SAP systems and simple job / BW process chain
monitoring data collected by Business Process Monitoring in SAP Solution Manager. These KPIs provide an
overall picture about the actual system workload caused by background processing in order to identify
possible optimization potential in specified managed systems connected to the SAP Solution Manager. The
reporting dashboards make use of the SAP Business Information Warehouse (BW) component available in
SAP Solution Manager (SolMan) as a SAP Netweaver 7.0 system and offer views on different aggregation
levels and timeframes. The JSM Health Check is a standalone toolset which can be set up for regular, ad-
hoc analysis or even in situations where you face serious issues in your job scheduling landscape (i.e.
bottleneck situations). For SAP Solution Manager 7.1 integration with the Job Management Work Center
regarding administration and access to the dashboards is available.
1.1 Concept of Job Scheduling Management Health

Check
The JSM Health Check uses the Extractor Framework (EFWK) of SAP Solution Manager Diagnostics (SMD)
to extract and to aggregate job execution data from managed systems and simple job / BW process chain
monitoring data collected by Business Process Monitoring in SAP Solution Manager (BPMon) into InfoCubes
located in the BW component of SAP Solution Manager. All jobs in selected managed systems with a final
status (“finished” or “cancelled”) as well as the available simple job / BW process chain monitoring data in
SAP Solution Manager are considered for the JSM Health Check and collected on an hourly basis, the
available aggregation for job execution data from daily for weekly and monthly views is done once a day
automatically. The available data can be displayed via predefined Dashboards (Web Templates which
execute queries on respective InfoCubes). Two different sets of extractors are available to extract job
execution data from the managed systems as well as job monitoring data from Business Process Monitoring.
The first set contains an extractor for taking only the job execution header information from table TBTCO into
account, while another is combining data from job execution header (TBTCO) and job execution item
(TBTCP) table. The second set contains extractors taking simple job and the BW process chain monitoring
data available in Business Process Monitoring into account (see figure1).
Figure 1 – Job Scheduling Management Health Check Concept
October 2011 5
Dashboards (BW Report) Web Template InfoCube Data Source

Daily View on Jobs 0SM_JSM_HC_XBP_DAILY_JOBS 0SM_JSM_H Table TBTCO in managed
systems
Daily View on Jobs(Step) 0SM_JSM_HC_XBP_DAILY_STEPS 0SM_JSM_H Table: TBTCO and TBTCP in
managed systems
Weekly View on Jobs 0SM_JSM_HC_XBP_WEEKLY_JOBS 0SM_JSM_D Aggregated from InfoCube
0SM_JSM_H
Weekly View on Jobs (Steps) 0SM_JSM_HC_XBP_WEEKLY_STEPS 0SM_JSM_D Aggregated from InfoCube

0SM_JSM_H
Monthly View on Jobs 0SM_JSM_HC_XBP_MONTHLY_JOBS 0SM_JSM_W Aggregated from InfoCube
0SM_JSM_D
Monthly View on Jobs(Steps) 0SM_JSM_HC_XBP_MONTHLY_STEPS 0SM_JSM_W Aggregated from InfoCube

0SM_JSM_D
Business Process Monitoring 0SM_JSM_HC_BPMON 0SM_JSM_S Table DSWP_BPM_JOSCHG
Job* in SolMan
Business Process Monitoring 0SM_JSM_HC_BPMON_CHAIN 0SM_JSM_C Table DSWP_BPM_JOSCHG
BW Process Chain* in SolMan
* The monitored jobs and BW process chain need to be setup in Business Process Monitoring session first.
The dashboards for job / jobstep execution data (Daily/Weekly/Monthly view) illustrate the following
information graphically as well as in tabular views in KPI sets for job execution data from managed systems
- Job Status Analysis: Finished vs. Canceled (number of jobs as well as accumulated duration of jobs,
top long runners; etc.)
- Workload Distribution (per job duration; per start delay; by creation or scheduling user; by execution
server; etc.)
The graphical views enable an easy overview about the job execution status and distribution in the managed
systems. The tabular views provide more detailed information via drilldown functionality. In addition these
tabular views can also be exported as MS excel files. With such reports, the JSM Health Check provides you
an overview about the job scheduling situation and system workload caused by background jobs in the
managed systems, thus enhances the transparency of the existing job schedule and jobs which are causing
problems or which can be improved.
The dashboards for Business Process Monitoring Job and BW Process Chain provide daily views of
maximum duration and maximum delay in the selected business process and step of a solution.
In SAP Solution Manager 7.1 the dashboards are fully integrated in the Job Management Work Center. In
SAP Solution Manager 7.0 the end user can execute the dashboards directly via Web Templates URL, i.e.
as favorites in the system or as Favorite Shortcuts directly from an Internet Browser (after additional
configuration).
6 October 2011
1.2 Benefits of Job Scheduling Management Health

Check
1.2.1 JSM Health Check on Jobs
The JSM Health Check on jobs / jobstep execution data (Daily/Weekly/Monthly view) benefits your system
by:
Identifying
o Longest running jobs
o Jobs that run and / or cancel most often
o Jobs with longest start delay times
Showing distribution of background jobs

o Across application servers
o Across creating / scheduling users
With the information, you can reduce the overall system workload caused by background jobs, ensure even
workload distribution across system servers, identify system bottlenecks such as lack of work processes, as
well as handle end user scheduled jobs that bypass central scheduling and cause high workload.
More advantages of the JSM Health Check on Jobs are:
Works as a standalone tool

Enables ad hoc analysis
Easy to implement and easy to use
Provides transparency on job execution data in a central tool in SAP Solution Manager
Incorporates configurable automatic housekeeping which controls data growth
Examples of JSM Health Check Reports:
As mentioned in section 1.1, the JSM Health Check Reports includes graphical views (BW-based bar charts)
as well as tabular views; the screenshots below show examples from the reports.
October 2011 7
Figure 2a – Report Examples based on job execution data
8 October 2011
1.2.2 JSM Health Check for Business Process Monitoring Job and BW Process Chain
The JSM Health Check for job and BW process chain monitoring data provides daily views of maximum
duration and maximum start delay within a Business Process Monitoring solution. They help identify long
running and long start delay time of your jobs and BW process chains that may have business impact on a
solution. These reports are standalone tools for ad hoc monitoring which provide transparency on job
execution time and delay via the SAP Solution Manager.
Figure 2a – Example BPMon simple job report
October 2011 9
Figure 2b – Example BPMon BW process chain report
Note that BPMon job and BW process chain reports are similar to the one from “Trend Analysis Reporting in
Business Process Monitoring” BW based reporting functionality with respect to setup of background
processing monitoring in BPMon for key figures “Maximum Duration” and “Start Delay”. However, the JSM
Health Check BPMon reports base on actual execution duration of jobs and BW process chains, whereas
Trend Analysis bases on measured duration at the time of alert creation. The measured duration of a job or a
chain at the time an alert is raised can differ from the actual execution duration.
For example, a monitored job usually finishes within 30 min duration. A yellow alert threshold for this job
within the key figure “Maximum Duration” in background processing monitoring is set at 45 min and a red
alert threshold, 1 hour. Data collection takes place every hour on the hour. The following scenario raise an
red alert when it took 2 hours to finish the job.
At 1:30 AM the job started

At 2 AM the data collection took place. The measured duration (30 min) was less than any threshold
values. No alert was raised.
At 3 AM the data collector took place again. The job was still running. Data collector detected that
current duration (1.5 hour) exceeded red threshold. It raised a red alert with measured duration 1.5
hour. No further alert was raised for this job.
At 3:30 AM the job finally finished
The measured duration is 1.5 hour (for Trend Analysis report) and actual duration is 2 hours (for JSM Health
Check BPMon job report).
10 October 2011
2 Setup
The JSM Health Check is developed for SAP Solution Manager 7.1 which includes setup support in the Job
Management Work Center. For Solution Manager 7.0 a downport is available with SPS23.
The setup process for the JSM Health Check with Solution Manager 7.0 and 7.1 will be described in sections
2.2 and 2.3 respectively.
Note:
The following activation steps can be either performed directly in the productive SAP Solution
Manager system or the activation steps can be applied first in the development SAP Solution
Manager system and get afterwards transported (via quality assurance system) to the productive
SAP Solution Manager.
DISCLAIMER:
Please use this Setup Guide for Job Scheduling Management Health Check at your own risk. All our
recommendations regarding the activation of this functionality are based on our general experience
and maybe are not valid for your specific implementation, especially when you are already using the
SAP BW component in SAP Solution Manager. In this case, please consult and involve the people
already working with BW in the target system to make sure that all functions in BW keep working.
2.1 Prerequisites
2.1.1 SAP Solution Manager System
The JSM Health Check is implemented in software component BW Content (BI_CONT or ST-BCO). If there
is no BW client maintained in your system, please define it in the SAP Solution Manager Configuration. In
general, it is recommended using the same client as BW client as is used as Solution Manager client. The
client assignment cannot be changed later on after the initial configuration.
As technical prerequisites for using the JSM Health Check, the following components are required on the
respective backend system.
Software Component Recommended Minimum

Requirements
SAP Solution SolMan 7.0 with SP27 & ST-BCO SolMan 7.0 with SP23 & BI_CONT
Manager 7.0 400 SP0 (or higher) and ST-A/PI 7.04 SP07 (or higher) and ST-A/PI
01M* (or higher) on the respective 01M* (or higher) on the respective
backend system (SAP BASIS 620 or backend system (SAP BASIS 620 or
higher with SAP Note 1564604 higher)
implemented)
SAP Solution SolMan 7.1 with SP02 & ST-BCO SolMan 7.1 with SP01 & BI_CONT
Manager 7.1 710 SP0 (or higher) and ST-A/PI 7.05 SP01 (or higher) and ST-A/PI
01M* (or higher) on the respective 01M* (or higher) on the respective
backend system (SAP BASIS 620 or backend system (SAP BASIS 620 or
higher with SAP Note 1564604 higher)
implemented)
Info: BW is previously known as BI. Both BW and BI refer to the SAP Business Information Warehouse.
Note:
If you want to set-up the data extraction on job step level, combining the data from table TBTCO and TBTCP
as mentioned in section 1.1, it is necessary to fulfill the recommended software component requirements.
October 2011 11
2.1.2 Relevant SAP Notes

- SAP Note 1564604: “JSM Health Check: Program errors in data extractors”
This note corrects errors in the used data extractors, especially for the combined extraction of job execution
header and item information. As mentioned in section 2.1.1, this note is a prerequisite if you want to include
job step data from table TBTCP into your analysis.
- SAP Note 1578583: “BW content for SAP Solution Manager”

This note summarizes the details (affected releases) related to the transfer of the SAP Solution Manager BW
objects from software component BI_CONT to ST-BCO, as mentioned in section 2.1.1.
- SAP Note 1436853: “BPM for BW Process Chains and Steps - Prerequisites”
Please review the section “2.) Required Notes:” and implement the mentioned notes in the monitored BW
system. This is to ensure that the monitoring for BW process chains works.
In addition, we recommend implementing the following SAP Notes to get True Type Fonts in the graphical
charts and a more clear display of the coordination axis in the chart:
Optional SAP Notes
- SAP Note 1028690: “True Type Fonts delivered with IGS”

The recommendation in this SAP Notes needs to be implemented if you predict that a font different than the
IGS standard font (with limited options) will be used.
- SAP Note 596825: “GFWCHART configuration file”

This SAP Note provides a solution for issues related to fonts in the IGS graphic charts and the layout of the
coordination axis.
Note: After application of SAP notes 1028690 / 596825, the application server has to be restarted.
2.1.3 Check of Repository changeability and cross-client customizing
Before starting the activation process, the changeability of the repository and cross-client customizing should
be checked. Modifications of these items should be allowed, because several changes affecting cross-client
topics are applied to the system configuration during the activation. Make sure that in transaction “SCC4” the
settings for the selected BW client are set to status “Changes to Repository and cross-client Customizing is
allowed” (see figures 3 & 4). Otherwise change it. After completing the activation process it can be reset to
its original status.
12 October 2011
Figure 3 – Double click on the selected BW client in transaction “SCC4”
Figure 4 – Changes to Repository and cross-client Customizing should be allowed
2.1.4 Check System Changeability
In order to ensure objects related to the BW Reporting functionality can be activated, three namespaces
have to be set to status “modifiable” in transaction “SE03”. Following the node “Set System Change Option”,
you have to check if the namespaces “/B10/” (Generation Namespace for SAP BI Content), “/BI0/’ (Business
Information Warehouse – SAP Namespace) and “/BIC/” (Business Information Warehouse: Customer
Namespace) are modifiable. If not, change them to “modifiable” (see figures 5 & 6).
Figure 5 – Transaction SE03 used to set system change options
October 2011 13
Figure 6 – Check if relevant BW namespaces are modifiable - If not, change them accordingly.
2.1.5 Users and authorizations
For the activation process, users in the SAP Solution Manager client and in the BW client with authorization
profile “SAP_ALL” are recommended, because it is likely that several changes within the system settings
(system administration) must be done during this activation process. (But do not use the SAP users such as
the “DDIC” user, because this user cannot activate objects in the customer namespace.)
If the profile “SAP_ALL” is not feasible, please configure the necessary roles / authorizations via transaction
PFCG as described below. These minimum authorizations are needed in order to activate JSM Health
Check and get a picture of the results.
In case the authorization configuration cannot be done in productive systems, please first do the
configurations in development system and then transport the changes to the productive systems. For the
activated BW objects, please use the BW Transport Connection available in the BW Administration
Workbench (RSA1).
1. Role Z_SAP_BW_CCMS_SETUP
- Create role Z_SAP_BW_CCMS_SETUP from standard role SAP_BW_CCMS_SETUP.

- Extend authorizations: extend the object class AAAB, object S_TCODE, field TCD with RSRV, SICF
and SU53.
14 October 2011
Figure 7 – Screenshot: Role Z_SAP_BW_CCMS_SETUP (1)
- Extend authorization: fill object class BC_A, object S_TABU_DIS, field DICBE with *.
- Insert authorization: fill object class BC_Z, object S_APPL_LOG, field ACTVT with 03, field ALG_0
with RSRV and ALG_S with Dialog.
October 2011 15
2. Role Z_JSM_HC_USER
- The following role must be manually created in the customer namespace, since there is no
corresponding standard role available. The role assigns the necessary authorizations for the
database access during the activation of JSM Health Check.
Figure 10 – Screenshot: Role Z_JSM_HC_USER
3. Profile S_DEVELOP
- This profile is necessary for activating the JSM Health Check.
4. If you are using SAP Solution Manager 7.1, please add the role SAP_SMWORK_JOB_MAN to the
user to be able to access the JSM Work Center.
16 October 2011
2.1.6 Set up Business Process Monitoring Job and BW Process Chain
This step is only required for JSM Health Check for BPM Job and BW Process Chain reports. If you only want
to use JSM HC for Jobs (Daily/Weekly/Monthly), this section can be skipped.
Please refer to the section 6.2 Background Processing of “Setup Guide – Business Process Monitoring” for
detailed steps to setup simple job and BW process chain monitoring. This guide can be downloaded from
https://service.sap.com/bpm
2.2 Activation with SAP Solution Manager 7.0

The following sections describe the activation process of the JSM Health Check in SAP Solution Manager
7.0 step by step. If any problems arise during activation, please refer to the Troubleshooting chapter 3 at the
end of the document.
Note: The activation of BW objects is performed in BW client, all other steps in Solution Manager client.
2.2.1 Activate SAP Business Information Warehouse objects
In order to activate the necessary BW objects for the JSM Health Check, execute the report
RS_BCT_SM_SETUP_JSM_HC in background or dialog mode with transaction SE38. It may take a few
minutes until the execution completes.
If you execute the report in dialog mode, the following selection screen is displayed (figure 11), please leave
the entry field empty and press the execution button (F8) to start the activation process:
Figure 11 – Screenshot: Report to generate BW objects

Info: If you run the report in Dialog Mode instead of running it in the background, there will be a pop-up with
warning message “Active BI Content might be overwritten. Continue?” In this case click “Yes” to continue. In
October 2011 17
addition, there may be a popup for “Select Source Systems”, just click on “yes” to continue (it has no effect in
our case).
Once all objects are configured you should receive message “All steps successfully performed” as shown in
figure 12:
Figure 12 – Screenshot: successful messages after activation of BW objects
The result can be checked in the Data Warehousing Workbench:

1. Go to Data Warehousing Workbench via transaction code RSA1;
2. Select the “InfoProvider” on the left side;
3. Expand the “SAP Solution Manager”, then expand the subtree “SAP Solution Manager - Job
Scheduling Management”;
4. You will see the JSM objects, similar as shown in the screenshot below.
Figure 13 – Screenshot: Data Warehousing Workbench
18 October 2011
2.2.2 Check if the Extractor Framework (EFWK) and housekeeping job are working
The JSM Health Check on Jobs has three dashboards views with different aggregation levels and
timeframes (i.e. daily view, weekly view, monthly view) based on the data collected by the extractors. To
enable this functionality, the EFWK and housekeeping jobs must be working to start the automatic
aggregation and reorganization process.
Please follow the steps below to check the jobs in transaction SM37 in the SolMan client. If the jobs are not
scheduled in the system yet, schedule and activate them.
1. The report E2E_EFWK_RESOURCE_MGR starts extraction cycle of EFWK and executes due data
extractor according to scheduling; this job should run every minute.
Figure 14 – Screenshot of SM37: check BW Extractor job
This job should be scheduled during configuration of SAP Solution Manager. It starts data extraction process
from configured managed systems and saves data in the JSM Health Check hourly InfoCube 0SM_JSM_H.
2. The housekeeping report E2E_HK_CONTROLLER performs data aggregation and reorganization within
the EFWK regarding the configuration in the underlying tables E2E_BI_AGGREGATE and
E2E_BI_DELETE; this job should run daily (e.g. one time shortly after midnight):
Figure 15 – Screenshot of SM37: check the housekeeping job

For more information about the aggregation levels and data reorganization, please refer to the sections 2.2.5
and 2.2.6.
October 2011 19
2.2.3 Check E2E Resources used by the Extractor Framework
In this step you need to check table E2E_RESOURCES which contains RFC resources available for data
extraction within EFWK with transaction SE16. Normally all systems should be defined here that have been
configured in managed system setup in the configuration of SAP Solution Manager. If an entry is missing you
can manually create it as well, but maybe you should check before the managed systems setup.
Figure 16 – Screenshot: check E2E Resources

The naming convention for the RFCRESOURCE is “SM_SIDCLNT000_READ” (replace “SID” with the
system ID, the “000” with the client number). Please make sure that the list includes the needed system, as
well as the entries “NONE”, “SOLMANDIAG” and “SOLMAN_DIALOG_WORKPROCESSES”.
Note: if BW client is different from Solution Manager client (i.e. RFC destination to BW is not “NONE”), then
there should be an entry in this table for RFC destination to BW client under RFCRESOURCE(see field
“String” in table E2E_WA_CONFIG where type = SAP_BID).
Information about the field RESOURCECAP:

It defines the maximum number of dialog work processes which can be used for data extraction purposes.
2.2.4 Maintain table for active worklist items in Extractor Framework (EFWK)
In this step, we have to configure the system specific data extraction process for the JSM Health Check by
updating table E2E_ACTIVE_WLI for active worklist items within the EFWK. This table contains the
scheduling information for all extractors being executed.
The maintenance on the active worklist items table E2E_ACTIVE_WLI is performed via executing function
module DSWP_BPM_JSM_HC_ADD_EXTRACTOR in transaction SE37.
2.2.4.1 JSM Health Check on Jobs (Daily/Weekly/Monthly view)

JSM Health Check extractors here to trigger data transfer between SAP Solution Manager and managed
systems. We recommend scheduling either the extractor for job or for job step execution data for one specific
system you want to include in the JSM Health Check.
20 October 2011
The extractor for job execution data only collects information from table TBTCO; the extractor for job step
execution data collects job step data in addition, by joining the tables TBTCO and TBTCP.
In order to schedule for a specific system the extractor for jobs, enter “F86_JSMHC_EXTRACTOR_JOBS”,
to schedule the extractor for job steps, enter “F87_JSMHC_EXTRACTOR_STEPS” as local extractor in the
following selection screen (figure 17) – all relevant fields are described below.
All the other parameters are similar in both cases in the selection screen.
Here is the list of all the parameters in the selection screen which you should fill in (leave all the other fields
empty). The input values in bold are independent of your specific system settings.
Parameter Input Value

SID SID of the managed system
INSTNO Installation number of the managed system
MAINEXTR E2E_ME_ST_API_ASYNC
F86_JSMHC_EXTRACTOR_JOBS for jobs
EXTRACTO F87_JSMHC_EXTRACTOR_STEPS for job steps
ACTIVE X
NAME Enter your description, for e.g. "JSM Health Check - Job"
SOURCERF RFC connection to collector in managed system, see section 2.2.3
DTRUN 60 (default value, minute)
DTSCAN 1 (default value, hour)
AGGLEVEL 1 (default value)
TARGETRF RFC connection to BI client (see description below on how to check it)
TARGTYPE CUBE
TARGNAME 0SM_JSM_H
DATAL SMD_DATA_LOADER100
Information about ACTIVE flag:

- This flag can be used to deactivate the data collection for a period of time.
Information about field TARGETRF:

- To verify the RFC connection to BI client, you can check the relevant entry in table
“E2E_WA_CONFIG” - do selection with TYPE “SAP_BID”, double-click on the selected item, then
check the STRING.
Note about fields DTRUN (unit: Minute) and DTSCAN (unit: Hour):
- Value of these two fields shall be synchronized in order to avoid overlaps or missing data. For
example “DTRUN = 60 minutes, DTSCAN = 1 Hour” means one run for each 60 minutes and each
run scans the data in the past one hour, thus ensures a full coverage of the data collector.
In the following example the extractor for job execution data is scheduled:
October 2011 21
Figure 17 – Screenshot: Schedule the Extractor for jobs
2.2.4.2 JSM Health Check for Business Process Monitoring Job and BW Process Chain
The extractors collect information from the table DSWP_BPM_JOSCHG in the SAP Solution Manager.
The import parameters for the function module DSWP_BPM_JSM_HC_ADD_EXTRACTOR in transaction

SE37 are as follows:
For job monitoring data from Business Process Monitoring

SID SID of Solution Manager
INSTNO Installation number of Solution Manager
MAINEXTR E2E_ME_RFC_ASYNC
EXTRACTO DSWP_BPM_JSM_HC_BPMON
ACTIVE X
NAME Enter name, e.g. JSM Health Check for Business Process Monitoring
SOURCERF NONE
22 October 2011
TARGETRF RFC connection to BI client (see table E2E_WA_CONFIG, type SAP_BID)

TARGTYPE CUBE
TARGNAME 0SM_JSM_S
For BW process chain monitoring data from Business Process Monitoring

SID SID of Solution Manager
INSTNO Installation number of Solution Manager
MAINEXTR E2E_ME_RFC_ASYNC
EXTRACTO DSWP_BPM_JSM_HC_BPMON_CHAIN
ACTIVE X
Enter name, e.g. JSM Health Check for Business Process Monitoring of
NAME BW Process Chain
SOURCERF NONE
TARGETRF RFC connection to BI client (see table E2E_WA_CONFIG, type SAP_BID)
TARGTYPE CUBE
TARGNAME 0SM_JSM_C
After executing this function module, an entry will be created in table E2E_ACTIVE_WLI with the extractor
information. Then the extractor gets started and extracts data.
2.2.5 Maintain table for target-source mapping for aggregation
Here we maintain the aggregation levels for the housekeeping job. This step is only required for JSM Health
Check on Jobs (Daily/Weekly/Monthly view).
The target source mapping for aggregation shall be defined in table “E2E_BI_AGGREGATE” via transaction
SE16, as shown in the examples below:
Figure 18 – Screenshots: Maintain Target Source Mapping for Aggregation
October 2011 23
Note: please follow naming convention for delivered InfoCubes.
In this example, the InfoCube 0SM_JSM_H contains the hourly information gathered by the extractor. The
hourly information will be aggregated to the InfoCube 0SM_JSM_D which contains only daily information.
The daily information will be aggregated to the InfoCube 0SM_JSM_W which contains only weekly
information. The aggregation is performed by the housekeeping job E2E_HK_CONTROLLER (see section
2.2.2). During the aggregation process from 0SM_JSM_H to 0SM_JSM_W will lose part of the detailed
information (e.g. job start time, or job count) due to the compression of the information, see the available
information in the different dashboards for further information.
Note: if BW client is different from Solution Manager client (i.e. RFC destination to BI is not “NONE”), then
the field BIDESTINATION should be the RFC destination to BW client (see field “String” in table
E2E_WA_CONFIG where type = SAP_BID).
2.2.6 Maintain table for definition of data reorganization
The next step is to maintain the table for deletion jobs “E2E_BI_DELETE” via transaction SE16. This step is
only required for JSM Health Check on Jobs (Daily/Weekly/Monthly view).
Figure 19 – Screenshots: Maintain Definition of Deletion Jobs
the field BIDESTINATION should be the RFC destination to BW client (see field “String” in table
E2E_WA_CONFIG where type = SAP_BID).
Explanation of the above example:

“0CALDAY” stands for the current day, for example 02.07.2011. If “DELTA = 1”, this means the threshold
date is current day minus 1 day (01.07.2011). In this case, all data in 0SM_JSM_H that is old than
01.07.2011 will be deleted. This configuration ensures that the data at lowest level will only be available for
one day, so that the data volume will be kept properly.
Please define the duration in field “LOW” according to your own requirements.
24 October 2011
SAP recommended values are:
0SM_JSM_H $DELTA=1$ (1 day)

0SM_JSM_D $DELTA=30$ (1 month)
0SM_JSM_W $DELTA=180$ (6 months)
2.2.7 Web Service Activation
Before the web template for JSM Health Check can be used in the system, the Business Explorer and MIME
web service have to be activated. For this call transaction “SICF”. There, select “SERVICE” as “Hierarchy
type”’. After executing this selection the following screen will appear:
Figure 20 – Screenshot: Activation of web services
Expand node “default_host” “‘sap” “bw” and check if service “BEx” (Business Explorer) and “MIME” are
active (black font). If they are not active (grey font), activate via right-mouse-click on item “BEx” or “MIME”,
choosing option “Activate”.
At this point, all activation steps have been executed successfully.
2.2.8 Create and store URL for specific Web Templates
As the administration via the Job Management Work Center is only possible in Solution Manager Release
7.1, the URL creation for Web templates has to be performed manually for Solution Manager Release 7.0, by
executing the report RS_TEMPLATE_MAINTAIN via Transaction SE38.
October 2011 25
Figure 21 – Screenshot: Create URL for Web Templates
Use the F4 help to select the templates, execute the report for each of the templates (Job and BW Process
Chain for BPM, job daily, weekly, and monthly).
Figure 22 – Screenshot: Web Templates names
After the execution of the report, you will see following screen, press the button “Preview in Browser” to see
the report in the browser; there you can copy the URL of the web template.
Figure 23 – Screenshot: Press “Preview in Browser” to get URL
Please note that the generated URL needs to be shortened.

For example, the part such as
“&USE_PERSONALISATION=X&JAVASCRIPT=X&TRACE=&VARIABLE_SCREEN=&SNIPPET_OPERATI
ONS=X&DEBUG=X“shall be removed.
26 October 2011
The final results will look like the following:

http://twdf1847.wdf.sap.corp:8000/SAP/BW/BEX?CMD=LDOC&TEMPLATE_ID=0SM_JSM_HC_XBP_DAIL
Y_STEPS.
For convenient access to the web templates, you may maintain the URLs in the Business Process
Operations work center.
1. Click on “Add” in the “Reports” view.
Figure 24 – Screenshot: Store URL for Web Templates (1)
2. Fill in the required fields.
Figure 25 – Screenshot: Store URL for Web Templates (2)
Info: Field Solution is mandatory, but has no impact therefore you can choose any solution. Field ID is the
web template name. Field Server (server: port) can be taken from the URL.
2.2.9 Check Job Scheduling Management Health Check Report
After extractor execution, the JSM Health Check Report can be checked via the generated URL.
Please expand the collapsed data to see the statistics and diagrams for job status and workload distribution
in the managed system.
October 2011 27
2.3 Activation with SAP Solution Manager 7.1

The following sections describe the activation process of the JSM Health Check in SAP Solution Manager
7.1 step by step. If any problems arise during activation, please refer to the Troubleshooting chapter 3 at the
end of the document.
Note: The activation of BW objects is performed in BW client, all other steps in Solution Manager client.
2.3.1 Activate SAP Business Information Warehouse objects
In order to activate the necessary BW objects for the JSM Health Check, execute the report
RS_BCT_SM_SETUP_JSM_HC in background or dialog mode with transaction SE38. It may take a few
minutes until the execution completes.
If you execute the report in dialog mode, the following selection screen is displayed (figure 11), please leave
the entry field empty and press the execution button (F8) to start the activation process:
Figure 26 – Screenshot: Report to generate BW objects
Info: If you run the report in Dialog Mode instead of running it in the background, there will be a pop-up with
warning message “Active BI Content might be overwritten. Continue?” In this case click “Yes” to continue. In
addition, there may be a popup for “Select Source Systems”, just click on “yes” to continue (it has no effect in
our case).
Once all objects are configured you should receive message “All steps successfully performed” as shown in
figure 27:
Figure 27 – Screenshot: successful messages after activation of BW objects
28 October 2011
Alternatively, you can run the report RAGS_JSM_CONFIG_CUSTOMIZE by checking “BW Content
Activation and entering RFC destination to BW to start report RS_BCT_SM_SETUP_JSM_HC in background
job.
Note: to verify the RFC connection to BI client for the field “RFC to BW”, you can check the relevant entry in
table “E2E_WA_CONFIG” (do selection with TYPE “SAP_BID”, double-click on the selected item, and then
check the STRING).
The result can be checked in the Data Warehousing Workbench:
1. Go to Data Warehousing Workbench via transaction code RSA1;

2. Select the “InfoProvider” on the left side;
3. Expand the “SAP Solution Manager”, then expand the subtree “SAP Solution Manager - Job
Scheduling Management”;
4. You will see the JSM objects, similar as shown in the screenshot below.
October 2011 29
Figure 28 – Screenshot: Data Warehousing Workbench
2.3.2 Check if the Extractor Framework (EFWK) and housekeeping job are working
The JSM Health Check on Jobs has three dashboards views with different aggregation levels and
timeframes (i.e. daily view, weekly view, monthly view) based on the data collected by the extractors. To
enable this functionality, the EFWK and housekeeping jobs must be working to start the automatic
aggregation and reorganization process.
Please follow the steps below to check the jobs in transaction SM37 in the SolMan client. If the jobs are not
scheduled in the system yet, schedule and activate them.
1. The report E2E_EFWK_RESOURCE_MGR starts extraction cycle of EFWK and executes due data
extractor according to scheduling; this job should run every minute.
Figure 29 – Screenshot of SM37: check BW Extractor job
This job should be scheduled during configuration of SAP Solution Manager. It starts data extraction process
from configured managed systems and saves data in the JSM Health Check hourly InfoCube 0SM_JSM_H.
2. The housekeeping report E2E_HK_CONTROLLER performs data aggregation and reorganization within
the EFWK regarding the configuration in the underlying tables E2E_BI_AGGREGATE and
E2E_BI_DELETE; this job should run daily (e.g. one time shortly after midnight):
30 October 2011
Figure 30 – Screenshot of SM37: check the housekeeping job
For more information about the aggregation levels and data reorganization, please refer to the sections
2.3.5.
2.3.3 Check E2E Resources used by the Extractor Framework
In this step you need to check table E2E_RESOURCES which contains RFC resources available for data
extraction within EFWK with transaction SE16. Normally all systems should be defined here that have been
configured in managed system setup in the configuration of SAP Solution Manager. If an entry is missing you
can manually create it as well, but maybe you should check before the managed systems setup.
Figure 31 – Screenshot: check E2E Resources
October 2011 31
The naming convention for the RFCRESOURCE is “SM_SIDCLNT000_READ” (replace “SID” with the
system ID, the “000” with the client number). Please make sure that the list includes the needed system, as
well as the entries “NONE”, “SOLMANDIAG” and “SOLMAN_DIALOG_WORKPROCESSES”.
there should be an entry in this table for RFC destination to BW client under RFCRESOURCE (see field
“String” in table E2E_WA_CONFIG where type = SAP_BID).
Information about the field RESOURCECAP:

It defines the maximum number of dialog work processes which can be used for data extraction purposes.
2.3.4 Activate data extraction process in Extractor Framework (EFWK)
In this step, we have to configure the system specific data extraction process for the JSM Health Check by
updating table E2E_ACTIVE_WLI for active worklist items within the EFWK. This table contains the
scheduling information for all extractors being executed.
For Job Daily/Weekly/Monthly view, we have to add the scheduling of the JSM Health Check extractors here
to trigger data transfer between SAP Solution Manager and managed systems. We recommend scheduling
either the extractor for job or for job step execution data for one specific system you want to include in the
JSM Health Check. The extractor for job execution data only collects information from table TBTCO; the
extractor for job step execution data collects job step data in addition, by joining the tables TBTCO and
TBTCP.
For BPMon Job and BW Process Chain reports, the extractors collect information from the table
DSWP_BPM_JOSCHG in the Solution Manager.
In SAP Solution Manager 7.1, all extractor entries should be created automatically by Robomate Setup, no
manual creation by function module DSWP_BPM_JSM_HC_ADD_EXTRACTOR is necessary. The
maintenance on the active worklist items table E2E_ACTIVE_WLI is therefore performed via the
administration view in the EFWK Administration Work Center.
1. Within the JSM Workcenter, go to tab “Administration” in the left window, the select option “Manage
Data Collection for Analytics” in the right window to enter the EFWK Workcenter.
Figure 32 – Screenshot: Maintain extractors
32 October 2011
2. As shown in the screenshot below, filter by “*jsm*” in the Extractor Overview list. Select the
corresponding extractor; then click on the change button to enter the change mode.
Figure 33 – Screenshot: select the extractor to be activated
3. Click on the “Activate” button for the reports you want to use, then the extractor is activated, which is
indicated by the light bulb in the “Active Status” column.
Figure 34 – Screenshot: activate the extractor
2.3.5 Maintain table for target-source mapping for aggregation and data reorganization
In this step we maintain the aggregation levels for the housekeeping job in table E2E_BI_AGGREGATE, as
well as maintain the table E2E_BI_DELETE for deletion jobs. This step is only required for JSM Health
Check on Jobs (Daily/Weekly/Monthly view).
The tables E2E_BI_AGGREGATE and E2E_BI_DELETE are maintained by executing report

RAGS_JSM_CONFIG_CUSTOMIZE.
October 2011 33
Figure 35 – Screenshot: execute report RAGS_JSM_CONFIG_CUSTOMIZE
Note: to verify the RFC connection to BI client for the field “RFC to BW”, you can check the relevant entry in
table “E2E_WA_CONFIG” (do selection with TYPE “SAP_BID”, double-click on the selected item, and then
check the STRING).
The standard job data life time in the InfoCubes related to the JSM Health Check are configured by the
report in table E2E_BI_DELETE in the following way:
Figure 36 – Screenshot: Reorganization parameters

with
0SM_JSM_H $DELTA=1$ (1 day)

0SM_JSM_D $DELTA=30$ (1 month)
0SM_JSM_W $DELTA=180$ (6 months)
Explanation of the above example:
34 October 2011
“0CALDAY” stands for the current day, for example 02.07.2011. If “DELTA = 1”, this means the threshold
date is current day minus 1 day (01.07.2011). In this case, all data in 0SM_JSM_H that is old than
01.07.2011 will be deleted. This configuration ensures that the data at lowest level will only be available for
one day, so that the data volume will be kept properly.
These entries can be changed any time manually according to your special needs.
2.3.6 Web Service Activation

Before the web template for JSM Health Check can be used in the system, the Business Explorer and MIME
web service have to be activated. For this call transaction “SICF”. There, select “SERVICE” as “Hierarchy
type”’. After executing this selection the following screen will appear:
Figure 37 – Screenshot: Activation of web services
Expand node “default_host” “‘sap” “bw” and check if service “BEx” (Business Explorer) and “MIME” are
active (black font). If they are not active (grey font), activate via right-mouse-click on item “BEx” or “MIME”,
choosing option “Activate”.
At this point, all activation steps have been executed successfully.
2.3.7 Check Job Scheduling Management Health Check Report
After extractor execution, the JSM Health Check Report can be checked in the “Job Management” Work
Center of SAP Solution manager 7.1.
October 2011 35
Before this, you have to define the views you want to see on each aggregation level in the JSM Work Center.
Therefore, select within the JSM Work Center the tab “Administration” in the left window, then the option
“Manage Reports for Job Scheduling Management” in the right window.
Figure 38 – Screenshot: Maintain views
Maintain in the pop-up window the views you want to use according to the scheduling of the extractors,
select in views you want to see either “without step” for data from the job header information extractor, or
otherwise “with step” for those extraction job header and item information.
For Job
Daily/Weekly/
Monthly view
For BPM Job

and BW
Process Chain
Figure 39 – Screenshot: Select views
36 October 2011
Confirm your configuration by pressing the OK-button. Now you can access the dashboards directly via the
JSM Work Center.
As shown in the screenshot below, go to the “Report” view; select the “BW Reports” as Reporting Views.
Figure 40 – Screenshot: JSM Health Check Reports
To open the report, click on the “Report” link. The corresponding report will be opened in your browser
(select the managed system to view the JSM Health Check results).
Please expand the collapsed data to see the statistics and diagrams for job status and workload distribution
in the managed system.
October 2011 37
3 Troubleshooting
When activating or working with the JSM Health Check, you could sometimes face technical issues for which
we want provide you – according to our experience – a short description how to handle and solve it.
If you face technical issues which are not included in this chapter, please feel free to create a customer
message on component SV-SMG-PSM, providing a detailed description of your issue.
3.1 Problems during activation process

3.1.1 Error during activation of BW objects (step in section 2.2.1 and 2.3.1)
Symptom:
As described in section 2.2.1, you executed report RS_BCT_SM_SETUP_JSM_HC in the BW client in order
to generate BW objects for the JSM Health Check. After the execution, the report returns error messages as
shown in the following screenshot.
Figure 41 – Screenshot: Error messages from the report to generate BW objects
Solution:
In the transaction RSOR, manually activate the InfoArea 0SM_JSM and all the related objects in the
process.
38 October 2011
3.1.2 Problem with EFWK Administration Work Center (step in section 2.3.4)
Symptom:
You want to perform the step described in section 2.3.4, but the EFWK Administration work center is not
working.
Solution:
Directly change the “ACTIVE” field in the table E2E_ACTIVE_WLI via transaction SE16. Set this field to “X”
to activate the extractors.
3.1.3 JSM extractors are missing in the list of available extractors (step in section 2.3.4)
Symptom:
You want to activate the JSM Extractors as described in section 2.3.4. The EFWK Administration work center
is working, however the JSM extractors are missing in the list of available extractors.
Solution:
There are some steps missing in managed system setup of the Solution Manager. Perform the following
steps:
Execute transaction SOLMAN_SETUP in the Solution Manager system. Go to ‘Managed System
Configuration’, select the relevant managed system and press ‘Configure System’. In step 8 ‘Configure
Automatically’ select ‘Extractors Setup’ and press ‘Execute Selected’ (see below picture). This will refresh
the available extractors for the managed system relevant for the product version.
Figure 42 – Screenshot: Setup extractors for the managed system
In case of errors check the details of the error message.
October 2011 39
3.2 Problems after activation process

3.2.1 No data available for the JSM Health Check Report
Symptom:
The JSM Health Check has been set up, but you do not see the results in the report because there is no
data in the InfoCube.
Solution:
1. First check the table “E2E_EFWK_STATUS” in Transaction SE16. As selection criteria, enter
“*JSM*” in the field “Extractor”. In the result list, check the SID to identify the entry for your InfoCube,
double-click on the entry. Then check the content of “Message” field to see if there is any error
message which may give you a hint on the problem. An example error screen shot shows an error
message “E EXTRACTOR NOT REGISTERED”. In this case the Main Extractor
“E2E_ME_ST_API_ASYNC” is configured incorrectly (see section 2.2.4 for correct parameters for
each report).
2. Then try to analyze and solve the problem based on the content of the error message.
3. After you solved the problem, delete the corresponding entry in table “E2E_EFWK_STATUS” so that
the extractor will be restarted.
40 October 2011

Язык

Добро пожаловать в Scribd!

JSM HC SetupGuide

Загружено:

Сведения о документе

Описание:

Дата загрузки

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Описание:

Авторское право:

Доступные форматы

JSM HC SetupGuide

Загружено:

Описание:

Авторское право:

Доступные форматы

Похожие издания

Job Scheduling Management

SAP Job Scheduling

with SAP Solution

HTML, DHTML, XML, XHTML are trademarks or registered

2.1.4 Check System Changeability ..................................................................................................13

2.2 ACTIVATION WITH SAP SOLUTION MANAGER 7.0 .........................................................................17

2.2.3 Check E2E Resources used by the Extractor Framework .....................................................20

2.2.6 Maintain table for definition of data reorganization ...............................................................24

2.2.7 Web Service Activation ...........................................................................................................25

2.3 ACTIVATION WITH SAP SOLUTION MANAGER 7.1 .........................................................................28

2.3.4 Activate data extraction process in Extractor Framework (EFWK) .......................................32

2.3.6 Web Service Activation ...........................................................................................................35

2.3.7 Check Job Scheduling Management Health Check Report ...................................................35

3.2 PROBLEMS AFTER ACTIVATION PROCESS....................................................................................40

1.1 Concept of Job Scheduling Management Health

Figure 1 – Job Scheduling Management Health Check Concept

Dashboards (BW Report) Web Template InfoCube Data Source

Weekly View on Jobs (Steps) 0SM_JSM_HC_XBP_WEEKLY_STEPS 0SM_JSM_D Aggregated from InfoCube

Monthly View on Jobs(Steps) 0SM_JSM_HC_XBP_MONTHLY_STEPS 0SM_JSM_W Aggregated from InfoCube

1.2 Benefits of Job Scheduling Management Health

1.2.1 JSM Health Check on Jobs

Showing distribution of background jobs

More advantages of the JSM Health Check on Jobs are:

Works as a standalone tool

Examples of JSM Health Check Reports:

Figure 2a – Report Examples based on job execution data

Figure 2a – Example BPMon simple job report

Figure 2b – Example BPMon BW process chain report

At 1:30 AM the job started

Software Component Recommended Minimum

2.1.2 Relevant SAP Notes

- SAP Note 1578583: “BW content for SAP Solution Manager”

Optional SAP Notes

- SAP Note 1028690: “True Type Fonts delivered with IGS”

- SAP Note 596825: “GFWCHART configuration file”

2.1.3 Check of Repository changeability and cross-client customizing

Figure 3 – Double click on the selected BW client in transaction “SCC4”

Figure 4 – Changes to Repository and cross-client Customizing should be allowed

2.1.4 Check System Changeability

Figure 5 – Transaction SE03 used to set system change options

2.1.5 Users and authorizations

- Create role Z_SAP_BW_CCMS_SETUP from standard role SAP_BW_CCMS_SETUP.

Figure 7 – Screenshot: Role Z_SAP_BW_CCMS_SETUP (1)

Figure 8 – Screenshot: Role Z_SAP_BW_CCMS_SETUP (2)

Figure 9 – Screenshot: Role Z_SAP_BW_CCMS_SETUP (3)

Figure 10 – Screenshot: Role Z_JSM_HC_USER

2.1.6 Set up Business Process Monitoring Job and BW Process Chain

2.2 Activation with SAP Solution Manager 7.0

2.2.1 Activate SAP Business Information Warehouse objects

Figure 11 – Screenshot: Report to generate BW objects

Figure 12 – Screenshot: successful messages after activation of BW objects

The result can be checked in the Data Warehousing Workbench:

Figure 13 – Screenshot: Data Warehousing Workbench

Figure 14 – Screenshot of SM37: check BW Extractor job

Figure 15 – Screenshot of SM37: check the housekeeping job

2.2.3 Check E2E Resources used by the Extractor Framework

Figure 16 – Screenshot: check E2E Resources