Embedded middleware: State of the art

Eila Niemelä, Tomi Korpipää, Arno Tuominen

Research output: Book/ReportReport

1 Citation (Scopus)

Abstract

Java, WWW, Internet and CORBA technologies will be enabling software technologies which make it possible to develop independent applications capable of communicating over various kinds of networks. Thus, embedded programs form networked client/server applications. Within these applications, they perform tasks, functioning as a part of a larger entity in a distributed network. Currently, firms have their own specialized solutions which require considerable maintenance resources. During development phase, the interoperability and extendibility of the systems are not given enough attention. Because of this, the solutions become rapidly obsolete. For several enterprises, a standardised solution for communications is in demand. Middleware is a general term that has come to represent a variety of distributed computing services in application development environments. Middleware products operate between the application logic and the underlying physical network. Embedded middleware provides standard communication services and object-oriented integration interfaces for networked embedded applications. The maturity of the commercial middleware products based on CORBA is insufficient and some of the services required in embedded systems are still unavailable. DCOM-based OPC will be a suitable solution for base stations that control data acquisition, monitoring and presentation. However, before it can be considered a suitable solution for client application executed in laptops or handheld PCs, OPC requires commercially available driver software. Embedded middleware requires communication services for remote procedure calls, events and messaging. If the system is connected to the Internet or other open networks, naming and security services are required as well. These services, and the generic interfaces which isolate the middleware from the operating system and protocols, have to be provided as component-based software which enables restricted adaptability during product life cycle. In future, applications will be composed of different types of components such as Java beans or applets, ActiveX components or CORBA components. Each of these component types requires its own interface technology.
Original languageEnglish
Place of PublicationEspoo
PublisherVTT Technical Research Centre of Finland
Number of pages109
ISBN (Electronic)951-38-5360-8
ISBN (Print)951-38-5359-4
Publication statusPublished - 1999
MoE publication typeD4 Published development or research report or study

Publication series

SeriesVTT Publications
Number375
ISSN1235-0621

Fingerprint

Middleware
Common object request broker architecture (CORBA)
Communication
Internet
Computer operating systems
Distributed computer systems
Interoperability
Embedded systems
World Wide Web
Base stations
Interfaces (computer)
Life cycle
Data acquisition
Servers
Network protocols
Monitoring
Industry

Keywords

  • embedded systems
  • middleware
  • information systems

Cite this

Niemelä, E., Korpipää, T., & Tuominen, A. (1999). Embedded middleware: State of the art. Espoo: VTT Technical Research Centre of Finland. VTT Publications, No. 375
Niemelä, Eila ; Korpipää, Tomi ; Tuominen, Arno. / Embedded middleware : State of the art. Espoo : VTT Technical Research Centre of Finland, 1999. 109 p. (VTT Publications; No. 375).
@book{c9180f9a25334a159aa865e973384434,
title = "Embedded middleware: State of the art",
abstract = "Java, WWW, Internet and CORBA technologies will be enabling software technologies which make it possible to develop independent applications capable of communicating over various kinds of networks. Thus, embedded programs form networked client/server applications. Within these applications, they perform tasks, functioning as a part of a larger entity in a distributed network. Currently, firms have their own specialized solutions which require considerable maintenance resources. During development phase, the interoperability and extendibility of the systems are not given enough attention. Because of this, the solutions become rapidly obsolete. For several enterprises, a standardised solution for communications is in demand. Middleware is a general term that has come to represent a variety of distributed computing services in application development environments. Middleware products operate between the application logic and the underlying physical network. Embedded middleware provides standard communication services and object-oriented integration interfaces for networked embedded applications. The maturity of the commercial middleware products based on CORBA is insufficient and some of the services required in embedded systems are still unavailable. DCOM-based OPC will be a suitable solution for base stations that control data acquisition, monitoring and presentation. However, before it can be considered a suitable solution for client application executed in laptops or handheld PCs, OPC requires commercially available driver software. Embedded middleware requires communication services for remote procedure calls, events and messaging. If the system is connected to the Internet or other open networks, naming and security services are required as well. These services, and the generic interfaces which isolate the middleware from the operating system and protocols, have to be provided as component-based software which enables restricted adaptability during product life cycle. In future, applications will be composed of different types of components such as Java beans or applets, ActiveX components or CORBA components. Each of these component types requires its own interface technology.",
keywords = "embedded systems, middleware, information systems",
author = "Eila Niemel{\"a} and Tomi Korpip{\"a}{\"a} and Arno Tuominen",
note = "Project code: E7SU00458",
year = "1999",
language = "English",
isbn = "951-38-5359-4",
series = "VTT Publications",
publisher = "VTT Technical Research Centre of Finland",
number = "375",
address = "Finland",

}

