Cisco TEO Getting Started Guide for SAP

Transcription

1 Release October 2012 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax: Text Part Number:

2 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB s public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental Cisco Systems, Inc. All rights reserved.

3 CONTENTS New and Changed Information Latest Release vii Previous Releases viii vii Preface xi Organization xi Conventions xii Product Documentation xiii Documentation Formats xiii Guides and Release Notes xiii Online Help xiii Open Source License Acknowledgements xiii Obtaining Documentation and Submitting a Service Request xiv CHAPTER 1 Prerequisites 1-1 System Requirements 1-1 Hardware Requirements 1-1 Software Requirements 1-2 Adapter System Requirements 1-4 SAP HANA Requirements 1-6 Disk Space Requirements 1-7 Reporting Database Sizing Requirements 1-8 TEO Performance Best Practice Guidelines 1-9 Recommended Hardware Requirements 1-9 Configuration Access Requirements 1-10 SAP User Account 1-10 SAP Support User Account 1-10 SAP ABAP System Information 1-10 SAP Java System Information 1-11 SAP Database Access Rights 1-11 Product Default Settings 1-13 CHAPTER 2 Importing Automation Packs 2-1 Importing the Automation Packs for SAP 2-2 iii

4 Contents Installing SAP.NET Connector Files 2-18 Installing SAP Java Library Files 2-18 Configuring SAP Multi-Tenant Support in Web Console 2-21 CHAPTER 3 Configuring Runtime Users 3-1 Accessing the Runtime Users View 3-1 Runtime User Accounts 3-2 Creating Runtime Users 3-2 Creating an SAP User Account 3-2 Creating a Runtime User Account 3-4 Managing Runtime User Definitions 3-7 Modifying an SAP User or Runtime User Record 3-7 Deleting an SAP User or Runtime User Record 3-7 CHAPTER 4 Configuring SAP Targets 4-1 Accessing the Targets View 4-1 SAP Target Types 4-2 Interfaces to SAP System Targets 4-2 Creating SAP System Targets 4-3 Creating an SAP System Target ABAP Connection 4-3 Creating an SAP System Target ABAP+Java Connection 4-10 Creating an SAP System Target Java Connection 4-20 Creating SAP Solution Manager Targets 4-27 Creating and Configuring HANA Targets 4-32 Creating SAP HANA Database Target 4-32 Creating Web Targets 4-35 Creating Unix/Linux System Target 4-37 Creating SAP System Target 4-41 Creating HANA System Service Target 4-41 Configuring References to Targets 4-43 Managing SAP Targets 4-46 Enabling an SAP Target 4-46 Disabling an SAP Target 4-46 Deleting an SAP Target 4-47 CHAPTER 5 Managing Assignments and Notifications 5-1 Accessing Task Rules View 5-2 Configuring Task Rules 5-3 iv

5 Contents SAP Default Assignment 5-3 Creating a New Task Rule 5-5 Managing Task Rule Definitions 5-12 Enabling Notification Based on Assignment Processes 5-14 CHAPTER 6 Managing Extended Target Properties 6-1 Accessing Extended Target Properties 6-1 Configuring Extended Target Properties 6-3 CHAPTER 7 Configuring SAP Global Variables 7-1 Accessing Global Variables 7-1 Configuring Global Variables 7-3 CHAPTER 8 Understanding SAP Processes 8-1 Accessing the SAP Processes 8-1 Filtering Processes by Category 8-2 Managing SAP Processes 8-3 Enabling a Process 8-3 Disabling a Process 8-3 Modifying Process Instance Archival 8-4 Modifying a Process Schedule 8-5 Running Processes 8-8 Starting a Process 8-8 Viewing Running Process 8-10 Viewing Process Results 8-11 Accessing Process View 8-11 Viewing Activity Results 8-12 Viewing Incidents 8-13 Viewing Automation Summary 8-16 APPENDIX A Configuring SAP v7.1x JARM Tracing Service A-1 Launching the SAP ConfigTool A-1 Configuring Properties A-2 APPENDIX B Registering TEO with SAP System Landscape Directory B-1 Registering Tidal Enterprise Orchestrator B-2 Registering the Product Manually B-2 v

6 Contents To Import Registration B-2 Transfer Registration via XML B-3 I NDEX vi

7 New and Changed Information New and changed information for the most recent releases of the Cisco TEO Getting Started Guide for SAP is as follows: Latest Release Previous Releases Latest Release Table 1 September Feature Updated Prerequisites chapter to include requirements for: SAP ABAP Adapter SAP Solution Manager Adapter SAP HANA Added instructions for importing the following new automation packs: Automation for SAP Solution Manager E2E Response Automation for SAP HANA Added instructions for creating the following SAP targets: SAP Solution Manager SAP HANA System Location Chapter 1, Prerequisistes Chapter 2, Importing Automation Packs Chapter 3, Managing SAP Targets vii

8 New and Changed Information Previous Releases Table 2 April Changes Feature Revised Text Part Number (-01 to -02). Updated Trademark and Copyright date Prerequisite changes: Updated hardware and software requirements Updated supported SAP versions Added TEO Performance Best Practice Guidelines section Added SAP Support User Account section Added prerequisite for SAP.NET Connector 3.0 dll files; included instructions for copying files to TEO server. Revised automation pack names: Core Automation for SAP BW, BOBJ and In-Memory Computing Incident Response for SAP IT Task Automation for SAP Added instructions for configuring SAP multi-tenant support in the Web Console Added SPI for HP OpenView for Unix to the Incident Reponse for SAP automation pack. New feature for supporting duplicate SAP system IDs Updated Extended Targets Target Property Value dialog box allows options to set multiple targets. Location Front cover, footers Inside cover page Chapter 1, Prerequisites Chapter 2, Importing the Automation Packs Chapter 2, Importing the Automation Packs Chapter 2, Importing the Automation Packs Chapter 4, Configuring SAP Targets Chapter 6, Managing Extended Target Properties viii

9 New and Changed Information Table 3 September Changes Feature Updated guide name, automation pack names, and added Text Part Number to document. Changes/Updates to Importing the Automation Pack include: New Default Incidents Assignee Setup panel in Automation Pack Import Wizard (Core Automation for SAP tap). Added Assessment for SAP BWA tap Added Core Automation for SAP BW, BWA and BOBJ tap Added Common Activities tap Updated Installing Java Library Files section. Updates to SAP System Wizard Database Connection panel. New chapter on using the Task Rules feature. New chapter on using the Extended Target Properties feature. Location All Chapter 2, Importing Automation Packs Chapter 2, Importing Automation Packs Chapter 4, Configuring SAP Targets Chapter 5, Managing Assignments and Notifications Chapter 6, Managing Extended Target Properties ix

10 New and Changed Information x

11 Preface Tidal Enterpise Orchestrator (TEO) is designed to enhance the management and administration of your SAP environment. TEO s powerful process automation engine provides the logical constructs necessary to support even the most complex requirements to automate the administrative and operational tasks necessary to manage your SAP systems. Cisco TEO automation pack files are a collection of processes (workflows) authored by subject matter experts that work out of the box to automate best practices for a particular technology. The SAP-related automation packs include the content necessary to provide functionality specific to the SAP environment. This guide is intended to provide information on installing, configuring, and using the SAP-related objects in TEO. Organization This guide includes the following sections: Chapter 1 Prerequisites Provides information on the system requirements and user access information for installing the SAP-related automation packs in TEO. Chapter 2 Importing Automation Packs Provides instructions for importing the SAP-related automation packs in TEO. Chapter 3 Configuring Runtime Users Provides information on configuring the runtime users to be used in the processes that run against your SAP environment. Chapter 4 Configuring SAP Targets Provides instructions for creating and managing the SAP targets on which to run the processes. Chapter 5 Chapter 6 Managing Assignments and Notifications Managing Extended Target Properties Provides instructions on using the Task Rules feature to configure assignments and notifications. Provides instructions on using the Extended Target Properties feature to configure the properties that ship with the automation packs. xi

12 Preface Chapter 7 Configuring SAP Global Variables Provides information configuring the global variables that are used in the SAP processes. Chapter 8 Understanding SAP Processes Provides information on using and managing the SAP processes. Appendix A Appendix B Configuring SAP v7.1x JARM Tracing Service Registering TEO with SAP System Landscape Directory Provides instructions for configuring the JARM tracing service. Provides instructions for registering TEO with the SAP System Landscape Directory. Conventions This guide uses the following conventions: Convention bold font italic font Indication Commands and keywords and user-entered text appear in bold font. Document titles, new or emphasized terms, and arguments for which you supply values are in italic font. [ ] Elements in square brackets are optional. {x y z } Required alternative keywords are grouped in braces and separated by vertical bars. [ x y z ] Optional alternative keywords are grouped in brackets and separated by vertical bars. string A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks. courier font Terminal sessions and information the system displays appear in courier font. < > Nonprinting characters such as passwords are in angle brackets. [ ] Default responses to system prompts are in square brackets.!, # An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line. Note Means reader take note. Tip Means the following information will help you solve a problem. Caution Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data. xii

13 Preface Timesaver Means the described action saves time. You can save time by performing the action described in the paragraph. Warning Means reader be warned. In this situation, you might perform an action that could result in bodily injury. Product Documentation Documentation Formats Documentation is provided in the following electronic formats: Adobe Acrobat PDF files Online help You must have Adobe Reader installed to read the PDF files. Adobe Reader installation programs for common operating systems are available for free download from the Adobe Web site at Guides and Release Notes You can download the TEO product documentation from Cisco.com. Release Notes can be found on Cisco.com and the product CD. Online Help Online help is available and can be accessed using the following methods: Click the Help button on any dialog in the application to open the help topic in a pane to the right of the dialog. In the Tidal Enterprise Orchestrator console: Click the Help Pane tool on the toolbar to open the help topic in a pane to the right of the console results pane. Click Help on the menu bar. Open Source License Acknowledgements Licenses and notices for open source software used in Cisco Tidal Enterprise Orchestrator can be found in the Open Source License Acknowledgements found on Cisco.com. If you have any questions about the open source contained in this product, please external-opensource-requests@cisco.com. xiii

14 Preface Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: Subscribe to the What s New in Cisco Product Documentation as a RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0. xiv

15 CHAPTER 1 Prerequisites This chapter provides information on the system requirements and user access information that must be met before installing the SAP-related automation packs in Tidal Enterprise Orchestrator (TEO) and information needed for configuring the product. It includes the following sections: System Requirements, page 1-1 TEO Performance Best Practice Guidelines, page 1-9 Configuration Access Requirements, page 1-10 Note For complete information on system requirements and user access information, see the Cisco TEO Installation and Administration Guide. System Requirements Before installing TEO, it is recommended that you verify that your system meets the minimum hardware and software requirements. The requirements in this section outline the minimum requirements necessary to operate TEO on demo or development systems only. For best performance for production environments, please review the TEO Performance Best Practice Guidelines, page 1-9. Hardware Requirements The following tables contain the minimum hardware requirements for TEO. Table 1-1 Minimum Hardware Requirements Component Client Server CPU 2.8 GHz or higher core (Dual core 64-bit 2.8 GHz or higher core (Dual core systems recommended) systems recommended) Memory 2 GB RAM minimum (4 GB RAM or higher recommended) 2 GB RAM minimum (4 GB or higher recommended) 8 GB of RAM (If MSSQL is installed on same machine as TEO) It is recommended that the database reside on a separate server. 1-1

16 System Requirements Chapter 1 Prerequisites Table 1-1 Minimum Hardware Requirements Component Client Server Disk Space 1 GB of available hard disk space dedicated to Tidal Enterprise Orchestrator (2 GB or higher recommended) For disk space sizing formula, see Disk Space Requirements, page 1-7. Network adapter 1 GB of available hard disk space dedicated to Enterprise Orchestrator (2 GB or higher recommended) For disk space sizing formula, see Disk Space Requirements, page 1-7. Network adapter Software Requirements The following table provides the minimum software requirements. Table 1-2 Minimum System Requirements Component Client Server Web Console ASP.NET ASP.NET 2.0 Internet Information Service (IIS) Manager Java SE Runtime Environment Operating System Microsoft Windows Server 2008 (Standard, Enterprise, or Datacenter) Microsoft Windows Server 2003 (Standard or Enterprise) Microsoft Windows 7 Microsoft Vista Microsoft Windows XP ASP.NET Web Service Extensions IIS 6.0 IIS 6.0 IIS 7.0 with 6.0 compatibility IIS 7.0 with 6.0 compatibility 64-bit JRE 6 Update 1.6 HP-Unix Enterprise Edition (Limited to Oracle database support) Microsoft Windows Server bit (Standard, Enterprise, or Datacenter) Microsoft Windows Server bit (Standard or Enterprise) Oracle Solaris Enterprise Edition (Limited to Oracle database support) Redhat Linux Enterprise Edition 6 (Limited to Oracle database support) 1-2

17 Chapter 1 Prerequisites System Requirements Table 1-2 Minimum System Requirements Component Client Server Web Console Microsoft.NET Framework Processes Database Reporting Database Microsoft.NET Framework 4 Oracle 11g R2 or later Microsoft.NET Framework 4 Microsoft SQL Server 2008 (Standard or Enterprise Edition) or later. Microsoft SQL Server 2005 Oracle Database Enterprise Edition 11g R2 or later (Both 32-bit and 64-bit are supported) Specific versions of operating systems are limited to the Oracle versions that are supported on them. It is strongly recommended that the database settings should be case-insensitive. See Modifying Oracle DB Instance Case-Sensitive Settings in the Cisco TEO Installation and Administration Guide. Microsoft SQL Server 2008 (Standard or Enterprise Edition) Microsoft SQL Server 2005 Microsoft SQL Server Reporting Services (2005 or later) -or - Business Objects Enterprise XI 3.1 SP1 Note Only one of the reporting tools is required. 1-3

18 System Requirements Chapter 1 Prerequisites Adapter System Requirements This section provides the system requirements for individual adapters. Table 1-3 Minimum Adapter System Requirements Adapter SAP ABAP Adapter Component SAP GUI The SAP ABAP Adapter requires SAP.NET Connector 3.0 for.net 4.0 on x64 version or higher. The following dll files must be copied to the TEO server: sapnco.dll sapnco_utils.dll Before you can configure an SAP ABAP system target, these files must be installed on the TEO server. See Installing SAP.NET Connector Files, page 2-18 for instructions on installing these files. SAP Versions: SAP R/3 Note 46c (Support Package 50) 46d (Support Package 15) 6.10 (Support Package 6) 6.20 (including 4.7) RFCs that depend on the TEO ABAP Transport files are not supported in SAP On SAP v7.1x application servers, you must configure the JARM tracing service with custom values before TEO can monitor Java portals. See Appendix A, Configuring SAP v7.1x JARM Tracing Service for instructions. SAP task automation remote function calls using the Cisco add-on are supported on 7.0 SP13 or higher. 1-4

