By Jeremy Burdette & Daniel Gottlieb

It is an architecture It is not a technology May not fit all businesses “Service” doesn’t mean Web Service It is a controlled way of working a solution to ensure desired goals are met

XML – Extensible Markup Language Used to create custom markup languages WSDL – Web Services Description Language An XML based language that provides a model for describing Web Services Describes protocol bindings and message formats required to interact with the web service UDDI – Universal Description, Discovery & Integration An XML based registry for businesses worldwide to list themselves and their services on the internet Provides access to WSDL documents SOAP - Simple Object Access Protocol Describes protocols for exchanging XML based messages, like WSDL, over computer networks Forms the foundation layer for web services, providing a basic messaging framework upon which abstraction layers can be built

Web Service – “a software system designed to support interoperable machine-to-machine interaction over a network” by W3C

ESB – Enterprise Service Bus An abstraction layer that allows messaging without writing code Reduces the number of points of point connections to allows applications to communicate BPEL – Business Process Execution Language A language that specifies business process behavior based on Web Services Programming in the Large Dividing programming into modules that will behave in a specific format Code does not need to edited even if situations change

Reuse: “Strategic reuse of assets across multiple department’s applications” Reduced Costs : “Efficiency in terms of time to market and development cost” Agility: “Need to provide more agile support to business processes,” and “to handle change management impacts more efficiently and effectively.” Flexibility: “Efficiency in terms of time to market and development cost” Data Rationalization: “Master Data Management” Integration: “Integrate legacy systems”, and “Bring together diverse lines of business across many geographies with faster speed to market”

Reduces time that new business processes can be brought to market Reduces cost of creating new business processes based on existing services while keeping in accordance with the reference architecture Creates consistency across the enterprise in terms of user interfaces and data

Service 1 Service 4 Service 3 Service 4 Service 2 Accounting Department Marketing Department Business Process 1 Business Process 2

Accounting Department Marketing Department S1S2S3S4 BP1BP2 ESB

Based on reuse and all of the benefits associated with reusing services Combines existing services from a repository reducing the likelihood of needing to develop new services Requires comprehensive catalog of searchable well defined services

Service 2 Service 5 Service 1 Sales Department Service 1 Service 4 Service 3 Service 4 Service 2 Accounting Department Marketing Department Business Process 1 Business Process 2 Business Process 3

Accounting Department Marketing Department S1S2S3S4 Sales Department S5 BP1BP2BP3 ESB

Allows a user with a single set of credentials access across domains Helps simplify the user’s experience by not having to use multiple local domain logins Reduces costs and management complexities by having a seamless interface between different networks

Provides universal connectivity to existing systems and data using an ESB. Provides services that connect to the overall enterprise and avoids point-to-point connections. Use of a semantic model is required.

Design Time Discovery - uses a repository which provides a catalog of available services Search capabilities Service details Usage statistics Run Time Discovery – uses a registry to identify an endpoint after a service has been requested See example repository See example repository

Handheld Device Web Portal Telephone System Clients ESB Java Web Service.NET Web Service BP1BP2BP3 Java Web Service.NET Web Service Enterprise Java Bean Java Web Service Java Web Service