INTRODUCTION
• DUE TO THE ONGOING GLOBALIZATION, ENTERPRISES ALL OVER THE WORLD HAVE TO FACE A
FIERCE COMPETITION.
• AND TO STAY IN BUSINESS, THEY HAVE TO DEVELOP THEIR BUSINESS PROCESSES,
INTEGRATE WITH THEIR BUSINESS PARTNERS, AND PROVIDE NEW SERVICES TO CUSTOMERS.
• THE IT GOAL HAS ALSO CHANGED DUE TO THE CHANGING DEMANDS IN BUSINESS. AS TODAY
IT HAS TO ACTIVELY SUPPORT ENTERPRISES IN THAT GLOBAL COMPETITION.
RESPONSIBILITIES
ENTERPRISES IT
• ENTERPRISES HAVE TO TRY TO
ACHIEVE THE GOAL BY DEVELOPING A
SERVICE-ORIENTED ARCHITECTURE
(SOA). WHY?
• IN SOA THE BUSINESS FUNCTIONALITY:
1. IMPLEMENTED BY DIFFERENT
APPLICATIONS
2. IS PROVIDED VIA COARSE-GRAINED,
LOOSELY-COUPLED BUSINESS
SERVICES WHICH ALLOW TO EASILY
CREATE, AUTOMATE BUSINESS
PROCESSES BY USING REUSING
COMPOSING THE PROVIDED SERVICE
FUNCTIONALITY.
IT HAS TO MAKE BUSINESS INFORMATION
AVAILABLE ACROSS THE ENTERPRISE TO
ALLOW:
1. SOFTWARE ENGINEERS TO CREATE,
AUTOMATE AND INTEGRATE BUSINESS
PROCESSES.
2. COMPANY WORKERS TO ACCESS ALL
KINDS OF INFORMATION IN A UNIFIED WAY
VIA A DEPARTMENT/ENTERPRISE-WIDE
PORTAL.
• SO TO SURVIVE IN THAT FIERCE COMPETITION ENTERPRISES SHOULD ACHIEVE
INTEGRATION IN ALL THE DOMAINS BY USING THE BEST APPROACHES OF EAI
ENTERPRISE APPLICATION INTEGRATION (EAI)
BEST EAI APPROACHES
• VARIOUS RESEARCH/CONSULTING COMPANIES SUCH AS FORRESTER RESEARCH, IDC,
AND GARTNER INC BELIEVE THAT ESB IS THE MOST PROMISING APPROACH FOR EAI OF
THE LAST YEARS.
• GARTNER INC. ANALYST ROY SCHULTE WROTE IN 2002: ”A NEW FORM OF ENTERPRISE
SERVICE BUS (ESB) INFRASTRUCTURE COMBINING (MESSAGE-ORIENTED MIDDLEWARE(MOM),
WEB SERVICES, TRANSFORMATION, AND ROUTING INTELLIGENCE) WILL BE RUNNING IN THE
MAJORITY OF ENTERPRISES BY 2005. ... THIS HIGH-FUNCTION, LOW-COST ESBS ARE WELL
SUITED TO BE THE BACKBONE FOR SERVICE-ORIENTED ARCHITECTURES AND THE ENTERPRISE
NERVOUS SYSTEM”.
ESB AN INNOVATIVE APPROACH TO EAI
• THE TERM ESB IS OBVIOUSLY OFTEN USED TO HAVE DIFFERENT DEFINITIONS, FOR
EXAMPLE, AN ARCHITECTURE, A PRODUCT, OR A WAY OF DOING THINGS. WE’LL DEFINE
IT LATER.
• HOWEVER, AS A MATTER OF FACT, MOST ENTERPRISES TODAY TRY TO DEVELOP AN
SOA BY USING AN ESB.
• TO KNOW ESB AND EAI AND THE GOAL THAT WE NEED TO ACHIEVE WE SHOULD
ANSWER THE FOLLOWING QUESTIONS FIRST:
1. WHY DO WE NEED INTEGRATION?
2. WHY DO WE NEED THE ESB?
3. WHAT DOES THE ESB PROMISE?
1. WHY DO WE NEED INTEGRATION?
• TO BE ABLE TO FACE THE FIERCE COMPETITION THAT THE ONGOING GLOBALIZATION
CAUSED.
• TO STAY IN BUSINESS COMPANIES HAVE TO REDUCE THEIR COSTS AND GAIN NEW
MARKET SHARES THROUGH THE PROCESS AND PRODUCT INNOVATIONS.
• AS A CONSEQUENCE THE HEADS OF DIFFERENT DEPARTMENTS HAVE TO START
COLLABORATING TO KEEP THEIR DEPARTMENTS A LIVE, IN BUSINESS AND NOT TO
OFFEND THE ENTERPRISE'S MANAGEMENT.
EAI COMMON APPROACHES
• THERE WERE TWO COMMON APPROACHES FOR EAI IN THE PAST:
1. A POINT-TO-POINT INTEGRATION: AIMS TO DIRECTLY CONNECT TWO
APPLICATIONS.
2. A CENTRALIZED EAI BROKER: AIMS TO CONNECT TWO OR MORE APPLICATIONS
VIA A CENTRALIZED MEDIATOR WHICH IS CABABLE OF
ROUTING/TRANSFORMING MESSAGES SENT BETWEEN THE APPLICATIONS.
• TODAY’S BEST EAI APPROACH IS ESB.
2. WHY DO WE NEED THE ESB?
• THE RESULTING ARCHITECTURE OF CONDUCTING NUMEROUS APPLICATIONS BY
THE COMMON EAI APPROACHES POINT-TO-POINT AND EAI BROKER WAS
ACCIDENTAL AS:
1. THE POINT-TO-POINT INTEGRATION APPROACH LEADS TO UNRELIABLE, INSECURE,
NON-MONITORABLE, AND IN GENERAL NON-MANAGEABLE COMMUNICATION
CHANNELS BETWEEN
APPLICATIONS.
THE PROCESS AND DATA TRANSFORMATION LOGIC ARE ENCODED INTO THE
APPLICATIONS.
THUS, EACH TIME A CHANGE OCCURS IN AN APPLICATION, A NEW INTEGRATION
PROJECT
HAS TO BE LAUNCHED IN ORDER TO REFACTOR THE DEPENDING APPLICATIONS.
2. THE EAI BROKER INTEGRATION APPROACH TRIES TO INTEGRATE ALL KINDS OF
APPLICATIONS USING A CENTRALIZED EAI BROKER WHICH LEADS TO WHAT WE CALL
ISLANDS OF INTEGRATION.
ISLANDS OF INTEGRATION EXIST BECAUSE THE HEADS OF THE DEPARTMENTS REFUSE
TO GIVE UP CONTROL OVER THEIR RESOURCES VIA INTEGRATING THEM OR MOVING
THEM TO A CENTRALIZED INFRASTRUCTURE CONTROLLED BY THE ENTERPRISES.
3. WHAT DOES THE ESB PROMISE?
• ESB PROMISES TO CONSTRUCT AN SOA BY ITERATIVELY INTEGRATING ALL KINDS OF ISOLATED
APPLICATIONS INTO A DECENTRALIZED INFRASTRUCTURE CALLED A SERVICE BUS.
• IT ALLOWS DEPARTMENTS TO PROVIDE SELECTIVE ACCESS TO THEIR BUSINESS INFORMATION TO
ENFORCE LOCAL POLICIES AND THEREFORE TO KEEP LOCAL AUTONOMY.
• DECENTRALIZED INFRASTRUCTURE IS ALSO HIGHLY DISTRIBUTED AND VERSATILE, IT RATHER
ALLOWS TO BRING ALL KINDS OF APPLICATIONS STEP-BY-STEP TO THE SERVICE BUS. THEREFORE,
THE INTEGRATION PROJECTS NOW HAVE THE
GOAL TO BRING THE BUSINESS FUNCTIONALITY IMPLEMENTED BY DIFFERENT APPLICATIONS.
• AS A RESULT OF THIS BUSINESS SERVICES CAN NOW BE REUSED AND COMPOSED IN SUBSEQUENT
PROJECTS.
DIFFERENCES BETWEEN ESB AND FORMER EAI
APPROACHES
• ESB FOLLOWS A LONG-TERM STRATEGY, THAT IS TO BRING ALL KINDS OF ENTERPRISE
APPLICATIONS AS BUSINESS SERVICES TO THE SERVICE BUS.
• ESB ARCHITECTURE IN WHICH ALL KINDS OF APPLICATIONS ARE PROVIDED AS
BUSINESS SERVICES AND CONNECTED VIA RELIABLE, SECURE, AND MANAGEABLE
VIRTUAL CHANNELS.
AS A CONSEQUENCE, PROCESS ORCHESTRATION AND DATA TRANSFORMATION LOGIC
CAN BE MOVED
TO THE BUS AND PROCESS INTERACTIONS CAN BE PERFORMED IN A CONTROLLED
MANNER.
CONCLUSION
• WE CAN SAY THAT ESB COMBINES BEST PRACTICES FROM EAI OF THE LAST YEARS,
REUSES AND INTEGRATES COMPONENTS THAT HAVE BEEN ON THE MARKET FOR
YEARS, AND MAKES IT MORE MANAGEABLE.
• IT COMBINES BEST PRACTICES FROM EAI BECAUSE IT IS BASED ON CONCEPTS FROM
MOM, EVENT-DRIVEN ARCHITECTURE (EDA), AND SOA.
• IT REUSES COMPONENTS, SUCH AS MESSAGING SYSTEMS, J2EE SERVERS,
INTEGRATION ADAPTERS FROM CENTRALIZED EAI SOLUTIONS, BUSINESS PROCESS
MANAGEMENT ENGINES, AND XML PROCESSING SERVICES, AND INTEGRATES THEM TO
PROVIDE ADDED VALUE.
• FINALLY, IT MAKES THE INTEGRATED COMPONENTS MORE MANAGEABLE AND
THEREFORE MORE VALUABLE BY PROVIDING A POWERFUL MANAGEMENT FACILITY AND
INTEGRATING THEM INTO IT.

