The document discusses service virtualization and how it differs from other types of virtualization. Service virtualization involves modeling the behavior of a service to stand in for the actual service during development and testing. It addresses limitations of hardware virtualization by virtualizing entire services or service interfaces. This allows development teams to have their own isolated testing environments with access to necessary services 24/7 without capacity or resource constraints.

1. ca DevCenter
Service Virtualization 101: What is a
Virtual Service and What Is Not
Chris Kraus
CA Technologies
Senior Principal Product Manager
DCX12E

2. Agenda
TYPES OF VIRTUALIZATION
HOW IS SERVICE VIRTUALIZATION DIFFERENT?
DEMONSTRATION
1
2
3
3 © 2014 CA. ALL RIGHTS RESERVED.

3. Types of Virtualization

4. Introduction: What is Virtualization?
Leading technology analysts
broadly define virtualization as
“the practice of simulating the
behavior of a physical asset.”
 For example, a server or
application in a software emulator
then hosting that emulator in a
virtual environment
5 © 2014 CA. ALL RIGHTS RESERVED.
The virtual environment
must behave enough like
the physical environment
to ensure interactions with
the emulated service look
like the real one.
Benefits of virtualization include:
 Control: Better ability to manage physical assets, simplifying change and
configuration management
 Capacity: Improved utilization of physical assets
 Agility: Reduced wait time (and associated costs) related to IT groups making changes
to environment configurations and hardware resource allocations

5. Virtualization Types
Virtualization is the creation of
a virtual (rather than actual)
version of an asset, such as:
 Operating systems
 Servers
 Storage Devices
 Network Resources
 Data Services
Virtualization examples:
 VM Ware
 Citrix
 VPN
 and others . . .
6 © 2014 CA. ALL RIGHTS RESERVED.

6. SDLC Challenges
Without Virtualization in Use
MF
SaaS or Hosted
Solution
Service 1 Service 2
INTEGRATION LAYER
Application 1 Application 2
Server issues:
1. Access restricted
2. Capacity constraints
3. Data volatility
4. Security concerns
Service provider issues:
1. Commingled services
2. Difficulties with parallel
development of apps and
services
7 © 2014 CA. ALL RIGHTS RESERVED.
Cloud/SaaS issues:
1. Costly access
2. Volatile data
Net effect of these issues:
 Server proliferation
 Lost productivity in
development
 Greater cost of third-party
systems
 Increased risk of production
issues
App team issues:
1. Every App team needs their
own infrastructure.
2. Every discipline (Dev, Test, Int)
wants their own environment.

7. Hardware Virtualization
Hardware virtualization is the simulation of hardware behavior.
The key driver of hardware virtualization is to improve utilization of physical capacity.
Can be used to:
 Virtualize test beds.
 Maintain the countless configuration of operating systems and platforms that software needs to run against.
Some limitations include:
 Many of the enterprises most complex (mainframes) and costly systems (externally hosted partner services, SaaS,
cloud-based systems and systems under a high degree of change) can not be imaged into a virtual machine.
 It does not adequately address non-hardware costs, such as licensing, data volatility, patch release management
and other significant IT admin costs (maintaining server images, software configurations, installs, etc.).
 It cannot contain cost and stabilize the data of third-party hosted applications, SaaS and cloud-based systems.
8 © 2014 CA. ALL RIGHTS RESERVED.

8. Hardware virtualization is helpful... but still NOT
enough.
MF
SaaS or Hosted
Solution
Application Application
Server issues UNCHANGED:
1. Restricted access
2. Capacity constraints
3. Data volatility
4. Security concerns
Service provider
issues HELPED:
1. Commingled services SOLVED
2. Difficulties with parallel
development of Apps and
Services
9 © 2014 CA. ALL RIGHTS RESERVED.
Cloud/SaaS issues
UNCHANGED:
1. Costly access
2. Data volatility
Net effect:
 Middle-tier server
proliferation prevented
 Largest, most complex, most
costly systems not affected
App team issues HELPED:
1. First level of connectivity solved
App team issues
UNCHANGED:
1. Back end systems/services
Virtual Server

9. How Is Service Virtualization Different?

10. Added Value Through Service Virtualization
[virtualized within VSE]
MFvs Service2vs
Service2vs
Integration Layer
Hardware Virtualized VM instance
11 © 2014 CA. ALL RIGHTS RESERVED.
App team BENEFITS:
1. All teams get their own extended
environment at very low
incremental cost.
2. There are no conflicts with other
application teams
Server BENEFITS:
1. Available 24/7
2. Unlimited capacity
3. Data consistency
4. Sensitized for security
Service provider
BENEFITS:
1. Services all in isolated
environment
2. Virtual services enable parallel
development.
Virtual Service Environment
Virtual Servers

