130614 ibm minimizesaptestingeffort

8/13/2019 130614 IBM MinimizeSAPTestingEffort

http://slidepdf.com/reader/full/130614-ibm-minimizesaptestingeffort 1/42

Minimize SAP Testing efforts

Vendor Name: IBM

Speaker Names/Titles:

James Hunter, IBM Segment Manager for SAP

Steve Pitschke, Lead Developer, IBM Rational Connector for SAP Solution Manager

Abhik Bose,

Moderator: Hello. Welcome to today’s presentation, Minimize SAP Testing Efforts, which is

being brought to you by IBM.

Before we begin, please notes that the slides for this presentation will be pushed to your screenautomatically and all audio will be streamed to you through your computer.

If you have any questions, you can enter them by clicking on the questions tab on the lower-lefthand side of your screen and click submit question. Your questions will be addressed at the end ofthe presentation.

With that said, it is my pleasure to introduce our speakers for today.

Today we will be joining by James Hunter, IBM Worldwide Offering Strategy and DeliveryManager. Also, Steve Pitshke, Lead Developer -– IBM Rational Connector for SAP SolutionManager; and Abhik Bose, Lead Solution Architect, Project Coach -– SAP Value Prototyping andCenter of Excellence.

With that said, it’s my pleasure to pass it over to James to Begin today’s presentation.

James, take it away.



Testing for SAP

James Hunter

IBM WW Offerings Strategy and Delivery Manager

[email protected]

Abhik Bose

SAP Principle Consultant, SAP Global Services

Steve Pitschke

IBM Lead Developer

[email protected]

© 2013 IBM Corporation

James Hunter: Great. Thank you very much everyone for joining us today in this call aroundtesting for SAP.

So let’s get straight into why we’re talking about that testing for SAP today.

Businesschanges

IT changesCompliance

changes

Modified Business Processes

M&A and Reorganizations

New Products, Vendors, etc… Maintenance

Upgrades

Regional rollouts

Governance

Risk Management

Compliance

Examples: SOX, SEC,

FDA, Basel3, etc…

Success depends on yourability to manage change.Success depends on yourability to manage change.

The challenge

For 40 years, IBM and SAP have consistently delivered superior ROI through thousands

of successful implementations.



This really has come about because our customers are telling us that they’re facing a number ofchallenges. When an organization is running on SAP, then the business depends on the success ofhow well they can manage change to that organization.

And they tell us that those changes are coming from a number of different areas which we try to

outline on this particular slide from a business perspective.

We are also merging or acquiring other businesses, even internally themselves; or whether they areresponding to the market, new products, new processes, and so on. There’s a whole host ofcompliance changes that are occurring today.

Moving on to table three, and the changes that take into account. As well as of course, our usualand traditional IT changes -– updates, (fixed access) and improvements; new technology that getsadded or extended; for example, the shift into utilizing mobile, which is significant for today.

All of these changes are affecting or have some impact on how well our organization runs on it’s

SAP infrastructure.

So of course the reason here I’ve been talking about some examples where they estimated that thelarger SAP organization -– you know, their SAP production (is down) for any particular reason -–It costs them between half a million and $800 thousand per hour, which is a tremendous amount.

But fortunately, IBM and SAP have been working together for around 40 years or so to ensure thatwe can help organizations to continue to execute their business on SAP in respect of the changes.

A radical SAP transformation to help us reach our goal of being an

efficient globally integrated enterprise (GIE).

Our own experience



Now, this actually is kind of come about because of our own experiences. We’ve gone to (our loss)on our own journey -– IBM (when we started with) SAP.

We started off many years ago having a number of SAP applications being used in different waysaround the world. Our objective was to identify the best practice, identify which part of SAP were

being used, and then to consolidate them into one, single environment which we call a GlobalIntegration Enterprise.

So we have to look at how do we capture the requirements of our team, of our business, of our partners, and even our customers as well? How do we manage change across large enterprise andwith our partners and other people involved as well?

And with the technology that we use, we ensure we have the governance of this change. How canwe be sure when we make a change that it’s tested, and then we have confidence that our businesscontinue to run?

So we went through this process. And today, we have a globally (inspired) enterprise. We support450 thousand users across 170 countries. And you can imagine that we’re such a large, compleximplementation at SAP. We’re making changes to our environment every single day. And thosechanges require testing and so we can be confident that our partners, ourselves, and our customerscan continue to operate using IBM adequately.

So it’s on this journey that IBM looked at the market, looked at our own technology and capability,and try to identify what would (be the core) capability that we require to implement manage changein SAP.

Well, on the back of that, we identify that there were three core areas that we wanted to look at -–Enterprise Planning, Lifecycle Management, and Testing.

From Enterprise Planning perspective, this is all about being able to identify (what parts) as far asSAP environment were actually being used in the different areas. Once we have captured that, the(soft bits of) information out of it, our different SAP implementations; we were able to get a viewof our SAP and non-SAP usage (on our) enterprise. And then just identify what’s going to be theimpact across our organization where we make a change or implement new applications.



Enterprise planning for SAP Lifecycle management for SAP Testing for SAP

Performancetesting

Impactanalysis

Architect the right

implementation Big picture view of existing

SAP implementation Visualize, analyze, plan and

communicate your SAP

deployment

Add team collaboration and

project transparency Complete application lifecycle

traceability Complete audit trail, process

and automated governance

Manage and test SAP and

non-SAP projects Automated functional and

integration testing Test bus iness process

changes for proper

deployment

Auto mati ontesting

Virtualization &Integration

testing

RationalQuality

Manager

Rational System Architect Rational C/ALM Rational Quality Manager

Reduce the cost and risk of delivering SAP

This is beginning as the first insight into what we’re going to need to prepare to test when we startimplementing SAP.

Once we have a control and a (view) of what are we going to implement from the SAPapplications, when you think about the Lifecycle management, this is being able to capture thoserequirements so we know what to test.

Managing the changes -– things like (defect) tracking, and updates, et cetera.; and of course beginning to identify other tests that we’re going to create to test the requirements against the ITand enterprise architecture that we capture in our enterprise plan.

And then of course the third solution really focuses at around testing. So this is a fundamental pain point for us, and the fundamental requirement to ensure that we can execute our business as weexpect.

So we really look at the -– how we can execute the tests for SAP.

So for a manual testing perspective, we wanted to use our core capability and (take that) into our