Niemelä, E, Korpipää, T & Tuominen, A 1999, Embedded middleware: State of the art. VTT Publications, no. 375, VTT Technical Research Centre of Finland, Espoo.

Embedded middleware : State of the art. / Niemelä, Eila; Korpipää, Tomi; Tuominen, Arno.

Espoo : VTT Technical Research Centre of Finland, 1999. 109 p. (VTT Publications; No. 375).

Research output: Book/ReportReport

TY - BOOK

T1 - Embedded middleware

T2 - State of the art

AU - Niemelä, Eila

AU - Korpipää, Tomi

AU - Tuominen, Arno

N1 - Project code: E7SU00458

PY - 1999

Y1 - 1999

N2 - Java, WWW, Internet and CORBA technologies will be enabling software technologies which make it possible to develop independent applications capable of communicating over various kinds of networks. Thus, embedded programs form networked client/server applications. Within these applications, they perform tasks, functioning as a part of a larger entity in a distributed network. Currently, firms have their own specialized solutions which require considerable maintenance resources. During development phase, the interoperability and extendibility of the systems are not given enough attention. Because of this, the solutions become rapidly obsolete. For several enterprises, a standardised solution for communications is in demand. Middleware is a general term that has come to represent a variety of distributed computing services in application development environments. Middleware products operate between the application logic and the underlying physical network. Embedded middleware provides standard communication services and object-oriented integration interfaces for networked embedded applications. The maturity of the commercial middleware products based on CORBA is insufficient and some of the services required in embedded systems are still unavailable. DCOM-based OPC will be a suitable solution for base stations that control data acquisition, monitoring and presentation. However, before it can be considered a suitable solution for client application executed in laptops or handheld PCs, OPC requires commercially available driver software. Embedded middleware requires communication services for remote procedure calls, events and messaging. If the system is connected to the Internet or other open networks, naming and security services are required as well. These services, and the generic interfaces which isolate the middleware from the operating system and protocols, have to be provided as component-based software which enables restricted adaptability during product life cycle. In future, applications will be composed of different types of components such as Java beans or applets, ActiveX components or CORBA components. Each of these component types requires its own interface technology.

AB - Java, WWW, Internet and CORBA technologies will be enabling software technologies which make it possible to develop independent applications capable of communicating over various kinds of networks. Thus, embedded programs form networked client/server applications. Within these applications, they perform tasks, functioning as a part of a larger entity in a distributed network. Currently, firms have their own specialized solutions which require considerable maintenance resources. During development phase, the interoperability and extendibility of the systems are not given enough attention. Because of this, the solutions become rapidly obsolete. For several enterprises, a standardised solution for communications is in demand. Middleware is a general term that has come to represent a variety of distributed computing services in application development environments. Middleware products operate between the application logic and the underlying physical network. Embedded middleware provides standard communication services and object-oriented integration interfaces for networked embedded applications. The maturity of the commercial middleware products based on CORBA is insufficient and some of the services required in embedded systems are still unavailable. DCOM-based OPC will be a suitable solution for base stations that control data acquisition, monitoring and presentation. However, before it can be considered a suitable solution for client application executed in laptops or handheld PCs, OPC requires commercially available driver software. Embedded middleware requires communication services for remote procedure calls, events and messaging. If the system is connected to the Internet or other open networks, naming and security services are required as well. These services, and the generic interfaces which isolate the middleware from the operating system and protocols, have to be provided as component-based software which enables restricted adaptability during product life cycle. In future, applications will be composed of different types of components such as Java beans or applets, ActiveX components or CORBA components. Each of these component types requires its own interface technology.

KW - embedded systems

KW - middleware

KW - information systems

M3 - Report

SN - 951-38-5359-4

T3 - VTT Publications

BT - Embedded middleware

PB - VTT Technical Research Centre of Finland

CY - Espoo

ER -

Niemelä E, Korpipää T, Tuominen A. Embedded middleware: State of the art. Espoo: VTT Technical Research Centre of Finland, 1999. 109 p. (VTT Publications; No. 375).