19 Chapter 1 Prerequisites System Requirements Table 1-3 Adapter Minimum Adapter System Requirements Component SAP BW SP SP Note RFCs that depend on the TEO ABAP Transport files are only supported on SAP BW 7.00 SP16 or later. BW remote function calls using the Cisco Add-on are supported on BW 7.01 SP8 or higher and BW 7.3. SAP BWA 7.2 (Rev. 8 or later) for BWA TREX Scripting It is recommended that you install the latest kernel patch for the installed SAP version. SAP Java Adapter SAP Business Objects Explorer 4.0 TEO requires the SAP jar files to monitor Java application servers. You must have access to one of the following CDs to install the jar files on the TEO server before configuring SAP Java application server targets: SAP NetWeaver 7.0 SR3 Java based Software Components Number SAP NetWeaver CE 7.1 SR5 Java Components Documentation Developer Workplace Number

20 System Requirements Chapter 1 Prerequisites Table 1-3 Minimum Adapter System Requirements Adapter SAP Solution Manager Adapter Component SAP.NET Connector 3.0 for.net 4.0 on x64 version or higher. The following dll files must be copied to the TEO server: sapnco.dll sapnco_utils.dll Before you can configure an SAP Solution Manager target, these files must be installed on the TEO server. See Installing SAP.NET Connector Files, page 2-18 for instructions on installing these files. SAP Solution Manager 7.1 SP05 or later The SAP Solution Manager 7.1 system and basic setup must be completed. Managed Objects must be configured. SAP ABAP/Netweaver 7.02 SP10 SAP HANA Requirements The following prerequisites must be met prior to configuring the SAP HANA targets in TEO. Table 1-4 SAP HANA Requirements Requirement SAP HANA Database Client Configure Windows Host File Create Data Source Description The SAP HANA Database Client for Windows must be installed on the server where TEO is installed. Download the SAP HANA CLIENT 1.00 (SP04 Revision 35 or later) for Windows on x64 64-bit from the SAP Service Marketplace. Note The revision number of SAP HANA CLIENT 1.00 for Windows on x64 64-bit installed on the TEO server must be the same as the revision number on the HANA database. The minimum supported version for the SAP HANA Client 1.00 is SP04 Revision 35. Before you can connect to the ODBC system DSN, you must add the HANA data source hostname and IP address to the Windows hosts file. See the Cisco TEO Process Automation Guide for Automation for SAP HANA for instructions. Before you can create HANA system targets, you must add the ODBC system data source used to connect to the HANA data provider from TEO. See the Cisco TEO Process Automation Guide for Automation for SAP HANA for instructions. 1-6

21 Chapter 1 Prerequisites System Requirements Table 1-4 SAP HANA Requirements Requirement Unix/Linux Target Prerequisites Description The following prerequisites must be met for Unix/Linux system target functionality: The following versions of Linux are supported: SUSE Linux Enterprise 11 Service Pack 1 SUSE Linux Enterprise 11 Service Pack 2 Linux peformance monitoring requires that the SYSSTAT Linux package be installed. To install the package, run the command yast -i sysstat. If you want to monitor all Linux hosts, you must configure Auto-SSH login proxy. See the Cisco TEO Process Automation Guide for Automation for SAP HANA for instructions.. Disk Space Requirements The amount of available disk space on the server where the TEO database server is installed depends on the number of records published to the database. The formula for calculating the disk space is based on the following record statistics: Table 1-5 Calculating Disk Space Formula for TEOProcess Database Database Record Process Workflow Activity Task Record Size 16 KB 7 KB 10 KB (with an average of 6 KB one out of 5 having paged (1 KB for output Auditing) Record Rate per/process 500 (estimate) Daily Total 80 MB MB MB Retention (months) For sizing estimates, the items in the above table will be grouped as one average-sized process that equals 73 KB (five activities inside a process). The disk space requirements formula as shown in the following table is based on the process database running 5000 processes per day and 500 tasks for 30 day retention: Table 1-6 Calculating Disk Space Formula Data Process Size Activity Size Task Size Total Size Formula MB/day x 30 days/month = GB MB/day x 30 days/month = MB 500 tasks x 6 KB MB/day x 30 days/month = MB DB initial size for 30 day retention = 5000 processes per day * 73 KB tasks *6 KB = KB or 368 MB *30 = KB or 11040MB or GB 1-7

22 System Requirements Chapter 1 Prerequisites Reporting Database Sizing Requirements The formula for calculating the disk space for the TEO Reporting database for an SAP environment is based on the following record statistics: Table 1-7 Calculating Disk Space Formula for TEO Reporting Database for SAP Environment Process Incident Alert Event Metric Audit Task Audit Record Size 2 KB 2 KB 1.5 KB 0.06 KB 0.2 KB 0.15 KB Record Rate (estimate) Daily Total Retention (months) 30/day per system 60 KB per system 200/day per system 400 KB per system 1/min per application server 2160 KB per application server 0.2 records/sec per application server 1036 KB per application server 3000/day per system 600 KB per system x number of alerts 90 KB per system The disk space requirements formula as shown in the following table is based on an environment that includes 1 SAP system with 5 application servers: Table 1-8 Calculating Disk Space Formula Data Incident Size Alert Size Event Metrics Process Audit Task Audit Total Size Formula 60 KB/system/day x 1 system x 6 months = 10 MB 400 KB/system/day x 1 system x 6 months = 72 MB 2160 KB/application server/day x 5 servers x 6 months = 1920 MB 1036 KB/application server/day x 5 servers x 6 months = 1864 MB 600 KB/system/day x 1 system x 6 months = 108 MB 90 KB/system/day x 1 system x 6 months = 16 MB 10 MB + 72 MB MB MB MB MB + 16 MB = 3.99 GB 1-8

23 Chapter 1 Prerequisites TEO Performance Best Practice Guidelines TEO Performance Best Practice Guidelines TEO's multi-threaded architecture allows it to fully utilize all processors on the TEO server system. TEO generally scales linearly with the number of processor cores and the clock speed at which processors execute. Adding more CPU cores is the single most effective factor in increasing TEO performance. To maximize performance capacity, include the maximum number of processor cores available in the hardware supporting the TEO server. The TEO server intelligently caches data such as actively running processes to optimize performance. Sufficient memory is required to minimize paging. Allow memory to handle burst situations, but plan the number of processor cores in the system to be sufficient for steady state (average) load. Database optimization is very important. While TEO ships with a schema which is performance optimized, including the relevant indices, etc., customers need to install and operate this database. Customers should refer to documentation associated with their chosen database platform for best practice. Among other things, in high performance scenarios, the following best practices can dramatically affect performance: A separate host server for the database versus other TEO architectural elements A separate high speed disk for the database, operating system and program files, and swap files. Sufficient memory to avoid paging. A high speed network connection. Typically this means the database is "close by" the TEO server. Certainly they should be in the same data center. Proper database server hardware and routine database maintenance can have substantial effects on performance. Recommended Hardware Requirements The following table contains the hardware requirements which maximizes TEO performance. Table 1-9 Recommended Hardware Requirements Component Client Server CPU 2.8 GHz or higher processor (Dual processors or higher) 64-bit 2.8 GHz or higher processor (Quad processors or higher) Memory 4 GB RAM or higher 8 GB RAM (If MSSQL is installed on same machine as TEO) Disk Space 2 GB of available hard disk space dedicated to Tidal Enterprise Orchestrator or higher For disk space sizing formula, see Disk Space Requirements, page 1-7. Network adapter It is recommended that the databases reside on a separate server. 4 GB of available hard disk space dedicated to Tidal Enterprise Orchestrator or higher recommended For disk space sizing formula, see Disk Space Requirements, page 1-7. Network adapter 1-9

24 Configuration Access Requirements Chapter 1 Prerequisites Configuration Access Requirements The following user rights and configuration requirements must be met prior to installing and configuring the SAP-related automation packs. SAP User Account The user must create a SAP user account for TEO to use to log into SAP. Cisco recommends that you create a user account as follows: Recommendation Required Authorization Account Type Language Setting Description S_A.System profile System, Service, or Communication user type is recommended English, German. The TEO server regional setting should match the language setting in SAP. SAP Support User Account The TEO Auditor Role, which has read-only permissions, can be used for SAP support users to perform troubleshooting and maintenance tasks in TEO. The default assignment of the TEO Auditor Role is to members of the TEO Auditors group in Windows Computer Management. Create the support user account and add it to the TEO Auditors group in Windows Computer Management. Alternately, the created account may be directly assigned to the TEO Auditor Role in TEO. For information on assigning support users to the TEO Auditors security group, refer to the "Configuring TEO Security" chapter in the Cisco TEO Installation and Administration Guide. SAP ABAP System Information The following information about your SAP environment should be gathered prior to installing TEO. You will need this information during the installation process. Field Display Name Application Server System Number SAP Router String (optional) Logon Information Description Name used to identify the SAP system Name or IP address for the ABAP application server SAP-specific system number Used for SAP systems outside the firewall User name, password and client for logging onto the SAP ABAP application server 1-10

25 Chapter 1 Prerequisites Configuration Access Requirements SAP Java System Information The following information about your SAP Java System should be gathered prior to installing TEO. You will need this information during the installation process. Field Application Server Port Logon Information Description Name or IP address for the Java application server The port number to connect to the server. The following convention should be used for specifying the port number: 5<J2EEinstance_number>04 Example: If your J2EE instance number is 15, the P4 port is User name and password for logging onto the SAP Java application server SAP Database Access Rights These access rights are optional. If you want to collect SAP database SQL query information, you must have the following access rights to the SAP database. Microsoft SQL Server Windows Authentication SQL Server SQL Authentication If SQL Server Windows authentication is being used, the following access rights must be set on the machine where TEO is installed. To change the connection settings through the database user configuration utility on TEO server, the logged in user needs to have write permission to the TEO installation folder. Windows Server 2003 The following user rights are required: The user account that connects to the database must be assigned Logon as Service rights. The user account that is logged in and using the user interface must be assigned Act as part of the OS rights. Windows Server 2008 The following user rights are required: The user account that connects to the database must be assigned Logon as Service rights. The user account that is logged in and using the user interface must be assigned Act as part of the OS rights. If SQL authentication is being used, the user account that connects to the database must have sysadmin (sa) rights on the machine where TEO is installed. However, if the company requires a higher level of access than the standard sysadmin access, then use the following scripts to create the logon script for access. 1-11

26 Configuration Access Requirements Chapter 1 Prerequisites Process Database Logon Script Use the following logon SQL script to create the necessary credentials for accessing the TEO processes database. IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N'teoprocess') DROP LOGIN [teoprocess] GO CREATE LOGIN [teoprocess] WITH PASSWORD=N'teo', DEFAULT_DATABASE=[TEOProcess], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF --For Windows authentication --CREATE LOGIN [domain\userid] FROM WINDOWS WITH DEFAULT_DATABASE=[TEOProcess] GO USE [TEOProcess] GO IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'teoprocess') DROP USER [teoprocess] GO CREATE USER [teoprocess] FOR LOGIN [teoprocess] WITH DEFAULT_SCHEMA=[dbo] GO EXEC sp_addrolemember N'db_datareader', N'teoprocess' GO EXEC sp_addrolemember N'db_datawriter', N'teoprocess' GO Reporting Database Authentication Script Use the following logon script to create a SQL user account for the TEO reporting database. The assumption is that TEOReporting database will be created by a sysadmin account first, after which the script can be used to create a teoreporting database account with limited permission, and change reporting database to use the TEOReporting user account. IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N'teoreporting') DROP LOGIN [teoreporting] GO CREATE LOGIN [teoreporting] WITH PASSWORD=N'teo', DEFAULT_DATABASE=[TEOReporting], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF --For Windows authentication --CREATE LOGIN [domain\userid] FROM WINDOWS WITH DEFAULT_DATABASE=[TEOReporting] GO USE [TEOReporting] GO IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'teoreporting') DROP USER [teoreporting] GO CREATE USER [teoreporting] FOR LOGIN [teoreporting] WITH DEFAULT_SCHEMA=[dbo] GO EXEC sp_addrolemember N'db_datareader', N'teoreporting' GO EXEC sp_addrolemember N'db_datawriter', N'teoreporting' GO 1-12

27 Chapter 1 Prerequisites Configuration Access Requirements Oracle Database Access Rights If you are using an Oracle database, it is recommended that the user account have read access rights to all tables and views assigned to it. The following minimum access rights must be assigned to the user account: SAP tables (SNAP and EDIDC) V$lock V$session V$sqlarea V$rowcache V$sql_plan V$librarycache V$sgastat Dba_free_space all_objects Dba_data_files DB2 Database Access Rights The following rights must be assigned to the user accounts for DB2 databases: The user account that connects to the DB2 UDB database must have SYSMON authority. Note After assigning the user account to the SYSMON group, the DB2 instance needs to be restarted to ensure that the privilege is active. The user account should have Select access on the following SAP tables: SNAP EDIDC Product Default Settings The following information should be gathered prior to installing the product. The information is necessary when importing the Core automation pack after the product installation has completed. Default Settings The Configuration panel on the Automation Pack Import Wizard is used to configure the default settings that will be used for activities. The following information is required to configure the settings during the configuration process: Setting Default SMTP server Description The name of the SMTP server that is used as the default server for sending messages 1-13

28 Configuration Access Requirements Chapter 1 Prerequisites Setting Default SMTP port Default sender Description The port number for the SMTP server. The default port number is 25 but can be changed if necessary. The address of the sender that is designated as the default sender for activities Default Windows Credentials The Default Windows Credentials panel on the Automation Pack Import Wizard is used to configure the default credentials to be used for the Windows automation target. The following information is required: Field Domain User name Password Description Name of the domain in which the Windows automation server target resides Name of the user account that is used to connect to the Windows automation server target Password assigned to the user account that is used to connect to the Windows automation server target 1-14

29 CHAPTER 2 Importing Automation Packs During the initial installation of Tidal Enterprise Orchestrator (TEO), you can choose to import and configure the automation packs or import them at a later time from within the Console. This chapter guides you through importing the SAP-related automation packs (tap files) during the initial installation. It includes the following sections: Importing the Automation Packs for SAP, page 2-2 Installing SAP.NET Connector Files, page 2-18 Installing SAP Java Library Files, page 2-18 Configuring SAP Multi-Tenant Support in Web Console, page 2-21 Note For information on importing a specific SAP-related automation pack from within the Console, see the appropriate Process Automation Guide. Note It is recommended that you review the system requirements and prerequisites before importing automation packs. 2-1

30 Importing the Automation Packs for SAP Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP You use the Automation Pack Import Wizard to import the automation packs. The wizard guides you through importing each automation pack in the order of their dependency on other automation packs. This section provides instructions for importing the SAP-related automation packs. Step 1 After running the Setup wizard to install the product, ensure that the Launch automation pack import wizard now check box is checked before closing the wizard. Note You can also launch the Automation Pack Import Wizard in the Console using the Administration workspace. See the Cisco TEO Installation and Configuration Guide or the appropriate Process Automation Guide for instructions. Step 2 On the Select Automation Packs dialog box, ensure that the following check boxes are checked and then click OK to launch the Automation Pack Import Wizard: Assessment for SAP BWA Automation for SAP BW and BWA Common Activities Core Automation for SAP BW, BOBJ and In-Memory Computing Core Automation for SAP Incident Response for SAP IT Task Automation for SAP Automation for SAP Solution Manager E2E Response Automation for SAP HANA Note See the Cisco TEO Installation and Administration Guide for instructions on importing and configuring the Core components for the product. 2-2

