Manola, F., S. Heidler, D. Georgakopoulos, M. Hornick and M. Brodie (1992) Distributed Object Management, International Journal of Intelligent and Cooperative Information Systems, Vol. 1, No. 1, March, pp. 5-42.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....persistent objects by multiple users or applications. Recent research in the area if intelligent and cooperative database systems, suggests that the adoption of knowledge based extensions of object oriented database systems can solve the majority of problems, in a consistent framework; see e.g. Manola et al. (1992) and Papazoglou et al. (1992) Model management It has long been recognised that better computer based systems are needed to support modelling in analytical organisations, where there are many models and many users. The typical model management system should support the following tasks: model ....

....Organisational Information Systems (IOIS) The background technology for IOIS is based on object oriented computing and distributed artificial intelligence. Distributed AI platforms, such as MACE [Gasser et al. (1987) and knowledge based extensions of object oriented technologies, as in Manola et al. 1992), may prove to be the starting vehicles for IOIS implementation. Such an approach would generate increased benefits. First, IOIS cooperation can provide an interesting metaphor for the natural interaction among human experts in various fields. Second, the conceptual architecture presented here ....

Manola, F., S. Heidler, D. Georgakopoulos, M. Hornick and M. Brodie (1992) Distributed Object Management, International Journal of Intelligent and Cooperative Information Systems, Vol. 1, No. 1, March, pp. 5-42.

....(AIOs) The background technology for AIOs is based on concurrent object oriented computing and distributed artificial intelligence. Distributed AI platforms, such as MACE [17] can provide the initial implementation framework, while approaches that merge AI and object oriented technologies, as in [27] and [16] may prove to be the starting vehicles for AIO implementation. Such an approach would generate increased benefits. First, AIO cooperation can provide an interesting metaphor for the natural interaction among human experts in various fields. Second, the use of such automated intelligent ....

Manola, F., S. Heidler, D. Georgakopoulos, M. Hornick and M. Brodie (1992) Distributed Object Management, International Journal of Intelligent and Cooperative Information Systems, Vol. 1, No. 1, March, pp. 542.

....query formulation, users must have information about the distribution and the semantics of data. Distributed Object Management (DOM) Another way to model heterogeneous distributed systems is to represent the resources of the system as a collection of interacting objects (PITOURA, 1995; ZU, 1994; MANOLA et al. 1992). Each component system defines a service interface and provides the implementation of such services. The OMA (OMG, 1995) architecture and the ODMG (CATTEL, 1997) model are important research works devoted to this approach. MIND METU Interoperable DBMS (DOGAC et al. 1995; DOGAC, 1996) and ....

MANOLA, F., et al., 1992, Distributed Object Management, In: International Journal of Intelligent and Cooperative Information Systems, Jun.

....can be incorporated into the multidatabase system by providing an object oriented interface between such sources and the global schema. The use of the object oriented model as a canonical model and language for interface definitions has been widely addressed and supported in the literature [17, 7, 2, 19, 16, 22]. The advantages of having a canonical object model integrating heterogeneous data sources include a common methodology for modeling and querying, encapsulation, inheritance, coupling and modular extension. In Donaj i, semantic information about the structure and organization of the data in the ....

Manola, F., Heiler, S., Georgakopoulos, D., Hornick, M., Brodie M., "Distributed Object Management," International Journal of Intelligent and Cooperative Information Systems, Vol. 1, No. 1, 1992.

.... efforts have also been made to further extend conventional object oriented database technology by combining several attractive features from programming, operating systems, and technology for integrating different data models and managing heterogeneous databases into a single unifying framework [22]. The main benefit of the use of object oriented technology in distributed IS is that objects represent a natural framework for system modularization, accommodation of the construction of complex entities with shared subcomponents, and provide flexible module interconnection capabilities beyond ....

F. Manola et al., "Distributed Object Management", Int'l Journal of Intelligent & Cooperative Information Systems, vol.1, no. 1, March 1992, pp. 5-42.

....configure and integrate such resources [18, 21] Objects interact with each other by sending messages defined in the subject interface. Modeling a distributed environment as a collection of distributed objects communicating via their interfaces is the appropriate paradigm for distributed resources [15]. Standardization activities related to the adoption of a systematic approach in systems development became a necessity. The Object Management Group (OMG) is among the organizations that are actively involved in setting standards for a generic architecture that allows for integration and ....

