Transcript Service

The User Organized
Enterprise
Ron Nunan
Director of Connector Services
Attachmate Corporation
AGENDA
The Services Oriented Host
• Brief on SOA
• SOA beyond the ‘Service’
• Requirements for existing systems
• Service Oriented Host
• Use Case Scenarios
WHY ARE WE TALKING ABOUT SOA?
“
A services-oriented architecture
(SOA) approach to IT can bring
agility and long-term savings to
businesses.
”
—PC Magazine, September 2004
SOA Is Part Of The Computing Cycle
What Is A Service-Oriented Architecture?
If a service is like a
musical instrument...
...Then SOA is like an
orchestra
Service Oriented Architecture
Let Services be
Services
and that’s all…
Do Not Call
List
1
SERVICE
…SOA takes
2
care of all the things a
services needs in order
to be successful in the
enterprise…
Coordination
Throughput
Performance
Monitoring
Registry
Security
Messaging
Operations
Workflow
Identity
ENABLEMENT
...and provides
for the delivery
of services to
consumers.
3
DELIVERY
SOA: Layers of Value
Services
Enablement
Delivery
Reusable Business Process
Foundation for the agility of 21st century demands
Enterprise Agility
Composition of services and business processes
User Empowerment
Composition of independent user views
Value of Services
Services
Enablement
Reusable Business Process
Foundation for the 21st Century Demands
Stand-alone Business Processes or Services
Basic-business process context defined
New services
Business-use context unknown
User-types context unknown
Legacy “host” services often combined with user type context
Delivery
Value of Enablement
Services
Enablement
Enterprise Agility
Composition of Services and Processes
Services Coordination, Services Enablement
Business-use context defined
Creates composite services
Builds wrapped services
Composes enterprise business processes
User types context unknown
Delivery
Value of Delivery
Services
Enablement
User Empowerment
Composition of Independent User Experience
Who?
Employees, customers, partners/vendors
What?
Transactions, intelligence, collaboration,
document and content management
Purpose? General, vertical, horizontal
How?
mail
Thick client, browser, wireless, PDA, e-
Delivery
What is this leading to?
User Empowerment
SOA Workgroup Experiences
Host Application Integration (SOA)
Host Presentation Integration (SOA)
Web-to-Host
Emulation
User Productivity
Standard Access
PRESENTATION
Application Logic
Application is or
appears monolithic
DATA
“Transactional” Access
PRESENTATION
OBJ
Application Logic
OBJ
DATA
OBJ
Use of “Transactional” Access
Application
Web Services
Services
PRESENTATION
OBJ
Application Logic
OBJ
DATA
OBJ
Service-Oriented Host
Services
Applications
Call Center
Presentation
Host
Online Banking
Logic
Application
Development
Self-Service
Data
e-Commerce
The Service Oriented Host
» This is about taking advantage of the promise of SOA
• It is not completely about the use of Web Services
• Web services is an implementation
• It is about correct use of existing applications within a
services approach
» Use a Services approach; transactionalize, add extensions,
create services, allow tactical use of Host Applications
within the push to SOA
Use Case Scenario
Kansas JobLink
A Services Oriented Host
The Issue
Discerned a problem on the horizon
» Economic climate change
• Cyclical demand requirements
• Currently approaching peak service requirement
• Unemployment rising
• Projected growth of claims processing in the double digits for
the next several years
» Inability to service the demand with current systems
• Anticipated increase in claims to 250,000 per year
• Call centers running at capacity of 110,000 claims per year
Current System
IVR
Terminal Emulation
CICS application
Call Center
Client Applications
Mainframe
Current Infrastructure
» IS Staff
• Internal IS staff developed legacy systems
• Consultants developed VB app with Internal IS
staff maintaining systems
» Call Center Staff
• Strong background using original "paper"
system and CICS transactions
• Trained in MS Office
• Trained to use GUI-based system
Business Objectives
» Modify customer service delivery model (add channels)
• Expand from phone to Web based self service
• Redesign IVR script to provide self service
» Extend hours of operation
» Reduce the time an agent needs to spend with customer
» Provide an agile platform to accelerate development times
• Improve existing software performance throughput
• Reuse code
• Reduce delivery risk
Looked At Two Options
» A grant team reviewed the requirements
» Two solutions were proposed to address the
requirements out of the review
• Mainframe service technology
• Reengineer the legacy system to a client server
environment
Mainframe Service Technology
Reengineer the legacy system
to a client server environment
Requirements Re-evaluated
» Combined critical path requirements
• Business requirements
• Staff skill-set capabilities
» Re-use capabilities
• Retention of existing systems
Solution evolved out of ability of new open and
market standards to access the critical legacy
systems
A Services Approach
» Issue was how to work in KDHR preferred
environments without throwing out Legacy
Systems
» Apply a Services Oriented
Architecture to the legacy systems
Services Architecture
Pick
appropriate
Supply a
services
interface
to themethod
CICS
Generate
Host
Interactions
Publish
asaccess
Service
applications
XML
Web services
Tasks
Screen Access
Direct CICS (DPL)
Direct Bridge Exits
CICS
.NET
Service
Provider
Java
COM
Mainframe
Preferred
Connectivity
APPLICATIONS
JobLink Phase 1
Web site
BizTalk
Web Service
Tasks
Tasks
MSMQ
XML-based
messaging
IVR
Web Service
Tasks
Tasks
Attachmate
Smart Connector
SNA, IP to mainframe
CICS application
Mainframe
JobLink Phase 2
Web site
BizTalk
Web Service
Tasks
Tasks
XML-based
messaging
IVR
Web Service
Tasks
Tasks
Attachmate
Smart Connector
Siebel app
Web Service
XML/ http
Tasks
Rules
CICS application
Higher Requirements
Native
schema
Mainframe
JobLink Phase 3
Web site
BizTalk
Web Service
Tasks
Tasks
XML-based
messaging
IVR
Web Service
Attachmate
Smart Connector
Tasks
Tasks
Siebel app
Web Service
XML/ http
CICS application
Tasks
Rules
Native
schema
Web Service
Mainframe
Tasks
Tasks
Web Service
Tasks
Rules
Benefits Applied
» ROI in less than a year
» The standard benefits used to bolster a services
oriented architecture were realized
• Simplified integration
• Agility
» Open standards made it a safe decision
• Use of accepted standards facilitates use with
future systems and technologies
• These solutions will be accounted for…
Thank You