31 Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP Figure 2-1 Welcome to the Automation Pack Import Wizard Step 3 On the Welcome panel, click Next. Figure 2-2 General Information Core SAP Automation Step 4 On the General Information panel, review the information about the automation pack and then click Next. 2-3

32 Importing the Automation Packs for SAP Chapter 2 Importing Automation Packs Figure 2-3 Default Incidents Assignee Setup Core Automation for SAP Use the Default Incidents Assignee Setup panel to specify the default person who should be assigned SAP-related incidents. Step 5 Click the Browse tool to specify the user. Figure 2-4 Select User or Group Step 6 Step 7 Step 8 Step 9 On the Select User or Group dialog box, click Location and choose the location from which the user will be selected. In the text box, enter the user name and click Check Names. If the name is found, the box will be populated with the appropriate address. Click OK to close the Select User or Group dialog box. On the Default Incidents Assignee Setup panel, click Next. 2-4

33 Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP Figure 2-5 Review Prerequisites Core Automation for SAP The Review Prerequisites panel displays the prerequisites for the automation pack being imported. The green check mark indicates that the prerequisite was found on the computer. The red X indicates that the prerequisite was not found on the computer. When this occurs, the import process is stopped and cannot continue until all prerequisites have been met. If all prerequisites are passed, the wizard automatically continues to the next panel. Figure 2-6 General Information Assessment for SAP BWA Step 10 On the General Information panel, review the information about the automation pack and then click Next. 2-5

34 Importing the Automation Packs for SAP Chapter 2 Importing Automation Packs Figure 2-7 Data Extraction Assessment for SAP BWA Use the Data Extraction panel to specify the destination for the extracted data and the data to be extracted. The Assessment for SAP BWA automation pack provides the following data that can be extracted and the check boxes are checked by default: ABAP Transport Files Extracts the ABAP Transport files that must be installed on the SAP systems to be able to use the RFCs that ship with this automation pack. BWA Assessment Files Extracts the support files used by the Assessment for SAP BWA automation pack. SQL Server Reporting Services Reports Extracts the report files to be imported into SQL Server Reporting Services after the automation pack has been imported. Step 11 On the Data Extraction panel, accept the default location or click the Browse tool to specify a new destination. Step 12 Step 13 In the Select data to extract area, verify that the check boxes are checked for the data that you want to extract. If you do not want to extract specific data, uncheck the check box. Click Next. 2-6

35 Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP Figure 2-8 Review Prerequisites Assessment for SAP BWA The Review Prerequisites panel displays the prerequisites for the automation pack being imported. The green check mark indicates that the prerequisite was found on the computer. The red X indicates that the prerequisite was not found on the computer. When this occurs, the import process is stopped and cannot continue until all prerequisites have been met. If all prerequisites are passed, the wizard automatically continues to the next panel. Figure 2-9 General Information Core Automation for SAP BW, BOBJ and In-Memory Computing Step 14 On the General Information panel, review the information about the automation pack and then click Next. 2-7

36 Importing the Automation Packs for SAP Chapter 2 Importing Automation Packs Figure 2-10 Data Extraction Core Automation for SAP BW, BOBJ and In-Memory Computing The Data Extraction panel is used to specify the destination where the BWA Script files will be extracted. The script files are used in the direct TREX monitoring processes and must be copied to the TREX server. Note If you uncheck the BWA Scripts check box, the files will not be extracted. Step 15 Accept the default location or click the Browse tool to specify a different location to extract the files and then click Next. Figure 2-11 Review Prerequisites Core Automation for SAP BW, BOBJ and In-Memory Computing The Review Prerequisites panel displays the prerequisites for the automation pack being imported. The green check mark indicates that the prerequisite was found on the computer. 2-8

37 Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP The red X indicates that the prerequisite was not found on the computer. When this occurs, the import process is stopped and cannot continue until all prerequisites have been met. If all prerequisites are passed, the wizard automatically continues to the next panel. Figure 2-12 General Information Common Activities Step 16 On the General Information panel, review the information about the Common Activities automation pack and then click Next. Figure 2-13 Review Prerequisites Common Activities The Review Prerequisites panel displays the prerequisites for the automation pack being imported. The green check mark indicates that the prerequisite was found on the computer. The red X indicates that the prerequisite was not found on the computer. When this occurs, the import process is stopped and cannot continue until all prerequisites have been met. If all prerequisites are passed, the wizard automatically continues to the next panel. 2-9

38 Importing the Automation Packs for SAP Chapter 2 Importing Automation Packs Figure 2-14 General Information Automation for SAP BW and BWA Step 17 On the General Information panel, review the information about the automation pack and then click Next. Figure 2-15 Data Extraction Automation for SAP BW and BWA The Data Extraction panel is used to specify the destination where the ABAP Transport files will be extracted. The ABAP Transport files must be installed on the SAP systems on which some remote function calls that are used in this automation pack will be executed. Note If you uncheck the ABAP Transport check box, the files will not be extracted. Step 18 Accept the default location or click the Browse tool to specify a different location to extract the files and then click Next. 2-10

39 Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP Figure 2-16 Review Prerequisites Automation for SAP BW and BWA The Review Prerequisites panel displays the prerequisites for the automation pack being imported. The green check mark indicates that the prerequisite was found on the computer. The red X indicates that the prerequisite was not found on the computer. When this occurs, the import process is stopped and cannot continue until all prerequisites have been met. If all prerequisites are passed, the wizard automatically continues to the next panel. Figure 2-17 General Information Incident Response for SAP Step 19 On the General Information panel, review the information about the Incident Response for SAP automation pack and then click Next. 2-11

40 Importing the Automation Packs for SAP Chapter 2 Importing Automation Packs Figure 2-18 Data Extraction Incident Response for SAP Use the Data Extraction panel to specify the destination for the extracted data and the data to be extracted. The Incident Response for SAP automation pack provides the following data that can be extracted and the check boxes are checked by default: Business Objects Reports Extracts the report files to be imported into BusinessObjects after the automation pack has been imported. Microsoft SCOM Management Packs Extracts management packs for integration with the Microsoft System Center Operations Manager 2007 framework. SPI for HP OpenView Windows Extracts the SPI for integration with the HP OpenView for Windows framework. SPI for HP OpenView Unix Extracts the SPI for integration with the HP OpenView for Unix framework. SQL Server Reporting Services Reports Extracts the report files to be imported into SQL Server Reporting Services after the automation pack has been imported. Step 20 On the Data Extraction panel, accept the default location or click the Browse tool to specify a new destination. Step 21 Step 22 In the Select data to extract area, verify that the check boxes are checked for the data that you want to extract. If you do not want to extract specific data, uncheck the check box. Click Next. 2-12

41 Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP Figure 2-19 Review Prerequisites Incident Response for SAP If all prerequisites are passed, the wizard automatically continues to the next panel. Figure 2-20 General Information IT Task Automation for SAP Step 23 On the General Information panel, review the information about the IT Task Automation for SAP automation pack and then click Next. 2-13

42 Importing the Automation Packs for SAP Chapter 2 Importing Automation Packs Figure 2-21 Data Extraction IT Task Automation for SAP The Data Extraction panel is used to specify the destination where the ABAP Transport files will be extracted. The ABAP Transport files must be installed on the SAP systems on which some remote function calls that are used in this automation pack will be executed. Note If you uncheck the ABAP Transport check box, the files will not be extracted. Step 24 Accept the default location or click the Browse tool to specify a different location to extract the files and then click Next. Figure 2-22 Review Prerequisites IT Task Automation for SAP If all prerequisites are passed, the wizard automatically continues to the next panel. 2-14

43 Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP Figure 2-23 General Information Automation for SAP HANA Step 25 Step 26 On the General Information panel, review the information about the automation pack. If you want to disable all the processes that are imported with the automation pack, check the Disable all imported processes check box. Note If you disable all the imported processes, you will need to manually enable the processes in the Console before they can execute. Step 27 Click Next to continue. Figure 2-24 Review Prerequisites Automation for SAP HANA If all prerequisites are passed, the wizard automatically continues to the next panel. 2-15

44 Importing the Automation Packs for SAP Chapter 2 Importing Automation Packs Figure 2-25 General Information SAP Solution Manager E2E Response Step 28 Step 29 On the General Information panel, review the information about the automation pack. If you want to disable all the processes that are imported with the automation pack, check the Disable all imported processes check box. Note If you disable all the imported processes, you will need to manually enable the processes in the Console before they can execute. Step 30 Click Next to continue. Figure 2-26 Data Extraction SAP Solution Manager E2E Response The Data Extraction panel is used to specify the destination where the ABAP Transport files will be extracted. The ABAP Transport files must be installed on the SAP Solution Manager systems on which some remote function calls that are used in this automation pack will be executed. 2-16

45 Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP Note If you uncheck the ABAP Transport check box, the files will not be extracted. Step 31 Accept the default location or click the Browse tool to specify a different location to extract the files and then click Next. Figure 2-27 Review Prerequisites SAP Solution Manager E2E Response If all prerequisites are passed, the wizard automatically continues to the next panel. Figure 2-28 Completing the Automation Pack Import Wizard Step 32 After all automation pack objects have been imported, review the information on the Completing the Automation Pack Import Wizard panel to verify that it is correct and then click Close to close the wizard. 2-17

46 Installing SAP.NET Connector Files Chapter 2 Importing Automation Packs Installing SAP.NET Connector Files The SAP ABAP Adapter requires the SAP.NET Connector 3.0 for.net 4.0 on x64 version or higher. Before you can create an SAP ABAP target, the dll files must be installed on the TEO server. SAP.NET Connector 3.0 for.net 4.0 on x64 v or higher can be downloaded from the SAP web site. Step 1 Step 2 Step 3 From the SAP.NET Connector 3.0 for.net 4.0 on x64 program files folder on the server where NCo is installed, locate the following files: sapnco.dll sapnco_utils.dll Copy the files to the following folder on the TEO server: <Install drive>:\program Files\Cisco\Tidal Enterprise Orchestrator\Adapters Restart the Tidal Enterprise Orchestrator Server service. Installing SAP Java Library Files The SAP Java Adapter requires certain SAP Java library files, which are available on the SAP Installation CD. Before you can configure an SAP Java application server target, these files must be installed on the TEO server. You must have access to one of the following CDs to install the jar files: SAP NetWeaver 7.0 SR3 Java based Software Components Number SAP NetWeaver CE 7.1 SR5 Java Components Documentation Developer Workplace Number Step 1 Step 2 Step 3 Stop the Tidal Enterprise Orchestrator Server service. Navigate to the directory where the TEO files are installed (C:\Program Files\Cisco\Tidal Enterprise Orchestrator). Double-click Tidal.Automation.SapJarInstaller.exe to open the SAP Libraries Install Wizard. 2-18

47 Chapter 2 Importing Automation Packs Installing SAP Java Library Files Figure 2-29 Welcome to the SAP Dependency Libraries Installer Step 4 Click Next to check for the adapter dependency libraries have been installed. Figure 2-30 SAP Dependency Libraries Checker Step 5 Click Next to continue. If the required files cannot be found, the SAP JMX Adapter Dependency Libraries Installer panel displays. 2-19

48 Installing SAP Java Library Files Chapter 2 Importing Automation Packs Figure 2-31 SAP JMX Adapter Dependency Libraries Installer Step 6 Check the check box next to the version of SAP that you are using. Step 7 Enter the path or click the Browse tool to navigate to the location where the SAP installation files are located and then click Next. Figure 2-32 Finishing the SAP Libraries Install Wizard Step 8 Step 9 Verify that the files were successfully installed and then click Close to close the installer. Restart the Tidal Enterprise Orchestrator Server service to complete the procedure. 2-20

49 Chapter 2 Importing Automation Packs Configuring SAP Multi-Tenant Support in Web Console Configuring SAP Multi-Tenant Support in Web Console When using the SAP multi-tenance feature and viewing the SAP systems in the Web Console, the organizations do not display by default. To view the organization column in the Task view, you must configure the WebConsole.config file to enable this column. Perform the following procedure to modify the WebConsole.config file. Step 1 Step 2 Step 3 Step 4 On the TEO server, navigate to the folder where the Web.config file is located. By default the files are located in the following directory: C:\Program Files\Cisco\Tidal Enterprise Orchestrator\WebConsole Open the Web.config file in Notepad and navigate to the AffectedOrganizations setting. name="affectedorganizations" enabled="false" /> Change the enabled setting to true. Save the file to complete the procedure. 2-21

50 Configuring SAP Multi-Tenant Support in Web Console Chapter 2 Importing Automation Packs 2-22

51 CHAPTER 3 Configuring Runtime Users Many operating systems and application activities require a user security context for proper execution. The Runtime Users feature is used to create a runtime user record to store the information about the user security context. You assign runtime users to processes or activities within a process to specify the proper security context with which to execute the process or activity. This chapter provides information on configuring and managing the runtime user accounts that are used in the SAP-related automation packs. It includes the following sections: Accessing the Runtime Users View, page 3-1 Creating Runtime Users, page 3-2 Managing Runtime User Definitions, page 3-7 Accessing the Runtime Users View Use the Definitions Runtime Users view to display the credentials of the runtime users and to specify new runtime user credentials, update the credentials of users, or delete users. Figure 3-1 Definitions Workspace Runtime Users 3-1

52 Creating Runtime Users Chapter 3 Configuring Runtime Users Runtime User Accounts The type of runtime user account that is required depends on the adapter that supports the automation pack. For the SAP-related automation packs, the following runtime user accounts are used: Runtime User SAP User Runtime User Description Specifies the credentials required to access the following SAP-related targets: SAP System SAP Solution Manager Specifies the credentials required to access the following SAP-related targets: SAP Database SAP Java Application Server SAP HANA System Creating Runtime Users You can create the runtime user accounts that will be used to access your SAP targets before creating the targets or while you are creating the targets. This section guides you through creating the accounts before creating the targets. Refer to Runtime User Accounts to determine the type of runtime user account that you need to create based on the type of SAP target you will be creating. Creating an SAP User Account The SAP User is the account that will be used to connect to an SAP ABAP application server or SAP system target. Step 1 In the Definitions workspace, right-click Runtime Users and choose New > SAP User to open the New SAP User Properties dialog box. 3-2

53 Chapter 3 Configuring Runtime Users Creating Runtime Users Figure 3-2 Runtime Users New SAP User Submenu Figure 3-3 New SAP User Properties General Tab Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. 3-3

