SAP Job Scheduling Management Health Check

Job Scheduling Management Health Check Setup and User Guideline SAP Job Scheduling Management Health Check with SAP Solution Manager May 2016

SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/6227/7-47474 F +49/6227/7-57575 www.sap.com Copyright 2011-2016 SAP SE. 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, NT, EXCEL, Word, PowerPoint and SQL Server 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, Informix and Informix Dynamic Server TM are trademarks of IBM Corp. in USA 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, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. JAVA is a registered trademark of Sun Microsystems, Inc. J2EE 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. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mysap, mysap.com, 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

TABLE OF CONTENTS 1 INTRODUCTION... 4 1.1 CONCEPT OF JOB SCHEDULING MANAGEMENT HEALTH CHECK... 4 1.2 BENEFITS OF JOB SCHEDULING MANAGEMENT HEALTH CHECK... 6 1.2.1 JSM Health Check on Jobs... 6 2 SETUP... 8 2.1 PREREQUISITES... 8 2.1.1 SAP Solution Manager System... 8 2.1.2 Relevant SAP Notes... 9 2.1.3 Check changeability of Repository and cross-client Customizing...10 2.1.4 Check System Change Options...11 2.1.5 Users and authorizations...12 2.2 ACTIVATION WITH SAP SOLUTION MANAGER 7.1...15 2.2.1 SAP Notes providing latest corrections for activation report...16 2.2.2 Activate SAP Business Information Warehouse objects...16 2.2.2.1 Activation using report RAGS_JSM_CONFIG_CUSTOMIZE...16 2.2.2.2 Alternative: Activation using report RS_BCT_SM_SETUP_JSM_HC...16 2.2.2.3 Activation results...17 2.2.3 Maintain table for target-source mapping for aggregation and data reorganization...18 2.2.4 Check if the Extractor Framework (EFWK) and housekeeping job are working...19 2.2.5 Check E2E Resources used by the Extractor Framework...21 2.2.6 Activate data extraction process in Extractor Framework (EFWK)...22 2.2.7 Web Service Activation...24 2.2.8 Check Job Scheduling Management Health Check Report...25 3 TROUBLESHOOTING...28 3.1 PROBLEMS DURING ACTIVATION PROCESS...28 3.1.1 Error during activation of BW objects (step in section 2.2.2)...28 3.1.2 Problem with EFWK Administration Work Center (step in section 2.2.6)...29 3.1.3 JSM extractors are missing in the list of available extractors (step in section 2.2.6)...29 3.2 PROBLEMS AFTER ACTIVATION PROCESS...30 3.2.1 No data available for the JSM Health Check Report...30 3.2.2 Error loading template when report is executed...31 3.2.3 Distribution and bookmark not available in Web Templates...32 May 2016 3

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. 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 an 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 from the managed systems into InfoCubes located in the BW component of SAP Solution Manager. All jobs in selected managed systems with a final status ( finished or cancelled ) 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). A set of extractors are available to extract job execution data from the managed systems. This 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 (see figure1). Figure 1 Job Scheduling Management Health Check Concept Dashboards (BW Report) Web Template InfoCube Data Source 4 May 2016

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 The dashboards for job / job step 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. 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). May 2016 5

1.2 Benefits of Job Scheduling Management Health Check 1.2.1 JSM Health Check on Jobs The JSM Health Check on jobs / job step 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 screen shots below show examples from the reports. 6 May 2016

Figure 2 Report Examples based on job execution data May 2016 7

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.1 will be described in sections 2.2. 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 Requirements SAP Solution Manager 7.0 SAP Solution Manager 7.1 Recommended SolMan 7.0 with SP27 & ST-BCO 400 SP0 (or higher) and ST-A/PI 01M* (or higher) on the respective backend system (SAP BASIS 620 or higher with SAP Note 1564604 implemented) SolMan 7.1 with SP02 & ST-BCO 710 SP0 (or higher) and ST-A/PI 01M* (or higher) on the respective backend system (SAP BASIS 620 or higher with SAP Note 1564604 implemented) Minimum SolMan 7.0 with SP23 & BI_CONT 7.04 SP07 (or higher) and ST-A/PI 01M* (or higher) on the respective backend system (SAP BASIS 620 or higher) SolMan 7.1 with SP01 & BI_CONT 7.05 SP01 (or higher) and ST-A/PI 01M* (or higher) on the respective backend system (SAP BASIS 620 or higher) 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. 8 May 2016