F. Manola, S. Heiler, D. Georgakopoulos, M. Hornick, and M. Brodie. Distributed object management. International Journal of Intelligent and Cooperative Information Systems, 1(1), March 1992.

....problems are resolved at the schema integration stage. This approach cannot scale well when new sources need to be added into an existing multidatabase system. Also the component schemas cannot evolve without the consent from the integrated schema. The distributed object management approach [Mea92, ODV93] generalizes the federated approach by modeling heterogeneous databases of different levels of granularity as objects in a distributed object space. It requires the definition of a common object model and a common object query language. Recent activities in the OMG and the ODMG standard ....

F. Manola and et al. Distributed object management. International Journal of Intelligent and Cooperative Information Systems, 1(1), March 1992.

....Person information. With the MIND approach, the interface of Person objects is not known to the ORB. The fact that MIND does not allow registration of fine granularity objects makes MIND different from the distributed object management approach towards database interoperability as described in [Man92] where all objects in all databases form an object space that is accessible via the ORB. The way MIND uses CORBA is largely as a sophisticated communication 20 Ling Liu, Ling Ling Yan, M. Tamer Ozsu backplane, and it has little impact on the major technical aspects of MIND, such as schema ....

F. Manola et al. Distributed Object Management. International Journal of Intelligent and Cooperative Information Systems, 1(1), March 1992.

....and their inter relationships across system boundaries. In this respect our approach overcomes most of the conventional problems met in logically centralized and federated database configurations and falls into line with other major activities in the area such as the distributed object management [15] and remote exchange protocol [16] projects. These projects allow more structured units of information to be freely shared and exchanged among interoperable database systems [16] 15] To achieve this, ISs are wrapped with an object skin , expressed in terms of a common object data model, and ....

....and falls into line with other major activities in the area such as the distributed object management [15] and remote exchange protocol [16] projects. These projects allow more structured units of information to be freely shared and exchanged among interoperable database systems [16] [15]. To achieve this, ISs are wrapped with an object skin , expressed in terms of a common object data model, and their functionality is extended to that of a real information broker able to accept client requests for services and locate the endpoint where these requests can be executed. As many ....

F. Manola et al., "Distributed Object Management", Int'l Journal of Intelligent & Cooperative Information Systems, vol.1, no. 1, March 1992, pp. 5-42.

.... issues concerning interoperability and databases are discussed in the next section, but for a broader overview of the subject the reader may reference the many papers which discuss more general issues [7,8,12] and some which discuss different interoperability mechanisms: Object Equivalencing [14], Mediation [15] KBS Assist [17, 19] Orb based Intelligent Co operating Systems [16,11,4,18] and Com based object systems [10] 4. Information Systems Interoperability There is a number of motivating factors for interoperability between different database systems with differing data models. ....