54 Creating Runtime Users Chapter 3 Configuring Runtime Users Step 2 On the General tab, specify the following information: Field Display name User name Password Client Description Description Name for the user account. User name assigned to the SAP user account that connects to the SAP system or ABAP application server. Password assigned to the SAP user account that connects to the SAP system or ABAP application server. SAP client number assigned to the user account. A description of the user account. Note The Used By tab displays objects used by the runtime user and will remain blank until used by an object. The History tab displays the history of actions taken against the runtime user and will remain blank until after the initial creation. Step 3 Click OK to close the dialog box. Creating a Runtime User Account The Runtime User is the account that will be used to connect to an SAP Java application server, SAP database, or SAP BI Warehouse server target. Step 1 In the Definitions workspace, right-click Runtime Users and choose New > Runtime User to open the New Runtime User Properties dialog box. 3-4

55 Chapter 3 Configuring Runtime Users Creating Runtime Users Figure 3-4 Runtime Users New Runtime User Submenu Figure 3-5 New Runtime User Properties General Tab Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. 3-5

56 Creating Runtime Users Chapter 3 Configuring Runtime Users Step 2 On the General tab, specify the following information: Field Display name User name Password Description Description Name for the user account. This field can populated with the information specified in the Domain and User name text fields, or you can enter a different name to display for the user account. User name assigned to the user account that connects to the SAP target. Check the check box and enter the password assigned to the user account. Note No password verification is done for the simple (generic) runtime user. A description of the user account. Note The Used By tab displays objects used by the runtime user and will remain blank until used by an object. The History tab displays the history of actions taken against the runtime user and will remain blank until after the initial creation. Step 3 Click OK to close the dialog box. 3-6

57 Chapter 3 Configuring Runtime Users Managing Runtime User Definitions Managing Runtime User Definitions Use the Definitions Runtime Users view to manage the runtime user definitions. Modifying an SAP User or Runtime User Record Use the Runtime User Properties to modify the runtime user credentials. Step 1 Step 2 Step 3 In the Definitions Runtime Users view, select the runtime user record, right-click and choose Properties. The selected [Runtime User] Properties dialog box displays. On the General tab, modify the appropriate information. See Figure 3-2 on page 3-3 or Figure 3-4 on page 3-5 depending on the type of runtime user record you are modifying. Click OK to save your changes and close the dialog box. Deleting an SAP User or Runtime User Record Use the Definitions Runtime Users view to delete a runtime user record. Step 1 In the Definitions Runtime Users view, select the runtime user record, right-click and choose Delete. The selected Confirm [Runtime User] Delete dialog box displays. Figure 3-6 Confirm SAP User Delete Step 2 Click Yes to confirm the deletion. 3-7

58 Managing Runtime User Definitions Chapter 3 Configuring Runtime Users 3-8

59 CHAPTER 4 Configuring SAP Targets Targets are used to define specific environments where activities, triggers and processes will be executed. You can define a target to run a process activity on a specific server, database connection, or application server. The targets can be defined once and reused in several processes. Before you can create or run processes in your SAP environment, you must create the targets on which the processes will run. This chapter provides instructions for creating and managing the SAP targets. It includes the following sections: Accessing the Targets View, page 4-1 Creating SAP System Targets, page 4-3 Creating SAP Solution Manager Targets, page 4-27 Creating and Configuring HANA Targets, page 4-32 Managing SAP Targets, page 4-46 Accessing the Targets View Use the Definitions Targets view to create and manage the SAP targets. Figure 4-1 Definitions Workspace Targets View 4-1

60 Accessing the Targets View Chapter 4 Configuring SAP Targets SAP Target Types The type of target that is required depends on the adapter that supports the automation pack. For the SAP-related automation packs, the following targets are used: Target SAP System SAP Solution Manager HANA System (Service target) Description The SAP System target is a collection of one or more of the following connections to your SAP systems: SAP system SAP ABAP connection SAP Java application server SAP database Use this target type to connect to an SAP Solution Manager system. Use this service target to reference all the targets in the SAP HANA environment. The following targets are referenced in the HANA System target: Generic Data Source (OLEDB) database target Web Target Unix/Linux System Target Interfaces to SAP System Targets The communication that occurs between TEO and the SAP system targets use one of the following technologies: SAP.NET Connector for RFC SAP JMX The communication mechanisms are not currently configured to enable SAP Secure Network Communications (SAP SNC) or secure HTTP. It is recommended that TEO be installed within a secured environment. 4-2

61 Chapter 4 Configuring SAP Targets Creating SAP System Targets Creating SAP System Targets This section guides you through creating SAP System targets. You can create a target for an SAP system that uses an ABAP connection to the application server, an ABAP and Java connection to the application server, or a Java connection to application server. Refer to the appropriate section for instructions on the type of system you are configuring. Note The SAP ABAP Adapter requires the dll files for SAP.NET Connector 3.0for.NET 4.0 on x64 version or higher. Before you can configure an SAP ABAP system target, these files must be installed on the TEO server. See Installing SAP.NET Connector Files, page 2-18 for instructions on installing these files. Creating an SAP System Target ABAP Connection You use the New SAP System wizard to create a target for an SAP system with an ABAP connection and the SAP database that is associated with the system. Step 1 On the Definitions workspace, right-click Targets and choose New > SAP System to open the New SAP System wizard. Figure 4-2 Welcome to the New SAP System Wizard Step 2 Click Next. 4-3

62 Creating SAP System Targets Chapter 4 Configuring SAP Targets Figure 4-3 System Setup The System Setup panel is used to specify the SAP system name, the type of system components to be configured, and the monitoring level for the SAP system. Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. Note You can only create one target for each SAP system. However, for multi-tenant environments, you can create targets for different SAP systems with the same system ID (SID). When using the same SID for different SAP systems, you must enter the organization for each SAP system so TEO can differentiate the alerts and incidents for each system. Step 3 Specify the following information about the SAP system: Field Display name System Components ABAP application servers Java application servers SAP database Description Enter a name for the SAP system. This is the name that will display in the Targets pane. Check this check box if the SAP system uses an ABAP connection to the application server. Check this check box if the SAP system uses a Java connection to the application server. Check this check box if you want to configure the SAP database that is associated with the SAP system. 4-4

63 Chapter 4 Configuring SAP Targets Creating SAP System Targets Field Monitor as production system Organization Description This check box is checked by default. Certain processes will run only on production systems. If you want to monitor the system as a non-production system (development or sandbox), uncheck the check box. Enter the group or organization within the company that owns the target. Note If you are configuring multiple SAP systems with the same SID, you must specify the organization for each SAP system target. Step 4 Click Next. Figure 4-4 ABAP Connection Use the ABAP Connection panel to enter the connection information for the SAP system. Note The system information entered on this panel must be unique. 4-5

64 Creating SAP System Targets Chapter 4 Configuring SAP Targets Step 5 Specify the connection information for connecting to the SAP application server: Field Connect using Application server Logon group Router string (optional) Default runtime user Description Choose the connection method from the drop-down list. The fields that display on the panel depend on the connection method selected. Choose this option to connect to the SAP system using the SAP application server connection information. Specify the information in the following fields: Server name Enter the name of the SAP application server. System number Enter the SAP system number. Choose this option to establish a connection using a logon group, which contains a group of SAP system instances. When a user logs on to a logon group, the message server directs the users to the server of this group that currently has the lightest load. Specify the information in the following fields: System ID Enter the SAP system ID (SID). Message server Enter the name of the server a user logs on to and that handles the communication between the application servers. For example, transport of update requests and lock requests. Group name Enter the name of the Logon Group to be accessed. The name entered in this field is case-sensitive. Enter the router string for accessing the SAP systems via SAPRouter. If you do not specify a router string, TEO accesses the SAP system directly. The router string must be formatted as: /H/host01/H/host02/H/ where host01 and host02 are the SAP systems that you want to access through the SAPRouter. Choose the user account that contains the credentials to connect to the target from the drop-down list. To view the properties for the selected runtime user, click the Properties tool. To create a new SAP User, click New > SAP User. See Creating an SAP User Account, page 3-2. Step 6 Click Next. 4-6

65 Chapter 4 Configuring SAP Targets Creating SAP System Targets Figure 4-5 Server Availability Step 7 The Server Availability panel is used to specify the SAP application servers that you want to monitor for availability and the ability to log in a user. Specify the following information: Field Servers available for monitoring Add Remove Select All Deselect All Description All detected servers are checked by default. Verify that the check box next to each server that you want to monitor is checked. If a server is offline during configuration, it will not be displayed in the list of available servers. To manually add the server, click Add and enter the name of the server. If you want to remove a server from the list, select the server and click Remove. If the check boxes have been unchecked and you want all servers to be monitored, click Select All. If all the check boxes are checked and you want to uncheck all of them, click Deselect All. Step 8 Click Next. If you are configuring the SAP database, the Database Connection panel displays. Otherwise, proceed to Step

66 Creating SAP System Targets Chapter 4 Configuring SAP Targets Figure 4-6 Database Connection Note The fields that display on this panel depend on the type of database that is being configured. Step 9 Step 10 Choose the Database type from the drop-down list to display the fields for the specific type of database. Specify the information for the type of database that is being configured. The fields that display depend on the database type. Field Server Hostname or data source SID Database name Database owner Database source Port Number Description Enter the name of the SAP application server where the database resides. Name of the host server or data source for the Oracle or Generic database. System ID for the server where the Oracle database resides. Enter the name of the SAP database that is associated with the SAP system. Enter the name of the user that owns the rights to the database. Enter the Data source to connect to the database. Enter the Port number used to connect to the database. 4-8

67 Chapter 4 Configuring SAP Targets Creating SAP System Targets Field Default timeout for activities (seconds) Default runtime user Connection string Description Enter the number of seconds before the activity times out. The default timeout period is 120 seconds. Choose the user account that contains the credentials to connect to the database from the drop-down list. To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user, click New > Runtime User. If the database has a custom connection string label appended to the name, check the check box and modify the string in the text field. Step 11 Click Next. Figure 4-7 Completing the SAP System Target Wizard Step 12 Verify that the information is correct and click Finish to complete the procedure. The SAP system, SAP ABAP Connection and SAP Database Connection display in the Targets pane. 4-9

68 Creating SAP System Targets Chapter 4 Configuring SAP Targets Creating an SAP System Target ABAP+Java Connection You can create a target for an SAP system that uses both an ABAP and Java connection to the SAP application servers. This section guides you through creating this type of target and configuring the SAP database that is associated with the SAP system. Note The SAP Java Adapter requires certain SAP Java libraries, which are available on the SAP Installation CD. Before you can configure an SAP Java application server target, these files must be installed on the TEO server. For instructions on installing the SAP Java libraries, refer to Installing SAP Java Library Files, page Step 1 On the Definitions workspace, right-click Targets and choose New > SAP System to launch the New SAP System wizard. Figure 4-8 Welcome to the New SAP System Wizard Step 2 Click Next. 4-10

69 Chapter 4 Configuring SAP Targets Creating SAP System Targets Figure 4-9 System Setup The System Setup panel is used to specify the SAP system name, the type of system components to be configured, and the monitoring level for the SAP system. Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. Note You can only create one target for each SAP system. However, for multi-tenant environments, you can create targets for different SAP systems with the same system ID (SID). When using the same SID for different SAP systems, you must enter the organization for each SAP system so TEO can differentiate the alerts and incidents for each system. Step 3 Specify the following information about the SAP system: Field Display name System Components ABAP application servers Java application servers SAP database Description Enter a name for the SAP system. This is the name that will display in the Targets pane. Check this check box if the SAP system uses an ABAP connection to the application server. To monitor both the ABAP and Java stack, this check box must be checked. Check this check box if the SAP system uses a Java connection to the application server. To monitor both the ABAP and Java stack, this check box must be checked. Check this check box if you want to configure the SAP database that is associated with the SAP system. 4-11

70 Creating SAP System Targets Chapter 4 Configuring SAP Targets Field Monitor as production system Organization Description This check box is checked by default. Certain processes will run only on production systems. If you want to monitor the system as a non-production system (development or sandbox), uncheck the check box. Enter the group or organization within the company that owns the target. Note If you are configuring multiple SAP systems with the same SID, you must specify the organization for each SAP system target. Step 4 Click Next. Figure 4-10 ABAP Connection Use this panel to enter the connection information for the SAP ABAP system. Note The system information entered on this panel must be unique. 4-12

71 Chapter 4 Configuring SAP Targets Creating SAP System Targets Step 5 Specify the connection information for connecting to the SAP application server: Field Connect using Application server Logon group Router string (optional) Default runtime user Description Choose the connection method from the drop-down list. The fields that display on the panel depend on the connection method selected. Choose this option to connect to the SAP system using the SAP application server connection information. Specify the information in the following fields: Server name Enter the name of the SAP application server. System number Enter the SAP system number. Choose this option to establish a connection using a logon group, which contains a group of SAP system instances. When a user logs on to a logon group, the message server directs the users to the server of this group that currently has the lightest load. Specify the information in the following fields: System ID Enter the SAP system ID (SID). Message server Enter the name of the server a user logs on to and that handles the communication between the application servers. For example, transport of update requests and lock requests. Group name Enter the name of the Logon Group to be accessed. The name entered in this field is case-sensitive. Enter the router string for accessing the SAP systems via SAPRouter. If you do not specify a router string, TEO accesses the SAP system directly. The router string must be formatted as: /H/host01/H/host02/H/ where host01 and host02 are the SAP systems that you want to access through the SAPRouter. Choose the user account that contains the credentials to connect to the target from the drop-down list. To view the properties for the selected runtime user, click the Properties tool. To create a new SAP User, click New > SAP User. See Creating an SAP User Account, page 3-2. Step 6 Click Next. 4-13

72 Creating SAP System Targets Chapter 4 Configuring SAP Targets Figure 4-11 Server Availability Step 7 The Server Availability panel is used to specify the SAP application servers that you want to monitor for availability and the ability to log in a user. Specify the following information: Field Servers available for monitoring Add Remove Select All Deselect All Description All detected servers are checked by default. Verify that the check box next to each server that you want to monitor is checked. If a server is offline during configuration, it will not be displayed in the list of available servers. To manually add the server, click Add and enter the name of the server. If you want to remove a server from the list, select the server and click Remove. If the check boxes have been unchecked and you want all servers to be monitored, click Select All. If all the check boxes are checked and you want to uncheck all of them, click Deselect All. Step 8 Click Next. If you are configuring the SAP database, the Database Connection panel displays. Otherwise, proceed to Step

73 Chapter 4 Configuring SAP Targets Creating SAP System Targets Figure 4-12 Database Connection Step 9 Step 10 Choose the Database type from the drop-down list to display the fields for the specific type of database. Specify the information for the type of database that is being configured. The fields that display depend on the database type. Field Server Hostname or data source SID Database name Database owner Database source Port Number Default timeout for activities (seconds) Description Enter the name of the SAP application server where the database resides. Name of the host server or data source for the Oracle or Generic database. System ID for the server where the Oracle database resides. Enter the name of the SAP database that is associated with the SAP system. Enter the name of the user that owns the rights to the database. Enter the Data source to connect to the database. Enter the Port number used to connect to the database. Enter the number of seconds before the activity times out. The default timeout period is 120 seconds. 4-15

