84162823 SAP TAO Administrator Guide

Administrator’s Guide

SAP Test

Acceleration and

Optimization 2.0

Target Audience

Quality administrators

Application testers

Document version: 2.0.07 (September 27, 2011)

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, System z9, z10, z9,

iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,

OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,

Power Architecture, POWER6+, POWER6, POWER5+, POWER5,

POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System

Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,

OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,

WebSphere, Netfinity, Tivoli and Informix are trademarks or

registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and

other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems Incorporated in

the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks of

Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. All other product and

service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express

warranty statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an additional

warranty.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is

only to be used by SAP’s Support Services and may not be

modified or altered in any way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:

http://service.sap.com/instguides

SAP AG

Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Terms for Included Open

Source Software

This SAP software contains also the third party open

source software products listed below. Please note that for

these third party products the following special terms and

conditions shall apply.

1. This software was developed using ANTLR.

2. gSOAP

Part of the software embedded in this product is gSOAP

software. Portions created by gSOAP are Copyright

(C) 2001-2004 Robert A. van Engelen, Genivia inc. All

Rights Reserved.

THE SOFTWARE IN THIS PRODUCT WAS IN PART

PROVIDED BY GENIVIA INC AND ANY EXPRESS

OR IMPLIED WARRANTIES, INCLUDING, BUT

NOT LIMITED TO, THE IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN

NO EVENT SHALL THE AUTHOR BE LIABLE

FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED

AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE)

ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY

OF SUCH DAMAGE.

3. SAP License Agreement for STLport

SAP License Agreement for STLPort between

SAP Aktiengesellschaft

Systems, Applications, Products in Data Processing

Neurottstrasse 16

69190 Walldorf, Germany

(hereinafter: SAP)

and

you

(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive,

non-transferrable, royalty-free license to use

the STLport.org C++ library (STLport) and its

documentation without fee.

B) By downloading, using, or copying STLport or

any portion thereof Customer agrees to abide

by the intellectual property laws, and to all of

the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled

with STLport (whether original or modified)

without any royalties or restrictions.

D) Customer shall maintain the following

copyright and permissions notices on STLport

sources and its documentation unchanged:

Copyright 2001 SAP AG

E) The Customer may distribute original or

modified STLport sources, provided that:

o The conditions indicated in the above

permissions notice are met;

o The following copyright notices are retained

when present, and conditions provided in

accompanying permission notices are met:

Coypright 1994 Hewlett-Packard

Company

Copyright 1996,97 Silicon Graphics

Computer Systems Inc.

Copyright 1997 Moscow Center for

SPARC Technology.

Copyright 1999,2000 Boris Fomitchev

Copyright 2001 SAP AG

Permission to use, copy, modify, distribute and

sell this software and its documentation for

any purposes is hereby granted without fee,

provided that the above copyright notice appear

in all copies and that both that copyright notice

and this permission notice appear in supporting

documentation. Hewlett-Packard Company

makes no representations about the suitability

of this software for any purpose. It is provided

“as is” without express or implied warranty.


sell this software and its documentation for any

purpose is hereby granted without fee, provided

that the above copyright notice appear in all

copies and that both that copyright notice and

this permission notice appear in supporting

documentation. Silicon Graphics makes no

representations about the suitability of this

software for any purpose. It is provided “as is”

without express or implied warranty.


sell this software and its documentation for

any purposes is hereby granted without fee,

provided that the above copyright notice appear

in all copies and that both that copyright notice

and this permission notice appear in supporting

documentation. Moscow Center for SPARC

makes no representations about the suitability

of this software for any purpose. It is provided

“as is” without express or implied warranty.

Boris Fomitchev makes no representations

about the suitability of this software for any

purpose. This material is provided "as is", with

absolutely no warranty expressed or implied.

Any use is at your own risk. Permission to

use or copy this software for any purpose is

hereby granted without fee, provided the above

notices are retained on all copies. Permission

to modify the code and to distribute modified

code is granted, provided the above notices

are retained, and a notice that the code was

modified is included with the above copyright

notice.

Permission to use, copy, modify, distribute

and sell this software and its documentation

for any purposes is hereby granted without

fee, provided that the above copyright notice

appear in all copies and that both that copyright

notice and this permission notice appear in

supporting documentation. SAP makes no

representations about the suitability of this

software for any purpose. It is provided with a

limited warranty and liability as set forth in the

License Agreement distributed with this copy.

SAP offers this liability and warranty obligations

only towards its customers and only referring

to its modifications.

b) Support and Maintenance

SAP does not provide software maintenance for the

STLport. Software maintenance of the STLport

therefore shall be not included.

All other services shall be charged according to the

rates for services quoted in the SAP List of Prices

and Conditions and shall be subject to a separate

contract.

c) Exclusion of warranty

As the STLport is transferred to the Customer on a

loan basis and free of charge, SAP cannot guarantee

that the STLport is error-free, without material

defects or suitable for a specific application under

third-party rights. Technical data, sales brochures,

advertising text and quality descriptions produced

by SAP do not indicate any assurance of particular

attributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall only

be liable for damage, including unauthorized

operation, if this (i) can be compensated under

the Product Liability Act or (ii) if caused due to

gross negligence or intent by SAP or (iii) if based

on the failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intent

caused by employees who are neither agents or

managerial employees of SAP, the total liability

for such damage and a maximum limit on the

scope of any such damage shall depend on

the extent to which its occurrence ought to

have anticipated by SAP when concluding the

contract, due to the circumstances known to

it at that point in time representing a typical

transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not

be liable for indirect damage, consequential

damage caused by a defect or lost profit.

D) SAP and the Customer agree that the typical

foreseeable extent of damage shall under no

circumstances exceed EUR 5,000.

E) The Customer shall take adequate measures

for the protection of data and programs, in

particular by making backup copies at the

minimum intervals recommended by SAP. SAP

shall not be liable for the loss of data and its

recovery, notwithstanding the other limitations

of the present Art. 4 if this loss could have been

avoided by observing this obligation.

F) The exclusion or the limitation of claims in

accordance with the present Art. 4 includes

claims against employees or agents of SAP.

4. Adobe Document Services

Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either registered trademarks or trademarks of

Adobe Systems Incorporated in the United States and

/ or other countries. For information on Third Party

software delivered with Adobe document services and

Adobe LiveCycle Designer, see SAP Note 854621.

Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example

text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see

Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

July 2011

7

Change History The administrator‟s guide is regularly updated on SAP Service Marketplace at http://service.sap.com/instguides.

Make sure you have the latest version of the administrator‟s guide by checking SAP Service Marketplace immediately before starting the installation.

The following table is an overview of the most important changes made in the latest versions.

Administrator’s Guide Version Important Changes

SAP Test Acceleration and Optimization 1.0 (August 7, 2008)