plans. We want to have impact analysis. We understand what’s in it. And that’s the testing weneed to do for a particular change or to make a testing. So we want to move away from manualtesting as much as possible.

Integration testing -– because we know like ourselves, many organizations are not just using SAP.They have other (inaudible) and technology as well -– Oracle, (Cisco), Microsoft, HP -– otherthings like that. So we want to be able to test those integrations as well.



Enterprise planning for SAP Lifecycle management for SAP Testing for SAP

Performancetesting

Impactanalysis

Architect the right

implementation Big picture view of existing

SAP implementation Visualize, analyze, plan and

communicate your SAP

deployment

Add team collaboration and

project transparency Complete application lifecycle

traceability Complete audit trail, process

and automated governance

Manage and test SAP and

non-SAP projects Automated functional and

integration testing Test bus iness process

changes for proper

deployment

Auto mati ontesting


testing

RationalQuality

Manager

Rational System Architect Rational C/ALM Rational Quality Manager

Reduce the cost and risk of delivering SAP

And performance testing -– an absolutely key that when we rolled out our capabilities, we need toknow that the hundreds or thousands or maybe even tens of thousands users that are executing andusing our SAP environment will continue to be able to deliver against their expectations of our SAPenvironment.

And lastly, virtualization -– which is where we wanted to be able to simulate a whole environmentas early as possible so we can start testing early in the Lifecycle; so we can start thinking about our

integration testing and our system testing early on before we go live.

So enterprise planning, (then) the Lifecycle management, which leads of course, to testing.

And on this particular Webcast, we’re going to focus on those areas to do with testing for SAP.

So let me go over a little bit deeper into each one of these areas, if I may.

So when we start thinking about testing, we will be capturing our test plans from perhaps, yoursolution manager, if you’re using solution manager; or independently if you’re not.

But if we are using solution manager, then we can start thinking about the impacts of makingchanges to our business process for the (SAP) applications that we actually have in store and areusing.



Minimise testing of SAP changes

Identify the optimized test scope for planned SAP changes.

Automatically create optimized SAP test plans.

Filter on parameters like manual test effort or test coverage.

Performancetesting

Impactanalysis

Auto mati ontesting


testing

RationalQuality

Manager

“BPCA can reduce the test scope for the changes that are coming into SAP landscape, and the integration withRational Quality Manager means there is a seamless way of transferring the impact analysis into end to end

testing, and that will significantly reduce testing efforts for our customers when it comes to managing SAP

changes.” Rajeev Gollapudi, SAP

So for this case we an integration between BPCA -– the SAP Business Process Change Analyzer,which allows us to identify what changes have been made in the business process. And thenautomatically generate (intro Graphical) Quality Manager. They tests (plan) -– that has theminimum amount of testing necessary for us to achieve a level of confidence that the changes thatwe made in our business process will actually work and the rest of our SAP landscape in our SAPenvironment will continue to work as well.

So this becomes very useful because organizations spend a lot of time investing in testing, particularly manual testing and automated testing. So this gives us an opportunity to stop playingaround with some of the parameters.

And what are the levels of risks that we are willing to accept in our organization?

Of course, in a perfect world we will test every single part of our SAP environment for every singlechange that has made. But we all know that that’s probably impractical, and of course very costly.

So using a BPCA gives us the opportunity to identify the minimum amount of testing we need todo, adapt it to the level of tolerance that we’re willing to accept. (And then we create) our test

plans directly in the Rational Quality Manager. So impact analysis allows us to minimize theamount of testing that we need to do.



Automated testing for SAP

Performancetesting

Impactanalysis

Auto mati ontesting


testing

RationalQuality

Manager

Writing code to test code is not the right answer

– Scriptless

– Reusable – Maintainable

– Supports all SAP platforms.

Rational Quality Manager and Certify

Risk Increases Over Time

Business processesTest resources

Risk Increases Over Time

Business processesTest resources

Business processesTest resources Rational Quality Manager and Certify

And in a similar manner, (you can think) about automated testing; again, working with RationalQuality Manager as the hub. We can begin to think about setting those manual tests and begin toautomate these traditional processes.

So why do we do that -– the (Certify) and Rational Quality Manager? This allows us to move awayfrom having to create scripts and same scripts for our automated testing. We want to be able tohave the business users who (are the main experts), start using a system as they would expect it to

use and from there, dynamically create the test that we can then be executed and repeated movingforward.

So the idea is to move away from having expensive manual testing and even expensive test scriptcreated, but move forward to a platform that allows business experts and lower level and identicaluser to be able to start creating tests and (next begin the tests) for the business and (attempts) at the business in itself.

We all know that testing resources are becoming more expensive and in many cases, (has the mostcash) as well.

So this capability around creating scripts automatically to drive (all those into) tests, linking that inthe Rational Quality Manager, which in turn (tie) back all requirements, our change, and solutionmanager; gives us the ability to have this very simple, very cost-free, reusable, and maintainableapproach to automated testing.

So for an automated testing perspective of our applications, we also need to be thinking about theother parts of our SAP landscape -– the other applications and environments, and (legacies) thatwe’re working with.



Integration testing and Test environment virtualisation for SAP

Capture and model virtual services:

– Test the integration of your SAP modules

– Test the integration of your SAP implementation with legacy applications

Rational Integration Tester

Performancetesting

Impactanalysis

Auto mati ontesting


testing

RationalQuality

Manager

Reduce the infrastructure costs of SAP testing environments:

– Virtualize SAP & non SAP hardware, software and services.

– Build virtual services using:

SAP message formats, HTTP, web services, SOA, JMS, TIBCO,

IBM WebSphere MQ, Oracle etc.

Rational Test Virtualization Server Databases Mainframeapplications

SAP app Under Test

Third-partyServices

SAP modules, messaging services, etc.

SAP developers & testers

So we need to think about integration testing and virtualization.

For integration testing -– is about simulating the connection between our SAP environments andour non-SAP environments.

And virtualization -– is beginning to create that testing environment, even perhaps -– maybe it’s not

even available at this time. So perhaps we have an SAP application connecting with a new serverthat’s being built, support our mobile devices. Or maybe we wish to simulate that server so we canstart (testing) against the responses that would be received from that particular server. So we canstart acting our integration testing and making sure that business process will continue to run.

Well, when that’s the case, we can start by creating a virtualized environment. So in this exampleI'm showing on the screen at the moment, we have an SAP application which is on the test. And perhaps we’re simulating or virtualizing our environment which contains databases, mainframeapplications, and third-party services.