74 Creating SAP System Targets Chapter 4 Configuring SAP Targets Field Default runtime user Connection string Description Choose the user account that contains the credentials to connect to the database from the drop-down list. To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user, click New > Runtime User. If the database has a custom connection string label appended to the name, check the check box and modify the string in the text field. Step 11 Click Next. Figure 4-13 Java Connection Step 12 The Java Connection panel is used to specify the Java application server that is used to connect to the SAP system. If the application server is already configured, it displays in the list box. If the server is in the list box, click Next. Otherwise, click New to open the New SAP Java Application Server Wizard and add the server. 4-16

75 Chapter 4 Configuring SAP Targets Creating SAP System Targets Figure 4-14 New SAP Java Application Server Wizard General Information Panel Step 13 Specify a name and description for the Java server in the following text fields: Field Display name Description Description Enter the name of the server that will be displayed in the Targets pane. Enter a text description for the server. Step 14 Click Next. Figure 4-15 New SAP Java Application Server Wizard JMX Connection Use the JMX Connection panel to specify the connection information to connect to the Java application server. You connect to the Java application server using a JMX connection. You can also configure to connect to the application server using a Telnet connection. 4-17

76 Creating SAP System Targets Chapter 4 Configuring SAP Targets Step 15 Specify the information for connecting to the SAP Java application server: Field Application server JMX Connection JMX port Use credentials of the following runtime user Monitor as Portal Central Instance Enable Telnet connection Description Enter the IP address or name of the SAP Java application server. Enter the JMX port number used to connect to the Java application server. Choose the default runtime user that contains the credentials to connect to the target from the drop-down list. Note The runtime user must be a J2EE Admin account. To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user, click New > Runtime User. Check the check box to run processes designed for portals on this Java server. Check the check box to run processes designed for central instances on this Java server. Check this check box if you want to specify the Telnet connection information to connect to the Java application server. Step 16 Click Next. If you enabled the Telnet Connection, the Telnet Connection panel displays. Figure 4-16 New SAP Java Application Server Wizard Telnet Connection 4-18

77 Chapter 4 Configuring SAP Targets Creating SAP System Targets Step 17 Specify the Telnet connection information for connecting to the Java application server: Field Telnet port Use credentials of the following runtime user Description Enter the Telnet port number used to connect to the Java application server. Choose the default runtime user that contains the credentials to connect to the target from the drop-down list. Note The runtime user must be a J2EE Admin account. To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user, click New > Runtime User. Step 18 Click Next. Figure 4-17 Completing the New SAP Java Application Server Wizard Step 19 Step 20 Verify that the information is correct and click Finish to add the SAP Java application server. After adding the Java application server, click Next on the Java Connection panel. 4-19

78 Creating SAP System Targets Chapter 4 Configuring SAP Targets Figure 4-18 Completing the New SAP System Wizard Step 21 Verify that the information is correct and click Finish to complete the procedure. The SAP system, SAP ABAP Connection, SAP Java Connection and SAP Database Connection display in the Targets pane. Creating an SAP System Target Java Connection You use the New SAP System Wizard to create a target for an SAP system that uses a Java connection to the application server. Note The SAP Java Adapter requires certain SAP Java libraries, which are available on the SAP Installation CD. Before you can configure an SAP Java application server target, these files must be installed on the TEO server. For instructions on installing the SAP Java libraries, see Installing SAP Java Library Files, page Step 1 On the Definitions workspace, right-click Targets in the navigation pane and click New > SAP System to open the New SAP System Wizard. 4-20

79 Chapter 4 Configuring SAP Targets Creating SAP System Targets Figure 4-19 Welcome to the New SAP System Wizard Step 2 Click Next. Figure 4-20 System Setup Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. Use the System Setup panel to specify the SAP system name, the type of system components to be configured, and the monitoring level for the SAP system. 4-21

80 Creating SAP System Targets Chapter 4 Configuring SAP Targets Step 3 Complete the following information on this panel: Field Display name System Components ABAP application servers Java application servers SAP database Monitor as production system Organization Description Enter a name for the SAP system. This is the name that will be displayed in the Targets pane. Check this check box if the SAP system uses an ABAP connection to the application servers. Note Uncheck this check box if the SAP system only uses a Java connection to the application servers. Check this check box if the SAP system uses a Java connection to the application servers. Check this check box if you want to configure the SAP database that is associated with the SAP system. Note Uncheck this check box if the SAP system only uses a Java connection to the application server. The check box is checked by default. Certain processes will run only on production systems. If you want to monitor the system as a non-production system (development or sandbox), uncheck the check box. Enter the group or organization within the company that owns the target. Step 4 Click Next. Figure 4-21 Java Connection Use the Java Connection panel to specify the Java application server. If the SAP Java application server is already configured, it displays in the list box. 4-22

81 Chapter 4 Configuring SAP Targets Creating SAP System Targets Step 5 If the server is in the list box, click Next. Otherwise, click New to open the New SAP Java Application Server Wizard and add the server. Figure 4-22 New SAP Java Application Server Wizard General Information Panel Step 6 Specify a name and description for the Java server in the following text fields: Field Display name Description Description Enter the name of the server that will be displayed in the Targets pane. Enter a text description for the server. Step 7 Click Next. Figure 4-23 New SAP Java Application Server Wizard JMX Connection 4-23

82 Creating SAP System Targets Chapter 4 Configuring SAP Targets Step 8 Use the JMX Connection panel to specify the connection information to connect to the Java application server. You connect to the Java application server using a JMX connection. You can also configure to connect to the application server using a Telnet connection. Specify the information for connecting to the SAP Java application server: Field Application server JMX Connection JMX port Use credentials of the following runtime user Monitor as Portal Central Instance Enable Telnet connection Description Enter the IP address or name of the SAP Java application server. Enter the JMX port number used to connect to the Java application server. Choose the default runtime user that contains the credentials to connect to the target from the drop-down list. Note The runtime user must be a J2EE Admin account. To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user, click New > Runtime User. Check the check box to run processes designed for portals on this Java server. Check the check box to run processes designed for central instances on this Java server. Check this check box if you want to specify the Telnet connection information to connect to the Java application server. Step 9 Click Next. If you enabled the Telnet Connection, the Telnet Connection panel displays. 4-24

83 Chapter 4 Configuring SAP Targets Creating SAP System Targets Figure 4-24 New SAP Java Application Server Wizard Telnet Connection Step 10 Specify the Telnet connection information for connecting to the Java application server: Field Telnet port Use credentials of the following runtime user Description Enter the Telnet port number used to connect to the Java application server. Choose the default runtime user that contains the credentials to connect to the target from the drop-down list. Note The runtime user must be a J2EE Admin account. To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user, click New > Runtime User. Step 11 Click Next. 4-25

84 Creating SAP System Targets Chapter 4 Configuring SAP Targets Figure 4-25 Completing the New SAP Java Application Server Wizard Step 12 Step 13 Verify that the information is correct and click Finish to add the SAP Java application server. After adding the Java application server, click Next on the Java Connection panel. Figure 4-26 Completing the New SAP System Wizard Step 14 Click Finish to complete the procedure. 4-26

85 Chapter 4 Configuring SAP Targets Creating SAP Solution Manager Targets Creating SAP Solution Manager Targets This section guides you through creating an SAP Solution Manager target. You use the New SAP Solution Manager wizard to create SAP Solution Manager targets. Note The SAP Solution Manager Adapter requires the dll files for SAP.NET 3.0 Connector for.net 4.0 on x64 version or higher. Before you can configure an SAP Solution Manager target, these files must be installed on the TEO server. See Installing SAP.NET Connector Files, page 1-5 for instructions on installing these files. Note When you create an SAP Solution Manager target, you must map the SAP systems that are monitored in Solution Manager to the SAP System targets configured in TEO. Therefore, you must create SAP System targets in TEO for the systems that are monitored in Solution Manager prior to creating an SAP Solution Manager target. See Creating SAP System Targets, page 4-3. Step 1 On the Definitions workspace, right-click Targets and choose New > SAP Solution Manager to open the New SAP Solution Manager wizard. Figure 4-27 Welcome to the New SAP Solution Manager Wizard Step 2 Click Next. 4-27

86 Creating SAP Solution Manager Targets Chapter 4 Configuring SAP Targets Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. Figure 4-28 System Setup Step 3 Specify the following information to connect to the SAP Solution Manager system: Field Display name Organization Description Enter a name for the SAP Solution Manager system. This is the name that will display in the Targets pane. Enter the group or organization within the company that owns the target. Step 4 Click Next. Figure 4-29 Connection 4-28

87 Chapter 4 Configuring SAP Targets Creating SAP Solution Manager Targets Note The system information entered on this panel must be unique. Otherwise, an error message displays informing you that the wizard detected another system already registered with the same information. Step 5 Specify the following information to connect to the SAP Solution Manager target: Field Connect using Application server Logon group Router string (optional) Description Choose the connection method from the drop-down list. The fields that display on the panel depend on the connection method selected. Choose this option to connect to the SAP Solution Manager target using the SAP application server connection information. Specify the information in the following fields: Server name Enter the name of the SAP Solution Manager application server. System number Enter the SAP Solution Manager system number. Choose this option to establish a connection using a logon group, which contains a group of SAP Solution Manager system instances. When a user logs on to a logon group, the message server directs the users to the server of this group that currently has the lightest load. Specify the information in the following fields: System ID Enter the SAP Solution Manager system ID (SID). Message server Enter the name of the server a user logs on to and that handles the communication between the application servers. For example, transport of update requests and lock requests. Group name Enter the name of the Logon Group to be accessed. The name entered in this field is case-sensitive. Enter the router string for accessing the SAP Solution Manager systems via SAPRouter. If you do not specify a router string, TEO accesses the SAP Solution Manager system directly. The router string must be formatted as: /H/host01/H/host02/H/ where host01 and host02 are the SAP Solution Manager systems that you want to access through the SAPRouter. 4-29

88 Creating SAP Solution Manager Targets Chapter 4 Configuring SAP Targets Field Default runtime user Description Choose the user account that contains the credentials to connect to the target from the drop-down list. To view the properties for the selected runtime user, click the Properties tool. To create a new SAP User, click New > SAP User. See Creating an SAP User Account, page 3-2. Step 6 Click Next. Figure 4-30 Options The Options panel is used to specify polling intervals and to map the systems that are being monitored by the Solution Manager target to the SAP System targets configured in TEO. The list box displays the systems that are mapped. Note The matching SAP System targets must already be created in TEO. 4-30

89 Chapter 4 Configuring SAP Targets Creating SAP Solution Manager Targets Step 7 Specify the following information: Field Description Poll Solution Manager alert not older than Specify the value (in minutes, hours or days) to indicate which SAP Solution Manager alerts to retrieve. Any alerts older than the specified value will be ignored. Select a system monitored by Solution Manager Select a matching system montored by TEO Add to List Refresh Choose the SAP system that is monitored by Solution Manager from the drop-down list. Choose the SAP system target that is configured in TEO from the drop-down list. This target must already be defined in TEO. Click this button to add the mapped configuration to the list of systems to be monitored. Click this button to refresh the list of systems to be monitored. Step 8 Click Next. Figure 4-31 Completing the SAP Solution Manager Wizard Step 9 Verify that the information is correct and click Finish to complete the procedure. The SAP Solution Manager target displays in the Targets pane. 4-31

90 Creating and Configuring HANA Targets Chapter 4 Configuring SAP Targets Creating and Configuring HANA Targets The Automation for SAP HANA automation pack includes a HANA System service target template that can be used to create a service target for the HANA environment. The service target will hold the reference to all of the connections to HANA that are needed for automation. Before you can reference the connections in the HANA System service target, you must create the targets that will be referenced (Web target, Linx/Unix targets, Database target, SAP System target). After you create these targets, you create a unique HANA System service target using the template and reference them. This section guides you through creating the targets in the HANA environment, creating a HANA System system target using the template, and then referencing the target using the Extended Target Properties feature. Creating SAP HANA Database Target You must create a database target for the SAP HANA using the Generic Data Source (OLEDB) target type. Use the New Generic Data Source (OLEDB) Properties dialog box to create the database target. Step 1 Step 2 On the Definitions workspace, right-click Targets and choose New > Generic Data Source (OLEDB) to open the New Generic Data Source (OLEDB) Properties dialog box. On the General tab, specify the following information: Field Display name Type Owner Status Status information Organization Description Description Name for the target. This is the name that will display in the Targets pane. Display only. Type of target. User name of the owner of the target. This is typically the person who created the target. Display only. Status of the target. Display only. Detailed information regarding the target status. Name of the group or organization within the company that owns the target. Optional field to enter a description for the target. Step 3 Click the Connection tab. Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. 4-32

91 Chapter 4 Configuring SAP Targets Creating and Configuring HANA Targets Figure 4-32 New Generic Data Source (OLEDB) Properties Connection Tab Step 4 On the Connection tab, specify the following connection information for the target: Field Hostname or Datasource Database Owner Default time out for activities (seconds) Runtime User Description Name of the server or data source where the HANA database resides. Enter the information in the following format: <server name>:port Note Port number will be 3XX15, where XX is the HANA System Number. Principal owner of the database. Indicates the length of time to wait before a command is complete Choose the runtime user account that is used to connect to the data source from the drop-down list. Note To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user account, click New and then choose Runtime User. See Creating a Runtime User Account, page 3-4. Note The HANA User account created for TEO should have SYSTEM level authorizations. 4-33

92 Creating and Configuring HANA Targets Chapter 4 Configuring SAP Targets Field Connection string Description Check the check box and enter the DSN connection string to the data source. For example: DSN=DH1; Step 5 Click the Permission tab. Figure 4-33 New Generic Data Source (OLEDB) Properties Permission Tab Step 6 Step 7 Click the Execute SQL command radio button. Click OK to close the dialog box and complete the procedure. 4-34

93 Chapter 4 Configuring SAP Targets Creating and Configuring HANA Targets Creating Web Targets If you want to configure TEO to monitor the Web targets in your HANA environment, you must create a Web target using the using the New Web Target Properties dialog box. Step 1 Step 2 On the Definitions workspace, right-click Targets and choose New > Web Target to open the New Web Target Properties dialog box. On the General tab, enter the information in the following text fields: Field Display name Type Owner Status Status information Organization Description Description Name for the target. This is the name that will display in the Targets pane. Display only. Type of target. User name of the owner of the target. This is typically the person who created the target. Display only. Status of the target. Display only. Detailed information regarding the target status. Name of the group or organization within the company that owns the target. Optional field to enter a description for the target. Step 3 Click the Connection tab. Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. 4-35