First version – no changes

SAP Test Acceleration and Optimization 2.0 (September 1, 2009)

SAP Test Acceleration and Optimization can record the user interactions and sequence of screens in a business process. This information is stored in the repository, for analysis. You can analyze the impact of changes due to upgrades or SAP patches, or custom development, on a test case, component, or consolidated component, and regenerate the affected components.

SAP Test Acceleration and Optimization 2.0 SP01 (October 26, 2009)

SAP Test Acceleration and Optimization displays the properties of the objects in SAP GUI.

You can now attach documentation (online or offline) to SAP Test Acceleration and Optimization.

The title of this guide has been changed from User Guide to Administrator’s Guide.

SAP Test Acceleration and Optimization 2.0 SP02 (May 17, 2010)

A new function, Self Check, to verify the prerequisites for operating SAP Test Acceleration and Optimization, has been introduced.

A new version of the RTL is provided.

SAP Test Acceleration and Optimization 2.0 SP04 (Nov 15, 2010)

The Self Check function has been improved, to verify:

User accounts in a managed system and SAP Solution Manager system are authorized to use SAP Test Acceleration and Optimization

STPI SP level

Path of the saplogon.ini.file

Existence and accessibility of the folder to contain data table files generated for test cases created during process flow analysis

SAP Solution Manager user has roles with authorization to create or update TBOM

Multiple prerequisites at the same time

The Object Spy functionality has been improved to:

Locate SAP GUI control that was spied on

Improve display spy results and sub-

Administrator’s Guide: SAP Test Acceleration and Optimization

8 July 2011

items

Display SAP Test Acceleration and Optimization RTL components related to the UI control that has been spied on

The invalid tests and their total number are displayed in a separate tab page, for consolidation.

The dependent tests (parents and children) of multiple tests can be identified at the same time and added to the consolidation list.

SAP Test Acceleration and Optimization 2.0 SP06 (July 25, 2011)

During configuration, you can:

Enable inspection to distinguish between simple text fields and fields with F4 help

Set how old can the entries of logs and traces in the investigation info be

This helps you to control the size of log files.

Process Flow Analysis, Inspection, and UI Scanning have been consolidated in Design module for faster access to create test cases and components.

You can execute multiple test cases at the same time to create multiple TBOMs.

You can create test sets from Change Analyzer.

July 2011

9

Contents

Change History …………………………………………………………7

1 Introduction ………………………………………………………..10

1.1 About this Document ............................................................................ 10

1.2 Before You Start ……………………………………………………………13

2 System Landscape ………………………………………………………..15

2.1 Landscape Components ....................................................................... 15

2.2 Hardware Requirement ......................................................................... 15

2.3 Operating Systems Supported ............................................................. 16

3 Installation ………………………………………………………..17

3.1 Installing Components .......................................................................... 17

3.2 Installing ST-TAO 200 Add-On and ST-PI Plugin ................................ 18

3.3 Applying Support Packages on ST-TAO 200 Add-On and ST-PI Plug-in …………………………………………………………….19

3.4 Installing SAP Test Acceleration and Optimization Client ................ 19

4 Configuration ………………………………………………………..20

4.1 Role Setting ……………………………………………………………20

4.2 Configuring SAP Quality Center .......................................................... 20

4.3 Creating an Application Area in QuickTest Professional .................. 21

4.4 Verifying the License ............................................................................ 22

4.5 Connecting to a Managed System ....................................................... 23

4.6 Connecting to SAP Quality Center Server .......................................... 23

4.7 Configuring SAP Test Acceleration and Optimization ....................... 24 4.7.1 Set up Inspection ........................................................................................................ 24 4.7.2 Set up Transfer of Components .................................................................................. 26 4.7.3 Set up Execution ......................................................................................................... 27 4.7.4 Set up Consolidation ................................................................................................... 28 4.7.5 Set Folder for BPCA ................................................................................................... 30 4.7.6 Set Log Levels ............................................................................................................ 31 4.7.7 Set up Process Flow Analyzer .................................................................................... 32 4.7.8 Set Application Behavior ............................................................................................. 34 4.7.9 Linking Documentation ............................................................................................... 35 4.7.10 Configuring Runtime Libraries .................................................................................. 36 4.7.11 Checking the Configuration ...................................................................................... 37

5 Security ………………………………………………………..39

6 Additional Information ....................................................................... 42

6.1 Using SAP Test Acceleration and Optimization (Hints and FAQ) ..... 42 6.1.1 SAP Test Acceleration and Optimization Inspection .................................................. 42 6.1.2 Understanding the Runtime Library Structure ............................................................ 42 6.1.3 Component Folder in SAP Quality Center .................................................................. 43 6.1.4 Performance during Testing ....................................................................................... 43 6.1.5 Use of SAP Quality Center or QuickTest Professional Output Parameters ............... 44 6.1.6 Consolidation .............................................................................................................. 44 6.1.7 Character Removal from Test Plan Name .................................................................. 44

6.2 Working with QuickTest Professional (Hints and FAQ) Error! Bookmark not defined.

1 Introduction

10 July 2011

1 Introduction This guide describes the installation and first steps in the use of SAP Test Acceleration and Optimization.

1.1 About this Document

Purpose

The highly secure and mission-critical nature of enterprise resource planning (ERP) data requires many SAP customers to test their ERP applications and business processes regularly. Many SAP customers use expensive customized manual procedures to test processes and applications. Manual testing is time-consuming, and frequently requires a team of experienced quality assurance (QA) professionals. Subject matter experts also often need to spend a lot of time communicating the process data flow to testers.

SAP Test Acceleration and Optimization streamlines the creation and maintenance of ERP business process testing.

SAP Test Acceleration and Optimization helps QA specialists to break down a test into components which are:

Assembled into test cases in a simple interface, using drag and drop

Parameterized for flexible reuse, such as reusing a test that has updated data

Maintained easily and inexpensively, even when screens, flows, or service packs change

SAP Test Acceleration and Optimization is designed for SAP-GUI-based applications. SAP Test Acceleration and Optimization users should be experienced quality managers who are familiar with the SAP Quality Center application by HP, SAP GUI ERP applications, and business process testing.

Automatic testing with SAP Test Acceleration and Optimization maximizes:

Testing deployment

SAP Test Acceleration and Optimization, with SAP Quality Center, dramatically reduces the amount of time required to build and execute test scripts.

Reuse

SAP Test Acceleration and Optimization eliminates the need to create new tests whenever a component changes. If one component in a group of tests changes, replace that component, and re-consolidate the tests.

Maintenance

SAP Test Acceleration and Optimization records component parameters. It provides a Microsoft Excel spreadsheet to save parameters for reuse and maintenance. SAP Test Acceleration and Optimization helps you to determine the need for repairs, and helps you to repair your components.

Robustness

