Using DDS to Enable The Real-Time Enterprise Service Bus (RT-ESB)

Transcription

1 Using DDS to Enable The Real-Time Enterprise Service Bus (RT-ESB) Rajive Joshi, Ph. D. Gerardo Pardo-Castellote, Ph.D. Real-Time Innovations, Inc OMG Real-time and Embedded Systems Workshop Arlington, VA, July 13,

2 Agenda Life at the Edge The Gap between the Enterprise and the Edge Bridging the Gap: The Real-Time ESB Critical technologies Integrating DDS and JMS Integrating DDS and SQL Integrating DDS and Web Services 2

3 Life at the Edge: Air traffic control example Avionics Airplane LAN Embedded Real-Time Gateway Real-Time Gateway Alarms Control Tower LAN Real-Time Gateway Enterprise Enterprise Gateway Enterprise Arrival time Airport LAN Backbone 3

4 Life at the Edge: Net-Centric Node 4 Net-Centric Implementation Framework Part 4: Node Design Guidance Figure 1. c

5 The Gap: Enterprise surrounds the Edge Presentation Layer: Portals, Web Apps, Mobile Apps & Thick Clients Data accessed from here Orchestration Layer: Composite Applications, BPM and Workflow Business Logic Layer: Web Services-based Business Objects Multiple Networks & Middleware in between Integration Layer: EII, EAI and Web Services Data Layer: Systems of Record, Enterprise Applications and Data Systems Oracle SAP SQL i2 Compass Data originates here 5 Diagram Source: Redshaw, Motorola

6 The Gap: Differing Requirements Edge Enterprise High performance a must low latency high throughput Same middleware stack on both sides acceptable LAN environment / Trust boundary Scalability is important Effective Interoperability a must Different stacks on either side Lower performance acceptable May cross LAN/trust boundaries Scalability is important Impedance mismatch! 6

7 Agenda Life at the Edge The Gap between the Enterprise and the Edge Bridging the Gap: The Real-Time ESB Critical technologies Integrating DDS and JMS Integrating DDS and SQL Integrating DDS and Web Services 7

8 Critical Technologies Live Data Access API DDS JMS Information Distribution Technology Stored Data Access API Data Storage Technology SQL ODBC JDBC Service Integration Technology 8 Service Access API Web Services XML WSDL SOAP

9 Information Distribution Messaging Technologies and Standards Web Services Java RTSJ (soft RT) RTSJ (hard RT) Java/RMI Java/JMS CORBA RT CORBA Data Distribution Service / DDS Non-real-time Soft real-time Hard real-time Extreme real-time MPI 9 Adapted from NSWC-DD OA Documentation

10 Information Distribution Middleware Choices Really only three choices Use proprietary middleware Eg. MQ Series, Tibco, In house, JMS Standards based Popular in Enterprise Java only API only, no wire interoperability spec DDS Standards based Popular in Edge applications Multiple platforms and languages Wire interoperability Real-Time QoS High performance 10

11 Publish-Subscribe Middleware Declare Intent Register Interest Consumer Producer Consumer Deliver Middleware: DDS or JMS Producer Consumer Producer Consumer Decouples Producers and Consumers 11

12 Data Distribution: DDS Synopsis DDS Peer (Producer) Application write() Data Update Peer-to-Peer Interaction Data-centric Matching Topic, Compatible QoS Data samples are routed directly from the Publisher to the Subscriber DDS Peer (Consumer) Application DataReaderListener.on_data_available() SubscriberListener.on_data_on_readers() read() take() Data Samples DataWriter Topic DataReader Publisher DomainParticipant Subscriber DomainParticipant Data Sample Key Data Sample Data-object DDS Domain (Global Data Space) DDS Domain (Global Data Space) 12

13 DDS Synopsis: Requested/Offered Semantics DDS Peer (Producer) Application Peer-to-Peer Interaction Data-centric Matching Topic, Incompatible QoS Communication is not established DDS Peer (Consumer) Application DataReaderListener.on_data_available() SubscriberListener.on_data_on_readers() DataWriter Topic DataReader Publisher Offered QoS Requested QoS Subscriber DomainParticipant Requested QoS Incompatible with Offered QoS DomainParticipant S Communication Not established DDS Domain (Global Data Space) DDS Domain (Global Data Space) 13

14 JMS Synopsis JMS Client (Producer) Application Client-Server Interaction JMS Client (Consumer) Application MessageListener.onMessage(Message m) send() Message Message-oriented receive() Message Message Producer Session Message Consumer Session Message Connection Messages are routed via the Destination JMS Provider (Server) Connection Message Message Destination 14 Administrative Tool (JNDI Namespace)

