Object Management Group. Object Management Architecture Guide. revision 3.0, OMG Technical Committee Document ab/97-05-05, June 1995.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....common technology base for objectoriented distributed systems. The objective of the OMG is to promote portability, reusability, and interoperability of software through the use of object oriented technologies. The OMG pursues its goals by providing a common architecture and a set of specifications [OMG92]. The OMG started its work by specifying the Object Management Architecture (OMA) to provide an overall framework for its activities and further specifications [OMG92] The OMA defines a reference model that divides the problem space of distributed systems into four distinct sub spaces, as ....

....the use of object oriented technologies. The OMG pursues its goals by providing a common architecture and a set of specifications [OMG92] The OMG started its work by specifying the Object Management Architecture (OMA) to provide an overall framework for its activities and further specifications [OMG92]. The OMA defines a reference model that divides the problem space of distributed systems into four distinct sub spaces, as illustrated in Figure 1. Two of them, the application objects and the CORBAfacilities, are concerned with application level issues, while the other two, the object request ....

[Article contains additional citation context not shown here]

Object Management Group, Soley, R.M. (Ed.), Object Management Architecture Guide, OMG TC Document 92.11.1, Revision 2.0, John Wiley & Sons, New York, USA, 1992.

....if the value of the investment in the portfolio is more than 10 of the total value of all investments. To date there exist di#erent approaches, frameworks and platforms to develop agents on di#erent levels of abstraction. For example, web services, the common object request broker architecture [21,22] and the parallel virtual machine [11] cater for the infrastructure of distributed systems, in general, and multiagent systems, in particular. Such systems tackle low level issues of distributed systems and form the technical basis of high level conceptual frameworks for designing and developing ....

Object Management Group. Object Management Architecture Guide. Wiley, 1993.

....resource manager and worklist manager may be built using X2TS. Consequently, the use of the transactional event action service provides the glue between the execution of activities and the invoked CORBA objects, and the workflow engine that controls both levels. We follow the principle of the OMA [27], that Object Services are the basic building blocks for distributed object applications. They can be used to construct higher level facilities and object frameworks. In that way, a CORBA workflow man agement facility [32] can benefit from the proposed extended transaction coordination ....

Object Management Group (OMG). Object Management Architecture Guide. 3rd Edit., R.M. Soley (ed.), John Wiley&Sons, inc., New York, 13. June 1995.

....Reliable Event Service. Section 5 discusses implementation issues and presents some performance measures. Section 6 compares our approach with related work and Section 7 summarizes the main contribution of the paper. 2 CORBA: Background 2. 1 The OMA The Object Management Architecture (OMA) [7] is a framework defined by the Object Management Group (OMG) which provides a conceptual infrastructure for building inter operable, reusable, portable 1 software components based on open, standard object oriented interfaces. Object Services Domain Int. Appl. Int. Common Fac. Naming, ....

Object Management Group. Object Management Architecture Guide. John Wiley & Sons, Inc, 3rd edition, June 1995.

....allows applications to interoperate across heterogeneous networks and systems. These interoperable applications are based on distributed objects, that comply with interface and protocol specifications that define the Object Management Architecture (OMA) The Object Management Architecture Guide [4] (in its first edition) was the first deliverable of the OMG, and set the framework within which the OMG would develop its specifications. 8 4.1 The OMA reference model There are four logical components in the OMA reference model. Object Request Broker The Object Request Broker (ORB) is the ....

Object Management Group. Object Management Architecture Guide, Revision 2.0, 1992. OMG TC Document 92.11.1.

....intensionally, a structured model of components, connectors, and component schemes has been introduced [Tai 96b] which is briefly summarized in Section 2. In this paper, we focus on connector abstractions for 1 CORBA object relations. Regarding the OMG s Object Management Architecture (OMA) OMG 92] and Common Object Service Specifications (COSS) OMG 95b] we introduce connectors for modeling asynchronous object communication, event notification as described in the event service specification [OMG 95c] and for (complex) structural relationships as described in the relationship service ....

Object Management Group. Object Management Architecture Guide, Rev 2.0, OMG TC Doc Number 92.11.1, 1992.

