Web Services, CORBA and Other Middleware

Home , Middleware

© Copyright IONA Technologies 2002 Dr. Seán Baker Dr. Seán Middleware IONA Technologies Web Services For The Integrated Enterprise, OMG Workshop, Munich Feb 2003 Feb Workshop, Munich OMG Enterprise, Integrated For The Web Services Web Services, CORBA and other offer? 2 Web Services 2 – what does So middleware Overview • There a number of different types

© Copyright IONA Technologies 2002 3 3 –CORBA –J2EE –.NET – MoM & EAI proprietary middleware Various – Sevices – Web new kid on the block. the are multiple – competing – choices: Middleware • Middleware enables integration, but there

© Copyright IONA Technologies 2002 , including: 4 technical grounds personal choice 4 – versus message passing RPC – Java specific versus multi-language – versus indirect communication Direct – versus occasional connection Permanent – versus integration middleware Platform There’s lots of choice • Some based on • Some based on

© Copyright IONA Technologies 2002 may be used at the two ends 5 5 ( & inter-enterprise security in general) • etc languages, system, operating well as different As – Firewalls – Different middleware enterprise Intra-enterprise versus inter-enterprise • middleware has been designed for intra- Most • adds at least two challenges Inter-enterprise

© Copyright IONA Technologies 2002 6 6 but ones that need to be addressed in any case formatting approach • through a firewall it can flow So • “cheat” This raises security and other concerns, • both sides can accept this as a “neutral” So – Its protocol is layered on HTTP – to format messages It uses XML Web Services • Aims to address both of these issues

© Copyright IONA Technologies 2002 Firewall 9 9 business functions, transactions and processes as well-defined services. SOAs are designed to allow reuse of services and rapid integration of applications with services. – IT architecture that exposes An components, • Oriented Architectures (SOA) Service Web Services – Level View Higher

© Copyright IONA Technologies 2002 (e.g. inter- 10 10 XML isn’t a panacea for interoperability understand the messages • send) – use of XML doesn’t ensure that both sides will So – “open” compared to proprietary / binary formats – has a poweful set of transformation tools XML – Also messages are larger (slower to marshall and enterprise) • is a very general formatting tool XML • it has advs for some uses However, Use of XML to format messages

© Copyright IONA Technologies 2002 11 11 – ERP e.g., communication 3 uses of Web Services • communication Inter-enterprise • (inter-middleware) Intra-enterprise • neutral interfaces to packages Technology

© Copyright IONA Technologies 2002 ” and not services using the Web Services ” 12 although MOM & EAI will have to adapt & EAI will have to MOM although integration middleware 12 standards. CORBA, J2EE and .NET are the only platform middlewares. – can’t implement You •CORBA •J2EE • MOM, EAI etc platform middleware “ and no one has money these days to fix what isn’t broken – incumbents The are strong, well suited to their uses, – Web Services are “ • as Such •Why: Web Services won’t replace existing middleware …

© Copyright IONA Technologies 2002 J2EE J2EE Web services Web services COM COM 13 Web Services Web Services 13 J2EE J2EE CORBA CORBA CORBA CORBA an enterprise CORBA CORBA • integrate between different enterprises to • and to integrate between different “islands” inside • Web Services Use Web Services – relationship to other middleware

Coupling B2B EAI

(inside one enterprise) CORBA

(more than one process) J2EE between enterprises between applications inside one application inside one process 14 Tighter Looser Program Application B2B Market, Global Enterprise Complex Application The Middleware Space Single-Site Enterprise;

© Copyright IONA Technologies 2002 Infostrada intelligent Network Synchronous ASAP Synchronous NASG Synchronous CORBA: Infostrada SOAPG 15 SOAP Interface : 15 SOAP/HTTP Synchronous InfoStrada Architecture SAS Wind BSCS Example:

© Copyright IONA Technologies 2002 • Inter-enterprise • Inter-middleware “sweet spots” for Web “sweet Services: a common set of standards? •the Concentration on • Will the industry agree on 16 16 – “Transactions” – and Forward Store • Security • Flow Process • connections Unreliable • and subscribe Publish • Management • and so on … Web Services standardisation will continue for many years

© Copyright IONA Technologies 2002 Activation Install Equip. Web Service Web Schedule Truck Roll Truck Billing Billing System Initialize Web Service Web 17 Workflow Workflow ISP 17 Account Web Service Web Setup ISP B2B Vendors Procure Equipment Web Service Web Equipment CORBA System Assign Inventory Process Flow Service Web Numbers

© Copyright IONA Technologies 2002 18 18 utilities, government, defence, computer animation, computer utilities, government, defence, so on and simulation, weather astronomy, • telecommunications, banking, well proven: …. And very oriented, robust, high-performance, reliable, transactional, secure, …. – Multi-language, multi-platform, object/component – … why would you need Web Services ? Web Services and CORBA • is platform middleware CORBA • what’s missing then? So

© Copyright IONA Technologies 2002 with CORBA CORBA Same applies to J2EE, etc. 19 Web Web Service Service 19 the web (technology and acceptance) – just across firewalls, but integration Not enterprise SOAP message Much better web-connectivity than any other web technology. • Integration across the web • Integration across “islands” within an

What can Web Services offer CORBA? © Copyright IONA Technologies 2002 EJB Other platform middlware, e.g., .NET EJB CORBA CORBA 20 Web Web Service Service 20 SOAP message An implementation platform! What can CORBA offer Web Services?

© Copyright IONA Technologies 2002 23 23 seriously trust the clients” rule – Latency – any 10x needs to be taken – CORBA interfaces break the “don’t Some – CORBA interfaces are “fragile” Some – WSDL interfaces, or XML schemas Standard can’t be translated directly into WSDL: • Other reasons why existing interfaces Other issues

© Copyright IONA Technologies 2002 Summary 24 24 – is very inappropriate technology web-based Previous –middleware single of a idea the forget – e.g., ERP 3 uses of Web Services • Inter-enterprise communication • Intra-enterprise (inter-middleware) communication • neutral interfaces to packages Technology

© Copyright IONA Technologies 2002 Summary 25 although MOM & EAI will have to adapt & EAI will have to MOM although 25 –CORBA –J2EE – MOM, EAI etc Web Services … • … won’t replace existing middleware ! Special support for integration of existing middleware with Web Services will be very valuable.

© Copyright IONA Technologies 2002 Summary 26 26 •QoS. Wrong translations. Awkward Too big. Compromises. – M2M isn’t trival – middleware can subsume No others – translation Runtime costs can sometimes be too high – Many standards required – QoS issues especially Integration (M2M) Web Services… • is the basis for Middleware to … • story for this it’s not the full But