15 JMS-DDS Semantic Mapping: Equivalents JMS Client Provider = client runtime + server (if any) Domains are PtP and Pub/Sub ConnectionFactory Connection start() Session Destination A named physical resource that gathers and disseminates messages addressed to it Message MessageProducer MessageConsumer DDS Application Middleware, Service Domain represents a global data space, comprised of a set of communicating user applications DomainParticipantFactory DomainParticipant enable() Publisher, Subscriber FooTypeSupport extends TypeSupport Used to register a user type Foo with a DomainParticipant Topic (of type Foo ) An abstraction with a unique name, data-type, and QoS, used to connect matching DataWriters and DataReaders Foo (data-object) An instance of type Foo FooDataWriter extends DataWriter FooDataReader extends DataReader 15

16 JMS-DDS Semantic Mapping: Differences JMS DDS Data Modeling Dataflow Routing Autonomous messages, Message-oriented, Payload is opaque Specific destinations Data-objects, Data-centric, Relational data model Matching Topics and Compatible QoS Discovery Data Typing Administered Predefined message types Spontaneous, Access to endpoint meta-data Arbitrary user data types 16

17 JMS and DDS: Practical Considerations Architecture Platforms Interoperability Transports Security Administration Performance Scalability Real-Time support Enterprise support Java None. No plans. JMS Client/Server, Centralized, Asymmetric Connection oriented. Requires inorder acknowledged delivery. (Username, Password) JNDI, External to JMS Limited by: PtP, Destinations Transactions, Application acknowledgements, Java EE DDS Peer-to-Peer, Decentralized, Symmetric Multiple languages (C, C++, Java, ) & platforms Wire protocol standardization in progress Connection-less unreliable transport like UDP Extensible mechanism None: plug-n-play Lower latency, higher throughput. Independent 10x better claims Many capabilities designed for real-time, low latency apps 17

18 Using DDS and JMS together JMS-DDS Bridging Translate between DDS updates JMS messages Data conversion overhead Least common denominator Integrate different sub-systems JMS/DDS Bindings Wrap DDS middleware with JMS APIs Port JMS applications to DDS JMS apps interoperable with DDS Higher performance JMS 18

19 Data Storage: Integrating DDS and SQL Live Data Access API DDS JMS Information Distribution Technology Relational Data Model Stored Data Access API SQL ODBC JDBC Data Storage Technology Previous Presentation Service Integration Technology 19 Service Access API Web Services XML WSDL SOAP

20 Service Integration: Integrating DDS and Web Services Live Data Access API DDS JMS Information Distribution Technology Stored Data Access API SQL ODBC JDBC Data Storage Technology WSDL SQL Mapping Service Integration Technology WSDL DDS Mapping 20 Service Access API Web Services XML WSDL SOAP

21 What is a Web Service? Web Service Data: XML Interface: WSDL Component W3C Definition A software system designed to support interoperable machine-to-machine interaction over a network Service Data Model: XML Schema XML = Extensible Markup Language XML Schema for describing XML documents (Data Types) Service Contract: WSDL Web Services Description Language Defines all details about a service contract (Interfaces) Encoding of Messages: SOAP Simple Object Access Protocol How to format XML documents for transmission between applications (Serialize/Deserialize) Family of Extensible Specifications 21

22 An Example Web Service Aircraft Tracking Service Data: XML Interface: WSDL Aircraft Tracking Component XML Schema Service Data Model TrackData x y z <complextype name= TrackData > <element name = x type= xsd:double > <element name = y type= xsd:double > <element name = z type= xsd:double > </complextype> WSDL <porttype name= AircraftTrackingServicePort > <operation name= GetPosition > <input message= AircraftIdMessage name= aircraftid > Service Contract GetPosition Message In Aircraft Id Message Out TrackData <output message= TrackDataMessage name= trackdata > </operation> </porttype> <message name= AircraftIdMessage > <part element= xsd:int name= aircraftid /> </message> <message name= TrackDataMessage > <part element= TrackData name= trackdata /> </message> 22

23 A Web Service is Just a Specification Technology Independent Service Level Data Model Technology Independent Service Contract Service Requester Service Proxy Service Contract Service Platform Service Skeleton Service Provider Binding Mapping of Requestor s Internal implementation Interfaces and data model to Service Level Contract and Data Model Service Contracts Service-Level Data Model Service-Level QoS Service Registry/Lookup Service-Level Security Service-Level Comm Model ServiceProxies & Skeletons Service-Level Management Multi-language bindings Binding Mapping of Service Level Contract and Data Model to Provider s internal implementation Interfaces and data model 23 Adapted from: Newcomer & Lomow

