This document discusses service-oriented architecture (SOA) and web services for integration and multi-channel access. It covers common business drivers for integration like mergers and acquisitions. It also discusses the differences between web service integration (WSI) which is opportunistic and tactical, and service-oriented integration (SOI) which is systematic. SOI involves refining data models, defining formal service contracts, and configuring legacy systems. The document also discusses how SOA allows for multi-channel access through a layered architecture with tiers for clients, channel access, communication infrastructure, and business services. This provides benefits like reducing costs and improving efficiency.

1. UNIT-4
SOA & WEB SERVICES FOR INTEGRATION AND MULTI-CHANNEL ACCESS

2. Common Business Drivers For Integration
• Mergers and acquisitions
• Internal reorganization
• Application/system consolidation
• Inconsistent/duplicated/fragmented data
• New business strategies
• Comply with new government regulations
• Streamlining business processes

3. • Challenges faced during integration
• Requirements that the ‘ideal’ integration solution must satisfy:
• Inexpensive
• Easy to learn
• Non-invasive
• Scalable, reliable, secure
• Flexible and easily customized
• Difference between strategic(systematic) and tactical(opportunistic)
spectrum

4. Integration can be performed at different
layers of the technology stack
• Data integration
• Message integration
• Component integration
• Application integration
• Service integration
• Process integration
• User interface integration
• B2B integration

5. Web service for integration
• Common approaches:
• Legacy data-driven
• API/method-driven
• Contract-driven
• Benefits:
• Interoperate
• Composite applications
• Easier to combine and analyse
• Mechanisms for interaction
• Interact

6. Two approaches for using XML and Web
Services for integration and interoperability
1. Web service integration (WSI)-tactical
2. Service-oriented integration(SOI)-systematic
XML,SOAP,WSDL

7. Web service integration (WSI)
• Opportunistic, tactical integration projects
• Advantage:
• Faster time-to-market
• Lower integration costs
• Limitations:
• Minimal consideration
• Messages sent directly using transport-level or middleware API
• Security
• No consideration for applying web services platform
• No provision for versioning the web services

9. Service-oriented integration(SOI)
• During start-up phase:
• SOA governance framework, processes, guidelines, models, tools are defined
• Formal modelling
• Service taxonomy
• Multiple options
• SOI project involves:
• Refining existing data model
• Defining formal service contracts
• Configuring legacy systems
• Defining data transformations
• Configuring execution environment

11. • Advantages:
• Formal and reusable
• Reduces vendor-lock in
• Enterprise qualities of services
• No need to implement
• Security architecture
• Limitations:
• High start up cost
• Skilled architects
• Business and technical managers

12. .NET and J2EE interoperability

13. • WSDL contract allows disparate systems to interoperate
• WSDL contract describes how to process the SOAP message

14. Service enabling legacy systems
• Mainframe systems (CICS and IMS)
• Distributed object applications (COBRA, DCOM, J2EE)
• Transaction processing systems (Tuxedo and Encina)
• Packaged applications (SAP, PeopleSoft, Oracle applications)
• DBMS (Oracle, Sybase,DB2, SQL server)
• B2B and messaging systems(SWIFT,EDIFACT,X12, HL7, WebSphere
MQ, JMS, MSMQ)

15. Service enabling CICS and IMS transactions

16. Service-enabling COBRA server

17. Enterprise service bus pattern
• It helps in converting:
• Database
• Messages and files
• Data
• Business documents
• Key elements of ESB pattern
• Metadata driven
• Transformation rules
• Declarative versus programmatic
• Static versus dynamic

19. SOA and Multi-channel
access

20. Some examples of service-oriented
businesses
• Service requesters
• Services
• Delivery channels
• End-users devices
In:
• Government
• Telecom, Communication
• Financial services
• Health care

21. Multichannel applications call for a service-
oriented architecture

22. Business benefits of SOA and multi-channel
access
• Multi-channel access reduces staffing costs
• Multi-channel access eliminates obsolete and expensive
infrastructure
• Service-oriented architecture reduces costs and improves efficiency

23. Service-oriented architecture for multi-
channel access
• This makes the organization more agile by allowing it to deliver all
products and services in a consistent manner across all distribution
channels.
• Architectural challenges:
• Connectivity
• Security
• Communication technology
• Architecture for multi-channel access:
• Channel access tier
• Communication infrastructure
• Business services access tier

24. Layered architecture for providing multi-
channel access

25. Client/presentation tier

26. Channel access tier
• Support all common data formats and protocols
• Support all common communication interaction patterns
• Payload mapping
• Protocol bridging
• Security facilities
• Data transformation and validation
• Service lookup and service routing
The channel access tier is composed of two types of components:
• Service process
• Client gateways

28. Communication infrastructure

29. Business service access tier
• Service registration and service lookup
• Session management
• Data transformation and validation
• Security services
• Service enablement
• Service orchestration and composition

30. Business service tier
• Legacy systems
• Greenfield services
• Composite services

31. SOA for developing composite applications
• Client/presentation
• Channel access tier
Security services for role-based access control and single sign-on
• Communication infrastructure
• Business access tier
• Business service tier

32. SOA for multi-channel access architecture
• Technology diversity
• Future agility
• Autonomy