94 Creating and Configuring HANA Targets Chapter 4 Configuring SAP Targets Figure 4-34 New Web Target Properties Connection Tab Step 4 On the Connection tab, specify the following connection information for the target: Field Base Url Description Enter the appropriate target URL to use as a base for the execution. For example: Runtime User where XX=HANA System Number Click one of the following radio buttons to indicate which runtime user account to use to connect to the target: No runtime user Click this radio button to indicate that no runtime user is required to execute a process or activity against the target. Default runtime user Click this radio button and then choose the default runtime user account that contains the credentials to connect to the target. Note To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user account, click New and then choose Runtime User. See Creating a Runtime User Account, page 3-4. Note The runtime user for this target should be the HANA OS SIDADM user. 4-36

95 Chapter 4 Configuring SAP Targets Creating and Configuring HANA Targets Field Ignore certificate errors Description Check or uncheck the check box to indicate whether the target should ignore any certificate errors on the specified web site. If the check box is checked, all errors will be ignored. Step 5 Click OK to close the dialog box and complete the procedure. Creating Unix/Linux System Target If you want to monitor the HANA Linux systems in your environment, you must create the Unix/Linux System targets. The Automation for SAP HANA content requires that two different Unix/Linux System targets be created with different runtime user accounts: HANA.SAP Administration Unix Target This target is used for SAP command line applications and uses the HANA OS SIDADM runtime user account. HANA.Linux Administration Unix Target This target is used for LINUX command line administration applications and uses a Linux user with OS administration permissions as the runtime user account. Note Review the SAP HANA Requirements, page 1-6 prior to creating the system targets Note If you want to monitor all Linux hosts, you must configure Auto-SSH login proxy. See Configuring Auto-SSH Login Proxy, page Note For additional information on creating and managing Unix/Linux System targets, see the Cisco TEO Adapter Guide for Terminal Adapter. Step 1 Step 2 On the Definitions workspace, right-click Targets and choose New > Unix/Linux System to open the New Unix/Linux System Properties dialog box. On the General tab, specify the following information: Field Display name Type Owner Status Status information Description Enter a name for the Database target. This is the name that will display in the Targets pane. Display only. Type of target. User name of the owner of the target. This is typically the person who created the target. Display only. Status of the target. Display only. Detailed information regarding the target status. 4-37

96 Creating and Configuring HANA Targets Chapter 4 Configuring SAP Targets Field Organization Description Enabled Description Name of the group or organization within the company that owns the target. Optional field to enter a description for the target. Check or uncheck the check box to enable or disable the target. The check box is checked by default. Step 3 Click the Connection tab. Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. Step 4 On the Connection tab, specify the connection information to connect to the Unix/Linux server: Field Host name Port Prompt prefix Description Host name or IP address of server. Port number used to access the server. Enter the command prompt prefix that will be used by the device type configurations and expects when issuing commands and connecting to the device. Adding a regex character, such as $, >, and #, at the end of a prompt in the Prompt Prefix field invalidates the command prompt prefix. Regular expressions should be placed in the appropriate Terminal Interaction Pattern fields. Example: Unix system prompt prefix is defined by the user default login script. it usually contains username, node name or current directory name. If the user does not define anything, the prompt prefix is empty. If you connect to the terminal, and the prompt is jsmith@tbd-sh03-it ~$, enter the regular expression that will match the entire prefix (before #) using any of the following expressions:.*tbd-sh03-it.* \[\w+@tbd-sh03-it.*\] 4-38

97 Chapter 4 Configuring SAP Targets Creating and Configuring HANA Targets Field Default runtime user Enable code injection prevention Maximum allowed concurrent sessions Description Choose the default runtime user account that contains the credentials to connect to the target from the drop-down list. To view the properties for the selected runtime user, click the Properties tool. To create a new runtime user account, click New > [Runtime User Type] to create a new Runtime User account. See Creating a Runtime User Account, page 3-4. Note The runtime user for this target should be the HANA OS SIDADM user. Check this check box to enable the protection which prevents code that is injected to exploit the security vulnerability. Enter the maximum allowed open sessions to run concurrently (default value is 3). If the user tries to open new session via Open Session activity, it will wait in a queue until there is a session available to open. Step 5 Click the Authentication tab to and specify the following information to indicate whether the target should allow authentication based on the host system: Field Use host-based authentication Use the default host keys Private key Description Check this check box to indicate that host-based authentication will be used with this target. If this check box is unchecked, then host-based authentication will not be used. This check box becomes enabled after the Use host-based authentication check box is checked. Check this check box to indicate the host keys defined on the Terminal Adapter property page will be used for this target. If this check box is unchecked, then the user will need to load the appropriate private key to be used to validate this target. This box becomes enabled only if the Use the default host keys check box is unchecked. To the right of the display-only field, click the Browse tool to launch the Load Private Key dialog box and select a private key. 4-39

98 Creating and Configuring HANA Targets Chapter 4 Configuring SAP Targets Step 6 Click the Advanced tab and specify the interaction patterns for the target. Field Use patterns common for the following device Customize patterns for this target Description Click the radio button one of the pre-defined device targets from the drop-down list. Cisco IOS Device Select this option to use the default pattern values used by the device during the completion of a session command. Unix/Linux System Select this option to use the default pattern values indicated for a Unix or Linux system during the completion of a session command. To view the properties for the selected device, click the Properties tool. To create a new device, click New > Expect Template to create a new expect template. Select this radio button to enable the display-only sections in order to customize the default values for the selected device type. Step 7 Click OK to close the dialog box and complete the procedure. Configuring Auto-SSH Login Proxy If you want to monitor all Linux hosts in your environment, you must configure an Auto-SSH login proxy. Note If you choose not to set up auto login proxy, only the TEO Linux system target will be monitored. Step 1 Step 2 Step 3 Step 4 Create a Linux user with permissions for the following linux commands: top iostat mpstat vmstat df Perform SSH login to the HANA Unix/Linux system target configured in TEO using the Linux user account created in Step 1. Execute the command ssh-keygen -t rsa. a. Enter passphrase as empty. b. Note the file location of the key. Execute the command ssh-copy-id -i <file path to key> < remote host> and replace the <remote host> with the hostname for all HANA hosts in the instance:. 4-40

99 Chapter 4 Configuring SAP Targets Creating and Configuring HANA Targets Step 5 Step 6 Test the remote connection by executing the command ssh <remote host> and confirm that you are no longer prompted for a password. Add the new Linux user name to the TEO extended target property HANA Linux Configuration HANA Linux Shell User. Creating SAP System Target If you want to use the Landscape Transformation (LT) processes, you must create the SAP System (ABAP) targets for the LT replication servers that replicate data into HANA. The SAP System Wizard is used to create these targets. See Creating SAP System Targets, page 4-3 for instructions on creating the SAP System (ABAP) targets. Creating HANA System Service Target Use the HANA System template to create the HANA System service target specific to your environment. This system target will reference the HANA web target, database target, Unix target, and SAP System target. If you want to rename the tempate target, you must create a copy of the HANA System template target and then rename it prior to configuring the extended properties. Note If you do not want to rename the HANA System template target, proceed to Configuring References to Targets, page 4-43 Creating Copy and Renaming HANA System Template Target Step 1 Step 2 On the Definitions workspace, click Targets. Navigate to the HANA ABAP System template and select it. 4-41

100 Creating and Configuring HANA Targets Chapter 4 Configuring SAP Targets Figure 4-35 Targets View Copying HANA System Target Template Step 3 Step 4 Step 5 Right-click HANA System template and choose Copy. In an open area of the Targets pane, right-click and choose Paste. Right-click Copy of HANA System Target Template and choose Properties. Figure 4-36 HANA System Target Template Properties Step 6 Step 7 In the Display name text field, enter a name for the HANA System target. Click OK to save the target and close the dialog box. 4-42

101 Chapter 4 Configuring SAP Targets Creating and Configuring HANA Targets Configuring References to Targets You must now configure the HANA System target to reference the Web target, Unix target and Database target. Use the Extended Target Properties feature to reference the targets. Creating Reference to HANA Database Target Use this procedure to reference the HANA Database target that was created in Creating SAP HANA Database Target section on page Step 1 Step 2 Step 3 On the Definitions workspace, click Targets. Right-click the HANA System target and choose Properties. On the HANA System Service Target Properties dialog box, click the Extended Properties tab. Figure 4-37 HANA System Target Properties Extended Properties Tab Step 4 Select the HANA Database Target property and click Edit. Step 5 On the Target Property Value dialog box, click the Browse tool next to the Value field. 4-43

102 Creating and Configuring HANA Targets Chapter 4 Configuring SAP Targets Figure 4-38 Target Property Value Select Target Step 6 Step 7 Step 8 On the Select Target dialog box, select the HANA Database target and click OK to add the database to the Value field on the Target Property Value dialog box. Click OK to close the Target Property Value dialog box and save the information. If you have completed configuring the extended properties, click OK to close the HANA System Target Properties dialog box. Creating Reference to HANA Web Target Use this procedure to reference the HANA Database target that was created in Creating Web Targets section on page Step 1 Step 2 Step 3 Step 4 On the Definitions workspace, click Targets. Right-click the HANA System target and choose Properties. On the HANA System Service Target Properties dialog box, click the Extended Properties tab. Select the HANA Web Target property and click Edit. Step 5 On the Target Property Value dialog box, click the Browse tool next to the Value field. Step 6 Step 7 On the Select Target dialog box, select the HANA Web target and click OK to add the Web target to the Value field on the Target Property Value dialog box. Click OK to close the Target Property Value dialog box and save the information. 4-44

103 Chapter 4 Configuring SAP Targets Creating and Configuring HANA Targets Step 8 Click OK to close the HANA System Target Properties dialog box. Creating Reference to HANA Unix Target Use this procedure to reference the HANA Unix target that was created in Creating Unix/Linux System Target section on page Step 1 Step 2 Step 3 Step 4 On the Definitions workspace, click Targets. Right-click the HANA System target and choose Properties. On the HANA System Service Target Properties dialog box, click the Extended Properties tab. Select the HANA Unix Target property and click Edit. Step 5 On the Target Property Value dialog box, click the Browse tool next to the Value field. Step 6 Step 7 Step 8 On the Select Target dialog box, select the HANA Unix target and click OK to add the Unix system to the Value field on the Target Property Value dialog box. Click OK to close the Target Property Value dialog box and save the information. Click OK to close the HANA System Target Properties dialog box. Creating Reference to HANA SAP (ABAP) System Target Use this procedure to reference the HANA SAP (ABAP) System target that was created in Creating SAP System Target section on page Step 1 Step 2 Step 3 Step 4 On the Definitions workspace, click Targets. Right-click the HANA System target and choose Properties. On the HANA System Service Target Properties dialog box, click the Extended Properties tab. Select the HANA ABAP Target property and click Edit. Step 5 On the Target Property Value dialog box, click the Browse tool next to the Value field. Step 6 Step 7 Step 8 On the Select Target dialog box, select the HANA SAP ABAP System target and click OK to add the system to the Value field on the Target Property Value dialog box. Click OK to close the Target Property Value dialog box and save the information. Click OK to close the HANA System Target Properties dialog box. 4-45

104 Managing SAP Targets Chapter 4 Configuring SAP Targets Managing SAP Targets Use the Definitions Targets view to manage the SAP targets, which includes modifying connection information to the SAP systems (for example, users and application servers), enabling and disabling the SAP targets, and deleting targets. You use the SAP Target Properties dialog box to modify the SAP targets, view the objects in the product that use the SAP target, view a history of changes made to the target, and how to delete the SAP target. For information on viewing and modifying the SAP target properties, refer to the appropriate adapter guide: SAP Target Type SAP System SAP ABAP Connection SAP Database SAP Java Application Server SAP BI Warehouse SAP Solution Manager Adapter Guide Cisco TEO Adapter Guide for SAP ABAP Cisco TEO Adapter Guide for SAP ABAP Cisco TEO Adapter Guide for SAP ABAP Cisco TEO Adapter Guide for SAP Java Cisco TEO Adapter Guide for OLAP Database Cisco TEO Adapter Guide for SAP Solution Manager Enabling an SAP Target A target is enabled by default after it is created. If a target is manually disabled, it must be enabled before it is available for execution. Step 1 Step 2 On the Definitions Targets view, use one of the following methods to enable the target: In the Targets pane, right-click the [SAP target] and choose Enable. In the Targets pane, select the [SAP target] and then click the Click here link in the Details pane. Verify that the status in the Enabled column in the Targets pane is True. If necessary, click the Refresh tool to update the view. Disabling an SAP Target Disabling a target prevents it from being available for execution. However, a disabled target is not removed from the list of targets in the Targets pane. Step 1 Step 2 On the Definitions Targets view, use one of the following methods to disable the target: In the Targets pane, right-click the [SAP target] and choose Disable. In the Targets pane, select the [SAP target] and then click the Click here link in the Details pane. Verify that the status in the Enabled column in the Targets pane is False. If necessary, click the Refresh tool to update the view. 4-46

105 Chapter 4 Configuring SAP Targets Managing SAP Targets Deleting an SAP Target Before deleting a target, open the SAP Target Properties dialog box and click the Used By tab to view where objects are being used by the target. This ensures that deleting the target does not affect any processes or activities. Step 1 In the Definitions Targets view, right-click the [SAP target] and choose Delete. Figure 4-39 Confirm Delete Step 2 Click Yes to confirm the deletion. The target will be removed from the product. 4-47

106 Managing SAP Targets Chapter 4 Configuring SAP Targets 4-48

107 CHAPTER 5 Managing Assignments and Notifications Task rules are used to manage task assignments and notifications for tasks, such as incidents and alerts, that are generated from processes. When you import the Core Automation for SAP automation pack, you are prompted to specify the default user or group who should be assigned SAP incidents. By default, this person will receive all assignments unless task rules are created to specify alternate users or groups for specific tasks. This chapter guides your through configuring task rules that ship with the automation packs and provides instructions for creating and managing task rules. It includes the following sections: Accessing Task Rules View, page 5-2 Configuring Task Rules, page 5-3 Creating a New Task Rule, page 5-5 Enabling Notification Based on Assignment Processes, page 5-14 Note If you do not want to create task rules for notifications, you can use the default notification based on assignment processes that ship with the Core automation pack. These processes are disabled by default and must be enabled if you want notifications to be sent (see Enabling Notification Based on Assignment Processes, page 5-14). 5-1

108 Accessing Task Rules View Chapter 5 Managing Assignments and Notifications Accessing Task Rules View The task rule that ships with the Core Automation for SAP automation pack can be accessed from the Definitions Task Rules view. Step 1 Step 2 On the Console, select the Definitions workspace and click Task Rules in the navigation pane. By default, all the rules display in the Task Rules pane. Click the Filter by link and choose Automation Pack > [Automation Pack Name] to filter for only the task rules that ship with the specific automation pack. Figure 5-1 Definitions Task Rules View The following information about the task rules displays by default: Column Display Name Enabled Type Owner Last Modified Time Last Modified By Id Description Type Description Created Time Description The name assigned to the task rule. Indicates whether the task rule is enabled (True) or disabled (False). A disabled task rule is unavailable for execution. Type of task. User name of the person or group who assigned the task rule. The date and time the task rule was last modified. The object or user name that last modified the task rule. Unique ID of the task rule. Brief description of the task rule. Brief overview of the task rule type. Time at which the task rule was created. 5-2

