Cisco TEO Getting Started Guide for SAP€¦ · Viewing Automation Summary 8-16 APPENDIX A Configuring SAP v7.1x JARM Tracing Service A-1 Launching the SAP ConfigTool A-1 Configuring

Cisco TEO Getting Started Guide for SAPRelease 2.3 April 2012

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-25161-02

http://www.cisco.com

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: www.cisco.com/go/trademarks. 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 TEO Getting Started Guide for SAP © 2010–2012 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

OL-25161-02

C O N T E N T S

New and Changed Information vii

Latest Release vii

Previous Releases viii

Preface ix

Organization ix

Conventions x

Product Documentation xi

Documentation Formats xi

Guides and Release Notes xi

Online Help xi

Open Source License Acknowledgements xi

Obtaining Documentation and Submitting a Service Request xii

C H A P T E R 1 Prerequisites 1-1

System Requirements 1-2

Hardware Requirements 1-2

Software Requirements 1-3

Adapter System Requirements 1-5

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-14

C H A P T E R 2 Importing Automation Packs 2-1

Importing the Automation Packs for SAP 2-2

Installing SAP .NET Connector Files 2-14

iiiCisco TEO Getting Started Guide for SAP

Contents

Installing SAP Java Library Files 2-15

Configuring SAP Multi-Tenant Support in Web Console 2-17

C H A P T E R 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-6

Modifying an SAP User or Runtime User Record 3-6

Deleting an SAP User or Runtime User Record 3-6

C H A P T E R 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

Managing SAP Targets 4-27

Enabling an SAP Target 4-27

Disabling an SAP Target 4-27

Deleting an SAP Target 4-28

C H A P T E R 5 Managing Assignments and Notifications 5-1

Accessing Task Rules View 5-2

Configuring Task Rules 5-3

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

C H A P T E R 6 Managing Extended Target Properties 6-1

Accessing Extended Target Properties 6-1

Configuring Extended Target Properties 6-3

ivCisco TEO Getting Started Guide for SAP

OL-25161-02

Contents

C H A P T E R 7 Configuring SAP Global Variables 7-1

Accessing Global Variables 7-1

Configuring Global Variables 7-3

C H A P T E R 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

A P P E N D I X A Configuring SAP v7.1x JARM Tracing Service A-1

Launching the SAP ConfigTool A-1

Configuring Properties A-2

A P P E N D I X B Registering TEO with SAP System Landscape Directory B-1

Registering Tidal Enterprise Orchestrator B-2

Registering the Product Manually B-2

To Import Registration B-2

Transfer Registration via XML B-3

I N D E X

vCisco TEO Getting Started Guide for SAP

OL-25161-02

Contents

viCisco TEO Getting Started Guide for SAP

OL-25161-02

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 April 2012—Cisco TEO Getting Started Guide for SAP 2.3 Changes

Feature Location

Revised Text Part Number (-01 to -02). Front cover, footers

Updated Trademark and Copyright date Inside cover page

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.

Chapter 1, “Prerequisites”

Revised automation pack names:

• Core Automation for SAP BW, BOBJ and In-Memory Computing

• Incident Response for SAP

• IT Task Automation for SAP

Chapter 2, “Importing the Automation Packs”

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.


viiCisco TEO Getting Started Guide for SAP

OL-25161-02

New and Changed Information

Previous Releases

New feature for supporting duplicate SAP system IDs

Chapter 4, “Configuring SAP Targets”

Updated Extended Targets—Target Property Value dialog box allows options to set multiple targets.

Chapter 6, “Managing Extended Target Properties”

Table 1 April 2012—Cisco TEO Getting Started Guide for SAP 2.3 Changes

Feature Location

Table 2 September—2011 Cisco TEO Getting Started Guide for SAP 2.2 Changes

Feature Location

Updated guide name, automation pack names, and added Text Part Number to document.

All

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

Chapter 2, “Importing Automation Packs”

Updated Installing Java Library Files section. Chapter 2, “Importing Automation Packs”

Updates to SAP System Wizard Database Connection panel.

Chapter 4, “Configuring SAP Targets”

New chapter on using the Task Rules feature. Chapter 5, “Managing Assignments and Notifications”

New chapter on using the Extended Target Properties feature.

Chapter 6, “Managing Extended Target Properties”

viiiCisco TEO Getting Started Guide for SAP

OL-25161-02

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.

OrganizationThis 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 Managing Assignments and Notifications

Provides instructions on using the Task Rules feature to configure assignments and notifications.

Chapter 6 Managing Extended Target Properties

Provides instructions on using the Extended Target Properties feature to configure the properties that ship with the automation packs.

ixCisco TEO Getting Started Guide for SAP

OL-25161-02

Preface

ConventionsThis guide uses the following conventions:

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.

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 Configuring SAP v7.1x JARM Tracing Service

Provides instructions for configuring the JARM tracing service.

Appendix B Registering TEO with SAP System Landscape Directory

Provides instructions for registering TEO with the SAP System Landscape Directory.

Convention Indication

bold font Commands and keywords and user-entered text appear in bold font.

italic 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.

xCisco TEO Getting Started Guide for SAP

OL-25161-02

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 FormatsDocumentation 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 www.adobe.com.

Guides and Release NotesYou can download the TEO product documentation from Cisco.com. Release Notes can be found on Cisco.com and the product CD.

Online HelpOnline 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 AcknowledgementsLicenses 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 email [email protected].

xiCisco TEO Getting Started Guide for SAP

OL-25161-02

http://www.cisco.com/en/US/customer/docs/net_mgmt/datacenter_mgmt/process_auto/teo/v2_2/reference/OpenSourceLicenses.html

mailto:[email protected]

Preface

Obtaining Documentation and Submitting a Service RequestFor 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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.

xiiCisco TEO Getting Started Guide for SAP

OL-25161-02

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

OL-25161-02

C H A P T E R 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-2

• 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.

1-1Cisco TEO Getting Started Guide for SAP

Chapter 1 Prerequisites System Requirements

System RequirementsBefore 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 RequirementsThe 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 systems recommended)

