CUSTOMER

SAP Solution Manager 7.2Document Version: 1.0 – 2016-12-19

Configuration Guide for Central Job OverviewIn SAP Solution Manager 7.2

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Activating Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 Activating ICF Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 Activating OData Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Search for the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Add the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Activate the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Setting Up the Remote Database Connection to CPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.1 SAP Notes for Database Multiconnect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2 Maintaining Database Logon Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.3 Installing Database Client and Database Shared Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.4 Maintaining Database Connection in DBCON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 Maintaining the Configuration Table SJO_CONFIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

5 Maintaining User Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165.1 Job Monitoring Template Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

6 Recommended: Creating Custom Authorization Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

7 Optional: Defining Custom Authorization Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2 C U S T O M E RConfiguration Guide for Central Job Overview

Content

1 Introduction

The Central Job Overview in SAP Solution Manager provides an overview of the status of jobs scheduled in your local ABAP system as well as those scheduled with the external scheduler SAP Central Process Scheduling by Redwood (SAP CPS). This configuration guide describes how to set up the remote database connection to CPS and configure the Central Job Overview.

NoteThe latest version of SAP CPS was renamed SAP Business Process Automation by Redwood 9.0 (SAP BPA) in March 2015. For more information, see SAP Note 2005087

Configuration Tasks

1. Activating Services [page 4]Activate Internet Connection Framework (ICF) and OData services for the Central Job Overview application

2. Setting Up the Remote Database Connection to CPS [page 7]Set up the remote database connection from SAP Solution Manager to the SAP CPS database using ABAP database connectivity (ADBC).

3. Maintaining the Configuration Table SJO_CONFIG [page 11]Maintain the CPS database connection configuration for the job info portal.

4. Maintaining User Roles [page 16]Assign the required roles for the Central Job Overview to SAP Solution Manager users.

5. Recommended: Creating Custom Authorization Checks [page 17]Create a custom Web service to limit user access to just the spool request (transaction SP01).

6. Optional: Defining Custom Authorization Checks [page 18]Implement the BAdI SJO_AUTH_CHECKS to limit what search results are displayed in the Central Job Overview based on custom authorization checks.

Configuration Guide for Central Job OverviewIntroduction C U S T O M E R 3

2 Activating Services

2.1 Activating ICF Services

Context

In this activity, you activate Internet Communication Framework (ICF) services for the Central Job Overview application in transaction SICF. The URL path is mapped in ICF subnodes (services). You have to activate each subnode separately.

For example, to activate the services for URL /sap/bc/ui5_ui5, you have to activate the service tree default_host . Then you activate services sap, bc, and ui5_ui5 separately.

Procedure

1. Start transaction SICF.

2. Activate the following service nodes:

/default_host/sap/bc/ui5_ui5

/default_host/sap/bc/ui5_ui5/sap/cjo_portal

/default_host/sap/bc/bsp/sap/cjo_portal 3. To activate an ICF service, select the required service node in the ICF tree.4. Activate the ICF service in one of the following ways:

○ In the menu, select option Service/Host Activate○ In the context menu select Activate Service.

4 C U S T O M E RConfiguration Guide for Central Job Overview

Activating Services

2.2 Activating OData Service

Context

In this activity, you activate the OData service for the Central Job Overview (CENTRALJOB_OVERVIEW_SRV).

If you configure the Technical Monitoring scenario in SAP Solution Manager Configuration (transaction solman_setup), this service will be activated as part of the guided procedure. Otherwise, you have to add and activate the service manually as described here.

2.2.1 Search for the Service

Context

The following steps will show you how to search for a service.

Procedure

1. Start transaction /n/IWFND/MAINT_SERVICE.2. Search for the service CENTRALJOB_OVERVIEW_SRV in the service catalog.3. If the service is already in the catalog and active, you do not have to do anything more.

2.2.2 Add the Service

Context

Figure 1: Add a Service

Procedure

1. If the service is not already in the catalog, choose Add Service.

2. Choose the system alias of your local SAP Solution Manager system.

Configuration Guide for Central Job OverviewActivating Services C U S T O M E R 5

3. In the Technical Service Name field, enter CENTRALJOB_OVERVIEW_SRV and choose Get Services. The service will appear in the list below. Click on the Technical Service Name link. The Add Service dialog appears. Under Creation Information, choose Local Object. Add the service to the catalog.

2.2.3 Activate the Service

Context

Procedure