24 Binding a Web Service to a Transport WSDL Defines Service Contract Service Communications Requirements: Operations, Structure and Typing of Messages Encoding & Transport of Messages Physical Endpoint Address XML Schema Runtime execution Service Requester SOAP Request XML SOAP Response HTTP, CORBA, JMS,DDS, Service Provider 24 Adapted from: Newcomer & Lomow

25 Enterprise Service Bus (ESB) The Enterprise Service Bus (ESB) Pattern End-Point End-Point End-Point End-Point WSDL WSDL WSDL WSDL Service Bus Enterprise Service Bus WSDL WSDL WSDL WSDL End-Point End-Point End-Point End-Point Collection of distributed, interconnected end-points Support multiple transports / middleware No internal canonical data format Instead: support transformation and routing 25 Adapted from: Iona, Next Generation ESBs

26 Enabling the Real-Time ESB Using DDS as a Transport for a Web Service WSDL/DDS Bindings WSDL/SQL Bindings Using DDS-SQL Integration to access the global data space Exposing DDS as a Web Service Exposes the underlying relational data model 26

27 Using DDS as a Web Service Transport Web Service Provider (Web Server or App Server) Web Service Requestor WSDL/SOAP Request WSDL/SOAP Reply JAX-WS (Java WSDP) WSDL DDS Data Mapping Java DDS API Bindings Auto-generated Application Code DDS DDS Domain Domain (Global Data Space) (Global Data Space) 27

28 Using DDS-SQL Integration as a Web Service Transport Web Service Requestor WSDL/SOAP Request WSDL/SOAP Reply Web Service Provider (Web Server or App Server) JAX-WS (Java WSDP) WSDL DB Data Mapping JDBC SELECT UPDATE DELETE CREATE TABLE DROP TABLE DB DDSQL/SkyBoard Auto-generated Application Code DDS DDS Domain Domain (Global Data Space) (Global Data Space) 28

29 DDS as a Web Service: Expose the Data Model DDS Web Service DDS Adapter Component Global Global Data Data Space Space Service Data Model ParticipantInfo DataTypeInfo TopicInfo PublisherInfo DataWriterInfo SubsriberInfo DataReaderInfo DataReaderListenerInfo : Service Contract CreateParticipant RegisterType CreateTopic CreatePublisher CreateDataWriter XML Schema Example <complextype name= ParticipantInfo > <element name = domain_id type= xsd:int > </complextype> : WSDL Example <porttype name= DDSPort > <operation name= CreateParticipant > <input message= ParticipantInfoMessage name= participantinfo > <output message= URIMessage name= participanturi > </operation> : </porttype> 29 CreateSubscriber CreateDataReader SetDataReaderListener : <message name= ParticipantInfoMessage > <part element= ParticipantInfo name= participantinfo /> </message>

30 New Possibilities using the Real-Time ESB Bridge the gap between the Edge and the Enterprise Resolve the impedance mismatch Real-Time Database Cache Exchange data between the edge and the enterprise Access enterprise data from embedded devices Integrate with disparate technologies Leverage integration of other technologies with Web Services Realize the promise of an ESB from the edge to the enterprise Real-Time SOA Enable high performance or real-time Web Services Using DDS as a transport for a Web Service Remote monitoring and control of DDS applications Using DDS as a Web Service 30

31 Bridging the Gap: Air traffic control example redux Avionics Airplane LAN Edge DDS Gateway RT-ESB DDS WSDL Alarms Control Tower LAN DDS Gateway Enterprise RT-ESB DDS WSDL or SQL ESB Arrival time Airport LAN 31

32 Bridging the Gap: Integrating DDS with JMS, SQL, Web Services Live Data Access API DDS JMS Information Distribution Technology Relational Data Model Stored Data Access API SQL ODBC JDBC Data Storage Technology WSDL SQL Mapping Service Integration Technology WSDL DDS Mapping Bridges between the Enterprise and the Edge Technologies 32 Service Access API Web Services XML WSDL SOAP

33 The Real-Time Enterprise Service Bus Publish-Subscribe Databases SOA Producer (DDS or JMS) Consumer (DDS or JMS) SQL Client Web Service Requestor Real-Time Enterprise Service Bus Pervasive Data Data Global Global Data Data Space Space 33

34 Thank You Q & A [email protected] Real-Time Innovations, Inc For more Information: RTI Whitepaper: A Comparison and Mapping of Data Distribution Service (DDS) and Java Message Service (JMS) 34