64-bit 2.8 GHz or higher core (Dual core 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.

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.

1 GB of available hard disk space dedicated to Enterprise Orchestrator (2 GB or higher recommended)


Network adapter Network adapter


OL-25161-02


Software RequirementsThe following table provides the minimum software requirements.

Table 1-2 Minimum System Requirements

Component Client Server Web Console

ASP.NET ASP.NET 2.0

ASP.NET Web Service Extensions

Internet Information Service (IIS) Manager

IIS 6.0 IIS 6.0

IIS 7.0 with 6.0 compatibility IIS 7.0 with 6.0 compatibility

Java SE Runtime Environment

64-bit JRE 6 Update 1.6

Operating System HP-Unix Enterprise Edition (Limited to Oracle database support)

Microsoft Windows Server® 2008 (Standard, Enterprise, or Datacenter)

Microsoft Windows Server® 2008 64-bit (Standard, Enterprise, or Datacenter)

Microsoft Windows Server® 2003 (Standard or Enterprise)

Microsoft Windows Server® 2003 64-bit (Standard or Enterprise)

Microsoft Windows 7

Microsoft Vista

Microsoft Windows XP

Oracle Solaris Enterprise Edition (Limited to Oracle database support)

Redhat Linux Enterprise Edition 6 (Limited to Oracle database support)

Microsoft® .NET™ Framework

Microsoft® .NET™ Framework 4

Microsoft® .NET™ Framework 4

Processes Database Microsoft® SQL Server 2008 (Standard or Enterprise Edition) or later.

Microsoft® SQL Server 2005


OL-25161-02


Oracle 11g R2 or later 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.

Reporting Database 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.

Table 1-2 Minimum System Requirements

Component Client Server Web Console


OL-25161-02


Adapter System RequirementsThis section provides the system requirements for individual adapters.

Table 1-3 Minimum Adapter System Requirements

Adapter Component

SAP ABAP Adapter SAP GUI

The SAP ABAP Adapter requires SAP .NET 3.0 Connector for .NET 4.0 on x64 version 3.0.6.4 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 Disk Space Requirements, page 1-7 for instructions on installing these files.

SAP Versions:

• SAP R/3

– 46c (Support Package 50)

– 46d (Support Package 15)

– 6.10 (Support Package 6)

– 6.20 (including 4.7)

– 6.30

– 6.40

– 7.0

– 7.10

– 7.11

– 7.20

Note 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.


OL-25161-02


• SAP BW

– 3.0

– 3.1

– 3.5

– 7.0

– 7.0 SP13

– 7.01 SP8

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.

• 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 51033513

SAP NetWeaver CE 7.1 SR5

• Java Components

• Documentation

• Developer Workplace

• Number 51033845

OLAP Database Adapter TEO requires that the Microsoft ADOMD.Net v10.0 client be installed on the TEO server to be able to communicate with SAP OLAP servers.

The Microsoft ADOMD.Net v10.0 client is a component in the Microsoft SQL Server 2008 Feature Pack and can be downloaded from the Microsoft website at www.microsoft.com/downloads.

Table 1-3 Minimum Adapter System Requirements

Adapter Component


OL-25161-02

http://www.microsoft.com/downloads


Disk Space RequirementsThe 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:

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-4 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 one out of 5 having paged output

6 KB

(1 KB for Auditing)

Record Rate (estimate)

5000 5 per/process 500

Daily Total 80 MB 0.0488 MB 2.4414 MB

Retention (months) 1 1 1 1

Table 1-5 Calculating Disk Space Formula

Data Formula

Process Size 78.125 MB/day x 30 days/month = 2.28882 GB

Activity Size 0.0488 MB/day x 30 days/month = 1.464 MB

Task Size 500 tasks x 6 KB 2.4414 MB/day x 30 days/month = 73.242 MB

Total Size DB initial size for 30 day retention = 5000 processes per day * 73 KB + 500 tasks *6 KB = 368000 KB or 368 MB *30 =11040000 KB or 11040MB or 11.04 GB


OL-25161-02


Reporting Database Sizing RequirementsThe formula for calculating the disk space for the TEO Reporting database for an SAP environment is based on the following record statistics:

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-6 Calculating Disk Space Formula for TEO Reporting Database for SAP Environment

Incident Alert Event MetricProcess Audit Task Audit

Record Size 2 KB 2 KB 1.5 KB 0.06 KB 0.2 KB 0.15 KB

Record Rate (estimate)

30/day per system

200/day per system

1/min per application server

0.2 records/sec per application server

3000/day per system

3x number of alerts

Daily Total 60 KB per system

400 KB per system

2160 KB per application server

1036 KB per application server

600 KB per system

90 KB per system

Retention (months)

6 6 6 12 6 6

Table 1-7 Calculating Disk Space Formula

Data Formula

Incident Size 60 KB/system/day x 1 system x 6 months = 10 MB

Alert Size 400 KB/system/day x 1 system x 6 months = 72 MB

Event 2160 KB/application server/day x 5 servers x 6 months = 1920 MB

Metrics 1036 KB/application server/day x 5 servers x 6 months = 1864 MB

Process Audit 600 KB/system/day x 1 system x 6 months = 108 MB

Task Audit 90 KB/system/day x 1 system x 6 months = 16 MB

Total Size 10 MB + 72 MB + 1920 MB + 1864 MB + 108 MB + 108 MB + 16 MB = 3.99 GB


OL-25161-02

Chapter 1 Prerequisites TEO Performance Best Practice Guidelines

TEO Performance Best Practice GuidelinesTEO'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 RequirementsThe following table contains the hardware requirements which maximizes TEO performance.

Table 1-8 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)

It is recommended that the databases reside on a separate server.

Disk Space 2 GB of available hard disk space dedicated to Tidal Enterprise Orchestrator or higher


4 GB of available hard disk space dedicated to Tidal Enterprise Orchestrator or higher recommended


Network adapter Network adapter


OL-25161-02

Chapter 1 Prerequisites Configuration Access Requirements

Configuration Access RequirementsThe following user rights and configuration requirements must be met prior to installing and configuring the SAP-related automation packs.

SAP User AccountThe 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:

SAP Support User AccountThe 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 InformationThe following information about your SAP environment should be gathered prior to installing TEO. You will need this information during the installation process.

Recommendation Description

Required Authorization S_A.System profile

Account Type System, Service, or Communication user type is recommended