The SAP Test Acceleration and Optimization inspection process ensures that SAP Test Acceleration and Optimization tests are more robust during changes. Inspection examines the parameter in a component, not just the screen object behavior.

Integration

SAP Test Acceleration and Optimization requires products from SAP, QuickTest Professional, and SAP Quality Center.

1 Introduction

July 2011

11

Functional Blocks

SAP Test Acceleration and Optimization examines SAP GUI screens and transactions, and creates components and tests in SAP Quality Center from the results of this examination. It improves the runtime performance of the tests in SAP Quality Center, by consolidation. This helps you to maintain and adapt them. SAP Test Acceleration and Optimization Windows Client comprises the following functional blocks:

Process flow analyzer

The process flow analyzer (PFA) records all user interactions, and the sequence of screens, in a business process, and stores them in the SAP Test Acceleration and Optimization repository. It automates inspection, retrieval of dynamic SAP GUI properties at runtime, and creation of components.

The PFA, together with RTL and components, provides check points in the recording, which allow certain actions and verify display texts and properties of some controls.

Inspection

Inspection of a screen helps you to create a screen component, which contains the controls (such as text fields, labels, and dropdown boxes) on the screen. This information is gathered from the definition of the screen in the managed system. The inspection fails if the screen is defined dynamically at runtime (dynamic screen).

SAP Test Acceleration and Optimization application has two modes of inspection.

The Inspection tab page in the SAP Test Acceleration and Optimization client selects multiple SAP GUI screens and transactions for testing, in an easy-to-use interface. It then determines whether these screens are valid, and sends them to SAP Quality Center as screen components. Use the PFA to record dynamic screens.

The UI Scanner tab page collects information from one screen at a time, and sends screen objects to SAP Quality Center, as components. The UI scanner requires QuickTest Professional on your local work station. Use the PFA to record dynamic screens.

The inspection of screens is included in the PFA. Use PFA first, to automate the testing of business processes. You use the inspection first for the screens that cannot be recorded using PFA.

Run and Report

Run and Report runs tests, and views test execution and technical bill of materials (TBOM) association and creation reports. You can navigate to the log files from the report, for detailed analysis.

Consolidation

Consolidation creates a single component from the objects and data in an SAP Quality Center test. The component contains all the code and screen elements in a test. It executes much faster than the individual components and helps you to maintain business processes. Consolidation also takes dependent tests into account.

The parameter of a basic component is available for a consolidated component, only if a value has been set for the parameter before consolidation. You can still edit this parameter after consolidation. If you add a parameter to the basic component after consolidation, you need to reconsolidate the basic component.

Consolidation synchronizes the content in the data table (number of lines), and the iterations of the component in the test which makes use of it (generated by SAP Test Acceleration and Optimization while consolidating the intial test).

Import/export

Import/export exchanges components between the SAP Test Acceleration and Optimization client and SAP Quality Center. It also performs maintenance functions,

1 Introduction

12 July 2011

such as moving components between servers or projects. The import/export module does the following.

Export components from the inspector in the SAP Test Acceleration and Optimization client to SAP Quality Center

Import components from SAP Quality Center to the SAP Test Acceleration and Optimization client

Export components from the local memory to SAP Quality Center

Export a component from the UI scanner and send it to SAP Quality Center, in the background

PFA also uses import/export while creating the test components.

Change analysis

Change analysis analyzes the impact of changes due to upgrades, SAP patches, or custom development, on a test, component, or consolidated component. The impact is found by comparing the results of the technical bill of materials (TBOM), transport requests and SAP patches.

Repository

The SAP Test Acceleration and Optimization repository is part of the SAP Solution Manager system, and stores data required to create, optimize and maintain components and tests. The repository contains the following:

User interactions and the sequence of screens in a business process

Information specific to SAP Test Acceleration and Optimization, that cannot be retrieved by other tools

Results or states during process flow analysis, before the component is created

The SAP Test Acceleration and Optimization repository tools comprise the following.

Component explorer

The component explorer views the list of components in a domain and project.

PFA explorer

The PFA explorer displays the analyses performed by PFA.

Self-Check

Self-Check verifies whether the installation is complete, and that the prerequisites for executing SAP Test Acceleration and Optimization are met.

Typical Use Case

This section describes how to test a simple business process with SAP Test Acceleration and Optimization and SAP Quality Center. You must have access to the SAP managed system that executes the business process transactions you are testing, SAP Quality Center, and the SAP Test Acceleration and Optimization client which is connected to your SAP Solution Manager system. For information on installing, configuring, and connecting SAP Test Acceleration and Optimization, see Chapter 3 Installation [page 17] and Chapter 4 Configuration [page 20].

...

1. Discuss the process flow with a subject matter expert.

2. Create a business process test of the process, with detailed steps.

3. Use the SAP Test Acceleration and Optimization process flow analyzer to record your business process and upload the results into SAP Quality Center.

4. Open SAP Quality Center, to verify the components and tests generated.

5. Verify the test.

1 Introduction

July 2011

13

6. In SAP Test Acceleration and Optimization, consolidate the test into a single component that consists of a transaction code and screen operations.

7. Execute the test.

8. Review the test for any discrepancies.

1.2 Before You Start The following sections provide information about:

SAP Notes for the installation

Information available on SAP Service Marketplace

1.2.1 SAP Notes for Installation and Upgrade Read the following SAP Notes before you start the installation or upgrade. The SAP Notes contain the most recent installation information, and corrections to the installation documentation.

Make sure that you have the up-to-date version of the SAP Notes, which you can find on SAP

Service Marketplace at http://service.sap.com/notes.

SAP Note Number

Title Description

1378813 List of Limitations of SAP TAO Release 2.0

Lists the known limitations of SAP Test Acceleration and Optimization.

1508606 TBOM content small or empty when recording TBOMs

Provides trouble shooting information for TBOM.

1368112 Installing ST-TAO 200 on SAP Solution Manager 7.0 EHP1

Provides the procedure for downloading ST-TAO 200 to the SAP Solution Manager system.

1228898 Installation/delta upgrade of ST-PI 2008_1

Provides information on installing agents in the managed system.

147519 Maintenance strategy/deadlines SAP GUI

Explains the maintenance strategy for SAP GUI for Microsoft Windows and SAP GUI for Java.

1609004 SAP TAO 2.0. Release Information SP06

Provides the release and upgrade information for SAP Test Acceleration and Optimization 2.0 SP06.

1.2.2 Information Available on SAP Service Marketplace For information about the following areas, see SAP Service Marketplace at

http://service.sap.com.

General Quick Links

Description Internet Address Title

http://service.sap.com/notes

https://service.sap.com/sap/support/notes/1378813





https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1609004

http://service.sap.com/

1 Introduction

14 July 2011

SAP Notes http://service.sap.com/notes –

Released platforms http://service.sap.com/platforms –

