More time for people!

Transcription

1 More time for people! Middleware Technologies and Trends Pekka Puhakka ICOPER Meeting , Brussels

2 Agenda Brief Introduction to Middleware and EAI The Possibilities and the Problems Middleware Models and Paradigmas Application Servers vs. Integration Servers XML and SOAP Case

3 Approach... Building Information Society: what are the key technologies to build eservices for customers and citizens? to provide services from single point of access to integrate processes and key applications across organizations to build new morern component based eservice applications effectively and flexibly Middleware technologies making it all possible...

4 Version: 2.0 eservices and Collaborative Information Society Shard Processes National Administration Internal Processes Shard Processes Citizen Customer Local Governments Internal Processes EU Internal Processes and Workflow Local Districts Internal Processes Customer Citizen Shard Processes Private Sector Internal Processes Shard Processes

5 Version: 2.0 Evolution of Digital Government Consistent Government Redefined organisations Automated information exchange dsociety Innovative new services Organisational boundaries are changing Re-engineered service processes New channels: Mobile, digi-tv... Value adding digital services Digital services Services in the Net, self-service solutions Improved service processes Stable technology Internet hype Reasoning Understanding of importance Development of legislation and infrastructure Planning and piloting Web-surfing, visioning, info-services 2001 Time

6 Middleware - definition Middleware is defined as a set of services required for providing connectivity and management services in a distributed computing environment. These services include database connectivity, messaging, remote procedure calls, object request brokers, transaction services, timing services, and naming services.

7 Application Integration Application Integration - the Problem Application Integration - the Problem A variety of systems is installed, each purchased for sound reasons - because it provided the best solution to a specific problem. But these systems are not often well connected at the application level. Communication is traditionally solved with a common database or with FTP. The result is that the information owned by the various systems is not being exploited in the best way. The challenge is to make best use of the total set of information and to exploit the synergy which may exist between the systems. The situation is the same between enterprises. The same communications challenges exist between organisations as within them. Increasingly, this situation is occurring as more and more supplier/consumer relationships are established via direct network communications.

8 Enterprice Application Integration (EAI) A new set of middleware services has been defined to enable Enterprise Application Integration (EAI). EAI allows packaged applications such as Baan, SAP, PeopleSoft, and others to to share information with other packaged applications as well as with custom applications. The services required to enable EAI include all the previously defined middleware services, in addition to application adapters that allow access to application data, data translation and transformation, message routing, and process management.

9 Version: 3.0 Loogical Layers in Modern eservice Solution Tietovarasto ja EAI Legacy Data/service access Komponentteja Sovelluskohtaiset komponentit eservice platform Servlet Engine Web Server Turvapalvelut Pääsynvalvonta Salaus Vahva tunnistus Käyttäjät Selain ja PC MOM Network WAP GW Allekirjoitukset Sulkulistakysely Application Data Valmiskomponentit Mobiili päätelaite DB ibroker - asionti framework tetransformer J2EE APIt tetransport Application GW Sovellus-sovellus käyttö

10 EAI to help applications talk together System CRM System System System System CRM System ERP System DW Interface Spaghetti System A System B ERP System DW EAI System A System B C C Route, map, transform, cleanse, trigger, aggregate; reduce complexity, cost

11 Middleware Models - Loosely Coupled MOM (Message Orinted Middleware) Prime model for loosely coupled integration Best model for distributed not centrally controlled systems Models: Peer-to-Peer (asyncronous- and sysncronous models) Publish and Subscribe Message brokering, message warehouses Both not object oriented and also ORB-type implementations Vendor spesific APIs and two standard APIs JMS (Java Messaging Service) for Java implementation CORBA Notification Service - language independent Key functionality Content based routing message transformation XML support

12 Middleware Models - Tightly Coupled ORB (Object Request Broker) Build type integration, tight coupling Component level integration IIOP, RMI, XML-SOAP vs. application level integration messaging type on integration with JMS and CORBA Notifivcation Serv Support for maintaining multiple versions of component so that prior versions can be accessed if desired. Based on some standard API Some wendors use RPC-technology underneath ORB paltform RPC (Remote Prosedure Call) - DCE-RPC Request/reply paradigm Can also be used to screen database Hard to maintain, not so tendy prosedural paradigm RDA (Remote Data Access) ODBC, SQL*Net

13 Middleware Models - Packaging Application Servers for Integration Build type integration with a wrapper component (acting as proxy) to back-end transaction or service e.g. Web Banking solutions Tightly coupled approach Most recent trend e.g. JAS + JMS Integration Servers for Integration Buy-and-Integrate type solution (with packeged applications) Loosely coupled approach Portal Servers Functionality of applications servers and integrations servers

14 Middleware Evolution - Stage I Heterogeneous Connectivity Base message based architecture provides reliable, transactional messaging across heterogeneous platforms and networks Disperate Systems Mixed Environments Complex Programming Limited Design Difficult Coordination of Data An asynchronous, message based architecture provides an ideal way to link both systems and applications, providing the features outlined Platforms Time independence Protocols

15 Middleware Evolution - Stage II Business Integration and Message Brokering Requirements for business and application integration Integration of applications and information sources Heterogeneous and decoupled environments Transactional and reliable Transformation of data Routing of data Database integration Administration and management tools Formatting Translation Rules

16 Middleware Evolution - Stage III Workflow for Business Integration Workflow and messaging are key to corporate responsiveness. In a workflow system, business activities instantly share status information through an event-driven model triggered from the content of individual business transactions. These events are reliably automated to trigger further activities or may pass to staff through worklists and personal activity. Workflow provides a process automation system for managing people, data, applications, and business processes throughout an organization, including external partners via the internet or intranets and extranets. People Applications Process