Language Setting English, German. The TEO server regional setting should match the language setting in SAP.

Field Description

Display Name Name used to identify the SAP system

Application Server Name or IP address for the ABAP application server

System Number SAP-specific system number

SAP Router String (optional) Used for SAP systems outside the firewall

Logon Information User name, password and client for logging onto the SAP ABAP application server


OL-25161-02


SAP Java System InformationThe following information about your SAP Java System should be gathered prior to installing TEO. You will need this information during the installation process.

SAP Database Access RightsThese 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

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.

SQL Server SQL Authentication

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.

Field Description

Application Server Name or IP address for the Java application server

Port 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 51504.

Logon Information User name and password for logging onto the SAP Java application server


OL-25161-02


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]GOCREATE 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]GOUSE [TEOProcess]GOIF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'teoprocess')DROP USER [teoprocess]GOCREATE USER [teoprocess] FOR LOGIN [teoprocess] WITH DEFAULT_SCHEMA=[dbo]GOEXEC sp_addrolemember N'db_datareader', N'teoprocess'GOEXEC 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]GOCREATE 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]GOUSE [TEOReporting]GOIF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'teoreporting')DROP USER [teoreporting]GOCREATE USER [teoreporting] FOR LOGIN [teoreporting] WITH DEFAULT_SCHEMA=[dbo]GOEXEC sp_addrolemember N'db_datareader', N'teoreporting'GOEXEC sp_addrolemember N'db_datawriter', N'teoreporting'GO


OL-25161-02


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:

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

• 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


OL-25161-02


Product Default SettingsThe following information should be gathered prior to installing the product. The information is necessary when importing the default automation packs after the product installation has completed.

Default Email Settings

The Email Configuration panel on the Automation Pack Import Wizard is used to configure the default email settings that will be used for email activities. The following information is required to configure the email settings during the configuration process:

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:

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.

Setting Description

Default SMTP server The name of the SMTP server that is used as the default server for sending email messages

Default SMTP port The port number for the SMTP server. The default port number is 25 but can be changed if necessary.

Default sender The email address of the sender that is designated as the default sender for email activities

Field Description

Domain Name of the domain in which the Windows automation server target resides

User name Name of the user account that is used to connect to the Windows automation server target

Password Password assigned to the user account that is used to connect to the Windows automation server target

Field Description

Display Name Name used to identify the SAP system

Application Server Name or IP address for the ABAP application server

System Number SAP-specific system number

SAP Router String (optional) Router string used to connect to SAP systems via SAPRouter

Logon Information User name, password and client for logging onto the SAP ABAP application server


OL-25161-02


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 Description

Application Server Name or IP address for the Java application server

Port 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 51504.

Logon Information User name and password for logging onto the SAP Java application server


OL-25161-02



OL-25161-02

OL-25161-02

C H A P T E R 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-14

• Installing SAP Java Library Files, page 2-15

• Configuring SAP Multi-Tenant Support in Web Console, page 2-17

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.


Chapter 2 Importing Automation Packs Importing the Automation Packs for SAP

Importing the Automation Packs for SAPYou 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

Note See the Cisco TEO Installation and Administration Guide for instructions on importing and configuring the Core components for the product.

Figure 2-1 Welcome to the Automation Pack Import Wizard

Step 3 On the Welcome panel, click Next.


OL-25161-02


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.

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.


OL-25161-02


Figure 2-4 Select User or Group

Step 6 On the Select User or Group dialog box, click Location and choose the location from which the user will be selected.

Step 7 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 email address.

Step 8 Click OK to close the Select User or Group dialog box.

Step 9 On the Default Incidents Assignee Setup panel, click Next.

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.


OL-25161-02


Figure 2-6 General Information—Assessment for SAP BWA


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.


OL-25161-02


Step 11 On the Data Extraction panel, accept the default location or click the Browse tool to specify a new destination.

Step 12 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.

Step 13 Click Next.

Figure 2-8 Review Prerequisites—Assessment for SAP BWA




Figure 2-9 General Information—Core Automation for SAP BW, BOBJ and In-Memory

Computing


OL-25161-02



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


OL-25161-02





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




OL-25161-02



Figure 2-14 General Information—Automation for SAP BW and BWA


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.



OL-25161-02


Figure 2-16 Review Prerequisites—Automation for SAP BW and BWA




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.


OL-25161-02


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 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.

Step 22 Click Next.


OL-25161-02


Figure 2-19 Review Prerequisites—Incident Response for SAP


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.


OL-25161-02


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.


Figure 2-22 Review Prerequisites—IT Task Automation for SAP



OL-25161-02

Chapter 2 Importing Automation Packs Installing SAP .NET Connector Files

Figure 2-23 Completing the Automation Pack Import Wizard

Step 25 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.

Installing SAP .NET Connector FilesThe SAP ABAP Adapter requires the SAP .NET 3.0 Connector for .NET 4.0 on x64 version 3.0.6.4 or higher. Before you can create an SAP ABAP target, the dll files must be installed on the TEO server.

Visit the SAP Service Marketplace on SAP.com to obtain the required files.

Step 1 From the SAP .NET 3.0 Connector 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

Step 2 Copy the files to the following folder on the TEO server:

<Install drive>:\Program Files\Cisco\Tidal Enterprise Orchestrator\Adapters

Step 3 Restart the Tidal Enterprise Orchestrator Server service.


OL-25161-02

Chapter 2 Importing Automation Packs Installing SAP Java Library Files

Installing SAP Java Library FilesThe 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 51033513

• SAP NetWeaver CE 7.1 SR5

– Java Components

– Documentation

– Developer Workplace

– Number 51033845

Step 1 Stop the Tidal Enterprise Orchestrator Server service.

Step 2 Navigate to the directory where the TEO files are installed (C:\Program Files\Cisco\Tidal Enterprise Orchestrator).

Step 3 Double-click Tidal.Automation.SapJarInstaller.exe to open the SAP Libraries Install Wizard.

Figure 2-24 Welcome to the SAP Dependency Libraries Installer

Step 4 Click Next to check for the adapter dependency libraries have been installed.


OL-25161-02

Chapter 2 Importing Automation Packs Installing SAP Java Library Files

Figure 2-25 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.

Figure 2-26 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.


OL-25161-02

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