So that’s where we would use Rational Test Virtualization Server, to build that environment and to

start showing the information and responses that would come from that particular environment.

Then we would start testing the integration themselves. And that’s when we would use RationalIntegration Test, to start simulating the information that would come from SAP to that third-partyenvironment, and back again.



Integration testing for SAP

Performancetesting

Impactanalysis

Auto mati ontesting


testing

RationalQuality

Manager

Reduce the infrastructure costs of SAP testing environments:

– Virtualize SAP & non SAP hardware, software and services.

– Build virtual services using:

SAP message formats, HTTP, web services, SOA, JMS, TIBCO,

IBM WebSphere MQ, Oracle etc.

Rational Test Virtualization Server Databases Mainframeapplications

SAP app Under Test

Third-partyServices

SAP modules, messaging services, etc.

SAP developers & testers

Capture and model virtual services:

– Test the integration of your SAP modules

– Test the integration of your SAP implementation with legacy applications

Rational Integration Tester

As I suggested in our case, we have 450 thousand users across 170 countries, which means performance testing is a very important part of our own process of making changes inside our SAPenvironment.

So SAP testing -– performance testing at SAP, we use Rational Performance tests. This allows usto start recording our scripts and helps us to utilize our existing automated scripts. And then itallows us to start extracting out the (reports) to identify where the hold-ups are, where the

bottlenecks are in our overall testing environment. And then we could feed these back in theseactual changes or updates through Rational Quality Manager and back into our Lifecyclemanagement environment.

So this way, we can begin to get an understanding of the overall health of our SAP changes insideour environment.

While performance testing is a very important part of our whole SAP application, which is I'm very pleased to be joined today by Abhik Bose from (products and sales).



Performance testing for SAP

Performancetesting

Impactanalysis

Auto mati ontesting


testing

RationalQuality

Manager

Rational Performance Tester

And Abhik, I'm going to ask a few questions to you Abhik. He’s also in the call. And I might juststart, if that’s OK.

And Abhik, if you could introduce yourself and where do you work inside the SAP.

Abhik Bose: Yes, absolutely. Thank you so much James.



Why SAP use IBM Rational for testing SAP

“Our collaboration with IBM Rational brings together the best of our

combined application lifecycle management market leadership and can

help customers reduce costs, manage change, and improve quality across

the enterprise applications lifecycle.”

Uwe Hommel, Executive Vice President, SAP

Abhik Bose

Principle Consultant, SAP Global Services and Head of SAP Value Prototyping

I am a Lead Solution Architect and a Project Coach working for SAP Value Prototyping and Centerof Excellence, where I go ahead and handle multiple SAP customer projects. To take a few names,it’s like the DHLs, AT&Ts, Unilevers of the world. And we get into multiple different types ofrequirements and projects from them. And then also get use RPT as well in those projects.

James Hunter: So Abhik, just to get back to basics perhaps, why do SAP customers run on SAP?What’s the fundamental reason?

Abhik Bose: OK. So most -– (we at SAP), being a product department -– product company alsohave a consulting wing. The customer gets a particular amount of satisfaction, guidance. We haveexperts which go ahead and suggest them on particular ways how they can handle their businesschanges and IT changes for SAP solutions.

And the customers really come back to SAP consulting department to have that advice, not onlycustomers, but partners as well. There are a lot of partners which come back to SAP consultingdepartment because being a wing of a product company, we have a lot of knowledge in theconsulting area for which basically the customers there (collected), to this particular service.

James Hunter: So what do you find that customers want to (about) -– to see what they needtesting of their SAP solutions?

Abhik Bose: OK, good question.

So in the beginning of the slide, you were mentioning about IT changes, business changes andthings like these. Now whenever this change is something which cannot be stopped -– the changewill happen in different layers of the business, IT, and everywhere.



And not all the time, your backend systems will change. It’s the processes and the data whichkeeps changing. And at that time, every change needs also to be tested in different areas when theygo live, or they rule-out because this is very business and business critical systems.

So in these cases, it’s much easier if we have a software to go ahead and (use all your) script, andkeep the script alive. Whenever there is a new change coming in, that change is identified and thescript runs through test if all these of the (ideas) work fine; if it works fine for all the users, whichare multiple users logging in simultaneously, so on and so forth.

So you know, it’s invest once or do once and use many times, of an approach -– which really helps-– and it’s one of the key parts of testing other than whenever a solution is released, of course it hasto be tested so on and so forth.

Does that answer your question?

James Hunter: Yes, thank you so much.

Abhik Bose: Great.

James Hunter: So your team use technology and you use Rational tools. But I'm interested if wego a little bit deeper now.

In your experience, how can Rational tools be used to simulate user loads and the performance ofSAP solutions?

Abhik Bose: Very good question.

So first, it’s always important to do a single-user functional test for a particular business area. Sowhen we work together with the customer, we first go ahead and (scope) exactly the system whichis under test.

We find out if it is a single-system that is under test, or there are multiple systems which are undertest because of a particular business need or a business change, or IT change from the customer’sside.

Once this is scoped down, then there is a single-user test which happens to -– then there is anautomated scripting and then there’s a single-user test happens which -– to automate the scripting.

There are a lot of customers which go into leasing agreements with hardware vendors. They needto find out based on these, I don’t know -– 1 thousand, 15 thousand, 20 thousand concurrent users.What is the amount of hardware that they need? What is the leasing agreement that they want to gointo for the next three years down the line? How do they recover this cost?

But for this, they need a sizing -– real-time sizing data and all that information.



This is exactly where the performance testing tools come into picture, because it is able to simulateso many users; it’s able to ahead and do the testing, do the analysis, store the results in differentgraphical formats the way you configure it as a performance tester; and then present it to thecustomer.

End-to-End testing for SAP – Lifecycle management

Rational Team Concert

• Defec t and Changemanagement

Rational Team Concert

• Defect and Changemanagement

Business BlueprintBusiness Blueprint

Test Planning

and Set-up

Test Planning

and Set-upTest ExecutionTest Execution

Deploy Changesto Production

Deploy Changes

to ProductionChange Impact

Anal ysi s

Change Impact

Analy sisSAP SolutionUpdate

SAP Solution

Update

New SAPSolution

New SAP

Solution

Solution Manager

Business ProcessChange Analyzer

Rational Quality Manager

• Test Pl anni ng

• Tes t Requirements

• Business requirementslinked with test cases


• Test Planning

• Test Requirements


Rational Requirements Composer

