Object Management Group. The Common Object Request Broker, July 1995.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....a CORBA based computation accesses the name service at least one: either to register itself via its IOR (Interoperable Object Reference) or to locate other CORBA objects IORs. One of the OMG s (Object Management Group) Common Object Services (COSes) is a name service standard, called CosNaming [9, 10]. The CosNaming specification takes into account the portability, interoperability and reusability aspects that are important concepts in open systems. However, these specifications do not include requirements of fault tolerance that are very important for distributed systems. One possible way to ....

Object Management Group. The Common Object Request Broker 2.0/IIOP Specification, Revision 2.0. OMG Document 96-08-04. Available from www.omg.org, 1996.

....three kinds of agents: ffl User Agents, which can be a textual or graphical user interface or any other application; ffl Wrappers for adapting the sources to conform to the object model of the mediator; ffl The Mediator itself. All communication between the agents will take place using CORBA [OMG95] and KQML [LF97] in combination [BDR97] KQML merely wraps expressions of arbitrary languages. Usually our agents have to answer queries to an object oriented database schema, so in we mostly use OQL (cf. CB97] as a content language of KQML. In this paper, we will concentrate on the mediator. ....

The Object Management Group. The Common Object Request Broker, Architecture and Specication, Revision 2.0, July 1995.

....servers (Figure 2) Over the past years, the use of workflow concepts and tools has been adverted for this purpose. A variety of commercial workflow systems are available, and workflow standards addressing the interoperability of proprietary workflow systems have been developed (WfMC, 1995; OMG, 1998c) At the same time, the relationship between workflow technology and business objects technology has emerged as an area of significant interest. Workflow components are deployed in a business component infrastructure which provides mechanisms for integrating business components that may be ....

....to process transactions across various data stores and other transactional resources in distributed environments is essential to a TBPS. A TBPS provides the (runtime) support for business objects representing resources which are to participate in diverse transaction protocols such as the CORBA OTS (OMG, 1998b) and its Java binding JTS, for example) the X Open DTP standard for distributed transaction processing (The Open Group, 1996) as well as advanced transaction protocols. Ideally, TBPS should also allow component managed access to data sources and resources as special cases. Some component ....

[Article contains additional citation context not shown here]

OMG (Object Management Group). The Common Object Request Broker, 1998 (a).

....few years which ensure interoperability among heterogeneous hardware platforms and software packages from different vendors. Object technology has been used to describe interfaces and interaction patterns for such distributed applications. The Common Object Request Broker Architecture (CORBA) OMG 95, Soley 95] is the most successful representative of an object based distributed computing infrastructure. There are a number of commercially available implementations of CORBA, which we refer to as object request brokers (ORBs 1 ) as a shorthand. 1. Throughout this report the term ORB will ....

Object Management Group. The Common Object Request Broker. Framingham, MA: Object Management Group, Inc., 1995.

....and new telecommunication services, the use of WWW technology only is, in most cases, not sufficient to realise complex services. Thus, Internet service architectures of general service providers require more powerful middleware technology. In most cases this middleware layer consists of CORBA [13] products as the core, WWW technology as the means for the initial access to services by the end user, and, potentially, Java applets as the glue between WWW and CORBA. The Java applets realise the end user system part of the CORBA based distributed application, which can be downloaded from the ....

....from one side to the other transparently to the applications. The integration of existing services with the CLUE requires the extension of the applications with interceptors, which usually means only linking and recompiling. The concept of interceptors is part of the OMG s CORBA specification [13] and is implemented in most commercial ORB products. In our prototype implementation of the CLUE, which we will describe in detail in the next section, we adopted the on line approach for obtaining the access control information and the interceptor approach for access control enforcement. The ....

Object Management Group (1998) The Common Object Request Broker, Architecture and Specification, Revision 2.2. available from http://www.omg.org/