Figure 2-27 Finishing the SAP Libraries Install Wizard

Step 8 Verify that the files were successfully installed and then click Close to close the installer.

Step 9 Restart the Tidal Enterprise Orchestrator Server service to complete the procedure.

Configuring SAP Multi-Tenant Support in Web ConsoleWhen 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 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

Step 2 Open the Web.config file in Notepad and navigate to the “AffectedOrganizations” setting.

name="AffectedOrganizations"

enabled="false" />

Step 3 Change the enabled setting to true.

Step 4 Save the file to complete the procedure.


OL-25161-02

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


OL-25161-02

OL-25161-02

C H A P T E R 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-6

Accessing the Runtime Users ViewUse 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


Chapter 3 Configuring Runtime Users Creating Runtime Users

Runtime User AccountsThe 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:

Creating Runtime UsersYou 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 AccountThe 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.

Figure 3-2 Runtime Users—New SAP User Submenu

Runtime User Description

SAP User Specifies the credentials required to access the SAP System target.

Runtime User Specifies the credentials required to access the following SAP-related targets:

• SAP Database

• SAP Java Application Server


OL-25161-02


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.

Step 2 On the General tab, specify the following information:

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.

Field Description

Display name Name for the user account.

User name User name assigned to the SAP user account that connects to the SAP system or ABAP application server.

Password Password assigned to the SAP user account that connects to the SAP system or ABAP application server.

Client SAP client number assigned to the user account.

Description A description of the user account.


OL-25161-02


Creating a Runtime User AccountThe 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.

Figure 3-4 Runtime Users—New Runtime User Submenu

Figure 3-5 New Runtime User Properties—General Tab



OL-25161-02


Step 2 On the General tab, specify the following information:

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.

Field Description

Display name 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 User name assigned to the user account that connects to the SAP target.

Password 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.

Description A description of the user account.


OL-25161-02

Chapter 3 Configuring Runtime Users Managing Runtime User Definitions

Managing Runtime User DefinitionsUse the Definitions—Runtime Users view to manage the runtime user definitions.

Modifying an SAP User or Runtime User RecordUse the Runtime User Properties to modify the runtime user credentials.

Step 1 In the Definitions—Runtime Users view, select the runtime user record, right-click and choose Properties.

The selected [Runtime User] Properties dialog box displays.

Step 2 On the General tab, modify the appropriate information. See Figure 3-2 on page 3-2 or Figure 3-4 on page 3-4 depending on the type of runtime user record you are modifying.

Step 3 Click OK to save your changes and close the dialog box.

Deleting an SAP User or Runtime User RecordUse 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.


OL-25161-02

OL-25161-02

C H A P T E R 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

• Managing SAP Targets, page 4-27

Accessing the Targets ViewUse the Definitions—Targets view to create and manage the SAP targets.

Figure 4-1 Definitions Workspace—Targets View


Chapter 4 Configuring SAP Targets Creating SAP System Targets

Figure 4-5 Server Availability

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.

Step 7 Specify the following information:

Step 8 Click Next.

If you are configuring the SAP database, the Database Connection panel displays. Otherwise, proceed to Step 12.

Field Description

Servers available for monitoring All detected servers are checked by default. Verify that the check box next to each server that you want to monitor is checked.

Add 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.

Remove If you want to remove a server from the list, select the server and click Remove.

Select All If the check boxes have been unchecked and you want all servers to be monitored, click Select All.

Deselect All If all the check boxes are checked and you want to uncheck all of them, click Deselect All.


OL-25161-02


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 Choose the Database type from the drop-down list to display the fields for the specific type of database.

Step 10 Specify the information for the type of database that is being configured. The fields that display depend on the database type.

Field Description

Server Enter the name of the SAP application server where the database resides.

Hostname or data source Name of the host server or data source for the Oracle or Generic database.

SID System ID for the server where the Oracle database resides.

Database name Enter the name of the SAP database that is associated with the SAP system.

Database owner Enter the name of the user that owns the rights to the database.

Database source Enter the Data source to connect to the database.

Port Number Enter the Port number used to connect to the database.


OL-25161-02


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.

Default timeout for activities (seconds) Enter the number of seconds before the activity times out. The default timeout period is 120 seconds.

Default runtime user 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.

Connection string 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.

Field Description


OL-25161-02


Creating an SAP System Target—ABAP+Java ConnectionYou 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 2-15.

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.


OL-25161-02


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 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 Description

Display name Enter a name for the SAP system. This is the name that will display in the Targets pane.

System Components

ABAP application servers 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.

Java application servers 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.

SAP database Check this check box if you want to configure the SAP database that is associated with the SAP system.


OL-25161-02


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.

Monitor as production system 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.

Organization 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.

Field Description


OL-25161-02


Step 5 Specify the connection information for connecting to the SAP application server:

Step 6 Click Next.

Field Description

Connect using Choose the connection method from the drop-down list. The fields that display on the panel depend on the connection method selected.

Application server 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.

Logon group 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.

Router string (optional) 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.

Default runtime user Choose the user account that contains the credentials to connect to the target from the drop-down list.


• To create a new SAP User, click New > SAP User. See Creating an SAP User Account, page 3-2.


OL-25161-02


Figure 4-11 Server Availability

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.

Step 7 Specify the following information:

Step 8 Click Next.

If you are configuring the SAP database, the Database Connection panel displays. Otherwise, proceed to Step 12.

Field Description

Servers available for monitoring All detected servers are checked by default. Verify that the check box next to each server that you want to monitor is checked.

Add 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.

Remove If you want to remove a server from the list, select the server and click Remove.

Select All If the check boxes have been unchecked and you want all servers to be monitored, click Select All.

Deselect All If all the check boxes are checked and you want to uncheck all of them, click Deselect All.


OL-25161-02


Figure 4-12 Database Connection

Step 9 Choose the Database type from the drop-down list to display the fields for the specific type of database.

Step 10 Specify the information for the type of database that is being configured. The fields that display depend on the database type.

Field Description

Server Enter the name of the SAP application server where the database resides.

Hostname or data source Name of the host server or data source for the Oracle or Generic database.

SID System ID for the server where the Oracle database resides.

Database name Enter the name of the SAP database that is associated with the SAP system.