11. CA Service Virtualization
Service virtualization involves the modeling of a virtual service process and the imaging of
software service behavior to “stand in” for the actual service during development and testing.
 Is complementary to hardware virtualization and provides a solution to address hardware
virtualization limitations
CA has developed the ability to virtualize the behavior of applications and infrastructure
components at either the entire endpoint or at an interface level. This enables organizations to:
 Provide 24/7 access to service end points
 Remove capacity constraints
 Remove contention for shared resources
 Provide an alternative to unavailable systems and those still under development
 Control complex data scenarios that are inherent during the SDLC
 Reduce or eliminate the cost of invoking third-party systems for non-production use
12 © 2014 CA. ALL RIGHTS RESERVED.

12. What does a “Virtual Service” do?
The function of a “virtual service” can be summarized in three steps:
LISTEN PROCESS RESPOND
The behavior of the “process” step can be a variety of actions:
 Perform some business logic:
‒ Deactivate expired accounts
‒ Send emails to customers
‒ Print weekly reports
 Retrieve the correct ZIP code for a supplied address
 Retrieve rows from a database to include in the response
 Add/update/delete rows from a database
13 © 2014 CA. ALL RIGHTS RESERVED.

13. Assumptions About Virtual Services
The virtual service (VS) created by CA Service Virtualization will stand in for the
real service
We are not duplicating all of the real service’s complex logic
Assumptions include:
VS can predict future behavior from current behavior:
 Behavior is fully encompassed in request/response loops (VSE txns)
 Variation in responses are based on either the input value variation and/or the context of the
conversation
VS can lie and consumers won’t know or care, however:
 The structure of the response must be what they expect
 Consumers will verify that values they provide as input match output, otherwise they will get upset
 Dates being outside of their expectations really make the consumer upset
14 © 2014 CA. ALL RIGHTS RESERVED.

14. The Big Problem: Constraints Across the SDLC
ESB
x x x
Incomplete
Development
“I can’t do anything until I have everything…
and I never have everything!”
15 © 2014 CA. ALL RIGHTS RESERVED.
!
!
! ! !
System Unavailable
x
Invalid data Access Fees

15. The Big Problem: Constraints
ESB
! ! !
System Unavailable Invalid data Access Fees
“I have everything I need, when I need it!"
16 © 2014 CA. ALL RIGHTS RESERVED.
Incomplete
Development

16. CA Enables True Agile Development
17 © 2014 CA. ALL RIGHTS RESERVED.
PRESENTATION
APPLICATION SERVICES
INTEGRATION LAYER
BACKEND
ESB
CA Application
Test

17. Service Virtualization: How does it work?
CAPTURE PROCESS MODEL
18 © 2014 CA. ALL RIGHTS RESERVED.
Living, breathing “live” model
TRUE AGILE
DEVELOPMENT
Sophisticated, contextual behavior
Automatic handling for dynamic
properties
Record traffic between existing systems.
Create from engineering specifications.
Draw from sources such as log files,
sample data, packet capture and
CA Continuous Application Insight.

18. DevTest Benefits
 Provide round-the-clock access to service end points.
 Remove capacity constraints.
 Remove contention for shared resources.
 Provide an alternative to unavailable systems and
those that are still under development.
 Control complex data scenarios that are inherent
during the SDLC.
 Reduce or eliminate the cost of invoking third-party
systems for non-production use.
 Increase agility and improve quality in complex and
changing IT environments.
19 © 2014 CA. ALL RIGHTS RESERVED.

19. Demonstration

20. Devcenter
CA Application Test
21 © 2014 CA. ALL RIGHTS RESERVED.
DevOps
Agile Parallel
Development
Related Technologies
Devcenter
CA Service
Virtualization
Devcenter
DevTest Overview
1:15 Monday

21. 22 © 2014 CA. ALL RIGHTS RESERVED.
Q & A

22. Session Evaluation
Please provide your feedback
about this session
23 © 2014 CA. ALL RIGHTS RESERVED.
Session Name:
Service Virtualization: What is a
Virtual Service and What Is Not
Access inside the CA World Mobile App
Click on SURVEY/SESSION EVALUATION
 If your badge was scanned at the entrance to
this session, click on the name of this session.

23. For Informational Purposes Only
Terms of this Presentation
© 2014 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
This presentation provided at CA World 2014 is intended for information purposes only and does not form any type of warranty.
Some of the specific slides with customer references relate to customer's specific use and experience of CA products and solutions so actual
results may vary.
Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belong
24 © 2014 CA. ALL RIGHTS RESERVED.
to their respective companies. CA confidential and proprietary. No unauthorized copying or distribution permitted.