System sizing http://service.sap.com/sizing Quick Sizer tool

Front-end installation

http://service.sap.com/instguides Front End Installation Guide

Security http://service.sap.com/security –

http://service.sap.com/notes

http://service.sap.com/platforms

http://service.sap.com/sizing


http://service.sap.com/security

2 System Landscape

July 2011

15

2 System Landscape This chapter contains information about landscape components and hardware requirements.

2.1 Landscape Components The SAP Test Acceleration and Optimization landscape consists of the following technical components:

SAP Managed System

The SAP R/3 or SAP ERP managed system (version 46C or later) allows you to realize your business processes. The managed system contains screens, transactions and their metadata. SAP Test Acceleration and Optimization makes use of this information, for example, during inspection.

SAP Test Acceleration and Optimization helps you to create or update a TBOM associated with a test, during its execution. To perform a test design and execution scenario, scripting must be enabled on the managed system and the front end.

SAP Solution Manager

SAP Solution Manager verifies your license, which is a prerequisite for using SAP Test Acceleration and Optimization. The Business Process Change Analyzer (BPCA) functions available in SAP Solution Manager are used by SAP Test Acceleration and Optimization interfaces during change analysis and TBOM creation or update.

SAP Solution Manager provides the repository, as described in the previous section.

SAP Quality Center

The SAP Test Acceleration and Optimization application uses the following components from SAP Quality Center:

SAP Quality Center

SAP Quality Center is a complete system for automatic and manual testing. It enables both non-professionals and QA experts to streamline the testing of SAP applications and business processes. It reduces test maintenance and simplifies test creation, with drag and drop functionality. Together with the SAP R/3 server and SAP Test Acceleration and Optimization, it constitutes a complete automatic testing environment.

QuickTest Professional

QuickTest Professional is an automatic test solution for functional and business process applications. It captures, verifies, and replays user interactions, automatically. SAP Test Acceleration and Optimization uses QuickTest Professional recording features with the UI scanner. QuickTest Professional can also execute the components of a business process test in SAP Quality Center.

SAP Test Acceleration and Optimization Client

SAP Test Acceleration and Optimization client is the central point of integration between SAP managed system, SAP Solution Manager, SAP Quality Center, and QuickTest Professional.

2.2 Hardware Requirement RAM: 4 GB

Free disk space: 500 MB

Direct LAN connection (fast ethernet) to SAP Quality Center server and SAP Solution Manager

2 System Landscape

16 July 2011

2.3 Operating Systems Supported Microsoft Windows 2000

Microsoft Windows 2003 (32 bits)

Microsoft Windows XP (32 bits)

Microsoft Vista (32 bits)

Microsoft Windows 7 (32 or 64 bits)

3 Installation

July 2011

17

3 Installation This chapter contains information about how to install and configure the components in the SAP Test Acceleration and Optimization landscape. For information on various compatible versions of components supported by SAP Test Acceleration and Optimization, see

http://service.sap.com/testing Test Management Additional Information

Test Management Compatibility Matrix SAP SolMan, SAP QC, Adapter & SAP TAO.

Invalid combinations might result in wrong data with no error messages. For example, if you execute SAP Test Acceleration and Optimization 2.0 SP2 client with ST-TAO SP1 backend, it would lead to incomplete SAP Quality Center components during PFA recording, because SP1 repository does store all the required data.

3.1 Installing Components

Prerequisites You have installed:

The appropriate version of SAP Solution Manager after checking the compatability matrix

A valid SAP front-end (SAPGUI) with the latest patch level

For information on maintenance strategy, see SAP Note 147519.

Microsoft .Net Framework 3.0 or higher

Microsoft Excel 97 or higher

You have administration rights.

Procedure 1. In the SAP Solution Manager system, install ST-TAO 200 add-on.

For more information, see 3.2 Installing ST-TAO 200 Add-On and ST-PI Plugin [page 18].

2. In the managed system, install the ST-PI plug-in.

The ST-PI plugin provides the SAP Test Acceleration and Optimization agent TAO 2.0, TAOAGENT. In the last release, this agent was TAO 1.0, TMW_TAOAGENT, and was available in the SAP _BASIS layer, which is no longer supported, so you have to install this plug-in. For more information, see 3.2 Installing ST-TAO 200 Add-On and ST-PI Plugin [page 18].

3. Install support package on ST-TAO 200 add-on.

For more information, see 3.3 Applying Support Packages on ST-TAO 200 Add-On and ST-PI Plug-in [page 19].

4. On the system where SAP Test Acceleration and Optimization client is to be installed, install SAP Quality Center.

SAP Test Acceleration and Optimization installer verifies the existence of SAP Quality Center. For information on the requirements for installing SAP Quality Center, see https://h10078.www1.hp.com/cda/hpms/display/main/hpms_content.js

p?zn=bto&cp=1-11-127-24%5E9679_4000_100__.

5. Install the following SAP Quality Center-specific add-ins:

HP Quality Center Connectivity add-in

HP Quality Center System Test Remote Agent

https://websmp101.sap-ag.de/testing


https://h10078.www1.hp.com/cda/hpms/display/main/hpms_content.jsp?zn=bto&cp=1-11-127-24%5E9679_4000_100__


3 Installation

18 July 2011

The names of the add-ins do not start with the word SAP because SAP did not

contribute to them. For more information, see http://updates.merc-int.com/qualitycenter/qc90/index.html.

6. Install HP QuickTest Professional (10 or 11).

Choose SAP Solutions Add-in during installation. For more information, see https://h10078.www1.hp.com/cda/hpms/display/main/hpms_content.js

p?zn=bto&cp=1-11-127-24%5E9674_4000_100__.

7. Install the following QuickTest Professional-specific add-ins:

QuickTest Professional for Business Process Testing add-in

QuickTest Professional add-in (if you are using QuickTest Professional version less than 10)

Depending on the QuickTest Professional version, further patches may be required. For more information, see QuickTest Professional-specific documentation delivered by HP.

8. Install SAP Test Acceleration and Optimization client.

For more information, see 3.4 Installing SAP Test Acceleration and Optimization Client [page 19].

3.2 Installing ST-TAO 200 Add-On and ST-PI Plugin You use this procedure to install the:

ST-TAO 200 add-on in the SAP Solution Manager system, to implement SAP Test Accleration and Optimization-specific functionality

ST-PI solution tools plug-in in the managed system

You cannot uninstall ABAP add-ons.

Prerequisites You have checked the compactability matrix for the appropriate version.

Procedure 1. Navigate to http://service.sap.com/swdc Installations and Upgrades.

2. Search for SAP TAO 2.0.

3. In the installer package, navigate to the SAP_TAO_2_0_ABAP folder.