....rules. 5.1.3 Summary The kernel data model (XKOM) minus the rule specification component, is a conventional message passing object model. Also, it is a basic object model similar to the one adapted by the Object Management Group (OMG) for the specification of the Object Request Broker (ORB) [OBJ92, COR92]) In other words, it has a small number of basic concepts: objects, classes, associations (aggregation and generalization) methods, and rules. What it does not have is a set of semantically rich constructs found in some of the existing data models (e.g. see survey in [HUL87] constraints ....

Object Management Group, Object Management Architecture Guide, John Wiley & Son, Inc., New York, September 1992.

....3.2.3 Summary The kernel data model (XKOM) minus the rule specification component, is a conventional message passing object model. Also, it is a basic object model similar to the one adapted by the Object Management Group (OMG) for the specification of the Object Request Broker (ORB) [OBJ92a, OBJ92b]) The addition of the rule specification component in XKOM allows the semantics of new class types, constraint types and association types to be explicitly defined by parameterized rules and be incorporated into the application schema by means of the extensibility mechanisms. 3.3 Meta Model ....

Object Management Group, Object Management Architecture Guide, John Wiley & Son, Inc., New York, September 1992.

....Tel. 44 0171 477 8918, msch cs.city.ac.uk 2 Institut fur Informatik, Universitat Leipzig, gw inf.fu berlin.de 1 To date there exist different approaches, frameworks and platforms to develop agents on different levels of abstraction. For example, the common object request broker architecture [32, 33] and the parallel virtual machine [15] cater for the infrastructure of distributed systems, in general, and multi agent system, in particular. Such systems tackle low level issues of distributed systems and form the technical basis of high level conceptual frameworks for designing and developing ....

Object Management Group. Object Management Architecture Guide. Wiley, 1993.

....process for each RFP. Currently there are three active task forces: Object Services, Revised Object Request Broker, and Object Model. 3.3.1 The OMG Architecture The OMG Architecture shown in Figure 2 is called the Object Management Architecture OMA . The initial version is described in [19], a later version in [20] An application which is OMA compliant consists of a set of interworking objects that interact via the Object Request Broker. The Object Request Broker component of the Object Management Architecture is the kernel of the standard. It provides an infrastructure allowing ....

Object Management Group, OMG 492 Old Connecticut Path, Framingham, MA 01701 USA. Object Management Architecture Guide, September 1990.

....the run time. Client and server objects communicate with messages. For sending and receiving messages the objects do not have to take up with communication details. Rather they use an abstraction layer the object request broker (ORB) ORB is the integral part of a distributed object model [1, 2, 17]. It is responsible for handling the details of the communication (Figure 1) marshalling the client s request, locating the appropriate target object, transferring the request, receiving the message request, demultiplexing, demarshalling and dispatching the request, performing ....

....messages: Call, Ping, DgcAck, ReturnData, HttpReturn and PingAck. 2.2. Common Object Request Broker Architecture (CORBA) General and Internet Inter ORB Protocol (GIOP IIOP) CORBA (Common Object Request Broker Architecture) is based on the Object Management Architecture and the Core Object Model [17]. The CORBA specification covers the following main parts: the object request broker (ORB) object services (CORBAservices) common facilities (CORBAfacilities) domain facilities and application objects. In this article we will focus on the CORBA object request broker only. CORBA is independent ....

Object Management Group, Richard Mark Soley, Christopher M. Stone, Object Management Architecture Guide, John Wiley & Sons, Inc., 1995

....the run time. Client and server objects communicate with messages. For sending and receiving messages the objects do not have to take up with communication details. Rather they use an abstraction layer the object request broker (ORB) ORB is the integral part of a distributed object model [1, 2, 17]. ORB is responsible for handling the details of the communication (Figure 1) marshalling the client s request, locating the appropriate target object, transferring the request, receiving the message request, demultiplexing, demarshalling and dispatching the request, performing ....

....RMI transport protocol defines six messages: Call, Ping, DgcAck, ReturnData, HttpReturn and . PingAck. 2.3. Common Object Request Broker Architecture (CORBA) CORBA (Common Object Request Broker Architecture) is based on the Object Management Architecture and the Core Object Model [17]. The CORBA specification covers the following main parts: Object request broker (ORB) is the integral component of the architecture. It hides all the details of the communication between the two objects the client and the server object. ORB is the object bus. Object services ....