1. Find the service in the catalog and select it.2. Under ICF Nodes, check if ODATA is active (green status).

3. If it is not already active, select the ODATA node and choose Activate from the ICF Node drop down menu.

4. In the Package dialog, choose Local Object and then activate the service.

6 C U S T O M E RConfiguration Guide for Central Job Overview

Activating Services

3 Setting Up the Remote Database Connection to CPS

The Central Job Overview needs to query the external CPS database using ABAP database connectivity (ADBC) to collect job data. The ADBC interface is an ABAP/OO-based API that supports all SAP-supported database management systems (DBMS).

The following figure illustrates the technical system landscape for remote database access:

On the left is the standard database access for a job data collector running on the ABAP stack of the monitored system. The data collector is an ABAP program that uses database-independent ABAP Open SQL syntax. Within the SAP Kernel and SAP database interface (DBIF), this is translated into the database-dependent native SQL syntax anyway, but it uses the default DBSL and database client for the local default connection to the database server with the SAP ABAP application data.

On the right is a data collector for remote database queries. It is also an ABAP program and therefore needs an ABAP stack, typically SAP Solution Manager. It works directly with native SQL syntax, keeping as closely as possible to the ANSI SQL standard.

Configuration Guide for Central Job OverviewSetting Up the Remote Database Connection to CPS C U S T O M E R 7

3.1 SAP Notes for Database Multiconnect

The following SAP Notes provide additional information on how to set up the secondary database connections (also known as database multiconnect).

Table 1:

DBMS Description Instructions

ADA SAP DB (ADABAS/D) SAP Note 955670 : DB multiconnect with MaxDB as secondary database

DB2 DB2 UDB for OS/390 SAP Note 160484 : DB2/390: Data­base multiconnect with EXEC SQL

DB4 DB2 UDB for AS/400 SAP Note 146624 : i5/OS: Database multiconnect for IBM DB2 for i5/OS

DB6 DB2 UDB for Unix/Win. SAP Note 200164 : DB multiconnect with DB6 as target database

HDB SAP HANA database SAP Note 1597627 : SAP HANA con­nection

MSS Microsoft SQL Server SAP Note 178949 : MSSQL: Database MultiConnect with EXEC SQL

3.2 Maintaining Database Logon Users

On the remote database, you must maintain at least one database logon user with read-only access to the database schema with the required application tables for job monitoring. You may want to maintain several database logon users so that you can set up multiple database connections to the same database instance, in order to grant different authorizations at the database level. You must know the password of the database user(s) to set up the database connection. For more information, see Maintaining Database Connection in DBCON [page 9]. For more information about the authorization check that takes place on the SAP ABAP stack, see Maintaining User Roles.

3.3 Installing Database Client and Database Shared Library

For each type of SAP-supported database management system (DBMS), you need an appropriate database client and database shared library (DBSL). The following must be installed on the system where the data collector runs (generally the SAP Solution Manager system):

8 C U S T O M E RConfiguration Guide for Central Job Overview

Setting Up the Remote Database Connection to CPS

● DBMS-specific database clientDatabase clients are available from the respective database vendor. However, note that not all vendors provide database clients for every SAP-supported operating system.

● SAP DBSL for the connected DBMSSAP provides the DBSL as a database-dependent add-on library for the database-independent SAP Kernel.

This requirement is already fulfilled if your CPS application uses the same database type as SAP Solution Manager. For example, if SAP Solution Manager runs on an IBM DB6 database, and the data collector wants to connect to a CPS application that also uses IBM DB6, no additional installation is required. The SAP database interface (DBIF) can reuse the existing database client and shared library for the remote database connection (secondary connection) to another IBM DB6 instance using ADBC. However, if your CPS system runs on Microsoft SQL Server, you need to install an additional DBSL and database client from Microsoft. Ideally, additional database clients and DBMS are installed on all application servers of the SAP system, but at a minimum on at least one application server. If the database client and DBMS are not available on all application servers, the execution of the data collector must be forced on a specific application server. This may require further system settings (such as additional RFC destinations or RFC server groups).

3.4 Maintaining Database Connection in DBCON

Context

Every connected secondary database must have at least one connection entry in table DBCON. The connection entry defines the technical details (database host, port number, connection parameters, etc.) and security information (logon user, encrypted password). You maintain this table by using transaction DBCO, or as of SAP Basis 7.0, with the more user-friendly transaction DBACOCKPIT.