• Business to IT requirements


• Business to IT requirements Identification of

business processes

affected by code /

customizing changes

Solution Manager

Business Blueprint

Setup of business

process hierarchy

Business requirements

Solution Manager

Service Desk

Incident Management


• La b Mana gemen t

• D efect Tracking


• Lab Management

• Defect Tracking

This analytics and this information which comes, gives a huge risk mitigation benefits. It giveshuge planning benefits for customers. SAP internally also uses it for a lot of projects internally.

And it also gives a huge benefit to SAP to understand their products -– you know what happenswhen it scales out to so many particular end-users, when an end-user is using a product. Or thereare so many jobs for -– it could be billing, it could invoicing, whatever transactions, critical jobs, orend-user’s kind of activity. It gives SAP or of other companies as well, a chance to find out thelimits of their software; or to level up even software here.

James Hunter: So when you’re using -– running performance testing and use the tools that you(talked) about getting some of use and the analysis that comes from it; what sort of insight do youfind -– do you discover when you’re using the Rational tools and performance testing those SAPsolutions?



Setup of business

process hierarchy


Test Scope

Identification

Test Planning

Test System SetupTest Execution Test Reporting

SoftwareChange

ChangeDeployment

SolutionManager

Business Blueprint

Solution Manager

Business ProcessChange Analyzer

Identification of business

processes affected by

code / customizing

changes


• Test planning


• Manual testing

Rational Quality Manager Test execution and reporting

• Incident m anagement

Service Desk

Impact analysis for SAP

BPCA

Auto mated int egrati on t estin g,

scalability and test virtualization

for SAP

Rational Test Workbench

Rational Performance Server

Rational Test Virtualization Server

Security testing for SAP

Appscan

Auto mated t estin g fo r SAP

Certify

End-to-End testing for SAP – Test execution

Abhik Bose: Good question. So the insight which we go ahead and discover -– they are across thecomplete stack. So you can go ahead and do operating system monitoring.

In today’s world of virtualization, there is all the infrastructure -– which is most of the customersuse infrastructure which are virtualized and they have different application softwares -– SAP andnon-SAP, everything on that platform.

So there is a period of time where they need to find out, when things hanged and they do a performance project, they need to find out who is the culprit.

So these kinds of analysis and these graphs beautifully isolate the problem. And it helps you to seeexactly who is the culprit when something is hanging around or stopping, which then affects yourtransactional system in turn. Because these are all integrated scenarios, they’re integrated to eachother. It’s a heterogeneous landscape.

So when we get these analysis, it goes ahead and helps you to find out the problem exactly where itis. Once we know the problem, then we can bring the solution.



Bringing it together… Rational solutions for SAP

Test Planningand Set-up

Test Planningand Set-up Test ExecutionTest Execution Deploy

to production

Deployto productionChange Impact

Analy sis

Change Impact Analy sis

SAP Solution

Update

SAP Solution

Update

Business BlueprintNew SAP

Solution

New SAP

Solution

Rational Team Concert• Defect, issue & change management

Rational Team Concert• Defect, issue & change management

Business Blueprint

Setup of business

process hierarchy






Service Desk

Incident m anagement

Business Process

Change Analyzer (BPCA)

Identification of business

processes affected by

code / customizing

changes


• Load and stress test


• Load and stress test

Rational System Architect

• Visualize, analyze, and communicate yourenterprise architecture

• Enterprise change and business transformation

Rational System Architect

• Visualize, analyze, and communicate yourenterprise architecture

• Enterprise change and business transformation

Auto mated i nteg ratio n tes ting ,scalability and test virtualization

• Rational Test Workbench

• Rational Performance Server

• Rational Test Virtualization Server

Auto mated i nteg ratio n tes ting ,scalability and test virtualization

• Rational Test Workbench

• Rational Performance Server

• Rational Test Virtualization Server

Certify• Functional testing

Certify• Functional testing


• Test planning

• Test execution


• Test planning

• Test execution

• Manual testing

• Impact analysis

• Defect tracking linked toTeam Concert


Most of the time, the issue is finding out the problem, which is a big part of problem solving ofcourse. So the Rational performance testing tools really help us to narrow down that so muchanalysis. We also figure out different data points.

So this is done across the stack. You can do an operating system, monitoring by this -– thisoperating system could be shared across multiple systems. Then there is database kind ofmonitoring which is possible. Then there is SAP application system itself where you can have your

multiple job (of change), or have (change), and it helps you to monitor and see where are the bottlenecks, and then how can we go ahead and then solve it.

James Hunter: Thank you Abhik.

Before we sign off, is there anything else you’d like to share (with everyone) today about your useof the Rational tools (with SAP)?

Abhik Bose: Sure. I think for SAP -– there’s one slide where you mentioned the relationship between SAP and then IBM since years now.

I think this is one of the most important things that are just very valuable for SAP. And this wasagain, reinstated, if I can put it that way, during our use of the Rational performance tools wherethe product (of development team), all the Rational performance testing tools really work hand inhand with us.

So thank you so much to IBM, to (Bern Ahmed), all the Rational performance (development)teams, and all of you guys to, you know; just face the challenge together with us, help ourcustomers, our joint customers and then help the product as well to, you know, grow.



James Hunter: Thanks Abhik. We appreciate your (input here).

Abhik Bose: Thanks.

James Hunter: So, we talked a little bit about the capability and the solution areas that again,discovered in our own engine that we prioritize and take out to customers. And talk aboutLifecycle management being the beginning of the planning and identifying what test executionwe’re going to take place in our current SAP project.

16

IBM Rational Connector for SAP Solution Manager

IBM Rational Connector for SAPSolution Manager

Business BlueprintBusiness Blueprint

Project ReportingProject Reporting

Incident ManagementIncident Management

Requirements ManagementRequirements Management

Quality ManagementQuality Management

Change/Defect ManagementChange/Defect Management

Functional View

Import SAP Solution Manager Business

Blueprint into IBM Rational Quality Manager

Update test results into SAP Solution Manager

Integrate with SAP Service Desk

Customer Benefits

Allows customers to combine SAP & IBM best practices &

standards

Combine SAP Solution Manager life-cycle management

capabilities with IBM Rational‘s integrated governance and

quality management capabilities

Enables end-to-end business process testing between

SAP and customer applications

Aligns enterprise architecture and requirements with SAP-

centric Solutions

Change Impact AnalysisChange Impact Analysis

And available at no charge from Jazz.net!

