• Save
SOA Service Reusability for iWay SM
Upcoming SlideShare
Loading in...5
×
 

SOA Service Reusability for iWay SM

on

  • 1,810 views

Hariharan\'s presentation in the IBI Summit 2010 conference

Hariharan\'s presentation in the IBI Summit 2010 conference

Statistics

Views

Total Views
1,810
Views on SlideShare
1,787
Embed Views
23

Actions

Likes
0
Downloads
0
Comments
0

3 Embeds 23

http://www.linkedin.com 13
http://www.openeaga.org 8
https://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

SOA Service Reusability for iWay SM SOA Service Reusability for iWay SM Presentation Transcript

  • Service Reusability and Best Design Practice for iWay Service Manager Hariharan V G – MGL Americas Inc
  • Agenda • Principles of Service Oriented Design • SOA and iWay Service Manager ESB • Common scenarios among iWay User Community • Design reusable process flows, channels and transformers • Expose reusable services using channels • Build reusable services & Save effort/cost • Pros & Cons • Best Practices before kick start • About MGL Agenda
  • Principles of Service Orientation • Service Contract Standards Service Contracts Increased • Service loose Coupling Interoperability Loose • Service Abstraction Coupling • Service Reusability Service Faster IT and Abstraction Business Alignment • Service Autonomy Service • Service Statelessness Reusability Increased ROI • Service Discoverability Service Results Autonomy Reduced IT Service Stateless Burdens Service Discover Increased Business Delivery Agenda
  • Service Oriented Architecture (SOA) • SOA– An architectural style of building enterprise solutions. • Value of SOA comes when reusable Presentation Services services utilized effectively. • Open standards ensure vendor- Business Process Services (BPEL) neutral implementation • Model and build business processes by orchestrating services using BPEL. Business Services (WSDL) • BPM for both management discipline and technology. • ESB, BPEL tools helps to build Integration Services (ESB) service and processes much faster then traditional coding. Agenda Slide 4
  • SOA Reference Architecture • Middleware view of SOA Reference Architecture - TOGAF Agenda
  • Role of ESB in SOA • Enterprise Service Bus (ESB) – building integration, event-driven and standard messaging services. • ESB plays as communication backbone in Enterprise SOA infrastructure. • The ESB architecture includes application adapters and message transformation and routing. • ESB helps to build communication services using File, FTP, MQ and email adapters for enterprise services environment. • ESB helps to build integration services for existing legacy and packaged application using application adapters. • ESB provides messaging which helps to transform any form of input message to industry standard format such as EDI, HIPPA etc. • Event based invocation and integration services helps to achieve quicker business requirements. Agenda
  • iWay Service Manager as ESB • iWay Service Manager is an ESB. • It provides support to implement SOA and EDA. • iWay SM as an ESB, It supports messaging, web services, routing and data transformation. • It also helps to implement quicker integration needs without writing integration code. • It provides adapters to build integration services for existing IT assets. • iWay SM supports event driven messaging / integration through listeners such as JDBC, File, FTP, MQ, HTTP, Email. Agenda
  • Event Driven Architecture using iWay Service Manager • EDA is an architecture pattern promoting detection, consumption and reaction to the events. • iWay SM provides listeners for detecting the events occurs in enterprise IT environments. • Some of the event listeners commonly used: • File • FTP • Email • JDBC • HTTP • Event consumption and reaction can be implemented through process flows and transformers. • iWay SM also helps to build automated business process for an events. • iWay SM supports to build event services for event driven infrastructure. Agenda
  • Common Scenarios in iWay SM Community • Building integration applications for a explicit project / business need. A iWay B Application • Mostly point-to-point integration between systems using iWay listeners/emitters. iWay A • Independent database for each integration Application 1 B applications. C iWay Application 2 • Every process flows connects to enterprise database independently. • Every process flows has its own exception flow A iWay B Application and notification. • Project specific iWay configuration and Config A deployment. A iWay Application • Inadequate / non-configurable connectivity Config B B retry mechanism. C iWay Application Agenda
  • Reusable Services using Channels Sales Force FTP Folder B Partner FTP Folder A Write File Download File Download File Write File HTTP URL HTTP XML Listener • Reusable FTP service that can download files from different FTP server and write into a specific folder based on HTTP request parameters Agenda
  • Reusable Process Flows eCommerce Order Order Payment Shipment Confirmation Process Flow Process Flow Process Flow Reusable Logging Process Flow DB Agenda
  • Reusable Data Transformation Services HTTP Partner Order Process Flow DB HTTP eCommerce Order Process Flow HTTP URL HTT P Agenda
  • Reusable Exception Process for iWay SM Integration eCommerce Order Order Payment Shipment Confirmation Process Flow Process Flow Process Flow HTTP HTTP HTTP Reusable Exception Handler Flow HTTP URL HTTP • Build your exception handling mechanism as service which can be consumed by current and future applications. Agenda Slide 13
  • Common Reusable Services for Integration Environment • Event Scheduler Services • FTP File Download / Upload Service • Email Notification Services • Data Access Services • Data Encryption / Decryption Service • Data Hub Services • Integration Exception Management Service • Data Transformation Service • Audit Trail Service • Partner Data Exchange Service • Data Reference Service Agenda Slide 14
  • Build Enterprise Services using iWay SM Place Order Order-to-Shipment Listener Listener Place Delivery Trigger Package Shipment Transfer Order & Notice Service Service Delivery Receive Order Listener Listener Import Order Partner Check Credit Validate Service FTP Finance Order Failure Email Limit Service Credit System Place Order Listener Check Inventory Validate Send Listener Inventory Level Service Email Send Email Inventory System Service • All the services can be reused by other business functions like warehouse transfer, finance status reporting, production check, corporate communications. Agenda
  • Save effort / Cost by building reusable Services 0% Efforts / Cost Investment 100 % 130 % Development Efforts / Cost Maintenance Efforts / Cost Enhancement Efforts / Cost Traditional Integration Coding Development Efforts / Cost Maintenance Efforts / Cost Enhancement Efforts / Cost ESB based Integration Construction Development Efforts / Cost Maintenance Efforts / Cost Enhancement Efforts Reusable ESB based Integration Construction Agenda
  • Pros & Cons of building reusable services Pros: • One time investment and can be reused by many times by other applications. • Easy to extend the existing integration interfaces which has been build as reusable services. • Easy to accommodate integration process change according to business requirement. • Quicker time-to market which will boost the IT support to achieve business goals. • Easy to track and monitor the performance of process and services, leads to potential process improvement opportunities. Cons: • Need higher investment in terms of effort and cost for the first time. • Need enterprise level governance to ensure maximum utilization of reusable services. Agenda
  • Best Practice prior to kick start iWay SM Project • IT should have strategic vision and leadership • IT should have properly defined strategy and roadmap prior to kick start SOA based integration initiatives. • Define your IT data sharing and communication policies and security needs. • Proper IT governance and system acquisition model eliminates unexpected cost. • Business and Integration operations model should be defined properly and implemented. Agenda
  • MGL SOA Service Offerings Agenda
  • For further clarification and service offerings soa@mgl.com