17 Middleware Evolution - Message Brokering Source and Copuright: : IBM, MQ Series Integrator

18 Business Process Integration Dimension

19 SOAP Definition The abstract of SOAP 1.1. specification: "SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in the specification document describe how to use SOAP in combination with HTTP and HTTP Extension Framework."

20 What is SOAP for? Defines a remote procedure call mechanism using XML syntax Implements component level interaction across a public network SOAP is not tied to any particular platform and programming language HTTP transport layer (other protocols possible: MOM products, SMTP, a file on a disk,...) XML for encoding: invocation requests, responses SOAP doesn't replace COM or CORBA or EJB COM and EJB are component models, CORBA is a specification of services that are useful for building distributed applications SOAP is simply a communication protocol that COM, CORBA or EJB objects can use to communicate SOAP might replace DCOM or IIOP SOAP is a wire protocol like DCOM and IIOP DCOM and IIOP have problems with firewalls - SOAP can use basic HTTP

21 Version: 2.0 The Birth of a Portal Server Portal User Interface / Client Portal User Interface / Server Portal Applications Context Add-on Applications Application Server Integration Broker Adapters Messaging Packages Legacy Systems Source: GartnerGroup, 1999/8

22 Version:1.0 Portal Framework Plug-In Enterprise Portal Components Report Server Repository Management OLAP Engine Connection to Collaboration System Enterprise Applications Portal Framework Personalization Engine Activity Tracking Profile Management Catalog Management Content Management Security Mgmt. Shared Portal Services Metadata Management DB Repository Management Modified from: META Group 2000

23 Evolution of the Application Server Synchronous (Tightly Coupled) Application Servers Driven by: Economy of Scale Lower Costs Rapid Extensibility Standards Convergence Build Integration Servers (Brokers) Buy & Integrate Source: GIGA World IT Europe Forum 2000 Asynchronous (Loosely Coupled)

24 MOM peer-to-peer type messaging Program A sends a message to program B via Queue 1

25 MOM Messaging Styles

26 Unified Application/Integration Architecture Framework Client Environment External Business Portal Presentation Data Synch./ Broadcast Workflow Client Business Event Console Directory Internet Interface Components Middle-Tier Business Logic & Process Tr. Component Container Integration Server Workflow Server Transaction Coordinator Resources Security: Authenticate Security: Permission Database Caching & Connection XML and Message Formatting Reliable Workload Management Messaging, Synchronization Integration Connectors End-to-End Management Source: GIGA World IT Europe Forum 2000

27 Application-Server Based Application Integration Solution Authoring Components Business Process Modeling Messaging (JMS, CORBA, ) Recource & Interface Modeling Web Communications Process Generator XML Parsing & Translation Process State Metadata Security, Directory, etc... Runtime Components Application Process Adapters Database Connection Pooling Process Manager Automated Process Executive Process Automation Services Authoring Components Runtime Components Format & Translation Mapper Adapter Toolikit Routing Rules Metadata Services Generator of Adapters, Rules, Filters Application Integration Services Application Server Services Integration Server: routing, request/reply, Quality of Service, Runtime Management Application Connectors Source: GIGA World IT Europe Forum 2000

28 Version:1.0 eservices Integration Enterprise Application Integration (EAI) Links data and business processes managed by disparate applications within a company to increase efficiency and reduce costs Web Application Integration Integrates Internet driven transactions with an enterprise s core IT infrastructure in real-time to increase accuracy and customer service Business to Business Integration (emarkets) Extends Business-to-Business (B2B) information and key processes beyond the enterprise to suppliers, partners and customers to create dynamic new markets and improve the planning and execution of critical business functions

29 Business Area 1 Self- Describing Messages (XML) Loos Coupling Loosely Coupled Service-Based Architecture X D Intelligent, Federated Business Process Y IAI C B A Business Area 3 Business Area 2 Well-Defined Service Interface (Contract) Tighter Coupling OK Within Domains Source: GIGA World IT Europe Forum 2000

30 Three Approaches to EAI Back-End Integration Function Integration Front-End Integration System A Data Broker System B System A System B System A System B DB DB DB DB DB DB Business Functions Business Functions Business Functions Message Broker Message Broker Consolidation Logic Presen- tation Presen- tation Presen- tation Presen- tation Presentation

31 XML's Role in Application Integration XML Possibilities Application Integration Features Application Application Adapters Communications Data Transformation Flow Controll Application Integration Management Message Dictionary Message Warehouse Application Application Modified from: GartnerGroup, 1999

32 Version: 2.0 The Birth of a Portal Server Portal User Interface / Client Portal User Interface / Server Portal Applications Context Add-on Applications Application Server Integration Broker Adapters Messaging Packages Legacy Systems Source: GartnerGroup, 1999/8

33 Version: 3.0 VTJ2000 Application-to-Application Gateway Population Register System (VTJ) Managem. DB data Queries DB data DCE Authenticat Audit Services MOM DCE Authenticat Audit Services MOM NETWORK Gateway Network Network API Generic App-to- App Gateway Geneeric Server Framework Transport (Socket/SOAP) MOM Interface to MOM Network Message Parsing: XML / Native Security & Audit (PKI/HST) Sock VPN Node File # &%. # &%. Customer VPN Node Sock Sock Application Application Application Application Native VTJ XML Native

34 More time for people!