This folder contains the initial installations for SAP Solution Manager add-on ST-TAO and the tools plug-in ST-PI for the managed system. Do not use the installer for SAP_TAO_2_0_.NET_FRONTEND. Download the appropriate version from support packages and patches section.

4. Install the ST-TAO add-on.

More Information For more information on installation of ST-TAO 200 add-on, see SAP Note 1368112.

For more information on installation of ST-PI plugin, see SAP Note 1228898.

http://updates.merc-int.com/qualitycenter/qc90/index.html

http://updates.merc-int.com/qualitycenter/qc90/index.html



http://service.sap.com/swdc



3 Installation

July 2011

19

3.3 Applying Support Packages on ST-TAO 200 Add-On and ST-PI Plug-in

Procedure 1. Navigate to http://service.sap.com/swdc Support Packages and Patches.


3. Apply the patches in the section Comprised Software Component Version – ST-TAO 200.

4. Install SAP Note, if required.

For example, you might need to install SAP Note 1520410 for SAP Test Acceleration and Optimization (SP4).

3.4 Installing SAP Test Acceleration and Optimization Client You use this procedure to install the SAP Test Acceleration and Optimization.

Prerequisites You have uninstalled the existing version of SAP Test Acceleration and Optimization client, using standard Microsoft Windows tools.

The customized settings are not lost when the current version is uninstalled.

Procedure 1. Navigate to http://service.sap.com/swdc Support Packages and Patches.


3. Install SAP Test Acceleration and Optimization, using the standard Microsoft Windows installer (setup.exe).

The installation of a new version will reuse the customized settings, such as connections and options, from the existing version.

4. Follow the instructions in the wizard.



4 Configuration

20 July 2011

4 Configuration This chapter contains information about configuring components in the landscape.

4.1 Role Setting SAP Test Acceleration and Optimization contains standard roles for SAP Solution Manager. For more information on configuring the SAP Solution Manager system and the managed system, see Customizing for SAP Test Acceleration and Optimization.

4.2 Configuring SAP Quality Center This procedure uploads the runtime library file to SAP Quality Center. You perform this procedure for each project in SAP Quality Center.

Procedure 1. To launch SAP Quality Center, do one of the following:

In the SAP Test Acceleration and Optimization client, click on SAP Quality Center.

In the browser, enter the SAP Quality Center server URL.

2. In the SAP Quality Center Site Configuration, set the following parameters:

DISABLE_EXTENDED_STORAGE=N

BACKWARD_SUPPORT_ALL_DOMAINS_PROJECTS=Y

3. Navigate to the Test Plan.

4. In the Subject folder, create a folder named BPT Resources.

5. In the BPT Resources folder, create a folder named Libraries.

Do not perform Steps 4 and 5 in Test Resources.

6. In the Libraries folder, upload the file <Runtime libraries installation

path>\CBASE_Init.vbs.txt.

The runtime libraries delivered with SAP Test Acceleration and Optimization are

located in C:\Program Files\SAP\SAP TAO\CBASE. You can also use a file

shared with other projects or users. For an example, see Figure 1.

4 Configuration

July 2011

21

Figure 1: Configuring SAP Quality Center (10.00)

4.3 Creating an Application Area in QuickTest Professional SAP Test Acceleration and Optimization components require an application area that contains the QuickTest Professional and web add-ins.

Prerequisites You have enabled execution of tests by other HP products, in QuickTest Professional.

Procedure 1. Launch the QuickTest Professional.

2. Add the SAP and Web add-ins.

3. Create an application area with the name _SAP_Doc.

For more information, see QuickTest Professional-specific documentation delivered by HP.

4 Configuration

22 July 2011

4.4 Verifying the License This procedure checks the license using SAP Solution Manager. SAP Test Acceleration and Optimization has a server-based licensing model. An SAP Solution Manager (with SP 20 or higher) instance distributes licenses to the clients.

You can use the features of SAP Test Acceleration and Optimization only if the license is approved.

Prerequisite You are authorized to access the SAP Solution Manager system.

You have added the SAP Solution Manager system to SAP Logon.

Procedure 1. On the SAP Test Acceleration and Optimization client, choose Configuration.

2. Choose License tab page.

3. If the SAP Solution Manager system is not listed on the Expert tab page, enable the use of an alternate path to the saplogon.ini file.

4. On the License tab page, enter the user credentials.

For more information on the user and role, see Chapter

[page 38].

5. To test the connection to the SAP Solution Manager system, choose Test SAP Connection.

6. Check the license.

Your local instance of SAP Test Acceleration and Optimization is now enabled.

7. Save your entries.

For more information, see Figure 2.

Figure 2: Verifying the License

4 Configuration

July 2011

23

4.5 Connecting to a Managed System This procedure connects to the managed system from SAP Test Acceleration and Optimization.

Prerequisites

You are authorized to access the managed system.

You know the access path and password for the managed system.

Procedure

1. In the navigation area of SAP Test Acceleration and Optimization client, choose Connect.

2. In the SAP Managed System screen area, select the managed system.

For more information about the screen area, see Figure.

3. Enter the user credentials.

4. To verify the connection to the managed system, choose Test SAP Connection.

5. Save your settings.

SAP Test Acceleration and Optimization saves the user credentials for future use. You can change this information. Only save valid connections. For more information, see Figure 3.

Figure 3: Connecting to the Managed System

4.6 Connecting to SAP Quality Center Server This procedure connects to SAP Quality Center server from SAP Test Acceleration and Optimization.

Prerequisites

You are authorized to access SAP Quality Center server.

You know the access path and password for the SAP Quality Center server.

4 Configuration

24 July 2011

Procedure

1. In the SAP Quality Center by HP screen area, enter the server URL and user credentials.

2. Choose Login.

3. Select a domain and a project.

4. Choose Connect to Project.

SAP Test Acceleration and Optimization can automatically detect the latest version of SAP Quality Center in your system.

5. Save your settings.

SAP Test Acceleration and Optimization saves the user credentials for future use. You can change this information. Only save valid connections. For more information, see Figure 4.

Figure 4: Connecting to SAP Quality Center

4.7 Configuring SAP Test Acceleration and Optimization

4.7.1 Set up Inspection This procedure selects the activities that SAP Test Acceleration and Optimization performs to inspect and create components. You use inspection or UI scanner to generate components, if you want to create a new component to add to an existing test.

4 Configuration

July 2011

25

For an example of inspection, see http://service.sap.com Application Life-Cycle

Management SAP Solution Manager and Tools SAP Test Acceleration and

Optimization SAP TAO How to Guide.

Procedure 1. In the SAP Test Accleration and Optimization client, choose Configuration.

2. Choose Inspect tab page.

3. Select the required options.

Option Purpose

Keep copy of components on local path To maintain a local copy of components from screen inspection

Upload components to SAP Quality Center

To upload the screen components to SAP Quality Center