Manola M., et al, `Distributed Object Management', International Journal of Intelligent and Cooperative Information Systems, 1992.

....use of a semantically rich common object model to ease application integration, the development of standards to interoperate among objects, the use of object oriented transaction models, etc. Well known research projects in object oriented multi database systems are Carnot [32] Disco [31] DOMS [21], Femus [2] GARLIC [7] InterBase [3] Pegasus [25] etc. A complete survey of object oriented multidatabase systems can be found in [4] The current paper focuses on IRO DB (Interoperable Relational and Object Oriented DataBases) 12] an ESPRIT project developed in Europe from 1993 to 1996. The ....

Manola F., Heiler S. Georgakopoulos D., Hornick M., Brodie M., "Distributed Object Management", Intl. Journal of Intelligent and Cooperative Information Systems, Vol 1, n°1, Pp. 5-42, March, 1992.

....systems. Therefore, we believe next generation hypermedia systems will also deal with intelligent tools and large amounts of information in a distributed, multiuser environment. A promising approach to the construction of next generation hypermedia systems is Distributed Object Management (DOM) Manola92, Ozsu93] The idea is to model heterogeneous computing resources as objects in a distributed object space and to provide the capabilities and protocols for object interaction and cooperation. The DOM approach involves generalizing and combining several technologies such as object oriented ....

....provides a good opportunity for architecturing next generation desktop computing systems, e.g. hypermedia systems, in a way that increases user productivity without performance penalty. Pursuing the objectives of Smalltalk like environments, extensible object managers [Exodus86] and DOM [Manola92] we go further in terms of integration of OOP, DBMS and DOS technologies. Our OO foundation provides extensible, protected and transparent management of distributed persistent objects. Similar to Smalltalk environments, the foundation is built on a nucleus of builtin objects available to all ....

F. Manola et al., Distributed Object management. Int. Journal of Intelligent and Cooperative Information Systems, 1(1), March 1992.

....not a model for the global schema. Similar approaches either specify a mediator knowledge base which has mapping knowledge among different schemas [Qian95, Raschid94] or use a common multidatabase language [Litwin86] Another approach which can be used for MDBMS is distributed object management [Manola92, Ozsu93] which generalizes the federated approach. The idea is to model heterogeneous databases at the appropriate level of granularity as objects in a distributed object space and to provide the capabilities and protocols for object interoperation. This involves the definition of a common ....

....1: MDBMS architecture. Following the distributed object management approach, each DBMS is accessed through a Local Application Interface (LAI) component which maps the common multidatabase language into the local language. The MDBMS component plays the role of a Distributed Object Manager (DOM) in [Manola et al., 1992] and offers multidatabase access using the multidatabase language. It typically provides transaction support and query processing. The MDBMS query processor relies on the multidatabase catalog which contains the import schemas and the schema mappings, all expressed in the common object model. For ....

F. Manola et al ., "Distributed Object management". Int. Journal of Intelligent and Cooperative Information Systems, 1(1), March 1992.

....management and business process re engineering. It is interesting to note that this accountability argument is partially in conflict with the vision of grand unifying system frameworks (switchboard architectures) For instance, distributed object systems such as DSOM of IBM [Lau94] DOM of GTE [Manola92], CORBA of OMG [OMG91] and OSF DCE DME [OSF93] on one hand provide ideal component ware frameworks, however, they also require a heavy investment to set up and to maintain a common, corporate wide system infrastructure. 4.2 Liberated Coordination A severe limitation of traditional information ....

Manola, Heiler, F., Georgakopoulos, D., Hornick, M. and Brodie, M., "Distributed Object Management", International Journal of Intelligent and Cooperative Information Systems 1, 1 (March 1992), Singapore: World Scientific, 5-42.

....can be high and hence the approach may have to be refined. We return to this issue later in section 6. The TSME system [16, 17] provides facilities for specifying workflow correctness requirements along with the workflow schemas using the Distributed Object Management (DOM) infrastructure [32]. Using the transaction specification language, dependencies can be specified between steps. Other than the state dependencies that specify a workflow structure, correctness dependencies can be specified to ensure one or more of the following: serializability, temporal correctness or cooperative ....

F. Manola, S. Heiler, D. Georgakopoulos, M. Hornick, and M. Brodie. Distributed Object Management. In Int. J.of Intelligent and Cooperative Information Systems 1, 1, March 1992. 18

....of a set of entities, object oriented programming is the natural candidate development style. We view the object oriented approach as the central ingredient facilitating the selective fusion of the various enabling technologies into a coherent architectural framework for distributed processing [4]. Here, we mention briefly the reasons that support this viewpoint. The next generation distributed database systems go far beyond the experiences gained in various other fields (such as software engineering, object oriented programming languages, object oriented database, and multidatabase ....

....a distributed system are seen at different levels of granularity and abstraction. Objects at a coarse granularity level may range from representing individual application abstractions to systems or nodes in a distributed environment; whereas fine grained objects may represent individual data items [4]. The main benefits of the use of object oriented technology in distributed information system design are that objects represent a natural framework for system modularization, accommodation of the construction of complex entities with shared subcomponents, and provide flexible module ....

F. Manola et al., "Distributed Object Management", Int'l Journal of Intelligent & Cooperative Information Systems, vol.1, no. 1, March 1992, pp. 5-42.

....the use of a semantically rich common object model to ease application integration, the development of standards to interoperate among objects, the use of object oriented transaction models, etc. Well known research projects in object oriented multidatabase systems are Pegasus [ADD91] DOMS [MHG92], Carnot [WSH93] Femus [ADS93] InterBase [BCD93] etc. A complete survey of object oriented multidatabase systems can be found in [BE95] The current paper focuses on IRO DB (Interoperable Relational and Object Oriented DataBases) Gar94] an ESPRIT project currently developed in Europe. The ....

Manola F., Heiler S., Georgakopoulos D., Hornick M., Brodie M., "Distributed Object Management", International Journal of Intelligent and Cooperative Information Systems, 1:1, March 1992, pp. 5-42.

....a distributed network to be treated as a commonly accessible collection of objects which can be combined in arbitrary ways to provide new information processing capabilities. These objects can range in granularity from entire systems to individual application objects (text strings, images, etc. [MANO92] describes general aspects of this technology in more detail. A number of proposals for generic Distributed Object Management System (DOMS) architectures have been developed, for example, the Common Object Request Broker Architecture (CORBA) defined by the OMG [OMG91] A typical feature of such ....

F. Manola, et. al., "Distributed Object Management", Intl. Journal of Intelligent and Cooperative Inf. Systems., 1(1), 1992, to appear.

.... specifications to construct a conventional transaction management mechanism) An approach for using ETM specifications to configure a run time transaction management mechanism that enforces various ETMs is discussed in [16,18] This is highly desirable in a Distributed Object Management System [28] which must support a variety of ETMs corresponding to advanced applications and workflows. Another important characteristic of our transaction specification framework is that it requires only standard quantifiers on finite transaction sets, and a single operator (transitive closure) We consider ....

F. Manola, S. Heiler, D. Georgakopoulos, M. Hornick and M. Brodie, Distributed Object Management, Int. Journal of Intelligent and Cooperative Inf. Systems, 1(1), March, 1992.

No context found.

F. Manola, S. Heiler, D. Georgakopoulos, M. Hornick, and M. Brodie, "Distributed Object Management", Intl. Journal of ICIS, 1(1), March 1992.

....can be determined by controlling their commitment order at the participating LDBSs. Although we address the problem of enforcing global serializability in the context of a multidatabase system, the solutions described in this paper can be applied to a Distributed Object Management System [8]. This paper is organized as follows. In Section II, we identify the difficulties in maintaining global serializability in MDBSs and review related work. The multidatabase model and our assumptions and requirements towards local database management systems are discussed in Section III. In Section ....

....of Houston. These activities include performance evaluation of the proposed ticket methods, and benchmarking of a prototype implementation. Current research conducted at GTE Laboratories, includes adaptation of ticket methods to provide consistency in a Distributed Object Management System (DOMS) [8] in which global transactions 14 IEEE TRANSACTIONS ON KNOWLEDGE AND DATA ENGINEERING, VOL. XX, NO. Y, DECEMBER 1993 access homogeneous objects that encapsulate autonomous concurrency control mechanisms, and or attached objects that represent data and functionality of autonomous and heterogeneous ....

F. Manola, S. Heiler, D. Georgakopoulos, M. Hornick, and M. Brodie, "Distributed object management", International Journal of Intelligent and Cooperative Information Systems, vol. 1, no. 1, March 1992.

No context found.

F. Manola, S. Heiler, D. Georgakopoulos, M. Hornick, and M. Brodie. Distributed Object Management. In A. K. Elmagarmid, editor, International Journal of Intelligent and Cooperative Information Systems, volume 1, pages 542, March 1992.

No context found.

Frank Manola, Sandra Heiler, Dimitrios Georgakopoulos, Mark Hornick, and Michael Brodie. Distributed Object Management. International Journal of Intelligent and Cooperative Information Systems, 1(1), June 1992.

No context found.

F. Manola, S. Heiler, D. Georgakopoulos, M. Hornick, and M. Brodie. Distributed Object Management. In Intl. J. of Intelligent and Cooperative Information Systenms 1, 1, 1992.

No context found.

F. Manola, S. Heiler, D. Georgakopoulos, M. Hornick, and M. Brodie, "Distributed Object Management," International Journal of Intelligent and Cooperative Information Systems, vol. 1, no. 1, June 1992.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC