SOA and Network Management

Transcription

1 SOA and Network Management David Cheng Applied Expert Systems, Inc. Monday August pm Session # 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,

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 3

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 4

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 Service Provider Service Request Service Consumer Service Response 5

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 6

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 7

8 Web Services Service Provider Directory Service Requestor 8 Directory Query Response via WSDL SOAP Service Description via WSDL XML Service Request via WSDL XML Service Response via WSDL

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 9

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, 10

11 A Simple Service-based Network Web Services Firewall UDDI Application SOA Services SOA Services DB Data Base Services 11

12 A More Complex Service-based Network Web Services Gift Wrap Service Application Traditional Firewall UDDI XML Firewall Credit Card Service Alert Service Inventory Service Accessed by Another Application Customer Acct Service Order Service Router DB Message Router Shipping Service Data Base Services Message Router 12

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? 13

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 14

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 15

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 16

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 17

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 18

19 Into the future UDDI European Hotels European Autos US Hotels US Autos US Airlines Asian Hotels European Airlines Asian Restaurants Asian Entertainment 19

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 20

21 Thank you! Our other presentations: Tuesday, 8:00 am - 9:00 am: CLEVER Solutions for z/os and zlinux and Network Service Level Monitoring Tuesday, 4:30 pm 5:30 pm: Establishing Service Levels for Critical IP and Business Services Thursday, 3:00 pm 4:00 pm: Diagnosing Mainframe Network Problems With Packet Trace 21