So if we look at it against the SAP recommended approach towards testing, starting off with theSAP changes, or SAP environment whether using blueprints to define the business process orcapture the more of the (impact) analysis.

But do the test planning stage, using the Rational Quality Manager as the place to create and definethe test plan, execute the manual testing; perhaps define requirements and compose it. But ofcourse ultimately, getting down to Rational Team Concert, which is our product that we use formanaging change to SAP environment that processes the applications and the like.

Well, from this Lifecycle Management perspective, are then suggested that we drill down a little bitdeeper into the test execution itself, whether that’s the impact analysis of SAP applications in ourenvironment using BPCA and Rational Quality Manager, or going further into an automated testingfor SAP using Rational Quality Manager and (Certify).



(Maybe) it’s integration testing using again, Rational Quality Manager and Rational IntegrationTester. Or even (use) again, as far as security testing in testing those SAP user interfaces, and the(exceptions) to the SAP environment that continued to get built.

So we continue to build down lower levels to support the implementation of change and

management of (new) change into SAP.

So now, I’d like to hand it over to Steve and ask Steve about a little of that further.

When we talk about some of the challenges, the problems and the technology (that occur) fromSAP (and the experience); Steve now will have the opportunity to bring it all together.

Steve, over to you.

Steve Pitshke: Thank you James. I just want to start my part of the presentation by stepping backa little bit from testing and give you again, an overview of the overall suggested process from SAP

and Rational.

So what you can see here is that you start by specifying the blueprint and/or updating the blueprintfor some impacted change that you’re going to make. You can export that blueprint into Rational’ssystem architect to generate topology. And then having done that analysis, you can then export the blueprint into the Rational (fill-in) tools to create test plans, test cases and requirements.

So given that background, let’s go and (dive) into the particular part of IBM and SAP Solutions -–the IBM Rational Connector for SAP Solution Manager which was developed cooperatively between IBM and SAP.

So the integration here as we can see, connects four different business functions on the SAP side,with three different functions on the IBM Rational side.

In SAP, we have Business Blueprinting functionality. We have business process change analyzed.And we have project reporting and we have incident management.

On the Rational side, we have requirements management, quality management and change anddefect management.

So from functional view, what this allows us to do is to import the blueprint from Solution Managerinto the Rational tool. And then create the testing artifacts and requirements, management artifactsthat are necessary to perform a test on your new or changed SAP packaged app.

When the inevitable problems occur, those problems may manifest themselves first on the testingside. And for that, we create work items within Rational Team Concert. But some of those problems are cross-cutting in such as that they need to be reflected back in incidents or in SAP’sService Desk.



Now, what the benefits are for the customer is that they get the excellent ALM features from theSolution Manager working together with the excellent ALM features of the Rational tools for you.

And this product is free at no charge -– download from jazz.net.

Basically, customers will already have Solution Manager and the Rational toolset. So theintegration is just a way of providing a solution across those (who do it). It doesn’t make sense tocharge separately for it.

So at this point, I’d like to talk a little bit about how we developed this integration, so you have asense of both the architecture for integration and how we at Rational and SAP are moving forwardto create better integrations between our products set.

At the heart of the Rational Connector for SAP is OSLCOpen Services for Lifecycle Collaboration

External tool

integrations

And many

others…

RequirementsComposer

RequirementsComposer

Quality

Manager

Quality

Manager

Team ConcertTeam Concert

There is a new initiative sponsored by IBM and 20 or so other companies called Open Services forLifecycle Collaboration.

And basically what this is, is an internet-based technology for integrating the various tools that you,as practitioners have in your development environment.

No customer is going to be using tools from just one vendor, so IBM and the other cooperatingorganizations have come up with suggested standards that allow you to have a heterogeneoustoolset for performing your day-to-day work.

The Connector is implemented using the standard OS (itself) and derived the benefits from thisability to integrate various tools.



Now, diving even more deeper into the architecture, you can see here that the blueprinting processand Service Desk features of Solution Manager are integrated through the application server ofSolution Manager ABAP, with the Rational Connector for SAP Solution Manager.

Architecture for the IBM Rational Connector for SAP Solution Manager

Web Application that sits as communication layer in front of the Rational Tools and interfaces

with SAP Solution Manager

Uses SAP provided SOAP web services to communicate with Solution Manager

– Web service requests secured by SAML trust relationships between servers

Rational

Connector for SAP

Solution Manager

ABAP

Rational

Quality

Manager

Rational

TeamConcert

Rational

Requirements

Composer

Business

Blueprinting

Service

Desk

SOAP

Web Serviceswith SAML

OSLC

OSLC

OSLC

SAP Solution Manager

And the way that these tools communicate is via SOAP Web services which are secured through(standard) trust relationships between the servers.

On the backend of the Connector, you can see that we use OSLC interfaces to call out to Rationalrequirements, composed of Rational Quality Manager and Rational Team Concert.

We’re moving forward with SAP to help them become partners in this OSLC contortion.

The architecture that we’ve used for the Connector is a pluggable Web-based architecture whichwill allow us overtime to add more component tools to this integration.



A typical end to end SAP scenario

Requirements Composer Quality Manager Team Concert

Model Business

Processes

Configure SystemConfigure System

Realize SpecificationRealize Specification

Transfer BlueprintTransfer Blueprint

Display Test Results

Handle SAP

Incidents

Display SAP

Incidents

Create Requirements Create Test Scripts

Create Test Cases &Test Plans

Execute TestsCreate Work Items

“defects”

Link Work Items to SAP

Link SAP Incidents to

Work Items

(with back linking)

(create directly from within Solution Manager)

Flexible mapping to

match your process or

outsourced agreements.

Flexible mapping to

match your process or

outsourced agreements.

Having created that business process hierarchy in your blueprint, you configure your system andrealize that specification in your system.

At this point, the integrations between Solution Manager and Rational CLM test come into effect.So you use a point of the integration that was developed by SAP to export your blueprint fromSolution Manager and publish it into the Rational tools suite.

As you do that publishing, what it will do is to create a Rational requirements -– compose arequirement that corresponds to every business requirement inside of the blueprint. In addition, forevery business scenario in the blueprint, you will create a test plan in RQM and a test case thatcorresponds to the test (subject).

Now, this mapping is a flexible mapping. So if for example, you have a very complex blueprintwith thousands of nodes, you might for example, want to create trial test plans for every tests -– forevery business process step.

We allow you to specify this when you configure the connector for each Solution Manager project.