Configuration Guide for Central Job OverviewSetting Up the Remote Database Connection to CPS C U S T O M E R 9

Procedure

1. 1. In DBA Cockpit (transaction DBACOCKPIT), switch to the DB Connections view by using the button at the top of the navigation pane on the left.

2. Verify that the CPS remote database is in the table.3. Perform a connection test to ensure that the remote database is reachable.4. If necessary, create a new connection entry with read-only authorization. There may be an existing DBCON

entry for your CPS database for the purposes of remote database diagnostics or administration. Typically such a connection entry uses a quite powerful database logon user with modification authorization. However, for application monitoring, a read-only user is sufficient. It is possible and recommended to create multiple connection entries towards the same database instance, but using different logins with customized table access rights.

10 C U S T O M E RConfiguration Guide for Central Job Overview

Setting Up the Remote Database Connection to CPS

4 Maintaining the Configuration Table SJO_CONFIG

In this activity, you maintain the CPS database connection configuration for the job info portal.

1. Start Maintain Table Views (transaction SM30).2. Open the table SJO_CONFIG.

Explanation of Columns:○ The number in the Ext. Sched. Set column is used to group all settings and systems belonging to a

specific CPS system.○ The number in the System Set column is used to group all parameters for a specific managed system /

client combination.3. Maintain the following parameters:

Table 2:

ExampleValues

Parameter Description VALUE1 VALUE2

Scheduler SAP CPS is supported as the external scheduler. Use value CPS to use Central Job Overview for SAP CPS.

Other external schedulers can be connected on a project basis.

CPS

Version of Scheduler Imple­mentation

Value 1.0 corresponds to SAP CPS V8. Validation of version 1.0 for SAP BPA V9 (SAP CPS V9) is ongoing.

1.0

Remote DB Connection and Schema

1. Remote database connec­tion name

2. Remote database schema name

SD7_TO_SB7 SAPSB7DB

Configuration Guide for Central Job OverviewMaintaining the Configuration Table SJO_CONFIG C U S T O M E R 11

ExampleValues

Parameter Description VALUE1 VALUE2

System and Client With this parameter, you to specify either the managed system ID and client or the CPS job type to search.

If you enter a number in the VALUE2 field, the Central Job Overview will search for ABAP jobs and ABAP jobs in job chains in the specified managed system.

If you enter CPS, BO, or PI in VALUE2, the Central Job Overview will search for jobs in the external scheduler. There will be no search in a managed system. The exter­nal scheduler is identified by the value in the Ext Sched. Set column. The VALUE1 field is ignored.

○ CPS: Central Job Over­view will search for any job type in the external scheduler.

○ BO: Search is limited to SAP Business Objects and SAP Data Services jobs

○ PI: Search is limited to SAP PI jobs.

SD7

--

--

--

200

CPS

BO

PI

12 C U S T O M E RConfiguration Guide for Central Job Overview

Maintaining the Configuration Table SJO_CONFIG

ExampleValues

Parameter Description VALUE1 VALUE2

Package Size for DB Selec­tion

Technical parameter influ­encing the generation of the SQL statements. Defines the maximum number of values in an IN list which is used in the WHERE clause of the SQL statement. The optimal size of IN lists depend on the database management sys­tem used.

This parameter can be used for tuning the database ac­cesses. A value of 100 should be used as the de­fault.

100

Configuration Guide for Central Job OverviewMaintaining the Configuration Table SJO_CONFIG C U S T O M E R 13

ExampleValues

Parameter Description VALUE1 VALUE2

URL A valid URL to display a spool request ID in a Web­GUI screen consists of sev­eral parts:

1. Protocol, host and port

2. Web service path and name: /sap/bc/gui/sap/its/webgui

3. Parameters of the Web service: ?sap-client=040&sap-language=EN

4. Parameter for transaction SP01: &~transaction=*sp01

5. Parameter for the spool request ID: %20S_RQIDEN-LOW=

6. Spool request ID

7. OK Code: DYNP_OKCODE=CRET

Most of the parts are static (parts 1, 2, 3, 4, 5). Only the spool request ID and the OK Code (parts 6 and 7) are generated into the URL by the Central Job Overview.

Maintain the content of parts 1, 2, 3, 4 and 5 in fields VALUE1 and VALUE2. The content of the two fields will be concatenated to the first part of the URL. The second part of the URL will be gener­ated during runtime.

The section Recommended: Creating a Custom Web Service describes how parts 2, 3 and 4 of https://

