Managing Enterprise Services

Brian Bubonic, Enterprise Architect

brian.bubonic@huntington.com

Emil Thomas, Solution Architectethomas@prolifics.com

Huntington Bancshares Overview

2

Midwestern US financial services holding companyMidwestern US financial services holding company

• Founded: 1866• Headquarters: Columbus, OH• Total assets: $54 Billion• Employees: 11,245

Prolifics at a glance

3

Abstract

4

Huntington National Bank is a Midwestern bank headquartered in Columbus, Ohio. Over the past year, Huntington has been trying to enforce service governance by using IBM SOA products and by adopting stricter policies and standards around design, development and usage of the services. With an estimated 500 plus enterprise services to be in Production by the end of 2013 and with challenging requirements to evolve services continually for the various consuming applications, this is no small feat. In this presentation, we will showcase the challenges faced in the journey, the approaches taken and the benefits achieved with enterprise service versioning and enforcing service governance to achieve enterprise service agility.

Goals

5

Better Business Experience

Enhance Business Agility

Reduce IT Overhead

Current State Overview

6

Benefits

7

Consistent Business and Customer Experience

Service Re-use across Service Consumers

Common Business logic and Rules

Self Describing Message

Challenges

8

Governance (Design or Run Time)

Unit of Work Control

Message Versioning

Single Service Timeout across all Consumers

Single Message Protocol

Multiple Middleware Applications

Current State Metrics – Service Usage

9

Current State Metrics – Service Reusability

10

Current State Metrics - Channels

11

Future State Metrics

12

Reference Architecture

13

Existing AppsProd/Dev PhasePlanning Phase

DataPower

WS

RR

We

bS

ph

ere

Re

gis

try

& R

ep

osi

tory

CICS

CICS Transaction Gateway

WebSphereProcessServer(WPS)

WebSphereEnterprise

ServiceBus

(WESB)

WebSphereOperational

DecisionManagement

(WODM)

FileNetLegacyService

WASService

.NetService

ITC

AM

Salesforce IVR WAS .NET DataStage

Enterprise Services

Technology Landscape

14

Channels

ESS

Service Gateway

Service Providers

PRPC ACAPS MAXOnline

Banking

DataPowerWSRR

WESB WPS

SecureMailWAS/ JavaServices

CTG MQ

Mainframe PEGA Adobe PRPC Services RightFaxFileNet

Data

Implements orchestration services and long running process

WSWSMQMQWS

MQ

REST

MQMQMQ

MQWS API API

ISRA API JDBC IP

Implements simple and composite Mediation services

WS

WODM

Implements decision based services

Mo

nito

ring

BM

I /

ITC

AM

s

Service Provider Proxies

Enterprise Service Gateway

15

Central governance for all services

Channel authentication

Service-level authorization

Message throttling and traffic shaping

Dynamic endpoint lookup

Up-front message validation

Enterprise Services

16

Bottom-up approach considering the legacy services already in place

Comprise of mediations, short running processes, long running

processes and decision services

Design standards and policies enable consistency and reuse

Design patterns ensures lesser development time and higher quality

output

Better management of enterprise services using service versioning

Service Provider Proxies

17

Better separation of concerns

ESB will not be blamed for all problems

Efficient utilization of resources

Consistent approach to access service providers

Monitoring

18

Real-time problem identification

Highly configurable events for alerts

Enables automation of certain run-time governance characteristics

through integration with other products

Metrics assist IT team to better plan for resources

Service Versioning

19

Technique used to minimize the disruption to channels due to service

changes

Enables consumers and providers adapt to changes more easily

Ability to add or sunset service versions independently

Implemented using namespace versioning in WSDLs

Major and minor versions to differentiate compatible and non-

compatible changes

Service Versioning

20

Authentication and Authorization

21

Supports multiple authentication mechanisms

Fine grained access control to services at channel / service version

level

Authorizations to be managed using SLAs in WSRR

Enables identification of rogue channels

Authentication and Authorization

22

Service Level Monitoring

23

Message throughputs controlled at Service / Channel level

Option to throttle or shape requests when thresholds exceeded

Protects downstream systems from unexpected spikes

Automated control of message throughputs through integration with

WSRR and ITCAM

Service Level Monitoring

24

Design Time Governance

25

Very thorough review process to ensure maximum reuse and service

management

Representation across business and IT, architects and developers in the

SOA Review Board

Schemas / WSDLs carefully managed to ensure compliance with

standards and guidelines

Sharepoint and SVN used for managing artifacts

Governance processes evolving continuously

Design time governance feeds directly to QA test cases

Design Time Governance

26

Challenges Faced

27

Funding – Our SOA roadmap is funded by each project which requires

services

Adoption – Deployment of the new technologies in the production

environment

Culture – Staff acceptance of the new technologies and design

patterns

Roadmap – Change in upper management and organizational

structure has led to delays

28

ThankYou