109 Chapter 5 Managing Assignments and Notifications Configuring Task Rules Column Created By Automation Pack Description Name of the user who created the task. Name of the automation pack associated with the task rule. Configuring Task Rules Use the Task Rules view to configure the task rule that ships with the Core Automation for SAP automation pack. SAP Default Assignment The Core Automation for SAP automation pack ships with the Default SAP Assignment task rule, which is used to specify the default user or group who will be assigned all SAP-related incidents unless otherwise specified in task rules. This task rule can be configured during the import process on the Default Incidents Assignee Setup panel (Figure 2-3 on page 2-4) or from the Task Rules view in the Console. Step 1 Step 2 Step 3 Step 4 Step 5 In the Definitions workspace, click Task Rules in the navigation pane to display the task rules in the results pane. Click the Filter by link and choose Automation Pack, and then choose Core Automation for SAP from the drop-down list to display the task rules that ship with the automation pack. Right-click the SAP Default Assignment task rule and choose Properties to open the SAP Default Assignment Properties dialog box. Click the Assign tab to specify the user or group that should receive assignments for incidents and alerts generated by the processes. On the Assign tab, click Add to open the Select Assignee to Add dialog box. 5-3

110 Configuring Task Rules Chapter 5 Managing Assignments and Notifications Figure 5-2 Adding Assignees to Task Rule Step 6 Step 7 Step 8 On the Select Assignee to Add dialog box, specify the assignees using one of the following methods: Click the Reference tool to select the appropriate variable reference containing the assignee or list of assignees from the Insert Variable Reference dialog box. Click the Browse tool to launch the Select User or Group dialog box to add user to the list of assignees. Click OK to add the assignee to the task rule. When you have completed adding assignees to the task rule, click OK to close the dialog box. 5-4

111 Chapter 5 Managing Assignments and Notifications Creating a New Task Rule Creating a New Task Rule Use the Task Rules view to create a new task rule. The procedure is the same for all types of task rules with the exception of the task-specific tab (Assign, Notify, Update) for the type of task rule you are creating. Note Only users with administrative rights can create task rules in TEO. You can create the following types of task rules: Task Rules Assign Task Rule Notify Task Rule Update Task Rule Description Assigns users to a task. Notifies users that a task has been created. Specifies the properties to be updated in a task.. Step 1 In the Definitions workspace, right-click Task Rules and choose New > [Task Rule Type] to open the New Rule Properties dialog box. Figure 5-3 New Rule Properties Dialog Box General Tab Step 2 On the General tab, enter the following information: Field Display Name Type Trigger Description Name of the task. Display only. Shows the type of object. Display only. Type of trigger associated with the task rule. 5-5

112 Creating a New Task Rule Chapter 5 Managing Assignments and Notifications Field Owner Description Enabled Description User name of the owner of the task rule. This is typically the person who created the task rule. Click the Browse tool to launch the Select User or Group dialog box to change the owner. A brief description of the task rule. The check box is checked by default to indicate that the task rule is available for execution. Uncheck the check box to disable the task rule. If the check box is unchecked, the task rule is disabled and will be unavailable for execution. Step 3 Click the Task Types tab to specify the types of tasks to be executed by the rule. Figure 5-4 New Rule Properties Dialog Box Task Types Tab Step 4 Check the check box for the type of task that will execute the rule. Task Type Alert Approval Request Guided Operation Incident Input Request Review Description Alerts reflect potential problems that a user may want to investigate and possibly diagnose the problem. Specifies the message and choices for the assignee who is approving the task. Details the steps a user takes to complete an assigned task. Task requires an operator to take action in order to resolve an issue. Task requires input from an individual or group. Task assigns a document for review. 5-6

113 Chapter 5 Managing Assignments and Notifications Creating a New Task Rule Step 5 Click the Conditions tab to specify the conditions of when the task rule action is to be taken based on an evaluation of the defined conditions. Note The Required Value icon displayed on a tab or page indicates that the field is required and is either missing a value or contains an invalid value. Figure 5-5 New Rule Properties Dialog Box Conditions Tab Step 6 On the Conditions tab, define the conditions that must be met for the rule to execute. Defining a Basic Condition: a. On the Basic page, click New to add a new property for the condition that must be met. Figure 5-6 New Rule Properties Dialog Box Basic Condition 5-7

114 Creating a New Task Rule Chapter 5 Managing Assignments and Notifications b. In the Property text field, click the Reference tool to choose a defined variable or reference an object on the Insert Variable Reference dialog box. c. Choose the condition expression from the drop-down list. d. Enter the condition description in the text box or click the Reference tool to choose a defined variable or reference an object on the Insert Variable Reference dialog box. e. Click New to define additional properties, if necessary. Defining an Advanced Condition: a. Click the Advanced tab to define a specific type of condition (Compound, Prior Process Instance, Time, or Variable). Figure 5-7 New Rule Properties Dialog Box Advanced Condition b. Click the link to modify the option for the condition equation. Option AND condition (all conditions must be met) OR condition (one condition must be met) Description Click this option if an action is to be taken only when all conditions in the list are true. Click this option if an action is to be taken when one condition in the list is true. c. Click New and choose the type of condition from the drop-down list. d. Specify the relevant information for the type of condition selected. Note Click the Reference tool to choose a defined variable or reference an object on the Insert Variable Reference dialog box. e. Click New to define additional properties, if necessary. Step 7 Click the task rule specific tab (Assign, Notify, or Update) and specify the relevant information for the specific type of rule. 5-8

115 Chapter 5 Managing Assignments and Notifications Creating a New Task Rule Assign Task Rule If you are creating an Assign Task Rule, the Assign tab displays on the New Rule Properties dialog box. Figure 5-8 New Rule Properties Dialog Box Assign Tab On the Assign tab, specify the assignees for task rule. Field Add Edit Remove Remove All Description Click this button to launch the Select Assignee to Add dialog box to specify the assignees. On the Select Assignee to Add dialog box, use one of the following methods to specify the assignee: Click the Reference tool to select the appropriate variable reference containing the assignee or list of assignees from the Insert Variable Reference dialog box. Click the Browse tool to launch the Select User or Group dialog box and add user to the list of assignees. Select the appropriate assignee in the list and click this button to view or modify the assignee of the task rule. Select the appropriate assignee and click this button to remove the assignee from the list. Click this button to remove all specified assignees from the list. 5-9

116 Creating a New Task Rule Chapter 5 Managing Assignments and Notifications Notify Task Rule If you are creating a Notify Task Rule, the Notify tab displays on the New Rule Properties dialog box. Figure 5-9 New Rule Properties Dialog Box Notify Tab On the Notify tab, specify the recipients of the notification that the task rule has executed. You can add individual recipients or include a notification recipient list. Field Add notification recipients Description Displays list of users to be notified by the task rule. Add Click this button to launch the Select Notification Recipient to Add dialog box to specify the recipients. On the dialog box, enter the address for the recipient or click the Reference tool to select the appropriate variable reference containing the recipient or list of recipients from the Insert Variable Reference dialog box and then click OK. Edit Select the appropriate recipient in the list and click this button to view or modify the recipient of the task rule. Remove Select the appropriate recipient in the list and click this button to remove the recipient from the list. Remove All Click this button to remove all specified recipients from the list. Add notification recipient list Click the Reference tool to select the appropriate variable reference containing list of recipients from the Insert Variable Reference dialog box. 5-10

117 Chapter 5 Managing Assignments and Notifications Creating a New Task Rule Update Task Rule If you are creating an Update Task Rule, the Update tab displays on the New Rule Properties dialog box. Figure 5-10 New Rule Properties Dialog Box Update Tab On the Update tab, specify the properties to be updated after the task rule has executed. Field Add Remove Property List action Value Description Click this button to add a new property to the Properties to update area. Click this button to remove the last property added to the Properties to update area. From the Property drop-down list, choose the item to update within the task. The properties displayed depend on the selected item. Choose the appropriate item from the drop-down list to determine which action to take with the selected property: Add Item Adds item to task. Remove item Removes item from task. Clear Removes property value from task. Enter new value for the property. Step 8 Click OK to save the task rule definition and close the dialog box. 5-11

118 Creating a New Task Rule Chapter 5 Managing Assignments and Notifications Managing Task Rule Definitions This section provides instructions on modifying task rules in the Definitions Task Rule view. Only users with administrative rights can modify task rules in TEO. Note For additional information on managing task rules, see the Tidal Enterprise Orchestrator Reference Guide. Enabling a Task Rule A task rule is enabled by default. If a task rule is manually disabled, the task rule must be enabled before it is available for execution. On the Definitions Task Rules view, select the task rule and then use one of the following methods to enable it: On the Results pane, right-click and choose Enable. On the Details pane, select Click here to enable. The Enabled column on the Results pane changes to True. If necessary, click the Refresh update the view. tool to Disabling a Task Rule Disabling a task rule prevents the item from being available for execution. The disabled task rule is not removed from the list of task rules on the Definitions Task Rules Results pane. On the Definitions Task Rule view, select the task rule and then use one of the following methods to disable it: On the Results pane, right-click and choose Disable. -or- -or- On the Details pane, select Click here to disable. The Enabled column on the results pane changes to False. If necessary, click the Refresh update the view. tool to 5-12

119 Chapter 5 Managing Assignments and Notifications Creating a New Task Rule Creating a Copy of a Task Rule The copy option is used when the user wants to leverage an existing task rule to define a new task rule using existing properties. Step 1 Step 2 Step 3 Step 4 On the Definitions Task Rules view, select the appropriate task rule, right-click and choose Copy. On the Results pane, right-click and choose Paste. A copy of the defined task rule is pasted onto the Results pane. To rename the copied task rule or other properties, right-click and choose Properties. Modify the task rule name, as appropriate, and click OK to close the dialog box. Sorting Task Rules The task rules are executed according to the order they are listed on the Definitions Task Rules view. You should sort the task rules based on the order in which you want them to execute. Note All task rules will execute even if there is more than one task rule assigned for the same condition. For example, if you have two assignment rules for the same incident, both rules will be executed in the order listed in the Task Rules view. On the Definitions Task Rules view, select the task rule and use one of the following methods to move it to the desired position in the list: Drag and drop the task rule into the appropriate position in the list. On the Actions toolbar, click Move Up or Move Down. Click the Actions menu and choose Move Up or Move Down. Right-click and choose Move Up or Move Down. The list of task rules are sorted according to the selected action. Deleting a Task Rule Use the Definitions Task Rules view to delete task rules that are no longer used. Step 1 Step 2 On the Definitions Task Rules view, select the task rule, right-click and choose Delete. On the Confirm Delete dialog box, click Yes to confirm the deletion. 5-13

120 Enabling Notification Based on Assignment Processes Chapter 5 Managing Assignments and Notifications Enabling Notification Based on Assignment Processes If you want to have s sent to whoever is assigned to a task but do not want to create notification task rules, you can enable the processes that ship with the Core automation pack that send s based on assignment. When these processes are enabled, the user or user group who was assigned to tasks will receive the notification. Step 1 Step 2 Step 3 In the Definitions workspace, click Processes. Click the Filter by link and choose Automation Pack > Core to filter for the processes that ship with the Core automation pack. Right-click the appropriate Notification Based on Assignment process and choose Enable. The following processes are for notification based on assignment: Process Name Default Alert Notification Based on Assignment Default Approval Request Notification Based on Assignment Default Change Request Notification Based on Assignment Default Guided Operation Request Notification Based on Assignment Default Incident Notification Based on Assignment Default Input Request Notification Based on Assignment Default Review Request Notification Based on Assignment Description Sends when an alert gets assigned. Sends when an approval request gets assigned. Sends when an change requests gets assigned. Sends when a guide operation request gets assigned. Sends when an incident gets assigned. Sends when an input request gets assigned. Send when a review request gets assigned. 5-14

121 CHAPTER 6 Managing Extended Target Properties The Extended Target Properties feature allows users to define a specific target property value and provides flexibility for others to set or access the values to be used to customize process behavior. The target properties can be used to reference other targets and to override certain variable properties assigned to targets when certain conditions occur. This chapter provides information on configuring extended target properties. It contains the following sections: Accessing Extended Target Properties, page 6-1 Configuring Extended Target Properties, page 6-3 Accessing Extended Target Properties The extended target properties that ship with the automation packs can be accessed from the Definitions Extended Target Properties view. Step 1 On the Console, select the Definitions workspace and click Extended Target Properties in the navigation pane. By default, all the properties display in the Extended Target Properties pane. Figure 6-1 Definitions Extended Target Properties View 6-1

122 Accessing Extended Target Properties Chapter 6 Managing Extended Target Properties The following information about the extended target properties displays by default: Column Display Name Description Value Data Type Automation Pack Customizable Target Types Last Modified Time Last Modified By Id Owner Created Time Created By Description Name of the target property. Text description of the target property. Value assigned to the target property. Type of value being used for the target property (Boolean, Encrypted String, Identity, Numeric, String, Table). Name of the automation pack that provides the target property. Indicates the customization setting for the target property in the automation pack. Indicates the targets associated with the target property. Date and time the variable was last modified. Name of the user who last modified the target property. Unique ID of the target property. User name of the owner of the target property. This is typically the person who created the target property. Date and time the target property was created. User name of the person who created the target property. Step 2 Click the Filter by link and choose Automation Pack > [Automation Pack Name] to filter for only the extended target properties that ship with the specific automation pack. 6-2

123 Chapter 6 Managing Extended Target Properties Configuring Extended Target Properties Configuring Extended Target Properties You use the Extended Target Properties Properties dialog box to view or modify the target property. You access the properties from the Definitions Extended Target Properties view. Step 1 On the Extended Target Properties pane, right-click [Extended Target Property] and choose Properties. Figure 6-2 Extended Target Properties General Tab Step 2 Step 3 On the General tab, review the information in the Description field to determine the values that need to be specified for the target property. Click the Value tab to view or modify the default value for all targets. Note The tab in the second position will depend on the variable type. See the Tidal Enterprise Orchestrator Reference Guide for instructions on configuring the different types of target properties. 6-3

124 Configuring Extended Target Properties Chapter 6 Managing Extended Target Properties Figure 6-3 Extended Target Properties Value Tab Step 4 Step 5 Click in the cell to specify the default value or change the default value for all targets. Click the Target Values tab to specify the targets that should be used to override the default value. Figure 6-4 Extended Target Properties Target Values Tab Step 6 Click New to add a new target override. 6-4

125 Chapter 6 Managing Extended Target Properties Configuring Extended Target Properties Figure 6-5 Target Property Value Dialog Box Step 7 On the Target Property Value dialog box, click one of the following radion buttons to indicate whether the value is for a single target or multiple targets: Set the value for a single target Click the radio button to specify a single target and then click the Browse icon to select the target. Set the same value for multiple targets Click the radio button to specify multiple targets and then click Add to choose the target and add it to the list. Figure 6-6 Select Target(s) Value Dialog Box 6-5

