CA LISA r7.5: Virtualization Fundamentals (Instructor's Guide)

CA LISA r7.5

Virtualization Fundamentals 200 Instructor Guide 88LSA20281

88LSA20281IG1 © 2014 CA. All rights reserved.

‐ PROPRIETARY AND CONFIDENTIAL INFORMATION ‐ These educational materials (hereinafter referred to as the “Materials”) are for the end user’s educational purposes only and are subject to change or withdrawal by CA Inc (“CA”) at any time only and are subject to change or withdrawal by CA, Inc. (“CA”) at any time.

These Materials may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. These Materials are confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THESE MATERIALS “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THESE MATERIALS, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of any software or product referenced in the Materials is governed by the end user’s applicable license agreement.

The manufacturer of these Materials is CA. Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227‐14, and 52.227‐19(c)(1) ‐ (2) and DFARS Section 252.227‐ 7014(b)(3), as applicable, or their successors. , , , g g p p All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright © 2014 CA. All rights reserved. CA confidential and proprietary information for CA or CA Partner Internal Use Only. No unauthorized copying or distribution permitted.

2

© 2014 CA. All rights reserved.

CA LISA r7.5 Virtualization Fundamentals 200

I. Introduction Welcome ...............................................................................................................................................................................I ‐ 2 Course Overview ...................................................................................................................................................................I ‐ 3 Participation ..........................................................................................................................................................................I ‐ 4 Start Components and Create a Project ...............................................................................................................................I ‐ 5

1. Describe Service Virtualization Module Objectives ................................................................................................................................................................1 ‐ 2 Describe Service Virtualization .............................................................................................................................................1 ‐ 3 Describe the Benefits of SV to the Software Development Lifecycle ...................................................................................1 ‐ 6 Module Summary .................................................................................................................................................................1 ‐ 7

2. Create a Virtual Service Module Objectives ................................................................................................................................................................2 ‐ 2 Describe how a Virtual Service Is Created by Capturing Transactions .................................................................................2 ‐ 3 Describe Basic CA LISA Virtualization Concepts ...................................................................................................................2 ‐ 7 Create a Virtual Service by Recording ..................................................................................................................................2 ‐ 19 Module Summary .................................................................................................................................................................2 ‐ 34

3. Execute Against a Virtual Service Module Objectives ................................................................................................................................................................3 ‐ 2 Execute Against a Virtual Service at Run‐time .....................................................................................................................3 ‐ 5 Execute Against a Virtual Service at Design‐time .................................................................................................................3 ‐ 6 Module Summary .................................................................................................................................................................3 ‐ 10

TOC‐1 Copyright © 2014 CA. All rights reserved.

CA LISA r7.5 Virtualization Fundamentals 200

4. Describe Virtual Service Matching and Responding Module Objectives ................................................................................................................................................................4 ‐ 2 Describe How Request/Response Pairs Are Stored in a Virtual Service Image ....................................................................4 ‐ 5 Describe How an Inbound Request to a Virtual Service Is Matched to Determine a Response ..........................................4 ‐ 10 Describe How a Virtual Service Responds with Static and Dynamic Data ............................................................................4 ‐ 28 Describe How Magic Strings and Dates Are Created and Used in a Response ....................................................................4 ‐ 32 Module Summary .................................................................................................................................................................4 ‐ 37

5. Manipulate Virtual Service Data Module Objectives ................................................................................................................................................................5 ‐ 2 Manipulate Request Data During Recording with Request Data Manager (RDM) Protocol ................................................5 ‐ 4 Desensitize Data During and After Recording ......................................................................................................................5 ‐ 9 Edit Virtual Service Data in the SIE .......................................................................................................................................5 ‐ 13 Module Summary .................................................................................................................................................................5 ‐ 17

6. Describe Virtual Service Model Steps Module Objectives ................................................................................................................................................................6 ‐ 2 Describe the Difference Between Virtual Service Model Styles ...........................................................................................6 ‐ 3 Describe the Roles of Common Virtual Service Model Steps ...............................................................................................6 ‐ 6 Module Summary .................................................................................................................................................................6 ‐ 16

7. Configure Virtual Service Execution Module Objectives ................................................................................................................................................................7 ‐ 2 Describe the Role of Virtual Service Execution Modes ........................................................................................................7 ‐ 3 View Execution Details in the VSE Dashboard ......................................................................................................................7 ‐ 11 Debug a Virtual Service Using Transaction Tracking Mode ..................................................................................................7 ‐ 17 Module Summary .................................................................................................................................................................7 ‐ 20

TOC‐2 Copyright © 2014 CA. All rights reserved.

CA LISA r7.5 Virtualization Fundamentals 200

8. Maintain and Troubleshoot a Virtual Service Module Objectives ................................................................................................................................................................8 ‐ 2 Maintain a Virtual Service .....................................................................................................................................................8 ‐ 3 Troubleshoot a Virtual Service ..............................................................................................................................................8 ‐ 8 Module Summary .................................................................................................................................................................8 ‐ 13 Course Summary ...................................................................................................................................................................8 ‐ 14

TOC‐3 Copyright © 2014 CA. All rights reserved.

CA LISA r7.5 Virtualization Fundamentals 200

TOC‐4 Copyright © 2014 CA. All rights reserved.

Introduction

I-1 Time: Lecture: 5 minutes; labs: 10 minutes

Introduction

CA LISA r7.5: Virtualization Fundamentals 200

Lab Exercises Solution Files • If you need a final version of a file created in a lab exercise, the LISACLIENT machine contains a copy of the ca_lisa_virtualization_fundamentals project and all the final versions of the files for each exercise.

• The ca_lisa_virtualization_fundamentals project can be opened in CA LISA Workstation and is located here: C:\Users\Administrator\My Documents\ca_lisa_training\instructor _files\ca_lisa_virtualization_fundamentals\solutions\ Examples Project Back Up If you modify the examples project files and need an original copy of the files again, you can find a back up of the full examples project in this location: C:\Users\Administrator\My Documents\ca_lisa_training\instructor_fil es\examples_project_source It is recommended to use Windows Explorer to replace the examples project files in LISA_HOME/examples rather than opening the examples project from this location. This way you will always have a clean set of source files.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Introduction

I-2

Introduction Welcome!

Welcome!

• We’re excited you are here to learn about CA LISA Virtualization!

Powerful and Versatile

• CA LISA Virtualization provides a broad range of powerful features for virtualizing complex systems to eliminate constraints on systems under development and test

Fundamentals are Essential

• The fundamental concepts taught in this class are essential to understanding the core of what CA LISA Virtualization can do and how it is done

Module I: Introduction

2 of 6

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Introduction

I-3

Introduction Course Overview Learning Methods

 Lecture  Review Questions  Hands-On Lab Exercises

Curriculum Topics Describe Service Virtualization Create a Virtual Service Execute Against a Virtual Service Describe Virtual Service Matching and Responding Manipulate Virtual Service Data

Results

Return to your workplace with the knowledge needed to collaborate with your team of specialists to implement CA LISA Virtualization

Describe Virtual Service Model Steps

Configure Virtual Service Execution Maintain and Troubleshoot Virtual Services

Module I: Introduction

3 of 6

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Introduction

I-4

Getting Started

Review attendance information:

Participation

• Class schedule (hours, breaks, lunch) • Sign in / How to receive credit

Cell Phones

If delivering ILT, review facility information:

• Silence or turn off • Vibrate is ok

• Restroom locations • Smoking policies

Email/Work

• Check email at breaks • Refrain from working

Discussions

• Ask questions • Limit side discussions

Module I: Introduction

• Emergency exits

4 of 6

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Introduction

I-5

Lab Exercises Start Components and Create a Project In the following lab exercises, you will:  Start components for CA LISA Virtualization training See lab I‐1 Start Components.  Create a project for CA LISA Virtualization training files See lab I‐2 Create a Project.

Module I: Introduction

5 of 6

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Introduction

Module I: Introduction

I-6

6 of 6

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Service Virtualization

1-1 Time: Lecture: 5 minutes; labs: 0 minutes

Describe Service Virtualization CA LISA r7.5: Virtualization Fundamentals 200

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Service Virtualization

1-2

Module Objectives Describe Service Virtualization After completing this module, you will be able to:  Describe service virtualization (SV)  Describe the benefits of service virtualization to the software development lifecycle (SDLC) Why you need to know:  Understanding the role of SV provides insight into where CA LISA Virtualization benefits your SDLC

Module 1: Describe Service Virtualization

2 of 8

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Service Virtualization

1-3

Service Virtualization How We Look at SV 

Reality is overrated...



Virtualize everything...



Make transformation happen!

Co-authored by John Michelsen, founder of ITKO and CTO of CA Technologies

Module 1: Describe Service Virtualization

•

3 of 8

More info at http://servicevirtualization.com/book

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Service Virtualization

1-4

Service Virtualization Reality is Overrated You no longer have to live with the reality of dependent system constraints 

Service virtualization allows you to:  Capture and simulate dependent system:  Behavior  Data  Performance characteristics

 Deploy a captured virtual service to represent the dependent system without constraints  Develop and deliver software:

Important Distinction:  Service virtualization is different than server virtualization, which is commonly referred to as hardware or OS virtualization, such as virtual machines

 Faster  At lower costs  With higher reliability

Module 1: Describe Service Virtualization

4 of 8

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Service Virtualization

1-5

Service Virtualization Virtualize Everything Service virtualization includes the technology and accompanying methodology for virtualizing almost any IT asset

Module 1: Describe Service Virtualization

•

5 of 8

This is just a representative list of technologies and services dependencies we have seen turned into virtual services by companies and is only a start of what you can do with service virtualization.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Service Virtualization

1-6

Service Virtualization Make Transformation Happen Practical applications of service virtualization enable companies to transform their SDLC  Deliver faster  Improve quality  Lower costs  Reduce infrastructure footprint  Isolate component-level performance and scale  Manage data scenarios

Module 1: Describe Service Virtualization

6 of 8

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Service Virtualization

1-7

Module Summary Describe Service Virtualization This module showed you how to:  Describe service virtualization  Describe the benefits of service virtualization to the software development lifecycle

Discussion Points  How does your team plan to use service virtualization?  What benefits do you expect from implementing service virtualization in your SDLC?

Module 1: Describe Service Virtualization

7 of 8

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Service Virtualization

Module 1: Describe Service Virtualization

1-8

8 of 8

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2-1 Time: Lecture: 1:15 minutes; labs: 30 minutes

Create a Virtual Service CA LISA r7.5: Virtualization Fundamentals 200

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2-2

Module Objectives Create a Virtual Service After completing this module, you will be able to:  Describe how a virtual service is created by capturing transactions  Describe basic CA LISA Virtualization concepts  Create a virtual service by recording  Create a virtual service by importing raw traffic Why you need to know:  The basic CA LISA Virtualization concepts of transactions and how a virtual service captures and processes transactions are the foundation for virtual service creation, maintenance, and troubleshooting

Module 2: Create a Virtual Service

2 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2-3

Create a Virtual Service

• Graphics showing common configuration.

Overview

• Creation methods discussed in next slide.

Creating a virtual service is the process of capturing and processing the request and response of transactions between a client and a server Client/Server Transactions

Client

Transaction Request Response

Server

Client/Server Transactions Captured by VSE Recorder VSE Recorder Client

Transactions

Server

Virtual Service

Module 2: Create a Virtual Service

3 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2-4 • Recording and providing request/response pairs are very common creation methods.

Create a Virtual Service Methods Virtual service creation methods:  Record  Import raw traffic  Provide a WSDL

This module covers using the VSE Recorder to capture live traffic, as well as importing raw traffic

 Provide request/response pairs  From PCAP  Create .vsm and .vsi files from scratch  Combine .vsi files  Auto-generate with CA LISA Pathfinder Agents

Module 2: Create a Virtual Service

4 of 34

• More detail around creation methods: • Recording: VSE Recorder listens to client/server traffic, records transactions, and creates virtual service files. Most common method.

• Importing raw traffic: VSE Recorder imports raw traffic and creates virtual service files.

• Provide a WSDL: A WSDL is provided and a list of operations from the WSDL is returned along with data from the string pattern database.

• Provide request/response pairs: Provide sample request/response pairs in a file in a directory and CA LISA generates the virtual service files from them. Popular method with developers since it can be done early in the life cycle when access to live system is limited.

• From PCAP: If you are using packet capture software such as Wireshark to create logs of traffic, VSE • can use those logs to create a virtual service image from a packet capture file (PCAP).

• From scratch: Create the entire virtual service (.vsm & .vsi files) manually. Almost never done. Available to do, but requires very advanced understanding of virtual services and is tedious.

• Combine: Merging virtual service image files (.vsi) files into a single file.

• Auto-generate with CA LISA Pathfinder Agents: CA LISA Pathfinder is capable of auto-generating virtual services files from transaction paths captured by the agent.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2-5

VSE Recorder Overview The VSE Recorder is a widely-used method for creating virtual services  Accessed from main toolbar  Provides step-by-step wizard  Runs as a part of CA LISA Workstation  Not dependent on VSE

 Listens and records raw traffic between client and server  Processes raw traffic into virtual service image and model files  Allows for export of raw traffic for import into a later session

Module 2: Create a Virtual Service

5 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2-6 • Student notes provide slide discussion points

VSE Recorder Architecture

CA LISA Workstation UI Client

Virtual Service Image (.vsi)

Server

VSE Recorder

Virtual Service Model (.vsm)

Raw Traffic File (.xml)

Project

Module 2: Create a Virtual Service

1.

2.

3.

4.

5.

6 of 34

VSE Recorder launched from CA LISA Workstation UI • VSE Recorder is not dependent on the VSE Traffic between the live client and server ported through the VSE Recorder VSE Recorder records request and response transactions between client and server When recording is complete, VSE Recorder process raw transactions into: • Virtual service image (.vsi): Normalized transaction data • Virtual service model (.vsm): Workflow model for virtual service execution • Raw traffic files (.xml): Transactions in their raw state before VSE Recorder processing Files are stored in the designated project and edited in the CA Workstation UI

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

Describe Basic CA LISA Virtualization Concepts

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

2-7

Create a Virtual Service

2-8

Overview

• Some terms commonly used in application development are used in CA LISA with a specialized meaning.

• Example: “Protocols” is used more loosely in CA LISA.

To use the VSE Recorder requires a basic understanding of CA LISA Virtualization concepts:

• This course focuses on HTTP/S transport protocol.

CA LISA Virtualization Concepts



Transactions  Stateless  Conversational  Tokens  Navigation



Protocols  Transport  Data



Data desensitization



Host and port configurations  Listen/Record Port  Target Host  Target Port

Module 2: Create a Virtual Service

8 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2-9 • Transactions are captured by configuring the client to send traffic to the VSE Recorder, which intercepts traffic between the client and server to create the virtual service.

Transactions Overview Transactions, comprised of request and response pairs from the client and server, are central to service virtualization Client/Server Transactions

Client

Transaction Request Response

Server

Client/Server Transactions Captured by VSE Recorder VSE Recorder Client

Transactions

Server

Virtual Service

Module 2: Create a Virtual Service

9 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 10

Transactions

• 75% of virtual service images are stateless

Stateless and Conversational

• Conversational service images are more complex

Raw transactions captured by the VSE Recorder are normalized (coalesced) into two categories: 

Stateless  No logical relationship between one transaction to the next  Transactions are independent from each other



Conversational (Stateful)  Logical relationship between one transaction to the next  Always dependent on context created by previous transaction

• Examples provided in student notes Stateless

 The "state" the previous transaction created  Creates the "conversation"

Conversational

Virtual Service Image (.vsi)

Module 2: Create a Virtual Service

10 of 34

Stateless Example: 1. List all users in banking system 2. Add a user to the system • Transactions not dependent on each other Conversational Example: 1. Insert ATM card (start the state of the conversation for the following transactions) 2. Enter pin 3. Select account 4. View balance of selected account 5. Withdraw money from selected account 6. View new balance of selected account 7. Log out and end session (end state of the conversation for the previous transactions) • Transactions are dependent on the results of previous transactions NOTE: Some transactions that would seem to be conversational can be stateless depending on the system, such as the example above.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 11

Transactions Virtual Service Image Normalization Process Raw Transactions

Raw transactions are captured by VSE Recorder

Logical Organization

Transactions are logically organized into conversational traffic and stateless transactions

Normalized Transactions

Duplicate transactions are removed and similar structures merged to create a conversational tree.

Transactions not in a conversation move to the stateless list. The .vsi file is created.

Module 2: Create a Virtual Service

•

11 of 34

VSE Recorder provides option to keep duplicates if needed.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 12

Conversational Transactions Conversation Starters The first transaction in a conversation is known as the conversation starter 

Start conversation here

Typically some kind of token in the transactions provides a starting point for a conversation  Example: Session cookie



Multiple conversations can exist in a virtual service image



Token-based conversations cannot be autodetected during recording  VSE Recorder knows how transactions happened from top to bottom, but not where conversations started  Tokens are manually identified in VSE Recorder after recording, but before processing

Module 2: Create a Virtual Service

12 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 13 • Star indicates selected transaction.

Conversational Transactions Navigation Navigation settings define how far from the last responding node the VSE can search for a match for the next request 

Navigation is configured at each transaction node



There are three navigation tolerance settings:  Close  Wide  Loose



Tolerance defines which transactions to search next for a matching request



Default navigation for all transactions is specified in the VSE Recorder  Last transaction navigation set separately

Module 2: Create a Virtual Service

• •

13 of 34

Navigation is covered again when discussing request/response matching Last transactions navigation tolerance is generally set to Loose allowing the most flexibility in matching the next request at the end of a conversation tree

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 14 • Student notes highlight important points

Conversational Transactions Conversation Trees in a Virtual Service Image

Module 2: Create a Virtual Service

• • •

14 of 34

Conversational transactions display as nodes in a conversation tree Conversational virtual service images can also contain stateless transactions Use drop-down in Transactions tab to switch between other conversations and stateless transactions

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 15

Stateless Transactions Stateless List in a Virtual Service Image

Module 2: Create a Virtual Service

•

15 of 34

Stateless transactions display as a list because there is no relationship from one transaction to the next

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 16 • The correct answer is B.

Review Question Normalization When the VSE Recorder normalizes raw traffic, transactions that do not fit into a conversation are:

A

Deleted

B

Moved into the stateless transaction list

C

Merged into the bottom of conversation paths

D

Clustered into an unorganized conversation tree

Module 2: Create a Virtual Service

16 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 17

Protocols

• Multiple data protocols are allowed. Known as chaining.

Transport and Data Protocols

• Request Data Manager is covered later.

• Not all transport protocols require/allow a data protocol.

VSE Recorder uses transport and data protocols for service virtualization 

• During recording, all transport protocols will attempt to detect the request's or response's payload and default appropriate data protocols on either the request or response side.

Transport Protocols  Define technology used to communicate (transport) request and response between client and server  Example: HTTP/S



Data Protocols  Define data format for request and response  Example: SOAP request  Many data protocols are auto-detected

 Manipulate data during processing  Example: Request Data Manager Module 2: Create a Virtual Service

17 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 18 • Data desensitization is covered in more detail later in this course.

Data Desensitization Overview Data desensitization replaces sensitive data from a live system with random, yet validly formatted, values  Examples:  Protected health information  Social Security numbers  Random data provided by string generator patterns  Data desensitization can take place at:  Transport protocol layer  Data desensitized during recording  Sensitive data is not stored in raw traffic file

 Data protocol layer  Data desensitized when processed into the virtual service image, or through manual search and replace  Sensitive data stored in raw traffic file Module 2: Create a Virtual Service

18 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

Create a Virtual Service by Recording

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

2 - 19

Create a Virtual Service

2 - 20

Host and Port Configuration

• Recorder passthru style Proxy setting is discussed later in course.

Recording Configurations for Training

• For this course, VSE Recorder is always configured to act as a gateway.

• For demonstrations and lab exercises we will record transactions between: • Clients • LISA Bank Kiosk (manual ATM transactions) • Test Cases (automated Web Service requests) • Server • LISA Bank Application Server (hosted by the Demo server)

VSE Recorder can record live traffic by acting as a gateway between client and server: 

Client must know which port to use to communicate with the VSE Recorder



VSE Recorder must know:

CA LISA Workstation UI VSE Recorder

 Port traffic will arrive on from the client  Host and port of the server to send client traffic to 

Client

Server must be running and responding normally

Module 2: Create a Virtual Service

•

•

Server

20 of 34

VSE Recorder host and port settings: • Listen/Record on port: Port used to send traffic between the client and the VSE Recorder (defaults to 8001) • Target Host: Name or IP address of server • Target port: Port used to send traffic between the VSE Recorder and the server Note: Recorder passthru style must be set to gateway before target host and port can be set

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 21

VSE Recorder Basics Configurations

Pay close attention to the paths. It is easy to confuse the different virtual service folders and place files in the incorrect folders.

You can just enter the name of the .vsm file and it is saved automatically to the VServices folder

Module 2: Create a Virtual Service

•

•

21 of 34

Following fields are required: • Write image to: Path and name for .vsi file • Transport protocol: Protocol used to communicated request/response data.

Note: Subsequent VSE Recorder screens are protocol-specific. This course focuses on HTTP/S.

Details • Write image to: Path and name for virtual service image file creation. File name ends with .vsi. Required.

• Import traffic: Path and name of raw traffic file to import.

Imported transactions are processed on their own or merged into transactions from recording session.

• Transport protocol: Protocol used to communicate request/response data. Required.

• Desensitize (transport layer): Recognize sensitive data and substitute random, yet validly formatted, values using string generator patterns.

• Treat all transactions as stateless: VSE Recorder will not create conversational transactions when processing recording.

• Default navigation: Navigation tolerance for all conversational transactions except the last transactions in a conversation.

• Last: Navigation tolerance for all last transactions in a conversation.

• Export to: Path and name for raw traffic file creation. File name ends with .xml.

• Model file: Path and name for virtual service model file creation.

File name ends with .vsm.

• VS Model style: − More flexible: Generates 8-step virtual service model.

Includes two additional prepare steps used to modify the request and response. − More efficient: Generates 6-step virtual service model.

Prepare steps are absent.

• Load recording session file: Click the folder icon to load configurations saved in a previous session.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 22 • Listen/Record on port: Port client uses to send traffic through the VSE Recorder

VSE Recorder Connection Configurations

• Target host: Host address for the server. Gateway only • Target port: Port VSE Recorder uses to send and receive traffic from the server. Gateway only.

• Gateway: VSE Recorder acts as a pass-through for traffic. Requests are sent directly to the VSE Recorder and not the server. In an HTTP recording, the URL would contain the host and port of the VSE Recorder. Setting enables Target host and Target port fields.

• Proxy: VSE Recorder listens in proxy mode. In an HTTP recording, the URL would contain the host and port of the server, and the browser proxy settings are set to the VSE Recorder. Setting disables Target host and Target port fields.

Module 2: Create a Virtual Service

22 of 34

• SSL fields: Used to configure SSL settings for the recording

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 23 • VSE Recorder is in recording mode listening for traffic on the port designated in the Listen\Record on port field

VSE Recorder Transaction Recording

• As traffic is detected and recorded, the VSE Recorder displays the transactions by operation name and updates the Total transactions count • Tip: Double-click an operation to view transaction details

8001

8080

Module 2: Create a Virtual Service

23 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 24

Review Question

• The correct answer is D.

VSE Recorder Configuration

• Subsequently the Listen/Record on port configured in the VSE Recorder becomes the listen port set in the .vsm (if generated).

Which configuration designates where the VSE Recorder will receive requests from the client?

A

Target port

B

Target host

C

Transport protocol

D

Listen/Record on port

Module 2: Create a Virtual Service

24 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 25 • Ensure the Base path is correct

VSE Recorder Path Configurations

Module 2: Create a Virtual Service

25 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 26 • VSE Recorder attempts to auto-detect required protocols

VSE Recorder Request and Response Data Protocols Configurations

Module 2: Create a Virtual Service

26 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 27 • This screen only displays if Treat all transactions as stateless is unchecked, because specifying conversation starters only applies to conversational virtual services.

VSE Recorder Conversation Starter Transactions

1. Select transaction

This screen only displays if Treat all transactions as stateless is cleared

• Review the method for marking a token as a conversation starter (see student notes).

3. Select moved transaction 2. Click left arrow to move transaction

4. Highlight token

Module 2: Create a Virtual Service

5. Click rubber stamp to set token

27 of 34

Method for marking a token as a conversation starter example: 1. Select transaction containing token in Remaining Transactions 2. Click left-facing arrow to move to Conversation Starter Transactions 3. Select transaction in Conversation Starter Transactions 4. In text box below, highlight token (between <return></return> tags in example shown) 5. Click Mark (red rubber stamp) 6. Token is highlighted in yellow

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 28

VSE Recorder

• End of wizard

Virtual Service Final Processing

• Raw transactions are processed based on configurations set in wizard • Options to open the virtual service image and model files when Finish is clicked • Option to create a virtual recording session file from the session, which is very useful in situations where recording may need to be repeated.

Module 2: Create a Virtual Service

28 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 29

VSE Recorder Virtual Service Files

Virtual service model (.vsm) listens for requests

Virtual service image (.vsi) responds with data

• VSE Recorder creates the files designated during the session • .vsm configured to listen on specified port and get responses from .vsi • .vsi captured traffic used to determine virtual service responses • Raw traffic files do not display in the Project Panel • Note: Virtual service files for different transport protocols may look slightly different (for example, step names).

Module 2: Create a Virtual Service

29 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 30

VSE Recorder Session Files Overview VSE Recorder Session files (.vrs) provide the ability to save a VSE Recorder session parameters and reload the parameters into a new session

Save

 Saves configuration time when rerecording  Save session on last window of VSE Recorder  Load session on first window of VSE Recorder  Store .vrs files in VServices  VRScenarios  Folder created with new projects by default

Load

Module 2: Create a Virtual Service

30 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 31

Demonstration Create a Virtual Service by Recording In the following demonstration, you will learn how to:  Record a stateless conversation with the VSE Recorder  Capture LISA Bank transactions from a test case executing in the ITR  Create virtual service image and model from recorded transactions  Create a raw traffic file from the recorded transactions

Module 2: Create a Virtual Service

31 of 34

Demonstration Instructions: 1. Mention: Demo covers basic virtual service recording process using HTTP/S transport protocol. Some settings will be skipped and covered later. A test case will act as the client and an alternate configuration will be created and used to send traffic to the VSE Recorder.

2. Start (or ensure started) Registry and VirtualServiceEnvironment on LISASERVER + LISAWorkstation and DemoServer on LISACLIENT. 3. Open webservices-xml.tst in the examples project and open Add User step Web Services Execution (XML) Step Type Editor.

4. Discuss ENDPOINT1 property is set in the project.config file and is setting the port in the WSDL to 8080 (reference configs covered in Foundations course). Next step will create a new config file to change the value of ENDPOINT1 to port 8001 which will route the traffic from the test case to the VSE Recorder.

5. Create config file called, demoClient, set value of ENDPOINT1 to 8001, close and save, then Make Active.

6. Return to test case and show the port has changed for ENDPOINT1 property.

7. Click VSE Recorder in Main toolbar and configure fields as follows: 8. Write image to: Name service image webservices-xml.vsi 9. Transport protocol: Select HTTP/S 10. Treat all transactions as stateless: selected 11. Export to: Click browse choose VServices > Images folder and name raw traffic file webservices-xml.xml.

12. Model file: Name webservices-xml.vsm.

13. Click Next.

14. Select Gateway and set Target host: localhost and Target port: 8080.

15. Click Next. Point out Total transaction = 0. Once test case is executed, the transaction count will reflect the number of transactions captured.

16. Return to test case and execute in the ITR. When execution completes return to VSE Recorder and Total transactions = 3, plus transactions are listed.

17. Click Next to stop recording.

18. Base path default settings can remain as they are. Click Next.

19. Mention the SOAP request side protocol was auto-detected. No more configurations are needed and click Next.

20. Check Open the service image and Open the generated virtual service model then click Finish 21. Show the open virtual service image and model files and point them out in the Project Panel. Mention the raw traffic file is not displayed although it is stored in the VServices > Images folder.

22. Clean-up: Close image, model, and test case files. Make project config active.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 32

Lab Prep

• LISA Bank Kiosk is used in lab exercises

LISA Bank Kiosk Tour

• Quick review of location and features used If the Refresh icon does not update the configurations, check the UI - if there is a Retry option, click the Retry button to Refresh.

• There is a shortcut to the LISA Bank Kiosk on the Desktop of the LISACLIENT virtual lab

Click name to select user from list, then double-click the card to log in (like inserting the card into an ATM)

ATM

User/Accounts Application Form

Configuration (Host and Port)

Refresh (after updating configurations)

Module 2: Create a Virtual Service

• •

32 of 34

LISA Bank Kiosk is used in lab exercises Refresh and Retry: Sometimes, when switching between server and port settings, the kiosk will lose connectivity and display a message such as , “Error communicating with bank.” A Retry option is displayed as well. When this happens, the Refresh button in the toolbar is disabled and the Retry button on the UI must be used to refresh the server and port configurations.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 33

Lab Exercises Create Virtual Services In the following lab exercises, you will:  Create a stateless virtual service and raw traffic file by recording transactions performed in the LISA Bank Kiosk See lab 2‐1 Create a Stateless Virtual Service by Recording.  Create a conversational virtual service by importing raw traffic created in the previous exercise See lab 2‐2 Create a Conversational Virtual Service by Importing Raw Traffic.

Module 2: Create a Virtual Service

33 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Create a Virtual Service

2 - 34 • Discussion Point Answer: When you need to maintain “state” between transactions.

Module Summary Create a Virtual Service

• Discussion Point Examples: • The promotional credit in LISA Bank requires a new user to make an initial withdrawal. A conversational virtual service is required to support this scenario because the “state” of the user (i.e. a “new” user) and balance need to be maintained between transactions.

This module showed you how to:  Describe how a virtual service is created by capturing transactions  Describe basic CA LISA Virtualization concepts  Create a virtual service by recording  Create a virtual service by importing raw traffic

• However, a purely stateless virtual service can provide valid responses for all LISA Bank operations independently.

Discussion Point  When might you require a conversational virtual service over a purely stateless virtual service?

Module 2: Create a Virtual Service

• Discussion Point Important Point: • In most cases, a purely stateless virtual service can be used.

34 of 34

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-1 Time: Lecture: 15 minutes; labs: 20 minutes

Execute Against a Virtual Service CA LISA r7.5: Virtualization Fundamentals 200

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-2

Module Objectives Execute Against a Virtual Service After completing this module, you will be able to:  Execute against a virtual service at run-time  Execute against a virtual service at design-time Why you need to know:  Execution at design-time involves running a virtual service with the ITR and is used to test a virtual service before deployment to a Virtual Service Environment (VSE)  Execution at run-time involves deploying and starting a virtual service in a VSE to stand in for the live service

Module 3: Execute Against a Virtual Service

2 of 10

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-3

Deploy and Start a Virtual Service Review Virtual services are deployed and started in a VSE 

Virtual services are commonly deployed to a VSE by right-clicking a .vsm file in the Project Panel and selecting Deploy to VSE@LABNAME  There can be multiple labs with a VSE



VSE Dashboard is the GUI for VSE  Access through Server Console  Manage deployed virtual services via:  Toolbar  Right-click menu



A VSE must be running to deploy a virtual service or access the VSE Dashboard

Module 3: Execute Against a Virtual Service

• •

3 of 10

Only the default lab is used in this course.

Lab functionality is not covered in this course.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-4

Deploy and Start a Virtual Service Review Continued Virtual Services can be deployed using additional methods: 

VSEasy: Selecting a VSE server and a transport protocol, entering a name, Adding RR Pairs or .vrs files and click on Create and Deploy



VSE Manager Eclipse plug-in



LISA Invoke REST API



Command-line utility servicemanager.exe

Module 3: Execute Against a Virtual Service

• • •

4 of 10

The VSE Manager is an Eclipse plug-in that lets you deploy and manage LISA virtual services.

LISA Invoke is a REST interface for invoking CA LISA from another application.

The command-line utility servicemanager.exe is located in LISA_HOME/bin and can be used for managing virtual service environments.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-5 • When a .vsm file is deployed to VSE and displays a Status of Running in the VSE Dashboard, it is running on the machine where the VSE is running (in training labs, the host name is LISASERVER).

Execute Against a Virtual Service Run-Time To execute against a virtual service at runtime:  Deploy .vsm file to a VSE

 Configure applications to send traffic to VSE host and virtual service listen port

• The port the virtual service listens for requests on is defined in the Listen step of the .vsm.

 In training labs:

 Start virtual service  Verify “Running” Status in VSE Dashboard Clicking the link will prompt to save the VS MAR file locally

 Virtual service stands in for live service

 Host: LISASERVER  Port: 8001

Port (configured in .vsm file) that the virtual service is listening for requests on

Count of transactions processed by the virtual service

Module 3: Execute Against a Virtual Service

Tag to group virtual services

5 of 10

Multiple ways to start virtual service: • When deploying from Project Panel , select “Start the service on deployment” option in the Deploy Virtual Service settings • From VSE Dashboard, right-click a deployed virtual service and select Start (or select virtual service and click Start icon in toolbar)

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-6

Execute Against a Virtual Service

• When a .vsm file is run with the ITR, it is running on localhost.

Design-Time

• The port the virtual service listens for requests on is defined in the Listen step of the .vsm.

To execute against a virtual service at design-time:  Run .vsm file in ITR  Debug and verify virtual service is functioning properly before deploying to VSE  Most changes are made in .vsi file  Verify by executing transactions against virtual service running in ITR, and check for expected responses

 In training labs:

A virtual service model is always listening when it is not processing a request.

Click Cancel in the Executing Step dialog box to end ITR execution.

 Host: localhost  Port: 8001

Module 3: Execute Against a Virtual Service

6 of 10

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-7

Execute Against a Virtual Service

Explain when and why you might use a test case as a client.

Client Configuration

For example, you want to quickly test a virtual service is responding as expected.

To execute against a virtual service, the client must send traffic to the virtual service running in an ITR session or on a VSE  Test cases acting as a client can use config file properties to define, and easily switch, the host and port to send traffic to  LISA Bank Kiosk client configures host and port to send traffic to within the application ITR Example: Virtual service model (configured to listen on port 8001) running locally

VSE Example: Virtual service model (configured to listen on port 8001) deployed and started on VSE running on LISASERVER

Module 3: Execute Against a Virtual Service

•

• Use a test case, which invokes operations supported by the virtual service and verifies responses, to automatically execute transactions against the virtual service.

• This can often be faster than configuring your client application to send traffic to the virtual service, and then manually executing transactions and verifying responses.

7 of 10

Screenshots show client-slide configuration needed in each example scenario. These configurations will be used in training demonstrations and lab exercises.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-8

Demonstration Execute Against a Virtual Service at Design Time In the following demonstration, you will learn how to:  Run a virtual service model with ITR  Execute against a virtual service running in the ITR to ensure the virtual service is functioning properly

Module 3: Execute Against a Virtual Service

8 of 10

Demonstration Instructions • Open kioskV6.vsm and run in the ITR • Point out that while the Listen step is listening, the Execute Step dialog box continues to spin and does not move to the next step until it receives a request.

• Configure LISA Bank Kiosk to send traffic to virtual service running locally in ITR (note: the virtual service model is configured to listen on port 8001): • Host: localhost • Port: 8001 • Log in as LISA SIMPSON - PW: golisa - and then immediately log out. Note no unexpected responses, so virtual service appears to be functioning properly.

• Return to ITR • Click Cancel on the Execute Step dialog box window.

• Mention this is how the ITR execution is ended (i.e. Listen step will keep listening until model execution is ended).

• Point out steps that executed in Execution History.

• Close kioskV6.vsm without saving changes.

• Reset LISA Bank Kiosk Configuration: • Host: localhost • Port: 8080

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3-9 Lab 3-2: Some students may encounter issues with this lab. A few known fixes:

Lab Exercises Execute Against a Virtual Service

• In step 8, ensure the http:// field is configured to lisaserver, not localhost or lisaclient.

In the following lab exercise, you will:  Run a virtual service model with ITR

• In step 10, ensure the student clicks the Refresh icon on the Kiosk.

 Execute against a virtual service running in the ITR

• Occasionally the Kiosk will connect to the VSE but not register a transaction, hang, or not display the ATM card. To fix this, shut down the Kiosk, remove the VS, restart the VSE, deploy the VS, then restart the Kiosk.

See lab 3‐1 Execute Against a Virtual Service at Design Time.  Deploy and start a virtual service in a VSE  Execute against a virtual service running in a VSE See lab 3‐2 Execute Against a Virtual Service at Run Time.

Module 3: Execute Against a Virtual Service

9 of 10

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Execute Against a Virtual Service

3 - 10 Discussion Starter: Testing a new version of a virtual service to be sure it is responding as expected before replacing the older version on a VSE.

Module Summary Execute Against a Virtual Service This module showed you how to:  Execute against a virtual service at run-time  Execute against a virtual service at design-time

Discussion Point  Describe a scenario where you would run a virtual service with ITR and execute transactions against it.

Module 3: Execute Against a Virtual Service

10 of 10

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4-1 Time: Lecture: 60 minutes; labs: 0 minutes

Describe Virtual Service Matching and Responding CA LISA r7.5: Virtualization Fundamentals 200

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4-2

Module Objectives Describe Virtual Service Matching and Responding After completing this module, you will be able to:  Describe how request/response pairs are stored in a virtual service image  Describe how an inbound request to a virtual service is matched to determine a response  Describe how a virtual service responds with static and dynamic data  Describe how Magic Strings and Dates are created and used in a response Why you need to know:  Matching and responding processes determine how effectively a virtual service can respond to the live client. Knowledge of these processes provides the ability to optimize and fine-tune virtual service images

Module 4: Describe Virtual Service Matching and Responding

2 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4-3

Virtual Service Matching and Responding Concepts Matching is the process of searching virtual service image requests to find a match for an inbound request and determine the best response based on the match

Virtual service matching and responding requires a basic understanding of CA LISA Virtualization concepts:  Requests   

Arguments Attributes Meta data

 Responses

Search all transactions for a match

NO

Is there a match?

YES

  

Body Meta data Think time

 Matching    

Transaction types Match style Match script Matching order of operations



Navigation tolerance

 Responding  

Static and dynamic data Magic Strings and Dates

Module 4: Describe Virtual Service Matching and Responding

3 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4-4

Virtual Service Matching and Responding SIE Virtual service data used for matching and responding is stored in the virtual service image and edited in the Service Image Editor (SIE)

Module 4: Describe Virtual Service Matching and Responding

4 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

Describe How Request/Response Pairs are Stored in a Virtual Service Image

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

4-5

Describe Virtual Service Matching and Responding

4-6

Request/Response Pairs SIE Display Request and response data displays in the SIE by operation

Module 4: Describe Virtual Service Matching and Responding

6 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4-7 • Arguments • Example: SOAP request parameter and value are mapped to the name and value of an argument

Request/Response Pairs Request Data

• Attributes and meta data: • Stored to ensure the data is retained in the event it is needed.

• Example: Can be used in a custom-written match script to serve as matching criteria (covered later).

Request data from the client is processed and formatted in the virtual service image into three groups:  Arguments  Name/Value pairs used to determine a match for a request sent to the virtual service

 Attributes  Key/Value pairs used to store payload/body information  Not used in matching

 Meta data  Key/Value pairs used to store information not a part of the payload/body  Not used in matching

Module 4: Describe Virtual Service Matching and Responding

7 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4-8

Request/Response Pairs

Response Body Format:

Response Data

• Generally (unlike a request, which is converted into the virtual service image data format) the response retains the format needed to send the response to the client. In the screenshot examples, response retains the SOAP response format.

Response data from the server is processed and formatted for the virtual service image into three groups:  Body

• Occasionally, the response body will display in the SIE differently even though it's technically unchanged when sent back to the client.

 Response returned to client if a match is made to the corresponding request  Formatted in schema for client

 Meta data

• Sometimes a protocol will store the response body differently, say as XML, and then convert it back to the format the client expects when the response is sent to the client.

 Additional response data not part of the body  Key/Value pairs  Sent with response in the event the client requires the information

 Think time  Time the server took to respond during capture  Simulates performance Module 4: Describe Virtual Service Matching and Responding

8 of 38

• Data protocols can be applied to the response - for instance, a response might be a compressed file that needs to be decompressed in the SIE (for editing transactions, changing magic strings, etc.) and then recompressed when returned to the client.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4-9

Review Question

• The correct answer is B.

SIE Organization

• Logical transactions containing request and response data are shown in Conversational trees and the Stateless transactions list, organized by Operation.

Request and response data for transactions in the SIE is organized by:

A

Body

B

Operation

C

Attributes

D

Meta data

E

Arguments

Module 4: Describe Virtual Service Matching and Responding

• The other answer options are parts of request/response data for each operation.

9 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

Describe How an Inbound Request to a Virtual Service is Matched to Determine a Response

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

4 - 10

Describe Virtual Service Matching and Responding

4 - 11

Matching Review Matching is the process of searching virtual service image transaction requests to find a match for an inbound request and determine the best response based on the match

Search all transactions for a match

Is there a match?

Module 4: Describe Virtual Service Matching and Responding

11 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 12

Matching Transaction Types Transactions in the stateless list and conversation tree are referred to as logical transactions



Within a logical transaction are two types of transactions used in matching:

Logical

Meta Specific

 Meta  Specific

Module 4: Describe Virtual Service Matching and Responding

12 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 13

Matching Meta Transactions A logical transaction contains one meta transaction used for matching a request and potentially providing a response 

Search: Meta transaction always searched before specific transactions for matching request criteria  If no match is found in a meta transaction:  Specific transactions are not searched

Logical

Meta

 Moves to next logical transaction

 If a match is found in a meta transaction:  Specific transactions are searched  If no matches are found in specific transactions: Meta transaction provides the response Module 4: Describe Virtual Service Matching and Responding

13 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 14

Matching Specific Transactions A logical transaction consists of one or more specific transactions used to provide a specific response to a request 



There can be more than one specific transaction in a logical transaction  Example: Multiple depositMoney specific transactions made with different account numbers and amounts Search: Specific transactions searched only if a meta transaction is matched first  If no match is found in a specific transaction: Search moves to next specific transaction in list  If a match is found in a specific transaction: Specific transaction provides the response  If no matches are found in all specific transactions: Response in the meta transaction is used

Logical

Meta Specific

Module 4: Describe Virtual Service Matching and Responding

14 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 15 • Match styles can be changed as needed.

Matching Match Style

• For example, one logical transaction could use "Operation" match style and another could use "Signature“ match style.

Match Style determines the matching rules within a transaction 

Operation:  Operation names match



Signature:  Operation names match  Argument names match

• Within a list of specific transactions, the match style can also vary (one could be "Exact" and another in the same list could be a match script).

• The first transaction to match determines what response is sent.

 Argument values are not inspected  Order of arguments is not considered



Exact:  Operation names match  Argument names match  Argument values match  Specific transactions only

Module 4: Describe Virtual Service Matching and Responding

•

15 of 38

Enabling Allow duplicate specific transactions will allow the virtual service to respond more than once to the same call, choosing a different response.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 16 • Operator logic is in student notes. Review if needed.

Matching Comparison Operators Comparison operators determine how to match the value of the inbound request to the value of the arguments in the virtual service image  Specific transactions only  Can include regular and property expressions  Expressions are entered in the Value field

Module 4: Describe Virtual Service Matching and Responding

• • • • • • • • •

16 of 38

Anything: Always returns true (default for date arguments). = Returns true if the values are the same. != Returns true if the values are different. < Returns true if the inbound value is less/before/earlier than the value in the virtual service image. <= Returns true if the inbound value is less/before/earlier than or equal to the value in the virtual service image. > Returns true if the inbound value is greater/after/later than the value in the virtual service image. >= Returns true if the inbound value is greater/after/later than or equal to the value in the virtual service image.

Regular Expression: Returns true if the inbound value (string) matches the value in the virtual service image (regular expression).

Property Expression: Returns true if inbound value matches value of the property.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 17

Matching Match Script Match Script is used to create custom matching criteria 

Overrides default matching logic  Example: Match against arguments and an attribute key/value pair



Defined in meta and specific transactions



Properties add flexibility to the script



Do not use the script checkbox deactivates script without deleting the script

Module 4: Describe Virtual Service Matching and Responding

17 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 18

Matching No Match Found The customizable Response for Unknown Request is used from the Service Image tab when a match is not found

Module 4: Describe Virtual Service Matching and Responding

18 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 19

Matching Hierarchy Search all logical transactions (conversational then stateless)

Return unknown request response

NO

Match Priority: 1. Specific conversational 2. Specific stateless 3. Meta conversational 4. Meta stateless 5. Unknown response

Meta match?

Try to find a match before returning default response

YES

Search specific transactions

Specific match?

NO

YES

Return meta transaction response

Return specific transaction response

Module 4: Describe Virtual Service Matching and Responding

19 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 20

Matching

• Star indicates selected transaction

Navigation Tolerance Review

• Navigation tolerance image on slide is a general representation.

The following are basic examples to gain the general concepts.

They may vary inside an actual complex virtual service image.

• CLOSE: Only search transactions directly below • WIDE: Search CLOSE, then search left/right with CLOSE tolerance • LOOSE: Search WIDE, then search from top down.

Navigation tolerance determines how far from the last responding node the VSE can search for a match to the current request 

Configured in the meta transaction details of each logical transaction node



There are three navigation tolerance settings:  Close  Wide  Loose



Default navigation for all transactions is specified in the VSE Recorder  Last transaction navigation set separately

Module 4: Describe Virtual Service Matching and Responding

20 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 21 • When current “state” is depositMoney (meaning this was the last request responded to by the virtual service), the navigation tolerance shown here allows withdrawMoney or getAccount to be searched when looking for a match for the next request.

Matching Navigation Tolerance: Conversations Executing against a conversational virtual service image is bound to the specific order of operations (script) represented by the conversation tree navigation 

“State” maintained



Navigation generally moves from top to bottom



Navigation tolerance can provide flexibility by allowing cross-searching of branches

• However, deleteToken is not searched for a match because it is outside of the navigation tolerance.

Examples (for conversation above)

 Wide provides most accurate flexibility

Supported script: 1. Log in (getNewToken) 2. Deposit money (depositMoney) 3. Check balance (getAccount) 4. Log out (deleteToken)

 Typically navigation tolerance settings created by VSE Recorder perform optimally and do not need adjustment

Non-supported script: 1. Log in (getNewToken) 2. Deposit money (depositMoney) 3. Log out (deleteToken)

Module 4: Describe Virtual Service Matching and Responding

• Changing the navigation tolerance setting can make the search scope more narrow or more wide.

21 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 22

Matching Navigation Tolerance View: Transactionâ&#x20AC;&#x2122;s Tolerance Highlight tolerance

Select to view current tolerance settings of selected transaction

Set to wide

Module 4: Describe Virtual Service Matching and Responding

22 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 23

Conversational Navigation Navigation Tolerance for Last Transaction

Loose allows search to begin at top of navigation again Module 4: Describe Virtual Service Matching and Responding

23 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 24

Conversational Navigation Navigation Tolerance View: Close Select to preview close tolerance setting for selected transaction

Module 4: Describe Virtual Service Matching and Responding

24 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 25

Conversational Navigation Navigation Tolerance View: Wide Select to preview wide tolerance setting for selected transaction

Module 4: Describe Virtual Service Matching and Responding

25 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 26

Conversational Navigation Navigation Tolerance View: Loose Select to preview loose tolerance setting for selected transaction

Module 4: Describe Virtual Service Matching and Responding

26 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 27

Review Question

• The correct answer is C.

Response Selection

• See the Order of Operations slide for details.

If a match is found in a meta transaction, but a match is not found in the associated specific transactions, where does response come from?

A

No response is sent

B

The first specific transaction

C

The matching meta transaction

D

The Unknown Request Response

Module 4: Describe Virtual Service Matching and Responding

27 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

Describe How a Virtual Service Responds with Static and Dynamic Data

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

4 - 28

Describe Virtual Service Matching and Responding

4 - 29

Responding Static and Dynamic Data Responses in a virtual service image can contain static or dynamic data 

Static:  Hard-coded value  Does not change



Dynamic:

Static Data

 Property or expression  Varies depending on request

Dynamic Data

Module 4: Describe Virtual Service Matching and Responding

29 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 30

Responding Static Data Response values can be static – even inaccurate – without causing a client error 

True when you require a response to match format, but not value



Example: Does the response value match the format?  SSN format: ###-##-####  SSN response: 125-00-2356  Yes. Accept the value.

 Date format: MM/DD/YYYY

 Response value: 2013/01/01  No. Reject the value.

Module 4: Describe Virtual Service Matching and Responding

30 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 31 • Magic strings and dates covered in more detail later.

Responding Dynamic Responses can be altered to respond “dynamically” 

Custom scripts  Written in response body

Custom response script

 Can use properties and expressions



Magic strings  Built-in functionality  Responds with value from inbound request rather than the stored value



Magic dates  Built-in functionality  Calculates date values

Module 4: Describe Virtual Service Matching and Responding

31 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

Describe How Magic Strings and Dates are Created and Used in a Response

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

4 - 32

Describe Virtual Service Matching and Responding

4 - 33 • During recording, CA LISA attempts to identify request values that are intentionally repeated in the response and turns those values into magic strings.

Magic Strings Overview Magic Strings allow a virtual service image to return meaningful results for request values that were never captured 

Automatically created during recording



Dynamic value returned at run time  Property syntax is used to respond with value from inbound request, or default recorded value if inbound request does not provide data for magic string

With Magic Strings Recorded value: Inbound request: Response to client:

amount = 100.00 amount = 200.00 amount = 200.00

Without Magic Stings Recorded value: amount = 100.00 Inbound request: amount = 200.00 Response to client: amount = 100.00

• At run time, magic string values will vary based on values in inbound requests.

• For example: an airline booking system request includes a flight number, which is also included in the recorded response and therefore classified as a magic string. When the virtual service receives a request for a flight number that was never recorded, the correct flight number is included in the response.

 Original recorded value is stored in the magic string property in response body  Example: {{request_amount/*100.00*/}}



No calculations performed

Module 4: Describe Virtual Service Matching and Responding

33 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 34

Magic Strings

Advanced, but good to know…

Creation

• The lisa.magic.string.xml.tags property allows you to change the setting for considering anything within an XML tag for magic strings (false by default).

Magic Strings are created in a virtual service image when recorded request and response values match 

• The lisa.magic.string.exclusion property allows you to specify values that are not candidates for magic string identification.

Example  Request: accountId = 123

• Magic strings are detected not just in a simple request/response pair. If an argument is ever seen in any subsequent response in a conversation, it is deemed to be magic and the argument value is stored in the conversation state.

 Response: id = 123  Make value a magic string  Defined in the Request Data  Arguments tab  Generated in Response  Body tab  Can manually assign and edit  Regenerate as needed after editing a virtual service image

Regenerate magic strings in the virtual service

Module 4: Describe Virtual Service Matching and Responding

34 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 35

Magic Dates

Magic Date Functions

Overview

• Examples in student notes.

Magic Dates allow a virtual service to respond with meaningful date values 

Analyze inbound request to respond with the appropriate Magic Date value



Perform delta calculations based on builtin functions  From request date

Recorded date: Recorded delta: Current date: Response to client:

January 29, 2010 Current date + 3 March 13, 2013 March 16, 2013

 doDateDeltaFromRequest

• doDateDeltaFromCurrent is used if there is no date in the request.

All dates in the response are then treated as offsets from the current time of the request.

 doDateDeltaFromCurrent

Respond with valid data values dynamically



Prevent errors in systems with validation around date values

Module 4: Describe Virtual Service Matching and Responding

• One offsets from a date used as a parameter in the request, and the other from the current date of the request.

• doDateDeltaFromRequest is used if there is a date in the request data. All dates in the response are then treated as offsets from the first date in the request

 From current date 

• Main difference between the two functions is what offset is used.

35 of 38

Magic Date Functions DoDateDeltaFromRequest: {{=doDateDeltaFromRequest(“DATE FORMAT“,”OFFSET NUMBER”);/*RECORDED DATE*/}} Example: {{=doDateDeltaFromRequest("yyyy-MM-dd",“-10");/*2009-02-11*/}} • Recorded request input date: 2009-02-11 • Recorded response date offset: REQUEST INPUT DATE - 10 • Inbound request input value date: 2012/12/25 • Response date: 2012/12/15 DoDateDeltaFromCurrent: {{=doDateDeltaFromCurrent(“DATE FORMAT“,”OFFSET NUMBER”);/*RECORDED DATE*/}} Example: {{=doDateDeltaFromCurrent("yyyy-MM-dd","10");/*2009-02-11*/}} • Recorded current date: 2009-02-11 • Recorded response date offset: CURRENT DATE + 10 • Inbound request current date: 2013/01/15 • Response date: 2013/01/25

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 36

Magic Dates Creation Magic Dates are created during recording  Dates are analyzed during processing against Magic Date criteria  Criteria defined in lisa.properties

 Dates that meet the criteria are converted to Magic Dates  Delta values are captured with Magic Dates  Recorded date value is stored in response

Module 4: Describe Virtual Service Matching and Responding

36 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

4 - 37 Question: What are a few ways to increase the flexibility of a virtual service?

Module Summary Describe Virtual Service Matching and Responding

Suggested answers: This module showed you how to:  Describe how request/response pairs are stored in a virtual service image  Describe how an inbound request to a virtual service is matched to determine a response  Describe how a virtual service responds with static and dynamic data  Describe how Magic Strings and Dates are created and used in a response

Discussion Points  What are a few ways to increase the flexibility of a virtual service?  What are a few examples of when you may want to create a dynamic response?

Module 4: Describe Virtual Service Matching and Responding

37 of 38

• Create custom match scripts • Expand the virtual service image by recording many variations of the operation order in one session • Modify navigation tolerance Question: What are a few examples of when you may want to create a dynamic response?

Suggested answers: • Account balances • Tax calculations • Quantity calculations

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Matching and Responding

Module 4: Describe Virtual Service Matching and Responding

4 - 38

38 of 38

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5-1 Time: Lecture: 45 minutes; labs: 40 minutes

Manipulate Virtual Service Data CA LISA r7.5: Virtualization Fundamentals 200

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5-2

Module Objectives Manipulate Virtual Service Data After completing this module, you will be able to:  Manipulate request data during recording with Request Data Manager (RDM) protocol  Desensitize data during and after recording  Edit virtual service data in the SIE Why you need to know:  Understanding how to manipulate virtual service data enables you to fine-tune virtual services to meet the needs of your systems

Module 5: Manipulate Virtual Service Data

2 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5-3

Manipulate Virtual Service Data

• Examples provided in student notes.

Overview

• NOTE: Instruction will flow in the order needed to understand the different processes and not necessarily in the order outlined on this slide.

Request/Response data manipulation can take place during recording or after recording 

During: VSE Recorder  Manipulate data during processing to reduce manual editing



After: SIE  Fine tune the data manually for virtual service accuracy and efficiency

Module 5: Manipulate Virtual Service Data

3 of 18

Examples During: VSE Recorder • Desensitize data (transport layer) • Use Request/Response data protocols After: SIE • Edit existing transactions • Add transactions • Copy/Move transactions • Find and replace data

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

Manipulate Request Data During Recording with Request Data Manager (RDM) Protocol

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

5-4

Manipulate Virtual Service Data

5-5

Request Data Manager Protocol

Action

Overview

• Copy: Copy data in the request to another part of the request

The Request Data Manager (RDM) data protocol, which can be added in the VSE Recorder, manipulates data mapping into the virtual service image

• Move: Move data in the request to another part of the request • Delete: Delete data from the request • Keep: Keep data in a request and delete everything else in that data group Target Type • Operation • Argument • Attribute • Meta data • Request body

Module 5: Manipulate Virtual Service Data

5 of 18

• LISA session key (Used to set a conversational session key)

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5-6

Request Data Manager Protocol Example Example 

withdrawMoney contains 3 arguments



Only need to match on 2 arguments:  accountID  amount



Need to retain data for desc, but not consider it for matching



Use RDM to move the desc argument to request attributes

Module 5: Manipulate Virtual Service Data

6 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5-7

Demonstration

Demonstration Instructions

Move Arguments with the Request Data Manager

(Note: Config and raw traffic files were created in the Create a Virtual Service module demo under the examples project.)

In the following demonstration, you will learn how to:

1. Ensure demoClient.config is active

ď&#x201A;§ Reduce number of arguments in a request by moving some arguments to attributes using the RDM protocol

2. Launch VSE Recorder 3. Write image to: Replace newimage.vsi with rdmExample.vsi 4. Import traffic: VServices>Images webservices-xml.xml 5. Transport protocol: Select HTTP/S 6. Treat all transactions as stateless: Selected 7. Model file: rdmExample.vsm 8. Do not need to configure ports or base path (importing raw traffic allows these screens to be skipped)

Module 5: Manipulate Virtual Service Data

7 of 18

9. Add Request Data Manager protocol under the Web Services (SOAP) request side data protocol that was automatically added 10. Select addUser in Transaction list 11. Add an action 12. Change Action from copy to move 13. Select password in Argument list and click Source 14. Point out password argument populated Source Name in Action List 15. Change Target Type to attribute 16. Enter password in Target Name 17. Click Next 18. Check Open the service image 19. In VSI, go to addUser logical transaction and show in meta and specific transaction that password is no longer an argument and is now in the attribute list

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5-8

Lab Exercise Move Arguments with the RDM In the following lab exercise, you will:  Use the RDM protocol to move request arguments to attributes See lab 5‐1 Move Arguments with the RDM.

Module 5: Manipulate Virtual Service Data

8 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

Desensitize Data During and After Recording

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

5-9

Manipulate Virtual Service Data

5 - 10

Data Desensitization Review Data desensitization replaces sensitive data with random, yet validly formatted, values  Examples:  Protected health information  Social security number (SSN)

Dynamic operation in VSE Recorder  Desensitize (transport protocol)  Data Desensitizer (data protocols) Static operation in SIE  Edit each instance of data manually  Search and replace

Module 5: Manipulate Virtual Service Data

10 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5 - 11 • Recommend using a regex tool to help construct and verify regular expressions.

Data Desensitization desensitize.xml Dynamic data desensitization is managed by the desensitize.xml file located in LISA_HOME  Parsed each time VSE Recorder starts  Supplies preset patterns, such as: SSN, credit card number, email, and address  Executes regular expression (regex) pattern matching to recognize/find sensitive data  Customizable  Edit patterns to fit desensitization needs  Use built-in string generator patterns or custom regex as replacement data options

Module 5: Manipulate Virtual Service Data

11 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5 - 12

Lab Exercise Desensitize Data In the following lab exercise, you will:  Desensitize data at the transport layer during virtual service recording  Desensitize data manually in the SIE See lab 5‐2 Desensitize Data.

Module 5: Manipulate Virtual Service Data

12 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

Edit Virtual Service Data in the SIE

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

5 - 13

Manipulate Virtual Service Data

5 - 14

SIE Edit Data After Recording Virtual service request/response data is stored in virtual service image (.vsi) files and is edited in the SIE

Module 5: Manipulate Virtual Service Data

14 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5 - 15

Demonstration Edit Data with SIE In the following demonstration, you will learn how to:  Save an existing .vsi file with a new name  Add and edit request/response data  Alter a conversation tree  Copy a transaction from a conversation tree to the stateless transactions list  Search and replace values globally  Add a transaction

Module 5: Manipulate Virtual Service Data

15 of 18

Perform, and give high-level explanation of, basic editing in the SIE Note: Focus on examples of how to edit, rather than editing for proper functionality 1. In examples project, open kioskV6.vsi and save as kioskV6-updated.vsi 2. Change Image name to kioskV6-updated in Service Image tab 3. In Transactions tab, scroll left and select top depositMoney logical transaction (note: meta transaction details for this logical transaction are shown on right) 4. Expand Request Data and explain toolbar functions at bottom (add/reorder/delete/mass change arguments) 5. Select Magic String for desc argument (in meta transaction request) 6. Use Mass Change tool to change all desc/ATM Deposits to magic strings and explain basics of tool 7. In same depositMoney transaction, select first specific transaction 8. Change amount Comparison Operator 9. Grab depositMoney transaction and drop it on withdrawMoney to move branch 10. Scroll to far-right and select top getTransactions logical transaction 11. Add argument to meta transaction: Name=type, Value=Savings 12. Go to specific transaction. Point out can't add argument. It was added automatically. Change type value to SAVINGS 13. Go to the response and change type value to SAVINGS (note: double click in value field to edit) 14. Change Think time spec to 100 to simulate slightly slower performance 15. Go to stateless list and show there are no deleteToken transactions in the list – this virtual service only supports ending a session if conversation tree followed 16. Right-click any deleteToken and copy to stateless to support ending session at any time 17. Show deleteToken now in stateless list.

18. Go to first addUserObject in stateless list 19. Delete userObject_accounts_balance_1 and 2 20. Go to specific addUserObject and point out arguments were auto-deleted 21. Right-click addUserObject select Search and replace. Replace @itko.com with @ca.com for the entire image. Select a few transactions to show changes.

22. Add a new addUserObject stateless transaction with HTTP/S protocol 23. Add meta argument Name=userObject_login and Value=user200@ca.com 24. In request select Formatted text and enter: user200@ca.com is new 25. Copy meta transaction and paste in to create the specific transaction

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5 - 16

Lab Exercise Edit a Virtual Service Image with SIE In the following lab exercise, you will:  Edit an existing virtual service image  Test the virtual service changes at design time See lab 5‐3 Edit a Virtual Service Image with SIE.

Module 5: Manipulate Virtual Service Data

16 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

5 - 17

Module Summary

• Question: Why might you use data protocols in the VSE Recorder?

Manipulate Virtual Service Data

• Suggested answer: Prevents manual editing in the SIE and ensures accurate changes.

This module showed you how to:

• Question: Does your system hold sensitive data? What could you do if some fields are not automatically desensitized?

 Manipulate request data during recording with Request Data Manager (RDM) protocol  Desensitize data during and after recording

• Suggested answers: Search and replace in the SIE, use Data Desensitizer data protocol handlers, or update desensitize.xml.

 Edit virtual service data in the SIE

Discussion Points  Why might you use data protocols in the VSE Recorder?  Does your system hold sensitive data? What could you do if some fields are not automatically desensitized?

Module 5: Manipulate Virtual Service Data

17 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Manipulate Virtual Service Data

Module 5: Manipulate Virtual Service Data

5 - 18

18 of 18

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6-1 Time: Lecture: 15 minutes; labs: 0 minutes

Describe Virtual Service Model Steps CA LISA r7.5: Virtualization Fundamentals 200

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6-2

Module Objectives Describe Virtual Service Model Steps After completing this module, you will be able to:  Describe the difference between virtual service model styles  Describe the roles of common virtual service model steps Why you need to know:  Virtual service model styles impact the performance and execution of virtual services  Virtual service model steps are configured to provide various functions through different execution modes, such as transaction tracking for virtual service issue resolution, synchronizing with the live system, and manipulating request/response data at the step level

Module 6: Describe Virtual Service Model Steps

2 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

Describe the Difference Between Virtual Service Model Styles

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

6-3

Describe Virtual Service Model Steps

6-4 • NOTE: This course focuses on virtual services using HTTP/S transport protocol.

Virtual Service Models Overview

• Review execution modes at high-level to set context for this module. Execution modes are covered in more detail later.

Virtual service models manage the execution of a virtual service 

Model styles

Execution Modes:

 More efficient: 6 steps

• Virtual service executed in one of the following modes (commonly set from VSE Dashboard). Virtual service model steps (commonly set in VSE Recorder) implement execution mode behavior.

 More flexible: 8 steps



Execution modes  Most Efficient  Transaction Tracking

• Most Efficient • Minimal tracking • Best performance

 Live System  Image Validation  Dynamic

Module 6: Describe Virtual Service Model Steps

4 of 16

NOTE: This course focuses on virtual services using HTTP/S transport protocol

• Transaction Tracking • Track transaction request/response details • Debugging • Live System • Passes request through to live system for response • Image Validation • Validate live system and virtual service image match • Update (heal) image if live service has changed • Dynamic • Decide which mode to use on a per-request basis

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6-5 • NOTE: Step names are created dynamically. We will cover the steps and call them by their basic role rather than specific name or type.

Virtual Service Models Styles More Efficient 6 steps

More Flexible 8 steps

• Use more efficient if you don't need to manipulate the request or response.

• Use more flexible, if you need to manipulate the request and/or response. For example, you could add scripted logic to process the request/response.

Module 6: Describe Virtual Service Model Steps

5 of 16

More efficient: • 6 steps • Does not include Prepare Request/Response steps • Faster performance/default More flexible: • 8 steps • Includes Prepare Request/Response steps • Reduced performance/more dynamic

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

Describe the Roles of Common Virtual Service Model Steps

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

6-6

Describe Virtual Service Model Steps

6-7

Virtual Service Model Steps

• Actual step type: Virtual HTTP/S Listener

Virtual HTTP/S Listener Step

• Listen port: The port on which CA LISA listens for the HTTP/S traffic.

Virtual HTTP/S Listener step simulates an HTTP server

• Bind address: Enter the local IP address on which connections can come in. By default no bind address is specified, which indicates that the listen step accepts connections on the specified port regardless of the NIC (or IP address) it comes in on.



Listens for incoming HTTP request



Converts request to standard virtual service request format

• Use SSL to client: Select this box if you want to simulate a secure HTTPS Web site. Then supply the SSL keystore information • Base path: Used to route HTTP requests properly and is similar to a queue name or doc router.

• Format step response as XML: By default the step response is formatted as a list of response objects.

Module 6: Describe Virtual Service Model Steps

7 of 16

• Bind only: • Check this box to acquire the network resource and move to the next step.

• A second Listen step is required that does not use the Bind only option.

• This option allows the model to listen on a port (requests are queued until a listen step consumes them) and perform setup tasks before dropping into the wait/process/respond loop.

• For example, Step 1 of the model acquires the listening port (using Bind only) and step 2 triggers external software that sends requests.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6-8

Virtual Service Model Steps Virtual HTTP/S Listener Step Elements Virtual HTTP/S Listener step elements: 

Filter – Data Protocol Filter  Creates wrapper for a data protocol to act as a filter  Extracts meaningful information from the body of the transaction to assist with transaction processing



Assertion – Assert on Execution Mode (Named: If being efficient)  Automatically added to “more efficient” models  Alters workflow if execution mode is set to Most Efficient  If Most Efficient is true then execute VS Image Response Selection step next

Module 6: Describe Virtual Service Model Steps

8 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6-9 • Actual step type: Parse Text as Response

Virtual Service Model Steps Prepare Request Prepare Request step modifies request and saves it as a property  Automatically added to “more flexible” models  Allows for request manipulation before passing on for routing or searching virtual service image for response  Parses the request and stores it as XML string in lisa.vse.request property

Module 6: Describe Virtual Service Model Steps

9 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6 - 10

Virtual Service Model Steps

• Actual step type: Virtual Service Router

Virtual Service Router

• Note: named “Virtual Service Execution Router” in more flexible models.

Virtual Service Router step routes request to the next appropriate step based on the execution mode

• Live invocation is used by Live System & Image Validation execution modes

 Assert on Execution Mode (embedded assertion) determines execution mode and next step  If live invocation – use selected step  If dynamic – use subprocess or script to determine

Module 6: Describe Virtual Service Model Steps

•

10 of 16

May have to expand the editor window to see the Available Objects.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6 - 11 • Actual step type: Virtual Conversational/Stateless Response Selector

Virtual Service Model Steps VS Image Response Selection VS Image Response Selection step selects the correct response for a request  Retrieves request from lisa.vse.request  Specifies location of virtual service image  Retrieves response from virtual service image  Determines which step to execute next based on execution mode using Assert on Execution Mode assertions  If validating: HTTP/S Live Invocation  If tracking: Virtual Service Tracking step

Module 6: Describe Virtual Service Model Steps

11 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6 - 12 • Actual step type: Parse Text as Response

Virtual Service Model Steps Prepare Response Prepare Response step modifies the response  Automatically added to “more flexible” models  Allows for response manipulation before returning it to the client  Parses the response and stores as XML string in lisa.vse.response property

Module 6: Describe Virtual Service Model Steps

12 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6 - 13 • Actual step type: Virtual HTTP/S Responder

Virtual Service Model Steps Virtual HTTP/S Responder HTTP/S Responder step provides the response before it is sent to the client 

Sends response to Virtual HTTP/S Listener step  Virtual HTTP/S Listener step sends response to client



Defines conversational model properties  Allows values to be available to downstream conversational requests  Handles conversation “state” and other session-based information

Module 6: Describe Virtual Service Model Steps

13 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6 - 14 Actual step type: Virtual HTTP/S Live Invocation

Virtual Service Model Steps Virtual HTTP/S Live Invocation The Virtual HTTP/S Live Invocation step sends the request to the live server rather than the virtual service image  Supports execution modes:  Live System  Image Validation

 Assert on Execution Mode assertion determines which step to execute next  If validating: if execution mode is set to Image Validation, then go to Virtual Service Tracking step

Module 6: Describe Virtual Service Model Steps

14 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6 - 15 Actual step type: Virtual Service Tracker

Virtual Service Model Steps Virtual Service Tracking Virtual Service Tracker step captures request/response tracking data to display in the VSE Dashboard  Session Tracking Information tab  Tracks:  Request sent to the virtual service image  Request matched in virtual service image  Response sent from virtual service image to client

 Does not track responses from a live server

Module 6: Describe Virtual Service Model Steps

15 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Describe Virtual Service Model Steps

6 - 16 Discussion starter: Use more flexible, if you need to manipulate the request and/or response. For example, you could add scripted logic to process the request/response.

Module Summary Describe Virtual Service Model Steps This module showed you how to:  Describe the difference between virtual service model styles  Describe the roles of common virtual service model steps

Discussion Point  When might you want to use the “more flexible” model style?

Module 6: Describe Virtual Service Model Steps

16 of 16

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-1 Time: Lecture: 25 minutes; labs: 15 minutes

Configure Virtual Service Execution CA LISA r7.5: Virtualization Fundamentals 200

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-2

Module Objectives Configure Virtual Service Execution After completing this module, you will be able to:  Describe the role of virtual service Execution Modes  View execution details in the VSE Dashboard  Debug a virtual service using Transaction Tracking mode Why you need to know:  Execution modes allow a single virtual service to run in different ways  Execution modes and details in the VSE Dashboard are useful for debugging and updating virtual service images

Module 7: Configure Virtual Service Execution

2 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-3

Overview

• Most Efficient • Minimal tracking • Best performance

Virtual service Execution Modes change the behavior of the virtual service model by changing the workflow during execution

• Transaction Tracking • Track transaction request/response details • Debugging

Execution Modes:

• Live System • Passes request through to live system for response

Execution Modes

 Most Efficient  Transaction Tracking

• Image Validation • Validate live system and virtual service image match • Update (heal) image if live service has changed

 Live System  Image Validation  Dynamic

• Dynamic • Decide which mode to use on a per-request basis Module 7: Configure Virtual Service Execution

3 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-4

Execution Modes Configuring Execution Mode The Execution Mode can be changed dynamically at run-time from the VSE Dashboard

Most Efficient is the default mode

Module 7: Configure Virtual Service Execution

4 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-5 • Also, restricts generated event tracking.

Execution Modes Most Efficient Most Efficient mode is best for performance 

Does not execute steps:  Virtual Service Router  HTTP/S Live Invocation  Virtual Service Tracking

Module 7: Configure Virtual Service Execution

5 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-6 • Fires more events than Most Efficient mode.

Execution Modes Transaction Tracking Transaction Tracking mode tracks virtual service transaction execution details 

Records request/response and session activity  Tracking overhead slows performance  Tracking data accessed through the VSE Dashboard  Provides insight into transaction for debugging  Helps determine why a particular response was chosen for a given request



Does not execute HTTP/S Live Invocation step

Module 7: Configure Virtual Service Execution

•

6 of 20

Does not show live system responses.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-7 Any protocol that doesn't support Live Invocation simply won't have the step in the model.

Execution Modes Live System Live System mode executes the Live Invocation step to determine a response to the current request 

Model accesses the live service for the response, rather than the virtual service image



Performance is determined by the live system



Also known as “pass-through” mode



Does note execute steps:

 VS Image Response Selection  Virtual Service Tracking 

Applies to HTTP/S, Java, and TCP only

Module 7: Configure Virtual Service Execution

•

7 of 20

Useful to quickly switch to your live system without changing your configurations.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-8 • Anything that supports Live Invocation also supports Image Validation

Execution Modes Image Validation Image Validation mode compares responses provided by the virtual service image and the corresponding live service 

Patches (heals) the virtual service image to keep in sync with the live service



Also known as “model healing”



All steps execute



Worst performance



Applies to HTTP/S, Java, and TCP only

Module 7: Configure Virtual Service Execution

8 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7-9

Execution Modes Dynamic Dynamic mode dynamically determines which mode to execute on a per-request basis 

Subprocess or script in Virtual Service Execution Router step determines mode to use for each request



Performance is not predictable



Applies to HTTP/S, Java, and TCP only

EFFICIENT = Most Efficient TRACK = Transaction Tracking LIVE = Live System VALIDATION = Image Validation DYNAMIC = Dynamic

Module 7: Configure Virtual Service Execution

9 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 10 â&#x20AC;˘ The correct answer is E.

Review Question Debugging Which execution mode provides insight into virtual service transactions useful for debugging?

A

Dynamic

B

Live System

C

Most Efficient

D

Image Validation

E

Transaction Tracking

Module 7: Configure Virtual Service Execution

10 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

View Execution Details in the VSE Dashboard

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

7 - 11

Configure Virtual Service Execution

7 - 12

Execution Details VSE Dashboard Basics The VSE Dashboard provides insight into virtual service execution in the: 

Virtual Services Details



Metrics tab



Inspection View



Session/Tracking Information (Transaction Tracking only)

Module 7: Configure Virtual Service Execution

12 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 13

Execution Details

• Model Name: Selected virtual service model name.

Virtual Service Details

• Execution Mode: Current execution mode.

The Virtual Service Details displays basic information about a virtual service deployment options and run-time execution  Counts can be reset  Capacity, Think Scale, and Auto-Restart can be configured while a virtual service is running

• Last Start: Date and time this service was last started.

• Transaction Count: Number of transactions recorded since service start.

• Current txn/s: Number of transactions currently executing.

• Capacity: Number of virtual users (instances) allowed to execute against the virtual service at one time. Number can be updated while running.

• Config Name: Name of configuration file used by this service.

• Auto-Restart: Current auto-restart selection. Can be updated while running.

• Last End: Date and time last stopped.

Module 7: Configure Virtual Service Execution

13 of 20

• Error Count: Number of errors encountered.

• Peak txn/s: Largest number of transactions run concurrently.

• Think Scale: Think time percentage with respect to the recorded think time. Can be updated.

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 14 • On the Matching tab, recent requests processed by the virtual service are listed.

Execution Details Inspector - Matching The Matching tab in the Inspector tab displays matching details of requests and any events associated with the request during execution

• When a request is selected, a description is shown of how the request was (or was not) matched. This is essentially the same information that is recorded in the vse_matches.log file.

• If any events were associated with the selected request, they are displayed at the right side of the panel.

Module 7: Configure Virtual Service Execution

14 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 15

Execution Details Inspector – What Happened Text in the What Happened panel can be used to check for a match in the virtual service image:  Select the text and copy  Navigate to the virtual service image and click Match Description from Clipboard in the toolbar  If there is a match the transaction will display highlighted in yellow

Module 7: Configure Virtual Service Execution

15 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 16 â&#x20AC;˘ The Request Event Details tab lists inbound requests with errors and the events associated with the request for use in debugging.

Execution Details Inspector - Request Event Details The Request Event Details tab lists inbound requests with errors and the events associated with the request for use in debugging

Module 7: Configure Virtual Service Execution

16 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 17 • Update virtual service manually or using Image Validation mode.

Execution Details

Transaction Tracking  Session Data Session Data is captured in Transaction Tracking mode and provides details to determine why a response was selected for a request, which is useful in debugging and “healing” 

Update virtual service manually or using Image Validation mode

If blank, the virtual service did not find a match for the live request from the client

Module 7: Configure Virtual Service Execution

17 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 18

Execution Details Metrics Tab The Metrics tab generates charts of performance and transaction metrics To generate a chart: 

Select a chart



Select a service



Click Generate Chart

Module 7: Configure Virtual Service Execution

18 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 19

Lab Exercise Run a Virtual Service in Transaction Tracking Mode In the following lab exercise, you will: 

Deploy and run a virtual service in Transaction Tracking mode



Use Transaction Tracking data to determine why a request failed See lab 7‐1 Run a Virtual Service in Transaction Tracking Mode.

Module 7: Configure Virtual Service Execution

19 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Configure Virtual Service Execution

7 - 20 Discussion point question: What is the difference between Live System and Image Validation modes?

Module Summary Configure Virtual Service Execution This module showed you how to:  Describe the role of virtual service Execution Modes

Discussion point answer:

 View execution details in the VSE Dashboard

• Both modes communicate with the live system.

 Debug a virtual service using Transaction Tracking mode

• Live System bypasses the data in the virtual service image and passes through the virtual service to the live system.

Discussion Point  What is the difference between Live System and Image Validation modes?

Module 7: Configure Virtual Service Execution

• Image Validation communicates with the live system then compares the virtual service image with the live system and allows for “healing” of the virtual service image when differences are found.

20 of 20

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8-1 Time: Lecture: 10 minutes; labs: 20 minutes

Maintain and Troubleshoot a Virtual Service CA LISA r7.5: Virtualization Fundamentals 200

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8-2

Module Objectives Maintain and Troubleshoot a Virtual Service After completing this module, you will be able to:  Describe the common methods used to update a virtual service  Select the appropriate method for updating a virtual service  Identify and fix common problems with virtual services  Navigate to log files used for troubleshooting Why you need to know:  Change is inevitable during development requiring updates to virtual services  Virtual service updates can sometimes lead to problems with virtual service deployment and functionality

Module 8: Maintain and Troubleshoot a Virtual Service

2 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

Maintain a Virtual Service

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

8-3

Maintain and Troubleshoot a Virtual Service

8-4

Maintain a Virtual Service Overview Virtual services often require updates to keep in synch with development changes  Think of a virtual service image as a disposable asset  Not uncommon to rerecord an entire virtual service image to match large changes during development  CA LISA provides several methods to manage updates both small and large

Module 8: Maintain and Troubleshoot a Virtual Service

4 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8-5

Maintain a Virtual Service

• Manually editing the VSI is often the best choice for small changes.

Update Methods

• Image Validation mode enables “model healing”.

• Re-recording is often best choice for large changes.

There are both manual and automated methods available to maintain a virtual service image 

Manually edit the .vsi file in the SIE



Execute in Image Validation mode to synch virtual service image with live system



Re-record entire virtual service image completely



Merge new data into an existing .vsi file  Update an existing .vsi file using the VSE Recorder



Combine existing .vsi files  Select one or more .vsi files to combine into an existing one in the Project Panel

Module 8: Maintain and Troubleshoot a Virtual Service

• Merge method is useful for recording changes and updating an existing .vsi file at the same time.

• Combine method is useful when .vsi files with required transactions already exist.

5 of 14

Merge method details: • Select the existing .vsi for the Write image to field • Select Merge into option • New recording is merged into existing .vsi Combine method details: • Right-click original .vsi in the Project Panel and select Combine other service images into this one • New .vsi is combined with existing .vsi

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8-6

Maintain a Virtual Service Update Methods Recommendations Depending on scope of changes, different methods are recommended over others  Manual edits  Recommended for simple changes  Add/remove transactions and paths  Change request parameters  Add new fields and data to responses  Change think time

 Image Validation  “Model healing”  Recommended for many various updates to existing data  New operations  Different request/response data

 Re-record entire .vsi  Recommended for large changes  Recommended option when using automated tests as client

 Record and merge  Recommended when need to expand on the existing data

 Combine .vsi files  Recommended when existing .vsi files contain required transactions  Recommended to expand existing data and also keep independent versions of the original and new data

Module 8: Maintain and Troubleshoot a Virtual Service

6 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8-7

Review Question

• The correct answer is D.

Model Healing

• Image Validation Execution Mode enables “model healing” functionality.

Model healing is performed:

A

Manually in the SIE

B

By merging old and new .vsi files

C

By rerecording the virtual service image

D

By running the virtual service in Image Validation Execution Mode

Module 8: Maintain and Troubleshoot a Virtual Service

7 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

Troubleshoot a Virtual Service

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

8-8

Maintain and Troubleshoot a Virtual Service

8-9

Troubleshooting

Port conflicts scenario:

Common Issues and Fixes

• Listen port of virtual service set to 2010, but Registry is running on that port.

A few common errors seen when deploying and executing against virtual services, which can be easily fixed are: 

Port conflicts  Example: Virtual service deploys, but immediately ends with an error in VSE Dashboard  HTTP/S Listen step configured to listen on a port currently in use



Missing .vsi file scenarios:

 To fix issue, change Listen port in HTTP/S Listen step to an unused port

• A typo in .vsi file name or location

Missing .vsi file

• A new .vsi file is created and old is deleted, but .vsm was not updated with new file name.

 Example: Virtual service does not deploy and an error displays in LISA Workstation UI  Specified .vsi file can not be found  To fix issue, update Service image location in VS Image Response Selection step to correct .vsi path



• Note: Current Registry settings can easily be seen via Change Registry button in LISA Workstation UI main toolbar.

Unexpected response

• A stateless transaction is missing to support an operation that can be called at any time.

 Example: Virtual service image returns the Unknown Request Response  A transaction or some data is missing  To fix issue, add new transaction or data in SIE Module 8: Maintain and Troubleshoot a Virtual Service

Unexpected response scenarios:

• Arguments or matching criteria are incorrect.

9 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8 - 10

Troubleshooting Transaction Data Clean Up Transaction Data Cleanup provides options to clean up excess tracking data which can cause performance issues with a virtual service  Settings configured for a virtual service running in the VSE Dashboard  Values remain in effect until the service is stopped and restarted  Once stopped, values reset according to their defaults

 Defaults values set in .properties file

Module 8: Maintain and Troubleshoot a Virtual Service

10 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8 - 11 • lisatmp directory is located under the user’s home directory and named lisatmp_<lisa.version.number>

Troubleshooting CA LISA Log Files

vse_matches.log: CA LISA log files provide insight into errors with virtual services  vse.log  VSE server and process level logging  CA LISA Server machine

Work with your CA LISA Server administrator or Solution Architect (SA) to properly configure and read these files

• On CA LISA Workstation machine captures matching and response data any time a response lookup step of a virtual service model is run with ITR. • On CA LISA Server machine captures matching and response data any time a response is processed by a virtual service running in a VSE.

 In lisatmp directory

 vse_matches.log  VSE matching and navigation logging  Both CA LISA Server and Workstation machines  In lisatmp directory

 logging.properties  Configure logging levels for VSE logging  Both CA LISA Server and Workstation machines  In LISA_HOME

Module 8: Maintain and Troubleshoot a Virtual Service

11 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8 - 12

Lab Exercises Troubleshoot and Shutdown In the following lab exercises, you will: 

Troubleshoot a virtual service that does not run



Troubleshoot a virtual service that does not deploy

See lab 8‐1 Troubleshoot Deployment.



Troubleshoot an unexpected response

See lab 8-2 Troubleshoot Execution. 

Shut down components and labs See lab 8-3 Shut Down Components and Log Off Virtual Labs.

Module 8: Maintain and Troubleshoot a Virtual Service

12 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8 - 13

Module Summary

Discussion point possible answers:

Maintain and Troubleshoot a Virtual Service

• Manual: If not too many new operations.

 Describe the common methods used to update a virtual service

• Image Validation mode: If live system is available for automated “healing”.

 Select the appropriate method for updating a virtual service

• Re-record: If there are many changes.

This module showed you how to:

 Identify and fix common problems with virtual services

• Record and merge: Maybe, depending on how the operations are integrated.

 Navigate to log files used for troubleshooting

• Combine: If existing .vsi files contain required transactions.

Discussion Point  A new set of operations are added to a live system - which is virtualized for developing and testing against - which method might you use to update your virtual service, and why?

Module 8: Maintain and Troubleshoot a Virtual Service

13 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.

Maintain and Troubleshoot a Virtual Service

8 - 14

Course Summary CA LISA r7.5: Virtualization Fundamentals 200 You are now able to do the following: 

Describe service virtualization



Create a virtual service



Execute against a virtual service



Describe virtual service matching and responding



Manipulate virtual service data



Describe virtual service model steps



Configure virtual service execution



Maintain and troubleshoot virtual services

Module 8: Maintain and Troubleshoot a Virtual Service

14 of 14

CA LISA r7.5: Virtualization Fundamentals 200 CA CONFIDENTIAL AND PROPRIETARY INFORMATION. UNAUTHORIZED COPYING OR DISTRIBUTION PROHIBITED.