China
Africa
Explore chapters and articles related to this topic
Parallel and Distributed Processing
Published in David R. Martinez, Robert A. Bond, Vai M. Michael, High Performance Embedded Computing Handbook, 2018
Albert I. Reuther, Hahn G. Kim
Historically within embedded systems, the most commonly used distributed client-server middleware is CORBA. CORBA defines a distributed-object standard. The programmer describes the CORBA distributed objects in the CORBA interface definition language (IDL). The IDL code is then translated to build the client stub and server skeleton in the target language; these are used to interface the client and server code to the CORBA object request broker (ORB) (depicted in Figure 18-11). Thus, the programmer is not required to write these code stubs. The ORB is the translation (or marshalling) layer that enables heterogeneous platforms within the system to communicate. CORBA can be used in code written in a variety of languages, including C, C++, Java, COBOL, Smalltalk, Ada, Lisp, Python, and Perl, and some major interoperability problems were solved with the General Inter-ORB Protocol (see the Object Management Group’s website at http://omg.org/gettingstarted/corba-faq.htm). By default, a client invokes an object synchronously. The request is sent to the corresponding object server, and the client blocks the request until it receives a response. However, a client can also communicate with a CORBA object in a one-way, best-effort manner if it is not expecting a reply, or in an asynchronous request manner when it wants the reply to come back as a execution-interrupting callback (Tanenbaum and van Steen 2002).
General introduction
Published in Adedeji B. Badiru, Handbook of Industrial and Systems Engineering, 2013
The Pegasus service manager collaborates with third-party analysis servers (service providers) such as ANSYS to achieve the VAA process. Currently, the VAA architecture is implemented by common object request broker architecture (CORBA) (Siegel, 2000), which is an architecture and specification for creating, distributing, and managing distributed program objects in a network. It allows programs at different locations and developed by different vendors to communicate in a network through an "interface broker." An object request broker (ORB) acts as a "broker" between a client request for a service from a distributed object or component and the completion of that request. The ORB allows a client to request services from a server program or object without having to understand where the server is in a distributed network or what the interface to the server program looks like. CORBA serves as a bond to integrate the whole system and provides good features of openness for collaborative computation. The components in the distributed system have peer-to-peer relationships with each other. From the end-users' point of view, distributing application components between clients and servers does not change the look and feel of any single application, meaning that the system provides end-users with a single system image.
EOS: enterprise operating systems
Published in International Journal of Production Research, 2018
Joseph Rahme Youssef, Gregory Zacharewicz, David Chen, François Vernadat
At the beginning of the 1990’s, inspired by the IIS of CIMOSA, the first version of the Common Object Request Broker Architecture, known as CORBA, was proposed as a ‘standard’ in 1991 by the object management group (OMG). The final version is CORBA 3.3 published in November 2012 (OMG 2012). CORBA was designed for facilitating and enabling the communication of systems deployed on diverse platforms, written in different languages and implemented on different operating systems and models. It offered benefits such as inheritance, information hiding, reusability and polymorphism. However, CORBA can be better considered as a simple enterprise application integration platform rather than a true enterprise operating system (Bryan, Dipippo, and Fay-Wolfe 2005). For instance, it does not provide functionality for enterprise model execution.
Smart CPS: vertical integration overview and user story with a cobot
Published in International Journal of Computer Integrated Manufacturing, 2019
One of the first attempts to guide in a standardised fashion the development of MIES was SEMATECH CIM (Hawker 1999). Built on common object request broker architecture (CORBA), a standard used to achieve interoperability between distributed systems (CORBA n.d.). SEMATECH CIM was a standardised framework developed as a solution to the obsolete and inflexible custom built MIES to implement interoperability under a standardised approach (Cheng et al. 1999).