If this option is not selected, the parameters Overwrite components and Delimiter for Component/Unique Identifier on the Import/Export tab page are used to name new components.

Only deselect this option if necessary.

Display UI Scanner Tab To view the UI Scanner tab page for component creation

This tab page is not displayed by default.

Component path The location of components created during inspection

Duplicate components are overwritten without confirmation.

‘Execute Libraries’ The location of library files

Only deselect this option if necessary.

Component type To specify whether data is to be fetched from the screen (Get) or from a data table (Set)

The Get component saves the value of the supported objects in a

data table field (DT_). All the

parameters in a Get component are

DT_ values. You can use the

values to make a comparison, or as input to another field. The naming convention of Get components is the same as for Set components,

with a suffix of _GET.

Use technical names of parameters Use the technical name instead of the label


4 Configuration

26 July 2011

SAP Quality Center only supports ASCII or numeric names for component parameters, so use this option for languages such as Japanese and Korean, so that SAP Test Acceleration and Optimization uses the technical names to name parameters, not field labels.

Keep non-ASCII characters in component names

To have component names in foreign languages, for example Japanese

Do not distinguish simple text fields and F4 help

To prevent inpection from distinguishing between simple text fields and text fields with F4 help.

Only used this when the execution of the corresponding component fails to find some text fields due to confusion between 'GuiTextField' and 'GuiCTextField' control types.


Figure 5: Set up Inspection

4.7.2 Set up Component Transfer The Import/Export tab page specifies the activities to be performed when transferring components between SAP Quality Center and the SAP Test Acceleration and Optimization client. SAP Test Acceleration and Optimization can overwrite components each time one is uploaded.

4 Configuration

July 2011

27

Procedure 1. Choose Import/Export tab page.


You can activate the repository synchronization tool, which synchronizes the quality center and repository. Do not activate this tool unless requested to do so by SAP.

Option Meaning

Path to imported components The local location of imported components

Local Components Path The local location of exported components

Overwrite components Overwrite the existing components in SAP Quality Center with new ones (recommended). This also updates the tests in the SAP Quality Center which use the components. Import/Export will identify the out-of-date consolidated components.

Delimiter for Component/Unique Identifier

A suffix for a new component, to not overwrite an existing component.

The character # is dynamically replaced by an automatically-incremented number.


Figure 6: Set up Component Transfer

4.7.3 Set up Execution This procedure sets up Run & Report to execute tests, reporting, and TBOM functionality.

4 Configuration

28 July 2011

Procedure 1. Choose Run & Report tab page.

2. In the Run screen area, enter the following:

Name of the test set folder in SAP Quality Center containing the test set created by SAP Test Acceleration and Optimization.

Prefix of the test set in SAP Quality Center, to execute the test from SAP Test Acceleration and Optimization.

Prefix to be systematically concatenated to the timestamp when creating a new Run List in SAP Quality Center.

3. In the TBOM screen area, activate the TBOM functionality.


Figure 7: Set up Execution

4.7.4 Set up Consolidation This procedure selects the activities to be performed by SAP Test Acceleration and Optimization when consolidating test components.

Procedure 1. Choose Consolidate tab page.


Option Purpose

Create in SAP Quality Center Folder

The location of consolidated components in SAP Quality Center

Overwrite consolidated component in QC

To overwrite a consolidated component after reconsolidation to update the existing tests

4 Configuration

July 2011

29

(recommended).

Delimiter for Component/Unique Identifier

To specify a suffix for a new component, if you do not want to overwrite an existing one

The character # is dynamically replaced by an automatically-incremented number.

Update data table file If set, it will add/update the missing parameters fields in the component data table file

Data Table Prefix To add a prefix for the parameter value. It represents a data table field. We recommend the prefix DT_.

Create Test with Consolidated Component

To create a test which contains the consolidated component.

Create in SAP Quality Center Folder

Location of test in SAP Quality Center

Prefix in Test Name To add a prefix to the test name, appended by the consolidated component name.

Add component name to consolidated script

To put hints in a test script to identify the component.

Prompt for confirmation before consolidating

To display a confirmation window before consolidating a test.

Create „Empty“ Parameters To create an empty parameter representing all parameters that have no value.

Enable individual selection in consolidation list

To prevent dependent tests from being selected during consolidation.

Use Inline Parameters To add parameters other than the following, directly to the consolidated component‟s script:

C1_InitializeContext_DataTablePath

C1_InitializeContext_DataTableRow

C1_InitializeContext_StartingComponent


4 Configuration

30 July 2011

Figure 8: Set up Consolidation

4.7.5 Set Folder for BPCA In this section, you specify:

The folder created in SAP Quality Center to store the test set created by BPCA

Whether to use BPCA result ID as the test set name


4 Configuration

July 2011

31

Figure 9: Set Folder for BPCA

4.7.6 Set Log Levels This procedure sets the log levels and accesses the application logs, RFC logs, registry extracts, temporary PFA files, library files, and environment variables. The logs are written at runtime by the application, to debug issues.

Procedure 1. Choose Log tab page.

2. In the Log Levels screen area, set the log levels.

Field Meaning

Log Level The level of log entries written to the log files.

Displayed Log Level

Filter the importance of messages displayed in the status bar (as well as in the information box, if it is displayed).

Displayed Trace Level

Display Information Box

To view the information screen area in the lower part of SAP Test Acceleration and Optimization client. The information screen area displays the status bar message history. Check this option for debugging or error tracking.

Investigation Information

Collect the information that is useful to solve issues. Use functionality when sending a message to SAP, to speed up investigation by SAP Support.

Display Loaded Assemblies

To view the assembly files currently loaded by the application.

4 Configuration

32 July 2011

The log levels are:

ERROR

WARNING

INFO

DEBUG

DETAILED

3. In the Options screen area, set how old the entries of logs and traces in the investigation info can be.

This helps you to control the size of log files.

For more information on the log levels to be selected, see Figure 10.

Set the Log Level to ERROR to ensure that the information is available for a sufficient time period. The log level can be changed for detailed analysis.

RFC traces should not be active by default, as they create a large amount of data on the local file system.

Figure 10: Set Log Levels

4.7.7 Set up Process Flow Analyzer Process Flow Analyzer generates tests. For an example of process flow analysis, see

http://service.sap.com/saptao Important Links SAP TAO How to Guide.

Procedure On the PFA tab page, make the following settings:

Test Folder Path

The location of the tests created using the PFA, in the SAP Quality Center.

http://service.sap.com/saptao

4 Configuration

July 2011

33

Path to Default Components

The location of default components in the SAP Quality Center. PFA uses this path to access the default components when uploading the analysis and creating a test.

Overwrite Test With Same Name

Automatically replace a test with the same name, when uploading a PFA.

Suffix for Duplicate Test