Object Management Group, Richard Mark Soley, Christopher M. Stone, Object Management Architecture Guide, John Wiley & Sons, Inc., 1995

....Management Group (OMG) a consortium created by software vendors, developers and end users to promote object technology for the development of distributed computing systems. The OMG has proposed a set of standards for distributed object computing, which compose the Object Management Architecture [105]. The OMA is a framework of standards and concepts for open systems, centred in the Object Request Broker (ORB) In this architecture, methods of remote objects can be invoked transparently in a distributed and heterogeneous environment using the services provided by an ORB. 22 The Common Object ....

Object Management Group "The Object Management Architecture Guide", OMG Technical Document 92-11-1, September 1992.

....the OMG, a consortium created by software vendors, developers and end users to promote object technology for the development of distributed computing systems. The OMG has proposed a set of standards for distributed object computing, which are described by the Object Management Architecture (OMA) [3]. The OMA is a framework of standards and concepts for open systems, centred around the concept of the Object Request Broker (ORB) In this architecture, methods of remote objects can be invoked transparently in a distributed and heterogeneous environment through the ORB. The OMG also specifies a ....

Object Management Group "The Object Management Architecture Guide", OMG Technical Document 92-11-1, September 1992.

.... offers communication, naming and security services, COMANDOS [Cahill et al. 1994] defines and implements a virtual machine that hides distribution to the programmer, whileANSAware [APM, 1989] provides support for federated client server applications and distributed objects in a similar manner to Object Management Group s Common Object Request Broker Architecture (OMG CORBA) OMG, 1992a] OMG, 1992b] Mowbray and Brando, 1993] Existing middleware is mainly a collection of useful services, but most often not a very coherent collection. This is due essentially to the fact that existing middleware was developed ....

OBJECT MANAGEMENT GROUP, "Object Management Architecture Guide," num. Document 92.11.1, OMG Inc., Framingham, MA, Nov. 1992. OBJECT MANAGEMENT GROUP, "Common Object Request Borker: Architecture and Specification," num. Document 92.12.1, OMG Inc., Framingham, MA, Dec. 1992.

....a simple request reply model. The ROS model provides a number of constructs to describe the interactions between distributed objects, using the information object class construct of the Abstract Syntax Notation One (ASN.1) 3] On the other hand, the Common Object Request Broker Architecture [4] (CORBA) defined by the Object Management Group (OMG) consortium is rapidly becoming the technology of choice for building distributed applications in many areas of information technology using, as a key component, the Object Request Broker (ORB) to enable the transparent communications between ....

Object Management Group , "Object Management Architecture Guide," Revision 3.0, 1995.

.... The Common Object Request Broker Architecture (CORBA) CORBA1] defined by the Object Management group (OMG) consortium is rapidly becoming the technology of choice for building distributed applications in many areas of information technology using, as a key component of its architecture [OMA] , the Object Request Broker (ORB) to enable the transparent communications between application objects. CORBA provides an architecture that enables the telecommunication services and computer application components to work together despite the diversity of programming languages, operating ....

Object Management Group , "Object Management Architecture Guide," Revision 3.0, 1995.

No context found.

Object Management Group. Object Management Architecture Guide. revision 3.0, OMG Technical Committee Document ab/97-05-05, June 1995.

No context found.

Object Management Group, Object Management Architecture Guide, revision 3.0, OMG Technical Committee Document ab/97-05-05, June 1995 31

No context found.

Object Management Group, Object Management Architecture Guide, OMG TC Document 90-9-1, Revision 1.0, Object Management Group, Inc., Framingham MA, 1990.

No context found.

Object Management Group. Object Management Architecture Guide. New York:John Wiley, 1992.

No context found.

Object Management Group, Object Management Architecture Guide , ed. R.M. Soley, OMG Document Number 92.11.1, Revision 2.0 Second Edition, 1992

No context found.

Object Management Group. Object Management Architecture Guide, second edition, September 1992. OMG TC Document 92.11.1.

No context found.

Object Management Group. September 1992, Object Management Architecture Guide, Framingham, MA.

No context found.

Object Management Group, Richard Mark Soley, Christopher M. Stone, Object Management Architecture Guide, John Wiley & Sons, Inc., 1995

First 50 documents  Next 50

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