Database owner Enter the name of the user that owns the rights to the database.

Database source Enter the Data source to connect to the database.

Port Number Enter the Port number used to connect to the database.

Default timeout for activities (seconds) Enter the number of seconds before the activity times out. The default timeout period is 120 seconds.


OL-25161-02


Step 11 Click Next.

Figure 4-13 Java Connection

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.

Step 12 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.

Default runtime user Choose the user account that contains the credentials to connect to the database from the drop-down list.



Connection string 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.

Field Description


OL-25161-02


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:

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.

Field Description

Display name Enter the name of the server that will be displayed in the Targets pane.

Description Enter a text description for the server.


OL-25161-02


Step 15 Specify the information for connecting to the SAP 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

Field Description

Application server Enter the IP address or name of the SAP Java application server.

JMX Connection

JMX port Enter the JMX port number used to connect to the Java application server.

Use credentials of the following runtime user

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.



Monitor as Portal Check the check box to run processes designed for portals on this Java server.

Central Instance Check the check box to run processes designed for central instances on this Java server.

Enable Telnet connection Check this check box if you want to specify the Telnet connection information to connect to the Java application server.


OL-25161-02


Step 17 Specify the Telnet connection information for connecting to the Java application server:

Step 18 Click Next.

Figure 4-17 Completing the New SAP Java Application Server Wizard

Step 19 Verify that the information is correct and click Finish to add the SAP Java application server.

Step 20 After adding the Java application server, click Next on the Java Connection panel.

Field Description

Telnet port Enter the Telnet port number used to connect to the Java application server.







OL-25161-02


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 ConnectionYou 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 2-15.

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.


OL-25161-02


Figure 4-19 Welcome to the New SAP System Wizard

Step 2 Click Next.

Figure 4-20 System Setup


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.


OL-25161-02


Step 3 Complete the following information on this panel:

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.

Field Description

Display name Enter a name for the SAP system. This is the name that will be displayed in the Targets pane.

System Components

ABAP application servers 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.

Java application servers Check this check box if the SAP system uses a Java connection to the application servers.

SAP database 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.

Monitor as production system 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.

Organization Enter the group or organization within the company that owns the target.


OL-25161-02


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:

Step 7 Click Next.

Figure 4-23 New SAP Java Application Server Wizard—JMX Connection

Field Description

Display name Enter the name of the server that will be displayed in the Targets pane.

Description Enter a text description for the server.


OL-25161-02


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.

Step 8 Specify the information for connecting to the SAP Java application server:

Step 9 Click Next.

If you enabled the Telnet Connection, the Telnet Connection panel displays.

Field Description

Application server Enter the IP address or name of the SAP Java application server.

JMX Connection

JMX port Enter the JMX port number used to connect to the Java application server.






Monitor as Portal Check the check box to run processes designed for portals on this Java server.

Central Instance Check the check box to run processes designed for central instances on this Java server.

Enable Telnet connection Check this check box if you want to specify the Telnet connection information to connect to the Java application server.


OL-25161-02


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:

Step 11 Click Next.

Field Description

Telnet port Enter the Telnet port number used to connect to the Java application server.







OL-25161-02


Figure 4-25 Completing the New SAP Java Application Server Wizard

Step 12 Verify that the information is correct and click Finish to add the SAP Java application server.

Step 13 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.


OL-25161-02

Chapter 4 Configuring SAP Targets Managing SAP Targets

Managing SAP TargetsUse 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 to modify the SAP target, 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:

Enabling an SAP TargetA 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 On the Definitions—Targets view, use one of the following methods to enable the target:

• In the Targets pane, right-click the SAP System target and choose Enable.

• In the Targets pane, select the SAP System target and then click the Click here link in the Details pane.

Step 2 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 TargetDisabling 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 On the Definitions—Targets view, use one of the following methods to disable the target:

• In the Targets pane, right-click the SAP System target and choose Disable.

• In the Targets pane, select the SAP System target and then click the Click here link in the Details pane.

Step 2 Verify that the status in the Enabled column in the Targets pane is False. If necessary, click the Refresh tool to update the view.

SAP Target Type Adapter Guide

SAP System Cisco TEO Adapter Guide for SAP ABAP

SAP ABAP Connection Cisco TEO Adapter Guide for SAP ABAP

SAP Database Cisco TEO Adapter Guide for SAP ABAP

SAP Java Application Server Cisco TEO Adapter Guide for SAP Java

SAP BI Warehouse Cisco TEO Adapter Guide for OLAP Database


OL-25161-02

Chapter 4 Configuring SAP Targets Managing SAP Targets

Deleting an SAP TargetBefore 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 System target and choose Delete.

Figure 4-27 Confirm Delete

Step 2 Click Yes to confirm the deletion. The target will be removed from the product.


OL-25161-02

OL-25161-02

C H A P T E R 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 email 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).


Chapter 5 Managing Assignments and Notifications Accessing Task Rules View

Accessing Task Rules ViewThe task rule that ships with the Core Automation for SAP automation pack can be accessed from the Definitions—Task Rules view.

Step 1 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.

Step 2 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 Description

Display Name The name assigned to the task rule.

Enabled Indicates whether the task rule is enabled (True) or disabled (False). A disabled task rule is unavailable for execution.

Type Type of task.

Owner User name of the person or group who assigned the task rule.

Last Modified Time The date and time the task rule was last modified.

Last Modified By The object or user name that last modified the task rule.

Id Unique ID of the task rule.

Description Brief description of the task rule.

Type Description Brief overview of the task rule type.

Created Time Time at which the task rule was created.


OL-25161-02

Chapter 5 Managing Assignments and Notifications Configuring Task Rules

Configuring Task RulesUse the Task Rules view to configure the task rule that ships with the Core Automation for SAP automation pack.

SAP Default AssignmentThe 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-3) or from the Task Rules view in the Console.

Step 1 In the Definitions workspace, click Task Rules in the navigation pane to display the task rules in the results pane.

Step 2 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.

Step 3 Right-click the SAP Default Assignment task rule and choose Properties to open the SAP Default Assignment Properties dialog box.

Step 4 Click the Assign tab to specify the user or group that should receive assignments for incidents and alerts generated by the processes.

Step 5 On the Assign tab, click Add to open the Select Assignee to Add dialog box.

