Hello, my name is Joelle Gropper Kaufman. I'm the VicePresident of Marketing for Reactivity. I'm here to talk to you today about howcontrolling XML will lead you to a successful service-oriented architecture.
So why do you have XML all over your network? Well, you haveXML because you've taken your applications-your application developers have-andthey've realized that this part right here in the middle is used over and overagain by multiple applications. Perhaps it's the consumer account identity. Sothey created a service for consumer account identity. And then they realizedthat they could create services for other functionality that was in thatapplication and could be used across the business. So they've eliminated themonolithic application and created services that take advantage of each other.
So this service is getting customer information. Thisservice is getting customer information. And they're all operating using XMLfor the message format and using your network to transmit.
Well, what happens is once you have some services you tendto have entities that want to use it inside, so we call those consumers. Thoseconsumers are talking to your services. Your portal might be talking to yourservices. Your business partners might be talking to your services.
So whether you've intentionally created an architecture forservice orientation, or you've simply taken advantage of what's available indot-net, web logic, SAP, coming in Windows Vista 12 or any of 50, 60 otherapplication platforms and application packages, you've got services. You've gotXML . And you've got a network that's noticing there's a lot of traffic rightalong these lines, and it's big. It's consuming bandwidth. This service isbeing used and it's not getting the performance and we need more servers. Thecause is the invasion of XML messages.
So what you need is to go from being an invaded network tobeing an enabled network, so you can deal with speed, interoperability, accessrights so we'll call this access control hotspot, and since you're working withyour business partners and your customers in real time, you have to deal withperimeter security. Is the content of the XML payload private? Is it secure?
So you have these hotspots, and they're caused because XML'slarge, it requires a lot of processing, and it's text, so it's inherentlyinsecure.
So where are you going to deal with getting control of yournetwork? Getting control of this XML invasion? Well you can do it in each oneof these services themselves, but again, you've got many, many platforms, manydistributed servers all over your network. That's a very expensive place to tryto get control.
If you take control in your network by the introduction ofspecialized XML network devices that understand that XML payload completelymissed by your network infrastructure, and can deal with making it faster,making sure everything interoperates, enforcing access policies, and ensuringthe payload is safe, private and protected. Well, when you have that, you can getcontrol of your XML. With control, you can build many, many more services andconnect with many more of your business partners. And that delivers a bigimpact to the business and makes for a successful SOA.