Now, having created the test plan and test cases, the next step in the process would be to create testscript or associate existing test scripts with the test cases.

Typically, you’ll depend primarily on automatic test, but there may be some test cases as youdevelop your application where you want to create manual test cases.



Integration Scenario Sample – Blueprint Push

1. Initiate Blueprint Push from SolMan

2. Select a Business Scenarios for transfer

So having specified all of these test scripts, then you begin execution. All of the execution resultsare contained within RQM, where you can use the reporting facilities to do your test analysis. Butof course, not every member of your team is going to be an expert in the Rational tools. Forexample, a business analyst might very well do most of their work in Solution Manager.

For those users, you can export the test results from RQM through the Connector, back intoSolution Manager, which also has excellent reporting facility.

Now invariably, you’re going to experience test failures. And when that happen over in theRational CLM Suite, normally what you would do is to create a Rational Team Concert defect.And most of those defects are going to be managed entirely within the context of your Rationaltools. But some of them are cross-cutting and so what you do is to use an OSLC gesture withinRational Team Concert to export the defect and create a SAP Service Desk Incident.

Similarly, based upon your analysis of tests you make, (you can) create Service Desk incidentsentirely within Service Desk. And again, some of those may be cross-cutting. So you then exportthe incident to create a new work item within Rational Team Concert.

So at this point, what I’d like to do given that we can't really do a live demo, is to work throughsome screenshots that show you specific use cases in using the Connector.

So as I said in the previous slide, one of the first steps you want to do is to publish your blueprintfrom Solution Manager into the Rational tools suite.

So what you can see here is that SAP working with IBM has added a new menu item to the business blueprinting application to send the data to the IBM Rational project.




1. Connector creates requirements, test plans and test cases in CLM project

2. All data is linked for traceability using the OSLC standard3. Requirement collections are used to structure the requirements (Business

Scenarios, Processes, Steps)

Having executed that menu item, you can then select which of the nodes in the blueprint youwanted to export to the Rational toolset.

So in this case, what we are doing is selecting a particular business scenario to transfer.

Now I wanted to point out that this is the manual first step for publishing a blueprint. But typically,

once you’ve done this initial publish, there will be background jobs that you run on an hourly ordaily basis, that will incrementally record the changes and publish them that were made during the blueprinting process. And publish those changes back into the CLM tools suite.

So having published your blueprint, the effect is to create artifacts in the Rational tools suite. Andwhat we can see here is Rational Requirements Composer.

Now if you remember back to the previous slide, you’ll see that there was a business processhierarchy in your blueprint. And that business process hierarchy will be represented within RRC asa set of requirements folders mapping identically to all of the published blueprint nodes




1. Test case categories are used to reflect Blueprint structure

2. Supports easier navigation and enhances reporting

And down at the level of where a business requirement exists, you’ll see in those folders thecorresponding Rational Requirements Composer requirement.

So I also want to point out that there’s a traceability link here that’s been generated, that pointsfrom this business requirement to the trial test case that validates this requirement.

Here what we’ve done is we’ve jumped into the -– to Rational Quality Manager. And you can see

that test case that corresponds to the business requirement.

Now in RQM, the blueprint process hierarchy is also represented as a set of nested category for testcases and test plans. This allows you to more easily navigate back and forth between SolutionManager and RQM.



Integration Scenario Sample – Business Process Change Analysis

1. Use Solution Manager's BPCA feature to identify and

optimize the test scope for planned SAP changes

2. Automatically create test scope optimized test plans in

RQM, based on parameters like manual test effort or testcoverage

Now this second use case is impact analysis when you have made some changes in your ManagerSystem. For example, you might have imported a service pack for your packaged app or theunderlying SAP infrastructure, or you might be enhancing that packaged app.

Now, BPCA allows you to record every affected nodes in your blueprint represented in a key BOMa test -– Bill of Materials.



Integration Scenario Sample – Transfer Test Results

1. Test results are automatically transferred back in to Solution Manager

2. Supports SAP quality reporting and documentation best practices

Having recorded all of these, you can run BPCA to create a specific test plans to test those affectednodes in your blueprint or in your packaged app.

And you can optimize this test by various criteria. So for example, you might optimize on the basisof automatic versus manual testing. As all of us have resourcing issues that require us to make the best use of all of our automatic procedures.



1. Forward a defect in RTC to SAP Service Desk

2. Defect Submission form is populated with live data from SAP Service Desk

Integration Scenario Sample – Integrate Defect Management

You can specify multiple criteria. So for example, you might optimize as well on the previoushistory of test effort and the priority and importance of each of the nodes being tested.

So having executed your test plan, the next step would be -– if you want a business analyst to doreporting on the basis of the test results, to export those test results back from RQM into SolutionManager.

You can do this from the Connector administered in (doing), but again, typically having done thatinitial export, you’ll be running a background job within Solution Manager where every half houror hour will gather the incremental test results to publish them into Solution Manager.

Now, the test results appear both in the blueprinting transactions -– (Solar-01, or Solar-02), as wellas in some of the (canned) or customized reports, you can generate.




1. Forward an incident from SAP Service Desk to RTC

2. Use “Forward to external Help Desk” option in Service Desk

And what I’d like to point out here is that these are fully interactive reports where you can doubleclick on the nodes within the test matrix, and navigate back to the affected test cases, test scripts,and test results. So this allows your analyst to drill down and see what the causes were for any testfailures.

So in the case where you have discovered a bug in your test, some problem -– and this is the cross-cutting issue that you want to engage the Solution Manager part of your team; you can use the

OSLC gesture to create a related change request from the RTC work item within Service Desk.

And having clicked on this menu item, a popup window will appear with the fields to be filled outin the new incident. These fields are populated from Service Desk live at the time that you’redoing it. You can see here that we’re trying to select what type of text type this incident willappear in the node section of the incident.

So here, what we can see is the last use case I want to cover which is -– when you have an incidentthat occurred in the Solution Manager side and you want to publish that incident to create a workitem within RTC, the way that we’ve modeled this from the Service Desk side is that RationalTeam Concert appears as an external helpdesk.




1. New defect in RTC is linked to Service Desk incident

2. OSLC data linking model is used

So you use the gesture for the incident to the Rational Team Concert external helpdesk, and thuscreate a linked work item.

So having created the work item, then you can click on the work item number that appears in theexternal helpdesk section of your incident to navigate to the work item.

And here, what you’ll see as well is that the OSLC link capability allows you to hover over the link