Created By Name of the user who created the task.

Automation Pack Name of the automation pack associated with the task rule.

Column Description


OL-25161-02

Chapter 5 Managing Assignments and Notifications Configuring Task Rules

Figure 5-2 Adding Assignees to Task Rule

Step 6 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.

Step 7 Click OK to add the assignee to the task rule.

Step 8 When you have completed adding assignees to the task rule, click OK to close the dialog box.


OL-25161-02

Chapter 5 Managing Assignments and Notifications Creating a New Task Rule

Creating a New Task RuleUse 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:

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:

Task Rules Description

Assign Task Rule Assigns users to a task.

Notify Task Rule Notifies users that a task has been created.

Update Task Rule Specifies the properties to be updated in a task..

Field Description

Display Name Name of the task.

Type Display only. Shows the type of object.

Trigger Display only. Type of trigger associated with the task rule.


OL-25161-02


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.

Owner 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.

Description A brief description of the task rule.

Enabled 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.

Field Description

Task Type Description

Alert Alerts reflect potential problems that a user may want to investigate and possibly diagnose the problem.

Approval Request Specifies the message and choices for the assignee who is approving the task.

Guided Operation Details the steps a user takes to complete an assigned task.

Incident Task requires an operator to take action in order to resolve an issue.

Input Request Task requires input from an individual or group.

Review Task assigns a document for review.


OL-25161-02


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.


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


OL-25161-02


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.

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.

Option Description

AND condition (all conditions must be met) Click this option if an action is to be taken only when all conditions in the list are true.

OR condition (one condition must be met) Click this option if an action is to be taken when one condition in the list is true.


OL-25161-02


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 Description

Add 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.

Edit Select the appropriate assignee in the list and click this button to view or modify the assignee of the task rule.

Remove Select the appropriate assignee and click this button to remove the assignee from the list.

Remove All Click this button to remove all specified assignees from the list.


OL-25161-02


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 Description

Add notification recipients 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 email 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.


OL-25161-02


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.

Step 8 Click OK to save the task rule definition and close the dialog box.

Field Description

Add Click this button to add a new property to the Properties to update area.

Remove Click this button to remove the last property added to the Properties to update area.

Property From the Property drop-down list, choose the item to update within the task. The properties displayed depend on the selected item.

List action 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.

Value Enter new value for the property.


OL-25161-02


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.

-or-

• On the Details pane, select Click here to enable.

The Enabled column on the Results pane changes to True. If necessary, click the Refresh tool to update the view.

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-

• On the Details pane, select Click here to disable.

The Enabled column on the results pane changes to False. If necessary, click the Refresh tool to update the view.


OL-25161-02


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 On the Definitions—Task Rules view, select the appropriate task rule, right-click and choose Copy.

Step 2 On the Results pane, right-click and choose Paste.

A copy of the defined task rule is pasted onto the Results pane.

Step 3 To rename the copied task rule or other properties, right-click and choose Properties.

Step 4 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 On the Definitions—Task Rules view, select the task rule, right-click and choose Delete.

Step 2 On the Confirm Delete dialog box, click Yes to confirm the deletion.


OL-25161-02

Chapter 5 Managing Assignments and Notifications Enabling Notification Based on Assignment Processes

Enabling Notification Based on Assignment ProcessesIf you want to have emails 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 emails based on assignment.

When these processes are enabled, the user or user group who was assigned to tasks will receive the email notification.

Step 1 In the Definitions workspace, click Processes.

Step 2 Click the Filter by link and choose Automation Pack > Core to filter for the processes that ship with the Core automation pack.

Step 3 Right-click the appropriate Notification Based on Assignment process and choose Enable.

The following processes are for notification based on assignment:

Process Name Description

Default Alert Notification Based on Assignment

Sends email when an alert gets assigned.

Default Approval Request Notification Based on Assignment

Sends email when an approval request gets assigned.

Default Change Request Notification Based on Assignment

Sends email when an change requests gets assigned.

Default Guided Operation Request Notification Based on Assignment

Sends email when a guide operation request gets assigned.

Default Incident Notification Based on Assignment

Sends email when an incident gets assigned.

Default Input Request Notification Based on Assignment

Sends email when an input request gets assigned.

Default Review Request Notification Based on Assignment

Send email when a review request gets assigned.


OL-25161-02

OL-25161-02

C H A P T E R 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 PropertiesThe 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


Chapter 6 Managing Extended Target Properties Accessing Extended Target Properties

The following information about the extended target properties displays by default:

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.

Column Description

Display Name Name of the target property.

Description Text description of the target property.

Value Value assigned to the target property.

Data Type Type of value being used for the target property (Boolean, Encrypted String, Identity, Numeric, String, Table).

Automation Pack Name of the automation pack that provides the target property.

Customizable Indicates the customization setting for the target property in the automation pack.

Target Types Indicates the targets associated with the target property.

Last Modified Time Date and time the variable was last modified.

Last Modified By Name of the user who last modified the target property.

Id Unique ID of the target property.

Owner User name of the owner of the target property. This is typically the person who created the target property.

Created Time Date and time the target property was created.

Created By User name of the person who created the target property.


OL-25161-02

Chapter 6 Managing Extended Target Properties Configuring Extended Target Properties

Configuring Extended Target PropertiesYou 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 On the General tab, review the information in the Description field to determine the values that need to be specified for the target property.

Step 3 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.


OL-25161-02


Figure 6-3 Extended Target Properties—Value Tab

Step 4 Click in the cell to specify the default value or change the default value for all targets.

Step 5 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.


OL-25161-02


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


OL-25161-02


Step 8 Select the SAP system(s) and click OK.

Step 9 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.


OL-25161-02

OL-25161-02

C H A P T E R 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 VariablesUse the Definitions—Global Variables view to access the global variables that ship with the automation packs.

Step 1 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.

Step 2 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.


Chapter 7 Configuring SAP Global Variables Accessing Global Variables

Figure 7-1 Global Variables View

The following information about the variables displays by default:

Column Description

Display Name Name of the global variable.

Description Brief overview of the global variable.

Value Value of the variable.

Data Type Type of value being used for the variable (Boolean, Encrypted String, Identity, Numeric, String, Table).

Automation Pack Name of the automation pack that provides the object.