14 C U S T O M E RConfiguration Guide for Central Job Overview

Maintaining the Configuration Table SJO_CONFIG

ExampleValues

Parameter Description VALUE1 VALUE2

<host> :<port> /sap/bc/gui/sa p/its/webgui?s ap- client=040&sap - language=EN&~t ransaction=*sp 01%20S_RQIDEN- LOW= Example for a custom Web service: /sap/bc/gui/te st/zsjo_spool? s_rqiden-low==<spool_request_ID>;DYNP_OKCODE=C RET

Alternatively, it is possible to use a specific Portal service to call the WebGUI screen.

Maximum Number of Jobs Selected

Maximum number of jobs al­lowed

10000

RFC destination of external scheduler

RFC destination of external scheduler (required for Job Monitoring only)

CRONACLE- 7604586@SAP:SB 7-70

RFC destination of managed system

This parameter allows you to overrule the standard deter­mination of the RFC destina­tion used to access the man­aged system.

The standard determination identifies the RFC destina­tion in the following order: READ destination -> NONE -> TRUSTED destination.

READ and TRUSTED desti­nations are taken from the managed system configura­tion. It is possible to define an RFC destination per sys­tem set.

Configuration Guide for Central Job OverviewMaintaining the Configuration Table SJO_CONFIG C U S T O M E R 15

5 Maintaining User Roles

5.1 Job Monitoring Template Users

The following SAP-delivered standard roles provide SAP Solution Manager users the required authorizations for the Central Job Overview:

Table 3:

SAP Standard Role Description

SAP_SM_CENTRAL_JOB_OVERVIEW For remote database access, an authorization check based on theS_DBCON authorization object is performed on the SAP ABAP stack. This role provides authorization for object S_DBCON and other required authorization objects.

SAP_SM_RFC_DISP Allows users to display RFC destination lists in transaction SM59 and in applications.

SAP_SYSTEM_REPOSITORY_DISP Allows users to display systems.

The Job Monitoring: Level 1 and Level2 Template Users have been enhanced to include these required roles for the Central Job Overview. You can create users for job monitoring in SAP Solution Manager Configuration, in the Technical Monitoring Job Monitoring scenario, step Create Template Users.

16 C U S T O M E RConfiguration Guide for Central Job Overview

Maintaining User Roles

6 Recommended: Creating Custom Authorization Checks

The Central Job Overview can generate a URL that provides access to the spool list in the managed system. The standard Web service could be used in this call; however, the standard Web service does not have any restrictions by default.

For security reasons, we recommend that you create a custom Web service in order to allow access to the spool request (transaction SP01) and prevent access to all other transactions.

You use transaction SICF to manage Web services.

1. Create a new Web service.For more information, see Creating Services on the SAP Help Portal.Use the WebGUI service path (/default_host/sap/bc/gui/sap/its/webgui) as the template for your new service.

2. In the maintenance screen of the Web service, choose Service Data.3. Under Interactive Options, choose GUI configuration to open the service parameters.

The following sample parameters will generate a WebGUI screen for transaction SP01 when the Web service is called:

~WEBGUI 1

~THEME SL

~XSRFCHECK 1

~TRANSACTION SP01 (defines the transaction)

~SINGLETRANSACTION 1 (restricts the WebGUI screen to the defined transaction)

You can use the following additional parameters to define the menu bar and navigation options:

~WEBGUI_SIMPLE_TOOLBAR

~WEBGUI_ICON_TOOLBAR

For more information about these parameters, see Article - Employ SAP GUI for HTML instead of an Internet service on the SAP Community Network.

Configuration Guide for Central Job OverviewRecommended: Creating Custom Authorization Checks C U S T O M E R 17

7 Optional: Defining Custom Authorization Checks

The Enhancement BAdI: Authorization Checks in Central Job Overview (SJO_AUTH_CHECKS) was created to allow you to limit what search results are displayed in the Central Job Overview based on additional authorization checks.

The BAdI method IF_EX_SJO_AUTH_CHECKS~CHANGE_RESULT_LIST is called just before the result of the job search is displayed. You can use this method to modify the result list based on customer-specific authorization check logic.

18 C U S T O M E RConfiguration Guide for Central Job Overview

Optional: Defining Custom Authorization Checks

Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).

Configuration Guide for Central Job OverviewImportant Disclaimers and Legal Information C U S T O M E R 19

go.sap.com/registration/contact.html

© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.