126 Configuring Extended Target Properties Chapter 6 Managing Extended Target Properties Step 8 Step 9 Select the SAP system(s) and click OK. On the Target Property Value dialog box, enter the information in the Value area to be used for the specified target and then click OK. The target override displays on the Target Values tab. Figure 6-7 Extended Target Properties Target Values Tab with Override Step 10 Click OK to close the dialog box and save your changes. Note The Target Types tab is only available if you have explicit rights to the object. See the Tidal Enterprise Orchestrator Reference Guide for information on using this property page. 6-6

127 CHAPTER 7 Configuring SAP Global Variables The SAP processes use global variables for information that is used on a regular basis to avoid having to specify the same information in several processes or activities. Some of the variables that ship with the automation packs are configured with default values but can be modified to meet the requirements for your specific environment. Other variables do not have default values defined and must be defined by the user before it can be used in the processes. This chapter provides information on configuring global variables. It includes the following sections: Accessing Global Variables, page 7-1 Configuring Global Variables, page 7-3 Accessing Global Variables Use the Definitions Global Variables view to access the global variables that ship with the automation packs. Step 1 Step 2 On the Console, select the Definitions workspace and click Global Variables in the navigation pane. By default, all the variables display in the Global Variables pane. Click the Filter by link and choose Automation Pack > [Automation Pack Name] to filter for only the global variables that ship with a specific automation pack. 7-1

128 Accessing Global Variables Chapter 7 Configuring SAP Global Variables Figure 7-1 Global Variables View The following information about the variables displays by default: Column Display Name Description Value Data Type Automation Pack Last Modified Time Last Modified By Description Name of the global variable. Brief overview of the global variable. Value of the variable. Type of value being used for the variable (Boolean, Encrypted String, Identity, Numeric, String, Table). Name of the automation pack that provides the object. Time the global variable was last modified. Name of the user who last modified the global variable. 7-2

129 Chapter 7 Configuring SAP Global Variables Configuring Global Variables Configuring Global Variables If the automation pack ships with global variables, you must configure them before they can be used in the processes. This section guides you through configuring a global variable. Step 1 Step 2 Step 3 In the Definitions view, click Global Variables in the navigation pane to display the variables in the Global Variables pane. Click the Filter by link and choose Automation Pack > [Automation Pack Name] to filter for only the global variables that ship with a specific automation pack. In the Global Variables pane, right-click the global variable and choose Properties. Figure 7-2 Global Variable Properties General Tab Step 4 In the Value text field, enter the number of seconds to suppress duplicate alerts and click OK. 7-3

130 Configuring Global Variables Chapter 7 Configuring SAP Global Variables 7-4

131 CHAPTER 8 Understanding SAP Processes This chapter provides information on using the SAP processes. It includes information on accessing the SAP processes and filtering for specific processes, managing the SAP processes, starting a process, and viewing a running process, its results, and the automation summary generated by the process. It includes the following sections: Accessing the SAP Processes, page 8-1 Managing SAP Processes, page 8-3 Running Processes, page 8-8 Viewing Process Results, page 8-11 Viewing Automation Summary, page 8-16 Accessing the SAP Processes The processes that ship with the product can be accessed from the Definitions Processes view. Step 1 On the Console, select the Definitions workspace and click Processes in the navigation pane. By default, all the processes display in the Processes pane. Figure 8-1 Processes View 8-1

132 Accessing the SAP Processes Chapter 8 Understanding SAP Processes Step 2 Step 3 If you have multiple automation packs installed, you can filter the processes to display the processes specific to the automation pack. In the upper portion of the Processes pane, click the Filter by link and choose Automation Pack. In the drop-down list, choose [Automation Pack Name]. Figure 8-2 Filtering Processes by Automation Pack The processes display in the Processes pane. Filtering Processes by Category You can also filter the processes by category to find a specific process. Step 1 Step 2 In the upper portion of the Processes pane, click the Filter by link and choose Category. In the drop-down list, choose [Catgory]. Figure 8-3 Filtering Processes by Category Step 3 Scroll to the process. 8-2

133 Chapter 8 Understanding SAP Processes Managing SAP Processes Managing SAP Processes This section provides information on managing the SAP processes, including: Enabling and disabling processes Enabling and disabling the process archival feature Modifying a process schedule Enabling a Process Some of the processes that ship with the automation packs are disabled by default to reduce the load on the server. Note The Publish SAP Alerts on Windows Event Log Process is disabled by default. If you want this process to publish an event in the Windows event log on the TEO server when alerts are created by the SAP-related processes, you must enable the process. This process is necessary for integration with management frameworks such as Microsoft SCOM Perform the following steps to enable a process. Step 1 Step 2 In the Processes view, navigate to the process that you want to enable (disabled processes appear dimmed). Use one of the following methods to enable the process: Right-click the process and choose Enable from the submenu. In the Process Editor, click the General tab and then checke the Enabled check box. Click the Save tool to save your changes to the process and close the Process Editor. Disabling a Process Disabling a process prevents the process from executing. You may want to disable some processes to reduce the load on your server or while you are modifying the process definition. Perform the following steps to disable a process. Step 1 Step 2 In the Processes view, navigate to the process that you want to disable. Use one of the following methods to disable the process: Right-click the process and choose Disable from the submenu. In the Process Editor, click the General tab and then uncheck the Enabled check box. Click the Save tool to save your changes to the process and close the Process Editor. 8-3

134 Managing SAP Processes Chapter 8 Understanding SAP Processes Modifying Process Instance Archival TEO provides an option in the process definition that allows you choose whether or not to archive process and activity execution in the TEOProcess database. Disabling the Archive completed instances option helps improve performance and minimize the size of the database. It is also useful when debugging the execution of processes. The automation packs shipped by Cisco normally have the archival functionality disabled by default for the processes. If you want to view the execution of a process and its activities, or view the process instances after a process has completed, you must enable the archival functionality in the process definition. Perform the following steps to enable or disable the archival feature. Step 1 Step 2 In the Processes view, navigate to the process you want to flag for archival. Right-click the process and choose Edit from the submenu. Figure 8-4 Opening a Process to Edit Properties Step 3 On the process Properties dialog box, click the Options tab. 8-4

135 Chapter 8 Understanding SAP Processes Managing SAP Processes Figure 8-5 Process Properties Options Tab Step 4 On the Options tab, check the Archive completed instances check box to enable process instance archival. If the process is already flagged for archival and you no longer want to save the process instances for this process, uncheck the check box. Step 5 Click the Save tool to save your changes to the process and close the process Editor. Modifying a Process Schedule Many of the processes that ship with the automation packs are triggered by a schedule. You can modify when the process will be executed by disabling the existing schedule and then creating a new schedule for the process. You use the process Properties dialog box to modify the process schedule. Perform the following steps to assign a new schedule to a process. Step 1 In the Processes view, navigate to the process for which you want to modify. Step 2 Right-click the process and choose Edit from the submenu (see Figure 8-4 on page 8-4). Step 3 On the process Properties dialog box, click the Triggers tab. 8-5

136 Managing SAP Processes Chapter 8 Understanding SAP Processes Figure 8-6 Process Properties Triggers Tab Step 4 Step 5 On the Triggers tab, right-click the current Schedule and choose Disable from the submenu. Click New > Schedule to open the Schedule Properties dialog box to create a new schedule for this process. Figure 8-7 Schedule Properties Step 6 On the Schedule Properties dialog box, specify the criteria for the new schedule and click OK. 8-6

137 Chapter 8 Understanding SAP Processes Managing SAP Processes Note For information on creating schedules, see Managing Triggers in the Tidal Enterprise Orchestrator Reference Guide. The newly created schedule displays on the Triggers tab and is enabled. Figure 8-8 Process Properties Triggers Tab with Newly Created Schedule Step 7 Click the Save tool to save your changes to the process and close the process Editor. 8-7

138 Running Processes Chapter 8 Understanding SAP Processes Running Processes The processes that ship with the product will run based on the trigger that was defined in the process definition. For processes that are triggered by a schedule, you can also manually start a process at any time (adhoc). This section guides you through starting a process and viewing its progress as it runs. Note You can only view a running process and the process instances for processes that have the Archive completed instances feature enabled. See Modifying Process Instance Archival, page 8-4 for information on enabling the archival feature on a specific process. Starting a Process Step 1 In the Processes view, right-click the process and choose Start Process from the submenu. Figure 8-9 Starting a Process The Confirm Start Process dialog box displays. Figure 8-10 Confirm Start Process 8-8

139 Chapter 8 Understanding SAP Processes Running Processes Step 2 This process is defined to run on systems in the All SAP ABAP target group. In this example, we will override the default target and choose a specific system on which to run the process. On the Confirm Start Process dialog box, check the Override target (All SAP ABAP) check box to expand the fields on the dialog box. Figure 8-11 Specifying Target Override Step 3 Click the Target radio button and then click the Browse tool to open the Select Target dialog box. Step 4 Select the target in the list and then click OK. Step 5 On the Confirm Start Process dialog box, click OK to start the process. The Start Process Results dialog box displays. Proceed to Viewing Running Process, page

140 Running Processes Chapter 8 Understanding SAP Processes Viewing Running Process After starting the process, you can use the Process Viewer to view the process as it runs through each activity. Note You can only view a running process and the process instances for processes that have the Archive completed instances feature enabled. See Modifying Process Instance Archival, page 8-4 for information on enabling the archival feature on a specific process. Step 1 On the Start Process Results dialog box, right-click the process and choose Observe. Figure 8-12 Start Process Results Observe Submenu The Process Viewer displays the process workflow. Figure 8-13 Process Viewer Viewing Process Running 8-10

141 Chapter 8 Understanding SAP Processes Viewing Process Results Step 2 Step 3 View the process as it proceeds through the workflow. The activities within the process workflow will change to green as they complete (succeed). If an activity fails, an incident is created. When the process completes, close the Process Viewer and proceed to Viewing Process Results, page Viewing Process Results After a process completes, you can view the results in the Operations workspace. This section guides you through viewing the results from running the process. Note You can only view a running process and the process instances for processes that have the Archive completed instances feature enabled. See Modifying Process Instance Archival, page 8-4 for information on enabling the archival feature on a specific process. Accessing Process View Step 1 Step 2 Step 3 Step 4 On the Operations workspace, expand expand Process Views in the navigation pane and click View Adhoc (since the process was manually executed). Using the Filter by link, choose Automation Pack and then choose [Automation Pack Name] from the drop-down list. Scroll to the process and select it. In the View Results pane, expand the process to view each activity in the process workflow. 8-11

142 Viewing Process Results Chapter 8 Understanding SAP Processes Figure 8-14 Operations Workspace Viewing Process Results Step 5 Review the status of the process and each activity within the process to verify that it has succeeded. Viewing Activity Results You can view the results of a specific activity within the process using the Activity Instance Properties dialog box. Step 1 Step 2 In the View Results pane, scroll to an activity. Right-click [process activity] and choose Properties. Figure 8-15 Activity Properties Submenu Step 3 Click the appropriate tab to view the results. The tab that displays depends on the activity. 8-12

143 Chapter 8 Understanding SAP Processes Viewing Process Results Figure 8-16 Process Activity Properties Results Tab Step 4 When you have completed reviewing the results, click Close to close the dialog box. Viewing Incidents When a process detects an issue that requires action, an incident is generated. If you have configured the product to send notifications to a specific person in your organization, that person will receive an notification whenever an incident is generated. You can also view these incidents in the Task Views on the Operations workspace. Step 1 Step 2 On the Operations workspace, expand Task Views in the navigation pane and click View Incidents. In the View Incidents pane, choose View all tasks from the Task Assignee drop-down list to display all the incidents in the View Results pane. Note If you have a multi-tenant environment configured, you should select to display the Affected Organization column (right-click and choose Choose Columns from the shortcut menu). 8-13

144 Viewing Process Results Chapter 8 Understanding SAP Processes Figure 8-17 Viewing Incidents Step 3 To view a specific incident, right-click the incident and choose Open. Figure 8-18 Incident Open Submenu The Incident Report displays in your web browser. 8-14

145 Chapter 8 Understanding SAP Processes Viewing Process Results Figure 8-19 Tidal Enterprise Orchestrator Incident Report 8-15

146 Viewing Automation Summary Chapter 8 Understanding SAP Processes Viewing Automation Summary When incidents are generated, TEO delivers an online Automation Summary that details the analysis that was performed to identify a situation that may require action. It also shows relevant diagnostic and state information captured while performing the situation analysis, and provides a recommended resolution for the situation. You can access the Automation Summary from the Tasks View on the Operations workspace. Step 1 Step 2 Step 3 On the Operations workspace, expand Task Views in the navigation pane and click View Incidents. In the View Incidents pane, click the View all tasks radio button to display the incidents in the View Results pane. Right-click the incident and choose View Automation Summary. Figure 8-20 View Automation Summary Submenu The Automation Summary displays in your web browser. 8-16

147 Chapter 8 Understanding SAP Processes Viewing Automation Summary Figure 8-21 Automation Summary 8-17

148 Viewing Automation Summary Chapter 8 Understanding SAP Processes 8-18

149 APPENDIXA Configuring SAP v7.1x JARM Tracing Service This appendix provides instructions on configuring the JARM tracing service so that you can monitor iview response time on SAP v7.1x systems. It includes the following sections: Launching the SAP ConfigTool, page A-1 Configuring Properties, page A-2 Launching the SAP ConfigTool You use the SAP ConfigTool to configure the JARM tracing service. Step 1 Step 2 Step 3 On the SAP server, navigate to the following directory: usr\sap\[sid]\j01\j2ee\configtool Use one of the following methods to open the ConfigTool, depending on your operating system: In Windows, double-click the configtool.bat file. In UNIX, double-click the configtool.sh file. On the Connection Settings dialog box, click Yes to use the default DB settings. The AS Java ConfigTool opens. Proceed to Configuring Properties, page A-2. A-1

150 Configuring Properties Appendix A Configuring SAP v7.1x JARM Tracing Service Configuring Properties You must now configure the apptracing and monitor settings with custom values. Step 1 In the navigation pane, navigate to cluster-data > template > instance > services and click apptracing. Figure A-1 Apptracing Properties Step 2 Step 3 In the results pane, change the following properties by selecting the property name, entering the new value in the Custom value field and clicking Set. jarm/switch On jarm/maxreqcomphigh 2600 jarm/maxreqcomplow 2500 In the navigation pane, navigate to cluster-data > template > instance > services and click monitor. A-2

151 Appendix A Configuring SAP v7.1x JARM Tracing Service Configuring Properties Figure A-2 Monitor Properties Step 4 Step 5 Step 6 In the results pane, click jarm_history.started. In the Custom value field, enter false and click Set. Click Save on the toolbar. The Logs dialog box displays showing the changes that have been completed. Figure A-3 Logs Dialog Step 7 Step 8 Click OK. Close the ConfigTool. A-3