Last Modified Time Time the global variable was last modified.

Last Modified By Name of the user who last modified the global variable.


OL-25161-02

Chapter 7 Configuring SAP Global Variables Configuring Global Variables

Configuring Global VariablesIf 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 In the Definitions view, click Global Variables in the navigation pane to display the variables in the Global Variables pane.

Step 2 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.

Step 3 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.


OL-25161-02

Chapter 7 Configuring SAP Global Variables Configuring Global Variables


OL-25161-02

OL-25161-02

C H A P T E R 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 ProcessesThe 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


Chapter 8 Understanding SAP Processes Accessing the SAP Processes

If you have multiple automation packs installed, you can filter the processes to display the processes specific to the automation pack.

Step 2 In the upper portion of the Processes pane, click the Filter by link and choose Automation Pack.

Step 3 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 CategoryYou can also filter the processes by category to find a specific process.

Step 1 In the upper portion of the Processes pane, click the Filter by link and choose Category.

Step 2 In the drop-down list, choose [Catgory].

Figure 8-3 Filtering Processes by Category

Step 3 Scroll to the process.


OL-25161-02

Chapter 8 Understanding SAP Processes Managing SAP Processes

Managing SAP ProcessesThis 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 ProcessSome 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 2007.

Perform the following steps to enable a process.

Step 1 In the Processes view, navigate to the process that you want to enable (disabled processes appear dimmed).

Step 2 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 ProcessDisabling 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 In the Processes view, navigate to the process that you want to disable.

Step 2 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.


OL-25161-02


Modifying Process Instance ArchivalTEO 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 In the Processes view, navigate to the process you want to flag for archival.

Step 2 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.


OL-25161-02


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 ScheduleMany 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.


OL-25161-02


Figure 8-6 Process Properties—Triggers Tab

Step 4 On the Triggers tab, right-click the current Schedule and choose Disable from the submenu.

Step 5 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.


OL-25161-02


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.


OL-25161-02

Chapter 8 Understanding SAP Processes Running Processes

Running ProcessesThe 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


OL-25161-02


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.

Step 2 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 8-10.


OL-25161-02


Viewing Running ProcessAfter starting the process, you can use the Process Viewer to view the process as it runs through each activity.


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


OL-25161-02

Chapter 8 Understanding SAP Processes Viewing Process Results

Step 2 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.

Step 3 When the process completes, close the Process Viewer and proceed to Viewing Process Results, page 8-11.

Viewing Process ResultsAfter a process completes, you can view the results in the Operations workspace. This section guides you through viewing the results from running the process.


Accessing Process View

Step 1 On the Operations workspace, expand expand Process Views in the navigation pane and click View Adhoc (since the process was manually executed).

Step 2 Using the Filter by link, choose Automation Pack and then choose [Automation Pack Name] from the drop-down list.

Step 3 Scroll to the process and select it.

Step 4 In the View Results pane, expand the process to view each activity in the process workflow.


OL-25161-02


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 ResultsYou can view the results of a specific activity within the process using the Activity Instance Properties dialog box.

Step 1 In the View Results pane, scroll to an activity.

Step 2 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.


OL-25161-02


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 IncidentsWhen 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 email notification whenever an incident is generated. You can also view these incidents in the Task Views on the Operations workspace.

Step 1 On the Operations workspace, expand Task Views in the navigation pane and click View Incidents.

Step 2 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).


OL-25161-02


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.


OL-25161-02


Figure 8-19 Tidal Enterprise Orchestrator Incident Report


OL-25161-02

Chapter 8 Understanding SAP Processes Viewing Automation Summary

Viewing Automation SummaryWhen 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 On the Operations workspace, expand Task Views in the navigation pane and click View Incidents.

Step 2 In the View Incidents pane, click the View all tasks radio button to display the incidents in the View Results pane.

Step 3 Right-click the incident and choose View Automation Summary.

Figure 8-20 View Automation Summary Submenu

The Automation Summary displays in your web browser.


OL-25161-02


Figure 8-21 Automation Summary


OL-25161-02



OL-25161-02

OL-25161-02

A
P P E N D I X A 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 ConfigToolYou use the SAP ConfigTool to configure the JARM tracing service.

Step 1 On the SAP server, navigate to the following directory:

usr\SAP\[SID]\J01\j2ee\configtool

Step 2 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.

Step 3 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-1Cisco TEO Getting Started Guide for SAP

Appendix A Configuring SAP v7.1x JARM Tracing Service Configuring Properties

Configuring PropertiesYou 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 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

Step 3 In the navigation pane, navigate to cluster-data > template > instance > services and click monitor.


OL-25161-02


Figure A-2 Monitor Properties

Step 4 In the results pane, click jarm_history.started.

Step 5 In the Custom value field, enter false and click Set.

Step 6 Click Save on the toolbar.

The Logs dialog box displays showing the changes that have been completed.

Figure A-3 Logs Dialog

Step 7 Click OK.

Step 8 Close the ConfigTool.


OL-25161-02


Step 9 Stop the application server and restart it to complete the procedure.


OL-25161-02

OL-25161-02

A
P P E N D I X B Registering TEO with SAP System Landscape Directory
This appendix provides instructions for registering Tidal Enterprise Orchestrator to the SAP System Landscape Directory (SLD). You can manually register the product, import the registration information or transfer the product information via XML file.

After installing Tidal Enterprise Orchestrator, refer to the following paths:

File Name Location:

Default installation path C:\Program Files\Cisco\Tidal Enterprise Orchestrator

Default log/trace file path C:\Documents and Settings\[local user]\Local Settings\Application Data\Cisco\Tidal Enterprise Orchestrator

Default configuration file C:\Program Files\Cisco\Tidal Enterprise Orchestrator\Configuration Data

B-1Cisco TEO Getting Started Guide for SAP

Appendix B Registering TEO with SAP System Landscape Directory Registering Tidal Enterprise Orchestrator

Registering Tidal Enterprise OrchestratorPrior to registering the product with SLD, you must obtain the following information for the SLD server:

• Host—Name of the server hosting the SLD

• Port—Port number used for the server hosting the SLD

• User—User name assigned to the account logging onto the SLD (User must have a LcrInstanceWriterLD role.)