2.1.2 Relevant SAP Notes Please refer to SAP Note 2319931. This is a collective note for the JSM Health Check of the SAP Solution Manager 7.1 and the SAP Solution Manager 7.2. It includes all relevant notes with existing corrections and will be updated regularly. We strongly recommend implementing all corrections in order to assure an errorless operation of the infrastructure. May 2016 9

2.1.3 Check changeability of Repository and cross-client Customizing Note: In a productive system the settings for the Repository and cross-client Customizing might not be changeable. If this is the case, the activation steps have to be performed in the development system first. The changed objects have to be transported to the productive system in a second step. Before starting the activation process, the changeability of the Repository and cross-client Customizing has to be checked. Modifications of these items must 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 5 & 6). Otherwise change it. After completing the activation process it can be reset to its original status. Figure 3 Double click on the selected BW client in transaction SCC4 Figure 4 Changes to Repository and cross-client Customizing should be allowed 10 May 2016

2.1.4 Check System Change Options Note: In a productive system the settings for System Change Options might not be changeable. If this is the case, the activation steps have to be performed in the development system first. The changed objects have to be transported to the productive system in a second step. 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 7 & 8). Figure 5 Transaction SE03 used to set system change options May 2016 11

Figure 6 Check if relevant BW namespaces are modifiable - If not, change them accordingly 2.1.5 Users and authorizations 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. 12 May 2016

Figure 7 Screen shot: Role Z_SAP_BW_CCMS_SETUP (1) - Extend authorization: fill object class BC_A, object S_TABU_DIS, field DICBE with *. Figure 8 Screen shot: Role Z_SAP_BW_CCMS_SETUP (2) - 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. May 2016 13

Figure 9 Screen shot: Role Z_SAP_BW_CCMS_SETUP (3) 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 Screen shot: 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. 14 May 2016

2.2 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. Report RAGS_JSM_CONFIG_CUSTOMIZE supports the different steps of the activation. Note: The activation of BW objects is performed in BW client, all other steps in Solution Manager client. May 2016 15

2.2.1 SAP Notes providing latest corrections for activation report The following SAP Notes provide the latest corrections for the activation report RAGS_JSM_CONFIG_CUSTOMIZE. It is highly recommended to implement the corrections before the activation is performed. If all or some of the activation steps were performed already, follow the instructions in the SAP Notes to update the settings in the Solution Manager. SAP Notes: 2249196 - Catch-up run of extractor extract data only for the last one hour 2252512 - Data in the hourly cube should be kept longer to enable issue analysis 2.2.2 Activate SAP Business Information Warehouse objects 2.2.2.1 Activation using report RAGS_JSM_CONFIG_CUSTOMIZE In order to activate the necessary BW objects for the JSM Health Check execute the report RAGS_JSM_CONFIG_CUSTOMIZE by checking BW Content Activation and entering RFC destination to BW (this will create a background job for report RS_BCT_SM_SETUP_JSM_HC). Figure 11 Screen shot: Report RAGS_JSM_CONFIG_CUSTOMIZE 2.2.2.2 Alternative: Activation using report RS_BCT_SM_SETUP_JSM_HC Alternatively report RS_BCT_SM_SETUP_JSM_HC can be executed 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 15), please leave the entry field empty and press the execution button (F8) to start the activation process: Figure 12 Screen shot: Report to generate BW objects 16 May 2016

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). 2.2.2.3 Activation results Once all objects are configured you should receive message All steps successfully performed as shown in figure 16. If the activation was done in background the information can be found in the spool of the job which executed report RS_BCT_SM_SETUP_JSM_HC. Figure 13 Screen shot: successful messages after activation of BW objects 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 screen shot below. May 2016 17

Figure 14 Screen shot: Data Warehousing Workbench 2.2.3 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. Figure 15 Screen shot: 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). 18 May 2016

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 16 Screen shot: Reorganization parameters with 0SM_JSM_H 0SM_JSM_D 0SM_JSM_W $DELTA=8$ (8 days) $DELTA=30$ (1 month) $DELTA=180$ (6 months) Explanation of the above example: 0CALDAY stands for the current day, for example 09.07.2011. If DELTA = 8, this means the threshold date is current day minus 8 days (01.07.2011). In this case, all data in 0SM_JSM_H that is older than 01.07.2011 will be deleted. This configuration ensures that the data at lowest level will only be available for 8 days, so that the data volume will be kept low. These entries can be changed any time manually according to your special needs. 2.2.4 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. May 2016 19

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 17 Screen shot 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. 20 May 2016

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 18 Screen shot of SM37: check the housekeeping job For more information about the aggregation levels and data reorganization, please refer to the sections 2.2.3. 2.2.5 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. May 2016 21