that appears in your Rational Team Concert project to preview the contents of an incident.

Again, you can also click on this link within Rational Team Concert to navigate back to the browser interface for Service Desk for this incident.

Now, as we said earlier, the IBM Rational Connector for SAP Solution Manager is available as afree, no-charge download from jazz.net. You can use this URL or just Google for the name of the product and your browser will take you to the download.

At this point, I’d like to hand over the control back to James.

James, are you on mute?

James Hunter: Yes, sorry.



IBM Rational Connector for SAP Solution Manager

• Available as a no charge download from Jazz.net

–https://jazz.net/downloads/sap-connector/releases/4.0.0.1

So thank you Steve. That was a great in-depth view of the technology behind the capabilitiessupporting testing for SAP..

So I want to conclude by reiterating that the success of an organization running on SAP depends onhow well you can manage change. And change comes from all sorts of different areas, whether it’s

changing the user-experience, updating the technology -– for example, moving the database over toSAP HANA, adding mobile devices or support for mobile to SAP environment, adding new partners and further complicating your environment by having more integrations betweencapability, devices and partners as well.

But the solution of course as we’ve been describing, is having this integrated end-to-end approach,a lifecycle management that focus on testing. And that’s what’s being utilized and supportedthroughout the SAP market today.



SAP uses IBM for both production and

development, and IBM is one of the world’s

largest users of SAP.

A true reflection of the high level of mutual trust.

IBM and SAP – partners for 40 years

So the whole point of that using Rational tools and the reason we started doing the best insupporting SAP customers is to reduce the costs and the risks of managing change inside our SAPenvironment.

And to do that, we have to have a focus on supporting tests -– tests to support the changes madeacross our environment.

(Even on SAP), even on non-SAP environments are affecting our (inspiration) with our SAPapplications.

So wherever those changes may come from, the core capabilities provided by (inaudible) fromRational, for (current development) between SAP and IBM, so bringing value to SAP customerswho are trying to manage change today, I want to do so with reduced risk and with reduced cost.



“Our collaboration with IBM Rational brings together the best of our

combined application lifecycle management market leadership and canhelp customers reduce costs, manage change, and improve quality across

the enterprise applications lifecycle.”

Uwe Hommel, Executive Vice President

“With IBM’s assistance, we have delivered increased productivity, reduced

development times and lowered costs, while experiencing significantly

higher user adoption rates, which translate into greater business value.”

“The recipe is to run core operations on SAP applications, and extend the

power and reach of the developer community using Rational Team

Concert”

Arpad Hevi zi, VP of Supply Chain IT Solu tions

What customers say

What SAP say

In summary: Reduce the cost and risk of change

Business

changes

IT changesCompliance

changes

The Rational difference

Rational solutions reduce the costand risk of managing SAP change.

So we’ve reached the end of the presentation we wanted to share today. But we do want to leave alittle bit of time for questions.

So, perhaps I can hand it back over to yourself for any questions that may have come in.



James Hunter: OK, I’ll take that one as well.

Or Steve, perhaps you should answer them?

Steve Pitshke: Sure.

So IBM Connector has one of the only integrations between Solution Manager, BPCA and testingtools. And executing a business process change analysis on one of these changes, the last step inthat is to automatically create a test plan within RQM.

So the answer is (inaudible).

Moderator: Excellent, thank you.

And our next question is going to be -– do we have to use Solution Manager?

James Hunter: OK, so I’ll take that one there.

Yes. It’s a good question. And so, all SAP customers have SAP Solution Manager of course. Andthey (use) that for supports and other capabilities as well. But it recognize that not every customeris utilizing SAP Solution Manager for, for example for documenting all of their business processes,(that’s perhaps they shouldn’t have to do so).

It’s SAP’s strategy and direction that all customers should use SAP Solution Manager. That’s ourrecommendation as well as we are lined with SAP.

So not every customer has to use SAP Solution Manager, nor is to use the toolset we’ve beentalking about today.

And in fact, many customers are using for example, requirements composers as the way to startcapturing their requirements in their processes. And then they create their test plans and test scriptsand cases, and executing their tests through Rational Quality Manager.

But yet, certainly it’s a way to start our recommendation there, if you use SAP Solution Managerand use that as the way to capture and manage changes in the business process, and then connectthose in would be requirements management and testing capabilities provided by the Rational tools.

The answer is no, you don’t have to use it. But we do recommend that you do.

Moderator: OK, great. Thanks for that.

And I think the next question is directed for Steve. Steve, how is the data in Solution Managermove into the Rational toolset?



Steve Pitshke: So the actual GUI gesture is to go the (Solar-01) transaction, or (Solar-02) and toclick on blueprint, and do move.

Now, at a technical level, what happens is that the blueprint is represented as an XML document.That document is read through the Connector and then the Connector makes OSLC-based calls to

the three CLM tools to create artifacts within the CLM toolset.

Moderator: OK, excellent. Thank you.

And our next question -– does SAP recommend using Rational tools for testing SAP?

Abhik Bose: Yeah, I could say that. This is Abhik.

Yes of course, we do. It really reduces your time and effort. It gives you an end-to-end viewtogether with Solution Manager, BPCA, doing upgrades, doing migrations, doing a lot of differentthings.

So yes, of course we do recommend our customers to use automated testing tool and RPT beingone of them, of course, yes.

Moderator: OK, thank you. And next question is -– what is the difference between ALM featuresof SAP (as well as in those) of Rational CLM?

Steve Pitshke: So in many ways, they’re very complimentary.

Solution Manager has really the best of breed functionality in terms of the deployment of packetsthat’s across your enterprise, and from the initial development, sandboxes, all the way up into production.

On the Rational side, the CLM toolset is really -– the ALM that we perform there is more of thelifecycle of the code base for the individual code base components that you’re developing as part ofyour packaged app.

So by using the ALM features of the Solution Manager and of CLM, you’re getting the best of bothworlds.

Moderator: Thank you. And our next question is -– what is the recommended usage pattern forrequirements management between SolMan and RRC?

Steve Pitshke: So the industry as a whole has migrated from what I would call RequirementSpecification to Requirement Management.

And Solution Manager has excellent facilities for specifying the requirements for the overallapplication and the individual components.



When you push a blueprint from Solution Manager into CLM and specifically into RationalRequirements Composer, you create a link between that specification and the newly created RRCrequirement.

Within RRC, you can then embellish the requirement with things such use case flow diagrams.