....familiar types of Managed Objects will then generate requests for appropriate manager services and will be responsible for the appropriate assignment of SPs. 4 Related Work We restrict us to have a look at the well known industrial standards CORBA, OSF DCE and OSF DME respectively. OMG CORBA[14][3] The Object Management Group (OMG) has defined interfaces, which allows for construction of interoperable software according to the principles of object orientation. Service access and service implementation are strictly separated in order to reach distribution transparency. The specification ....

Object Management Group. The Common Object Request Broker. OMG Document Number 91.12.1, 1991.

....as efficient or as convenient as intra address space communication. Applications in the same address space cooperate by sharing data and objects. Applications in different address spaces can communicate only by copying or by using one of the new distributed object model systems such as CORBA [OMG95] Distributed objects may be an appropriate technology for some commercial Intranet systems, but CORBA systems require a large infrastructure. Small CORBA systems tend to occupy many tens of megabytes of size for small applications and hundreds of megabytes for large ones. In contract Java s ....

Object Management Group, The Common Object Request Broker, http:// www.omg.org/.

....during query processing. Mediators provide via wrappers [Wells 96, Wiederhold 95] access to information sources and only integrate those parts of the underlying information sources that are crucial for the user s query. Wrappers can be realized using distributed object managers such as CORBA [Object Management Group 95] or software agents [Genesereth Ketchpel 94, A. Ambite 97] Some current projects on mediation are TSIMMIS [Ullman 97] HERMES [Subrahmanian et al. Information Manifold [Levy et al. 96] SIMS [Arens et al. 96] AURORA [Yang et al. 97] DISCO [Tomasic et al. 95] Squirrel [Hull Zhou ....

....This also is a promising research area for data warehousing applications. Typically, warehouses contain static collections of materialized views of multiple data sources with dioeering security policies. Since our Multimedia Mediator (MMM) Biskup et al. 97a, Biskup et al. 97b] bases on CORBA [Object Management Group 95] there is a need to explore the applicability of our approaches in the CORBA communication environment. A nal area of research would be to re ne and formalize the model of role based query evaluation. ....

Object Management Group. (1995). The Common Object Request Broker, Architecture and Speciøcation, Revision 2.0. http://www.omg.org/corba/corbiiop. htm.

....are implemented as TINA COs or CO groups. TINA COs may have multiple interfaces, as opposed to CORBA objects, which have exactly one interface. We assume that each interface of a TINA CO will be implemented by a dedicated CORBA object, and thus each TINA CO will be realized as a set of CORBA objects (Kitson 1995). Since the functionality offered by a TINA CO is structured into interfaces according to the coherence of subfunctionalities, access control to a TINA CO can be applied at the granularity of TINA CO interfaces, which means that we only need to control access to whole CORBA objects. Furthermore, ....

Object Management Group (1995) The Common Object Request Broker, Architecture and Specification, Revision 2.0.

....as efficient or as convenient as intra address space communication. Applications in the same address space cooperate by sharing data and objects. Applications in different address spaces can communicate only by copying or by using one of the new distributed object model systems such as CORBA [OMG95] Distributed objects may be an appropriate technology for some commercial Intranet systems, but CORBA systems require a large infrastructure. Small CORBA systems tend to occupy many tens of megabytes of size for small applications and hundreds of megabytes for large ones. In contract Java s ....

Object Management Group, The Common Object Request Broker , http://www.omg.org/.

No context found.

Object Management Group. The Common Object Request Broker, July 1995.

No context found.

Object Management Group (1991). The Common Object Request Broker. OMG Document Number 91.12.1, 1991.

No context found.

Object Management Group (1995) The Common Object Request Broker, Architecture and Specification, Revision 2.0.

No context found.

Object Management Group (1995) The Common Object Request Broker, Architecture and Specification, Revision 2.0.

No context found.

CONCLUSION 15 Object Management Group (1995) The Common Object Request Broker, Architecture and Specification, Revision 2.0.

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