SOA and Network ManagementDavid ChengApplied Expert Systems, Inc.

Monday August 11th @ 4.30pmSession # 3716

2

John Chambers, Cisco Systems

“I believe we are moving from a device, or desktop, mode to a web-top mode. That means you won’t identify with your laptop or your TV, or your iPod, or XBOX game or whatever. You will think of it as any device connected to any content in whatever format you are comfortable. If that is true, all of the sudden the network plays a hugely different role…”*

*San Jose Mercury News, Business section, January 20, 2008

3

Topics

• What is SOA?

• Why SOA?

• WEB Services

• Pros and Cons of web services

• Networking is the Key

• Sample service based networks

• Designing the network

• Into the future?

• Conclusion

4

What is SOA?

• A collection of services. • The services communicate with each other. • The communication can involve either simple data passing

or it could involve two or more services coordinating an activity. • A means of connecting services to each other is needed.

• We are on the cusp of building "plug-compatible" software components

• That will reduce the cost(s) of our software systems• Increase the capabilities of IT systems

5

What is SOA?

• A service is a function that is well-defined, self-contained, and does not depend on the context or state of other services

http://www.service-architecture.com/

Service Request

Service Response

ServiceConsumer

ServiceProvider

6

Why SOA?

• Reusable & Sharable Components

• Duplicated Development World-wide

• Externalized Object-Oriented-Programming

• Standardized Interfaces

• Standardized Protocol

• Formalized Services Search Path

• Thin Applications – Easy to Install

• Responsive Applications – Automatic Upgrade

• Better Quality Applications

7

Web Services

• Web Services refers to the technologies that allow for making connections

• Web Services Description Language (WSDL) is used to describe the service

• SOAP is the protocol that provides means of sending messages

• Universal Description, Discovery and Integration (UDDI) as the directory

http://www.service-architecture.com/

8

Web Services

Directory

Service Provider

Service Requestor

Directory Query

Response via WSDLService

Des

cripti

on vi

a WSDL

XML Service Request via WSDL

XML Service Response via WSDL

SOAP

9

Pros & Cons of Web Services

• Pros• Standardized Web-ready Specifications

• Completely partitioned • Object based • Deployed to or ready to be deployed

to an application server • Internet as the backbone

• Popular and Ready• Clear Specifications

• WSDL• SOAP• UDDI

• World-wide Standards• OASIS Standards• W3C Standards

• Available Tools• Do a Web Search

• Cons• Security

• Authorization• XML content• Server• Etc.

• Performance• Network• Application• Application server• Bandwidth

• Internet/Intranet dependency

10

The Network is The Key

• Applications are no longer dependant upon the standalone backbone network

• LAN and Internet routes are playing the major roles in application availability and performance

• Future applications will rely heavily on expertise in network and performance management tuning

• Your business network tomorrow is no longer just your local area network

• Tools, Tools, Tools, …

11

A Simple Service-based Network

Data Base Services

UDDI

Web Services

SOA Services

Application

Firewall

SOA Services

DB

12

A More Complex Service-based Network

Accessed byAnother

Application

DB

Data Base Services

UDDI

Web Services

Order Service

Application

TraditionalFirewall

InventoryService

Router

ShippingService

Message Router

Alert Service

CustomerAcct Service

Credit CardService

Gift WrapService

XMLFirewall

Message Router

13

Designing the Network

• Just a (very) few things to consider:• Bandwidth

• Which are the high-use services?• Which are low use services?• How many users/applications can it support?

• Routes• Which are the critical routes?• Multiple routes to the same end-point?• How many hops are tolerable?

14

Designing the Network

• Just a (very) few things to consider:• Critical Services

• Which services are mission critical?• Which services can tolerate down-time?

• Scalability• How easily is the network expanded• Support growth without being re-designed• Can it handle double the

• Users• Bandwidth• Applications

15

Designing the Network

• Just a (very) few things to consider (continued):• Performance

• Service Level Agreements• How is it measured?• At what point is it measured?• How do you know it is failing?

• Resilience• Failure of any one link or device should not impact a client/server session• Automatic failover• Low convergence times – time to do a network change

16

Designing the Network

• Just a (very) few things to consider (continued):• Security and authorization

• Firewalls • How many? • Where?• Traditional?• XML Firewall?

• ipSec• Internet Exposure• Authorization technique

17

Designing the Network

• Just a (very) few things to consider (continued):• Outages

• Zero?• How will they be handled?• Who will handle them?• How do you know they occurred?

• What tools do you need?• Tracing• Analysis & diagnosis• Response time• Availability

18

Into the future

• SOA GRID Networks• Pay as you use applications• Location diverse• Network performance becomes a key issue• Is it the network or the application or the application provider?

• Turn Key Applications• Off the shelf applications• Plug and play• Buy from your favorite vendor

Asian Hotels

AsianRestaurants

Asian Entertainment

19

Into the future

UDDI

WWW.Travel.AESClever.com

US Hotels

US Autos

US Airlines

European Hotels

European Autos

European Airlines

20

Conclusion

• All businesses must be ready for the coming software revolution

• Network Security is still a major design consideration

• Network Availability is now your business availability

• Network Performance drives your profit directly

• The Local Area Network is only a small part of what you have to worry about

21

Thank you!davec@aesclever.com

www.aesclever.com650-617-2400

Our other presentations:

Tuesday, 8:00 am - 9:00 am: CLEVER Solutions for z/OS and zLinux and Network Service Level MonitoringTuesday, 4:30 pm – 5:30 pm: Establishing Service Levels for Critical IP and Business ServicesThursday, 3:00 pm – 4:00 pm: Diagnosing Mainframe Network Problems With Packet Trace