The suffix for a new test, if you do not want to overwrite the existing one. The character # is dynamically replaced by an automatically-incremented number.

Maximum Number of Tests

The maximum number of PFA analyses that can be stored in the repository, for the current user.

Data Folder

The location of the data table, which is a spreadsheet document. This folder must be accessible during tests since the runtime libraries get the values for the test from the data table. This folder must not be emptied.

Record Output

PFA records the output values, for example values which are output in some screens by the transaction. If not set, only input values are recorded. If this option is switched on, the PFA will create a second spreadsheet to store the recorded outputs.

Output values are recorded only when you use the PFA, so the spreadsheet is not updated when you execute a test. We do not recommend this option because it impacts recording performance and volume

On Failure

The behaviour of SAP Quality Center when a component fails during a test.

Do Not Use Screen Components

Whether screen components are to be inserted in the test. If selected, only default components will be used. Do not select this option unless required.


4 Configuration

34 July 2011

Figure 11: Set up Process Flow Analyzer

4.7.8 Set Application Behavior

Procedure On the Expert tab page, set the following:

Display application behaviour, such as the duration of a tooltip

Alternate path to the folder containing the saplogon.exe file. The saplogon.exe file starts the SAP GUI.

This setting may have to be updated on Microsoft Vista, Microsoft Windows7, or on Citrix-based installation. If the saplogon.exe path is not defined, Process Flow Analyzer cannot be started.

Alternate path to the folder containing the SAP Login.ini file. If this setting is configured incorrectly, SAP Test Acceleration and Optimization will not be able to list the system in the licensing and connection UI.

The communication check active option that enables pinging SAP backend servers regularly


4 Configuration

July 2011

35

Figure 12: Set Application Behavior

4.7.9 Linking Documentation The Others tab page links to the (online or offline) documentation of SAP Test Acceleration and Optimization. The link is set to the online documentation at http://help.sap.com/saphelp_tao20/helpdata/[language]/59/C592CF76844FBBADC7BD8C914CFCC5/frameset.htm by default.

You can specify whether Quick Test Professional should be stopped when SAP Test Acceleration and Optimization is stopped. This option is set by default. For more information, see Figure 13.

http://help.sap.com/saphelp_tao20/helpdata/%5blanguage%5d/59/C592CF76844FBBADC7BD8C914CFCC5/frameset.htm

http://help.sap.com/saphelp_tao20/helpdata/%5blanguage%5d/59/C592CF76844FBBADC7BD8C914CFCC5/frameset.htm

4 Configuration

36 July 2011

Figure 13: Linking Documentation

4.7.10 Configuring Runtime Libraries The runtime libraries (RTL) configuration wizard configures libraries. It starts automatically when you execute SAP Test Acceleration and Optimization for the first time after installation (there must be a valid connection to SAP Solution Manager and license). It can be started manually at any later time, from the RTL tab.

The configuration wizard tries to re-use compatible libraries from previous installations. It automatically creates a backup of older library versions if they cannot be used any more. For more information, see Figure 14.

4 Configuration

July 2011

37

Figure 14: Configuring Runtime Libraries

4.7.11 Checking the Configuration This procedure verifies whether all the components required by SAP Test Acceleration and Optimization have been installed and configured correctly.

Procedure 1. In the navigation area, choose Self-Check.

2. To check individual requirements, do the following:

Using the secondary mouse button, select the requirement.

Choose Start.

3. To check all the requirements, choose Start All.

The result is displayed on the Results tab page. Use the Information screen area to view clear information. The Information screen area is displayed only if you made the required settings on the Log tab page during configuration of SAP Test Acceleration and Optimization.

The Results tab page consists of coloured icons, as follows:

Color Meaning

Red The check has failed. A description is in the Help column and Information box.

Yellow The check has raised a warning. A description is in the Help column and Information box.

Green The check was passed.

4 Configuration

38 July 2011

Some checks with a red or yellow status might have an additional small wand in the bottom right corner of the coloured icon. In this case, you can use the secondary mouse button to start a wizard that helps you to fix the issue.

Ensure that all the checks are green before using SAP Test Acceleration and Optimization.

The application starts some of these checks automatically when connecting to the SAP Solution Manager or managed system backends, and the SAP Quality Center project. This is to ensure that the server to which the application connects is properly configured, or of a supported version. For more information, see Figure 15.

Figure 15: Checking the Configuration

5 Security

July 2011

39

5 Security This section provides an overview of security-relevant information that applies to SAP Test Acceleration and Optimization.

Why Security is Necessary With the increasing use of distributed systems and the Internet to manage business data, the demands on security are also increasing. When using a distributed system, you need to be sure that your data and processes support your business needs, without allowing unauthorized access to critical information. User errors, negligence, or attempted manipulation of your system should not result in loss of information or processing time. These demands on security also apply to SAP Test Acceleration and Optimization. We provide this security information to help you make your SAP Test Accleration and Optimization secure.

Security Guides SAP Test Acceleration and Optimization interacts with the SAP Solution Manager system, managed systems and SAP Quality Center, so their security guides also apply to SAP Test Acceleration and Optimization.

Component Where in the Service Marketplace?


http://service.sap.com/instguides SAP

Components SAP Solution Manager Release 7.0 EHP 1

4 Operations Security Guide

SAP Quality Center


Communication with Components SAP Test Acceleration and Optimization interacts with the SAP Solution Manager system, managed systems, and SAP Quality Center. See Figure 16 for the SAP Test Acceleration and Optimization communication channels.



5 Security

40 July 2011

Figure 16: Communication Channels of SAP Test Acceleration and Optimization

SAP Test Acceleration and Optimization communicates with the SAP Solution Manager system and managed systems, using standard RFC and OTA interfaces. To create these connections, the system generates technical users for the connection. These users are assigned to the profiles for data transfer.

The table below shows the name and type of interface used by SAP Test Acceleration and Optimization to communicate with the SAP Solution Manager system, managed systems and SAP Quality Center:

Name Type Description

SAP_SM_TAO_RFC ABAP Authorization for RFC communication between the SAP Test Acceleration and Optimization repository in SAP Solution Manager and the SAP Test Acceleration and Optimization client assigned to

technical user TAO_RFC. See

Customizing activity: Configuration in SAP

Solution Manager (technical

name: TAO_SM)

SAP_TAO_AGENT_RFC ABAP Authorization for communication between managed system and SAP Test Acceleration and Optimization client. See Customizing activity: Configuration in Managed

System (technical name:

TAO_MANSYS)

5 Security

July 2011

41

OTA COM Authorization for communication between SAP Test Acceleration and Optimization client and SAP Quality Center

Location of User Credentials The table below gives the location of user credentials to logon to a managed system and SAP Quality Center:

Component Registry

Managed system

HKEY_CURRENT_USER\Software\SAP\SAPTAO\UserConfig



SAP Quality Center