ESB.pptx

  • 2.
    INTRODUCTION • DUE TOTHE ONGOING GLOBALIZATION, ENTERPRISES ALL OVER THE WORLD HAVE TO FACE A FIERCE COMPETITION. • AND TO STAY IN BUSINESS, THEY HAVE TO DEVELOP THEIR BUSINESS PROCESSES, INTEGRATE WITH THEIR BUSINESS PARTNERS, AND PROVIDE NEW SERVICES TO CUSTOMERS. • THE IT GOAL HAS ALSO CHANGED DUE TO THE CHANGING DEMANDS IN BUSINESS. AS TODAY IT HAS TO ACTIVELY SUPPORT ENTERPRISES IN THAT GLOBAL COMPETITION.
  • 3.
    RESPONSIBILITIES ENTERPRISES IT • ENTERPRISESHAVE TO TRY TO ACHIEVE THE GOAL BY DEVELOPING A SERVICE-ORIENTED ARCHITECTURE (SOA). WHY? • IN SOA THE BUSINESS FUNCTIONALITY: 1. IMPLEMENTED BY DIFFERENT APPLICATIONS 2. IS PROVIDED VIA COARSE-GRAINED, LOOSELY-COUPLED BUSINESS SERVICES WHICH ALLOW TO EASILY CREATE, AUTOMATE BUSINESS PROCESSES BY USING REUSING COMPOSING THE PROVIDED SERVICE FUNCTIONALITY. IT HAS TO MAKE BUSINESS INFORMATION AVAILABLE ACROSS THE ENTERPRISE TO ALLOW: 1. SOFTWARE ENGINEERS TO CREATE, AUTOMATE AND INTEGRATE BUSINESS PROCESSES. 2. COMPANY WORKERS TO ACCESS ALL KINDS OF INFORMATION IN A UNIFIED WAY VIA A DEPARTMENT/ENTERPRISE-WIDE PORTAL.
  • 4.
    • SO TOSURVIVE IN THAT FIERCE COMPETITION ENTERPRISES SHOULD ACHIEVE INTEGRATION IN ALL THE DOMAINS BY USING THE BEST APPROACHES OF EAI ENTERPRISE APPLICATION INTEGRATION (EAI)
  • 5.
    BEST EAI APPROACHES •VARIOUS RESEARCH/CONSULTING COMPANIES SUCH AS FORRESTER RESEARCH, IDC, AND GARTNER INC BELIEVE THAT ESB IS THE MOST PROMISING APPROACH FOR EAI OF THE LAST YEARS. • GARTNER INC. ANALYST ROY SCHULTE WROTE IN 2002: ”A NEW FORM OF ENTERPRISE SERVICE BUS (ESB) INFRASTRUCTURE COMBINING (MESSAGE-ORIENTED MIDDLEWARE(MOM), WEB SERVICES, TRANSFORMATION, AND ROUTING INTELLIGENCE) WILL BE RUNNING IN THE MAJORITY OF ENTERPRISES BY 2005. ... THIS HIGH-FUNCTION, LOW-COST ESBS ARE WELL SUITED TO BE THE BACKBONE FOR SERVICE-ORIENTED ARCHITECTURES AND THE ENTERPRISE NERVOUS SYSTEM”.
  • 6.
    ESB AN INNOVATIVEAPPROACH TO EAI • THE TERM ESB IS OBVIOUSLY OFTEN USED TO HAVE DIFFERENT DEFINITIONS, FOR EXAMPLE, AN ARCHITECTURE, A PRODUCT, OR A WAY OF DOING THINGS. WE’LL DEFINE IT LATER. • HOWEVER, AS A MATTER OF FACT, MOST ENTERPRISES TODAY TRY TO DEVELOP AN SOA BY USING AN ESB. • TO KNOW ESB AND EAI AND THE GOAL THAT WE NEED TO ACHIEVE WE SHOULD ANSWER THE FOLLOWING QUESTIONS FIRST: 1. WHY DO WE NEED INTEGRATION? 2. WHY DO WE NEED THE ESB? 3. WHAT DOES THE ESB PROMISE?
  • 7.
    1. WHY DOWE NEED INTEGRATION? • TO BE ABLE TO FACE THE FIERCE COMPETITION THAT THE ONGOING GLOBALIZATION CAUSED. • TO STAY IN BUSINESS COMPANIES HAVE TO REDUCE THEIR COSTS AND GAIN NEW MARKET SHARES THROUGH THE PROCESS AND PRODUCT INNOVATIONS. • AS A CONSEQUENCE THE HEADS OF DIFFERENT DEPARTMENTS HAVE TO START COLLABORATING TO KEEP THEIR DEPARTMENTS A LIVE, IN BUSINESS AND NOT TO OFFEND THE ENTERPRISE'S MANAGEMENT.
  • 8.
    EAI COMMON APPROACHES •THERE WERE TWO COMMON APPROACHES FOR EAI IN THE PAST: 1. A POINT-TO-POINT INTEGRATION: AIMS TO DIRECTLY CONNECT TWO APPLICATIONS. 2. A CENTRALIZED EAI BROKER: AIMS TO CONNECT TWO OR MORE APPLICATIONS VIA A CENTRALIZED MEDIATOR WHICH IS CABABLE OF ROUTING/TRANSFORMING MESSAGES SENT BETWEEN THE APPLICATIONS. • TODAY’S BEST EAI APPROACH IS ESB.
  • 9.
    2. WHY DOWE NEED THE ESB? • THE RESULTING ARCHITECTURE OF CONDUCTING NUMEROUS APPLICATIONS BY THE COMMON EAI APPROACHES POINT-TO-POINT AND EAI BROKER WAS ACCIDENTAL AS: 1. THE POINT-TO-POINT INTEGRATION APPROACH LEADS TO UNRELIABLE, INSECURE, NON-MONITORABLE, AND IN GENERAL NON-MANAGEABLE COMMUNICATION CHANNELS BETWEEN APPLICATIONS. THE PROCESS AND DATA TRANSFORMATION LOGIC ARE ENCODED INTO THE APPLICATIONS. THUS, EACH TIME A CHANGE OCCURS IN AN APPLICATION, A NEW INTEGRATION PROJECT HAS TO BE LAUNCHED IN ORDER TO REFACTOR THE DEPENDING APPLICATIONS.
  • 10.
    2. THE EAIBROKER INTEGRATION APPROACH TRIES TO INTEGRATE ALL KINDS OF APPLICATIONS USING A CENTRALIZED EAI BROKER WHICH LEADS TO WHAT WE CALL ISLANDS OF INTEGRATION. ISLANDS OF INTEGRATION EXIST BECAUSE THE HEADS OF THE DEPARTMENTS REFUSE TO GIVE UP CONTROL OVER THEIR RESOURCES VIA INTEGRATING THEM OR MOVING THEM TO A CENTRALIZED INFRASTRUCTURE CONTROLLED BY THE ENTERPRISES.
  • 11.
    3. WHAT DOESTHE ESB PROMISE? • ESB PROMISES TO CONSTRUCT AN SOA BY ITERATIVELY INTEGRATING ALL KINDS OF ISOLATED APPLICATIONS INTO A DECENTRALIZED INFRASTRUCTURE CALLED A SERVICE BUS. • IT ALLOWS DEPARTMENTS TO PROVIDE SELECTIVE ACCESS TO THEIR BUSINESS INFORMATION TO ENFORCE LOCAL POLICIES AND THEREFORE TO KEEP LOCAL AUTONOMY. • DECENTRALIZED INFRASTRUCTURE IS ALSO HIGHLY DISTRIBUTED AND VERSATILE, IT RATHER ALLOWS TO BRING ALL KINDS OF APPLICATIONS STEP-BY-STEP TO THE SERVICE BUS. THEREFORE, THE INTEGRATION PROJECTS NOW HAVE THE GOAL TO BRING THE BUSINESS FUNCTIONALITY IMPLEMENTED BY DIFFERENT APPLICATIONS. • AS A RESULT OF THIS BUSINESS SERVICES CAN NOW BE REUSED AND COMPOSED IN SUBSEQUENT PROJECTS.
  • 12.
    DIFFERENCES BETWEEN ESBAND FORMER EAI APPROACHES • ESB FOLLOWS A LONG-TERM STRATEGY, THAT IS TO BRING ALL KINDS OF ENTERPRISE APPLICATIONS AS BUSINESS SERVICES TO THE SERVICE BUS. • ESB ARCHITECTURE IN WHICH ALL KINDS OF APPLICATIONS ARE PROVIDED AS BUSINESS SERVICES AND CONNECTED VIA RELIABLE, SECURE, AND MANAGEABLE VIRTUAL CHANNELS. AS A CONSEQUENCE, PROCESS ORCHESTRATION AND DATA TRANSFORMATION LOGIC CAN BE MOVED TO THE BUS AND PROCESS INTERACTIONS CAN BE PERFORMED IN A CONTROLLED MANNER.
  • 19.
    CONCLUSION • WE CANSAY THAT ESB COMBINES BEST PRACTICES FROM EAI OF THE LAST YEARS, REUSES AND INTEGRATES COMPONENTS THAT HAVE BEEN ON THE MARKET FOR YEARS, AND MAKES IT MORE MANAGEABLE. • IT COMBINES BEST PRACTICES FROM EAI BECAUSE IT IS BASED ON CONCEPTS FROM MOM, EVENT-DRIVEN ARCHITECTURE (EDA), AND SOA. • IT REUSES COMPONENTS, SUCH AS MESSAGING SYSTEMS, J2EE SERVERS, INTEGRATION ADAPTERS FROM CENTRALIZED EAI SOLUTIONS, BUSINESS PROCESS MANAGEMENT ENGINES, AND XML PROCESSING SERVICES, AND INTEGRATES THEM TO PROVIDE ADDED VALUE. • FINALLY, IT MAKES THE INTEGRATED COMPONENTS MORE MANAGEABLE AND THEREFORE MORE VALUABLE BY PROVIDING A POWERFUL MANAGEMENT FACILITY AND INTEGRATING THEM INTO IT.