And you can do a traceability analysis to look at issues like coverage and failures acrosscomponents; so while you continue to keep the specification for your requirement within theSolution Manager.

So in short, you specify the requirement in Solution Manager and then you do your embellishmentand traceability analysis in RRC.

Moderator: OK, thanks. And the next question is -– can outsourced partners have access to RTCfor defects and changes?

James Hunter: Yes. So we recognized that a lot SAP projects are supported by partners,

outsourced provider consultancy, and other things as well.

So yeah, the idea here that is behind that just because of backbone between all the teams that areinvolve in implementing SAP, whether it’s change for SAP environment across the landscape, oreven the non-SAP project is affecting them, SAP as well.

So yes, the information in all of the (lifecycle management) requirements, management change,management RTC and the test planning has (inaudible) -– there’s so much during the test execution(that stands) appropriate for the (top of the lifecycle) agreement you have as well.

All of those can be made available to outsourced providers and partners through the same toolset being used by the internal team.

And of course that can be controlled. And that (inaudible) can be controlled, anything that can besegregated as appropriate for the type of relationship that the SAP customers have with theiroutsourced providers.

Moderator: Great. Thank you.

And I think our next question is geared towards Abhik. Abhik, how can I contact the ValuePrototyping team at SAP?

Abhik Bose: There is -– when you go to the SAP portal, which is opened to partners, you just typevalue prototyping, and press search. You should get the link.

I think I could go ahead and send my e-mail address and the Value Prototyping e-mail address aswell, so that any address that people can go ahead and contact the Value Prototyping team also.

Moderator: OK, great. Thanks.



It looks like we time for a couple of more questions. One of those question is -– can outsource partners have access to RTC for defects and changes?

James Hunter: Sure. That might be repeated the question we just talked about a moment ago.

But to reiterate that -– yes. Outsourced provider is very important to the implementation anddelivery of SAP and so yes, we do support and enable outsourced providers have access to(inaudible) and in fact, to the same toolset and the same data source.

Moderator: OK, great. Thanks. And a couple more questions -– can we perform automatedRegression testing using these tools?

Steve Pitshke: Yes. So typically, that’s one of the strength of Rational Quality Manager, is torecord all of your Regressions suite and then automate the execution of that Regression suite.

Moderator: OK, great. And actually there are two more questions. One of them just rolled in as

well.

The first question of the two is -– we do a lot of manual testing, is that included in these tools?

James Hunter: So yes. Manual testing is embedded into Rational Quality Manager. So it’s thecore product that we use for manual testing on SAP.

Moderator: OK, great. Thank you.

And our last question is going to be -– can integration testing be performed using these testingtoolset?

James Hunter: So again, yes. During the (session) -– with the presentation, we talked aboutRational Integration Test that was just specifically designed to test the flow of information betweentwo different applications, in this case -– SAP and perhaps another SAP module, or an application,or a third-party component, an entry-point of application, a database, a legacy system, and so on.

So the integration testing is a core part of our overall testing solutions for SAP.

Moderator: OK, great. Thanks all.

That wraps up the Q&A session for today as well as the presentation in general.

James, Steve, and Abhik, is there any last minute comments or concerns that you have for theaudience members?

OK, great. Thanks to all. That wraps up the Q&A session.

We have on last minute closing comments from (Bern Eberhart) would like to join the line.



35

Acknowledgements and disclaimers

© Copyright IBM Corporation 2013. All rights reserved.

– U.S. Government Users Restricted Rights - Use, duplication or disclosure r estricted by GSA ADP Schedule Contract with IBM Corp.

IBM, the IBM logo, ibm.com, Rational, the Rational logo, Telelogic, the Telelogic logo, Green Hat, the Gr een Hat logo, and other IBM products

and services are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or

both. If these and other IBM trademarked terms are marked on their f irst occurrence in this information with a trademark symbol (® or ™), these

symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may

also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and

trademark information” at www.ibm.com/legal/copytrade.shtml

Other company, product, or service names may be trademarks or service marks of others.

Avail abili ty : References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries

in which IBM operates.

The workshops, sessions and material s have been prepared by IBM or the session speakers and reflect their own views. They are provided

for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any

participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided

AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise

related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating

any warranties or representations from IBM or its suppliers or li censors, or altering the terms and conditions of the applicable license

agreement governing the use of IBM software.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may

have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is

intended to, nor shall have the effect of, stating or im plying that any activities undertaken by you will result in any specific sales, revenue

growth or other results.

SAP and SAP products and services mentioned 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.

36

Acknowledgements and disclaimers

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal

without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and

it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal

obligation to deliver any material, code or functionality. Information about potential future productsmay not be incorporated into any contract. The development, release, and timing of any future

features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a

controlled environment. The actual throughput or performance that any user will experience will varydepending upon many factors, including considerations such as the amount of multiprogramming in

the user’s job stream, the I/O configuration, the storage configuration, and the workload processed.Therefore, no assurance can be given that an individual user will achieve results similar to those

stated here.

(Bern), take it away.

Hi (Bern), are you there?

(Bern Eberhart): We just want to remind our viewers to please join us at the same time, 11:00 amEastern Standard Time on June 24th for part two of this IBM and SAP Webcast series.



Moderator: OK, great. Well, thanks for that.

And at this time, I’d like to thank everybody for joining for today’s presentation. Today’s presentation was entitled Minimize SAP Testing Environment, which is being brought to you by

IBM.

And at this time, I’d like to thank everybody again, and have a great day.

© Copyright IBM Corporation 2013. All rights reserved. The informationcontained in these materials is provided for informational purposes only, and isprovided AS IS without warranty of any kind, express or implied. IBM shall not beresponsible for any damages arising out of the use of, or otherwise related to,these materials. Nothing contained in these materials is intended to, nor shallhave the effect of, creating any warranties or representations from IBM or itssuppliers or licensors, or altering the terms and conditions of the applicable licenseagreement governing the use of IBM software. References in these materials toIBM products, programs, or services do not imply that they will be available in allcountries in which IBM operates. Product release dates and/or capabilitiesreferenced in these materials may change at any time at IBM’s sole discretionbased on market opportunities or other factors, and are not intended to be acommitment to future product or feature availability in any way. IBM, the IBM logo,Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM productsand services are trademarks of the International Business Machines Corporation,in the United States, other countries or both. Other company, product, or s ervicenames may be trademarks or service marks of others.

END

130614 ibm minimizesaptestingeffort

Documents