The user and password details are encrypted. The encryption mechanism uses

System.Security.Cryptography.ProtectedData class.

Password Encryption The password used by SAP Quality Center to log on to an SAP system during test execution, is encrypted. The encrypted password is in the spreadsheet data table of the test. The encrypted password is generated by SAP Test Acceleration and Optimization during PFA upload. This password is only used by the LaunchAndLogin component.

6 Additional Information

42 July 2011


6.1 Using SAP Test Acceleration and Optimization (Hints and FAQ)

6.1.1 SAP Test Acceleration and Optimization Inspection SAP Test Acceleration and Optimization may not populate all screens associated with transaction codes in the inspection module. If the screens contain dynamically-generated objects and fail continuously during inspection, you can use the default components with the dynamic RTL, to complete a test. For more information, see

http://service.sap.com/instguides SAP Test Acceleration and Optimization

Release 2.0 Default Components SAP TAO 2.0 SP05.

Give priority to PFA over inspection. If the tests uploaded by PFA are incomplete, you can use the default components to complete the test.

SAP Test Acceleration and Optimization inspection can automatically generate components, by searching in metadata with the information of objects in a screen. This data can be stored in a different format, or even not stored in the metadata at all. This can cause the inspection method to return an error when inspecting some screens.

SAP Test Acceleration and Optimization can create a screen by either using the metadata, or by creating objects during execution (runtime). If an object is hidden during runtime, the metadata inspection will not be able to adjust to this change.

Some screens in SAP can be empty containers for dynamically-added content (it may be a screen or a field, depending on the programmer‟s needs). These screens are visible in SAP Test Acceleration and Optimization, but SAP Test Acceleration and Optimization cannot create test components from them. This normally happens when the UI is made up of tree and grids.

For an example on inspection and process flow analysis, see http://service.sap.com

Application Life-Cycle Management SAP Solution Manager and Tools SAP Test

Acceleration and Optimization SAP TAO How to Guide.

6.1.2 Understanding the Runtime Library Structure SAP Test Acceleration and Optimization RTL documentation is provided with the SAP Test Acceleration and Optimization installation. This guide includes a list of the functions in the framework, as well as best practices for creating new functions in the framework.

To help improve SAP‟s support and the overall stability of the runtime library, you need to understand the following CBASE structure:

Standard Libraries

Standard libraries delivered with SAP Test Acceleration and Optimization provide the implementation of the SAP Test Acceleration and Optimization default components.

To ensure stability of the runtime library, do not manually change the standard library files. This also applies to the components uploaded in Quality Center. These are SAP code, and must therefore not be updated manually.

In case of missing functionality in the runtime library or in the default components, develop:




July 2011

43

Custom code (custom wrappers) in the file CBASE_Custom_Wrappers .vbs

Custom components that you can upload to SAP Quality Center project

The custom components need to be added manually to the test script.

Hot Fixes

Hot fixes are delivered by SAP for urgent issues. The corrections are copied to a dedicated subfolder with the CBASE name “HotFixes”. An empty CBASE_HotFixes.vbs file is delivered with SAP Test Acceleration and Optimization in each release

Inform SAP Support if you detect a problem in the functions delivered in standard libraries. Informing SAP ensures that the defects are fixed in the next release of SAP Test Acceleration and Optimization.

To ensure stability of the runtime library, do not change the hot fixes manually.

Custom Libraries

You develop custom components for specific use cases. You copy the custom components to the CBASE_Custom_Wrappers.vbs file. Do not put any custom coding that could have a negative impact, in the standard libraries. Use a customer-specific prefix to all functions and global variables, to avoid potential conflicts.

Obsolete Libraries

Obsolete libraries contain functions such as support for web controls that were delivered with previous releases of SAP Test Acceleration and Optimization, but were not officially supported. Obsolete libraries are not loaded, by default. If your test and test components depend on the obsolete libraries, change the CBASE.Config file, to load them.

For more information, see http://service.sap.com Release & Upgrade Info

Installation & Upgrade Guides SAP Test Acceleration and Optimization Release 2.0 Default Components SAP TAO 2.0 SP5.

6.1.3 Component Folder in SAP Quality Center SAP Test Acceleration and Optimization creates a component folder in SAP Quality Center. If there are 2 folders called Components in the file system path of a component that is being uploaded, the system will create a component folder in SAP Quality Center, behind the components root folder.

Example:

C:\SAPTAORTL\Components\SAP Front End\Actions\LaunchAndLogin

Work-around:

C:\SAPTAORTL\AnotherName\SAP Front End\Actions\LaunchAndLogin

If all folders have different names, the system will not create a new component folder, and will use the component root folder as a reference.

6.1.4 Performance during Testing The runtime library (RTL) supports the SAP GUI scripting API that is used to access the SAP GUI user interface components. This improves the performance during test execution.

Consolidate the tests to optimize the performance during test execution. Initialization is performed only once, and only one component is loaded into the Quick Test Professional from the SAP Quality Center server. For more information on RTL, see

http://service.sap.com/instguides.




44 July 2011

CBASE refers to vbscript libraries only. The RTL refers to CBASE as well as the default components. CBASE and default components are delivered with SAP Test Acceleration and Optimization.

Update the runtime CBASE and default components of the SAP Quality Center project when you install a new version of SAP Test Acceleration and Optimization. For confirmation, run the self-checks under SAP Quality Center by HP, to perform a complete analysis of the project settings.

6.1.5 Use of SAP Quality Center or QuickTest Professional Output Parameters SAP Quality Center and QuickTest Professional provide input and output parameters to pass data between components. The SAP Test Acceleration and Optimization framework only uses input parameters, and determines internally whether the parameter writes information in a data table for other components to use, or is an input to an application.

6.1.6 Consolidation SAP Test Acceleration and Optimization consolidation works directly with the SAP Quality Center OTA API, at back-end level. When using consolidation features, do the following, to prevent damage:

Save the business process before consolidating

If a component will be overwritten by your consolidation:

Ensure that the component is not locked by another user or yourself. Deselect the component from the business component module

If the component being overwritten is being used by a test, select another test in the test plan module

For an example of consolidation, see http://service.sap.com Application Life-Cycle

Management SAP Solution Manager and Tools SAP Test Acceleration and

Optimization SAP TAO How to Guide.

6.1.7 Character Removal from Test Plan Name During consolidation, some characters are removed from the test plan name, for consistency with SAP Quality Center. SAP Quality Center test naming conventions and component naming convention prevent some characters from being used in the component or parameters names. The characters that are not allowed, are in the table below.

) ! Ä @

# $ Ä %

^ & Ö *

+ = ß [

] \ Ö /

{ } Ü &

| ; ü „

: “ spaces ,

( None None None

Table 1: List of Characters Not Allowed


Documents

84162823 SAP TAO Administrator Guide