FTA Technology 2011 Enterprise Service Bus Enterprise Service Bus Final... FTA Technology 2011 Enterprise

Embed Size (px)

Text of FTA Technology 2011 Enterprise Service Bus Enterprise Service Bus Final... FTA Technology 2011...

  • Manufacturing

    _experience the commitment

    Government and Healthcare Financial Services Telecommunications Manufacturing


    FTA Technology 2011 Enterprise Service Bus

    August 16, 2011

    Confidential – CGI Proprietary – August 2010

  • Agenda

    Modern Architecture for Tax Administration  Logical Architecture  Agency Blue Print  Service Oriented Architecture What is a Service Bus & What does it do Components and Features Service Bus Integration Framework Value Proposition (Features and Benefits) The Future of ESB Offerings Questions



  • Building Agility – Logical Architecture

    Service Development Life Cycle Tools and Methodologies

    E nt

    er pr

    is e

    S ec

    ur ity

    Service Consumers

    Service Interfaces

    Service Delivery Infrastructure

    Business Processes

    Core Business Applications

    E nt

    er pr

    is e

    M an

    ag em

    en t

    Data Data Data Data

    Portals and Web UI

    Program Logic


    User Interface Business Rules

  • Revenue Agency Blueprint



  • Service-Oriented Architecture

     Service Orientation  Use of “open” interoperability protocols to facilitate

    service interaction

     Architecture  A process of putting together components to

    achieve some overall goal  A blueprint that comprises the components

    organized by layers, visible properties, relationships and interactions, and constraints

     Definition of Key Terms  A repeatable business task  A way to integrate your business as linked services  An IT Architectural Style  A set of related and integrated services



  • What is a Service Bus

     A flexible connectivity infrastructure for integrating applications and services

     The ESB Empowers your SOA by reducing the number, size, and complexity of managing your interfaces

     SOA without ESB Decouples Interfaces from Applications

     SOA with ESB Decouples Interfaces from point to point connectivity

     Can be thought of as an abstraction layer on top of the Enterprise Messaging System



  • What Does an ESB Do?

    ESB is used as a multi-functional backbone Enables standards-based electronic data integration Provides the ability to connect resources Expose and mediate the communication among services Orchestrate processes Manages security and the quality of service Enables legacy systems to extend their functionality Sets the stage for future data exchange



  • Key ESB Components – Support Current and Future Needs Key Component Feature

    EDI Communication Support popular EDI communication standards such as VAN communication, HTTP, FTP, WebSphere MQ

    EDI Message Standards Support Industry standard message formats such as ANSI ASC X12, HIPAA, VICS, VDA, UCS, etc

    Access Manager Common Application Security components and network security components such as IPS apply consistent security policies for authenticating and authorizing EDI services

    Interceptor Integration Framework comes with extendable interceptors deployed in the ESB that process inbound and outbound EDI messages to provide audit, security functions


    Capability to create flows that are capable of acting as a proxy or intermediary with the EDI provider to negotiate communication and transact messages, followed up further routing transformation before delivering it to other solutions or a partner system

    Mediation Leverages the ESB to support protocol, message structure and even security token mediation

    Transformation Leverages the ESB transformation capabilities for transforming legacy and modern data structures

    Confidential 8

  • Key ESB Components – Support Current and Future Needs Key Component Feature

    Route/Distribute The CGI Integration Framework leverages the ESB messaging functions to provide point-to-point EDI delivery or publish the message to a set of EDI providers

    Messaging Integration Framework is capable of interacting with popular messaging providers such as MQ, JMS and MSMQ.

    Partner Profiles Partner data management, authentication and authorization features allow us to provide services tailored to the SLA established with the partner

    Transaction Management

    Integration Framework supports industry standard WS based transaction and is capable of backing out transaction using compensatory means as well. This allows us to transact with modern and legacy applications

    Adapters Integration Framework leverages ESB features such as adapters and connectors to popular EDI software and partner ERP systems

    Registry Repository of service definitions and service metadata. Used by EDI services to interact with partner systems



  • Service Bus Integration Framework

     Eclipse plug-in, is used by the developer to create, maintain and deploy the Integration components

     Development team to focus on solving the business problem

     Allows the developer to implement only the business logic

     Service end points are native to leading middleware containers such as ESB’s and Application servers

     Multi-functional backbone in service oriented architecture (SOA) to enable standards-based electronic data integration

     Ability to connect resources, expose and mediate the communication among services, orchestrate processes, manage security and the quality of service



  • Value Proposition (Features and Benefits) When does it make sense$

     When Organizations adopt a more holistic approach to SOA infrastructure

     Evaluate the cost and risks of complex infrastructure like a full fledged SOA Backplane

     Effort Pays off when investment is spread across multiple or large phased projects like ITS implementations

     Deploy SOA Backplane and Governance structures by “think global” act “local” approach

     Deploy an initial basic foundation comprising the ESB Core and some adapters



  • ESB Features and Benefits

    ESB Features – Today and Future Benefits to State

    Specification based support for reliable and guaranteed delivery

    Reliable Message exchanges between applications and partner system using specifications such as WS-Reliability The Messaging subsystem supports guaranteed delivery of messages with retry functionality

    Central Security, Audit & Monitoring

    Support for WS*-based security shared by the application layer

    Configuration-based audit support for Integration layer to capture content at access , mediation, and transformation layers. Information shared with common audit sub system to provide an enterprise wide view

    Integration layer monitoring tied to the central monitoring stack to provide a enterprise wide view of the application health

    Supports an “integration highway” between systems/platforms such as legacy, mainframe, standard COTS external partners

    Supports efficient integration during iterative implementation initiatives and beyond

    Lowers operational costs. Reduces risk

    Enforces a “quality of service” and consistency as data moves internally within COTS and externally throughout the enterprise

    Enables metrics-based approach for monitoring and continuous improvement

    Decreases cost

    Increases performance

    Supports COTS enterprise IT Governance and essential controls

    Supports strategic data integration patterns identified by the State Wide Data Strategy

    Confidential 12

  • ESB Features and Benefits

    ESB Features – Today and Future Benefits to State

    Supports EAI with EDI, and other industry standard-based communication protocols through the ESB included in the SOA platform

    Lowers cost Decreases risk Proven platform

    Allows creation and deployment of EDI quickly and easily between applications and services

    Supports common EDI formats out of the box Enables continued, uninterrupted EDI-based business interactions Leverages existing State assets

    Enables efficient legacy integration during phased implementation and reduced number and complexity of interfaces over time

    Supports iterative implementation Lowers operational cost

    Provides a common, application independent backbone for internal and external service integration and interaction

    Leverages existing services, development and configuration knowledge Increased scalability and interoperability

    Supports various Industry standard protocols new and legacy with option to add new protocol adapters as the specifications are standardized

    Supports integration of new and legacy applications Supports phased modernization Mediation between applications that do not share the exchange protocol Support for future protocols and data formats

    Scalable and Highly Available ESB Native support for clustered deployment Highly available integration services Scalability through easy addition of resources