Figure 19 Screen shot: 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 BI 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.6 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. In SAP Solution Manager 7.1, all extractor entries should be created automatically by Solution Manager Setup. The maintenance on the active worklist items table E2E_ACTIVE_WLI is therefore performed via the administration view in the EFWK Administration Work Center. 22 May 2016

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 20 Screen shot: Maintain extractors 2. As shown in the screen shot 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 21 Screen shot: select the extractor to be activated May 2016 23

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 22 Screen shot: activate the extractor 2.2.7 Web Service Activation Before the web template for JSM Health Check can be used in the system, the BEx (Business Explorer) and Mime (MIME in Web Reporting) Web services 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 23 Screen shot: Activation of web services 24 May 2016

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 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. 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 24 Screen shot: Maintain views May 2016 25

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 25 Screen shot: Select views Confirm your configuration by pressing the OK-button. Now you can access the dashboards directly via the JSM Work Center. As shown in the screen shot below, go to the Report view; select the BW Reports as Reporting Views. Figure 26 Screen shot: 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). 26 May 2016

Please expand the collapsed data to see the statistics and diagrams for job status and workload distribution in the managed system. May 2016 27

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.2) Symptom: As described in section 2.2.2, 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 screen shot. Figure 27 Screen shot: 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. 28 May 2016

3.1.2 Problem with EFWK Administration Work Center (step in section 2.2.6) Symptom: You want to perform the step described in section 2.2.6, 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.2.6) Symptom: You want to activate the JSM Extractors as described in section 2.2.6. 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 28 Screen shot: Setup extractors for the managed system In case of errors check the details of the error message. May 2016 29

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. Start Solution Manager Administration Work Center, select the tab Infrastructure. Then select Framework -> Extractor Framework. In the Extractor Overview list, filter by *JSM*. Select the related extractor, and check the status. As next step, select the related extractor, check the status. 2. In case the extractor is banned, you may check if the problem can be solved by releasing the extractor. 30 May 2016

3. If the problem persists or in case of error status you can check the extractor logs and extractor details by clicking on the extractor entry. 4. Try to analyze and solve the problem based on the content of the error logs. 5. After you have solved the problem, deactivate and reactivate the extractor so that the extractor will be restarted. 3.2.2 Error loading template when report is executed Symptom: A report is started in the Job Management Workcenter e.g. Daily view on jobs. The execution fails with error message Error loading template 0SM_JSM_HC_XBP_* (message BRAIN 276). Solution: The Web Template for the report had not been activated successfully. The Web Template can be checked and activated in transaction RSOR as follows: 1. Start transaction RSOR 2. Navigate to Object types 3. Expand node Web Template (Format SAP BW 3.x) and double-click on Select Objects. 4. Select Web Template e.g. 0SM_JSM_HC_XBP_DAILY_JOBS and transfer the selection. If the Web Template and the used queries are active, there is a green icon in column Active version available. If some of the objects are not active yet, they can be activated in the following way: Select the Web Template Choose 'Install' for activation in a productive system or 'Installation and Transport' for activation in a development system. Refresh the display (F5) Afterwards there should be a green icon in column 'Active version available'. Repeat the same procedure for the other Web Templates. May 2016 31

3.2.3 Distribution and bookmark not available in Web Templates Symptom: It is intended to distribute a JSM Health Check report to defined recipients on a regular basis. This is possible in two ways. Either a Bookmark is created for the report or the report is distributed using the BEx Broadcaster. Both functionalities cannot be used because the entries Distribute and Bookmark are missing in the context menu of the executed report. Solution: Follow the instructions in SAP Note 2241074 to activate the missing actions in the context menu. Follow this procedure to distribute a report with defined content: 1. Execute the report e.g. Weekly view on jobs 2. Expand the graphics and tables which should be included in the distributed report 3. Right-click in the report (e.g. on the legend of a graphic) to get the context menu displayed 4. Select Distribute By E-Mail 5. Create a new setting and schedule in the Broadcaster. The wizard will guide you through the steps. 32 May 2016

There are three output formats available: a. Online link to current data : The email will provide a link to the JSM Health Check report. The recipient must have a user ID in the Solution Manager with appropriate authorizations to display the report. b. HTML : The email have an attachment providing a precalculated version of the report. c. MHTML : Similar to HTML but in a different format. May 2016 33