• Passwd—Password assigned to the user account logging onto the SLD

Registering the Product ManuallyYou can manually register the product to the SLD by creating a product name/version and software component name/version in the software catalogue of the SLD.

Step 1 Log on to the SLD.

Step 2 Click Products > New Product Version and enter the following information:

• Product name—Tidal Enterprise Orchestrator

• Vendor name—Cisco Systems Inc

• Product version—V2.1

Step 3 Click Create.

Step 4 In the fourth empty field, enter the following information:

• Technical name—TIDAL_ENTERPRISE_ORCHESTRATOR

• Software component name—Tidal Enterprise Orchestrator

• Software component version—V2.1

• Production state—released

Step 5 Click Create.

To Import RegistrationYou can also import the product information to register it to the SLD.

Step 1 Log on to the SLD.

Step 2 Click Administration > Content > Import.

Step 3 In the Selected File field, enter the path to the SLD data zip file and then click Import Selected File.


OL-25161-02


Transfer Registration via XMLYou can also register the product information by transfering it via the XML file.

Step 1 Create the following folder to store the files:

C:\Example

Step 2 Copy the Test.class and the ThirdPartySystem.xml files into the folder.

Step 3 Enter the following command with the provided XML file:

- java -cp . example/Test SLD_host http_port user password ThirdPartySystem.xml

For example, enter the following:

C:\example>java -cp "../.." example.Test iccsolman40.sap.com 80 3rd_party isvconnect08 ThirdPartySystem.xml

After running the command, Retcode:200 displays.


OL-25161-02



OL-25161-02

OL-25161-02

I N D E X

A

ABAP application server 4-4, 4-11

ABAP system connection information 4-5, 4-12

about

configuring SAP system targets 4-3

creating SAP System targets 4-1

runtime users 3-1

accessing

extended target properties 6-1

global variables 7-1

task rules 5-2

access rights

DB2 database 1-13

Oracle database 1-13

SAP User account 1-10

adapter system requirements 1-5

adding assignees 5-4

approver for SAP incidents, specifying 2-3

assignments and notifications 5-1

assign task rule, creating 5-5, 5-9

Automation Pack Import Wizard

launching 2-2

automation packs

importing 2-1

C

configuration requirements 1-10

configuring


SAP System target 4-3

SAP System target on Java application server 4-20

task rules 5-3

connection information 1-15

ABAP system 4-5, 4-12

SAP database 4-7, 4-14

connection string 4-9, 4-16

copying task rules 5-13

creating

assign task rule 5-5, 5-9

notify task rule 5-10

SAP System target on Java server 4-20

SAP System targets, about 4-1

update task rule 5-11

credentials

ABAP system, specifying 4-5, 4-12


SAP User 3-3, 3-5

D

DB2 database, access rights 1-13

default

recipient for SAP incidents, specifying 2-3

runtime user, specifying 4-6, 4-13

defining

runtime user 3-4

SAP System target 4-3

SAP System targets 4-1

SAP User 3-2

deleting

runtime user records 3-6

SAP targets 4-28

task rules 5-13

disabling

IN-1Cisco TEO Getting Started Guide for SAP

Index

SAP target 4-27

task rule 5-12

disk space requirements, TEO database 1-7

E

email notifications 5-1

enabling

notification based on assignment processes 5-14

SAP target 4-27

task rule 5-12

extended target properties

accessing 6-1

managing 6-1

F

filtering


G

global variables

accessing 7-1

filtering 7-1

properties 7-3

H

hardware requirements 1-2, 1-9

I

importing

automation packs 2-1

J

Java application server 4-4, 4-11


SAP System target, creating 4-20

Java monitoring 4-16, 4-22

M

managing

extended target properties 6-1

SAP targets 4-27

task rules 5-12

message server, specifying 4-6, 4-13

modifying

global variable 7-3

runtime user records 3-6

monitor

ABAP application server 4-4, 4-11



server availability 4-7, 4-14

N

New SAP System Wizard 4-20

notify task rule, creating 5-10

O

Oracle database, access rights 1-13

P

prerequisites

hardware 1-2

software 1-2

TEO database disk space 1-7

processes

notification based on assignment 5-14

product default settings 1-14

default Windows credentials 1-14

email 1-14

OL-25161-02

Index

SAP ABAP System 1-10

SAP ABAP system 1-14

SAP Java system 1-15

properties

global variable 7-3

R

requirements

hardware 1-2

software 1-2

router string, specifying 4-6, 4-13

runtime user records

defining 3-4

deleting 3-6

modifying 3-6

runtime users

about 3-1

S

SAP database 4-4, 4-8, 4-11, 4-15

connection, specifying 4-7, 4-14

SAP incidents and approvals

specifying default 2-3

SAP system number 4-6, 4-13

SAP System target

defining 4-3

system components, specifying 4-4

SAP targets

enabling 4-27

managing 4-27

SAP User

credentials, specifying 3-3, 3-5

properties 3-3

SAP User, defining 3-2

SAP User account

about 3-1

access rights 1-10

OL-25161-02

server availability

specifying servers 4-7, 4-14

software requirements 1-2, 1-3

sorting task rules 5-13

specifying

application servers, availability monitoring 4-7, 4-14

default runtime user 4-6, 4-13


message server 4-6, 4-13

router string 4-6, 4-13

SAP database connection information 4-7, 4-14

SAP incidents approver 2-3

SAP incidents recipient 2-3

SAP system number 4-6, 4-13

SAP systems to monitor 4-4

SAP User credentials 3-3, 3-5

SQL Server Windows Authentication 1-11

system requirements 1-2

T

targets

deleting 4-28

disabling 4-27

SAP System on Java server, defining 4-20

task rules 5-1, 5-4

accessing 5-2

assign 5-5

conditions 5-7

configuring 5-3

copying 5-13

deleting 5-13

disabling 5-12

enabling 5-12

General properties 5-5

managing 5-12

sorting 5-13

task types 5-6

TEO database


Index

disk space 1-7

TEO Performance Best Practice Guidelines 1-9

U

update task rule, creating 5-11

user accounts

DB2 database 1-13

Oracle database 1-13

SAP 1-10

V

verifying user rights 1-10

SAP User Account 1-10

TEO Server 1-10


OL-25161-02