OMG Homepage MDA Homepage CORBA Homepage MOF Homepage UML Homepage CWM Homepage XMI Homepage DDS Homepage OMG MARTE BPMN Homepage SysML Homepage banner
Follow us: RSS Feeds twitter LinkedIn



Catalog of OMG CORBA®/IIOP® Specifications

This page provides a catalog of OMG CORBA/IIOP specifications. Specifications are listed alphabetically.

Description of Catalog Entries

Click here for a description of each field for specifications catalogued below.

Understanding Terms Used
In order to understand the various terms used to identify an OMG specification as it moves through its editing cycles, consult the OMG Specifications Tutorial. 

 
Specification Name: Authorization Token Layer Acquisition Service (ATLAS)
Description: Describes the service needed to acquire authorization tokens to access a target system using the CSIv2 protocol. This design defines a single interface with which a client acquires an authorization token. This token may be pushed, using the CSIv2 protocol in order to gain access to a CORBA invocation on the target. This specification solves the problem of acquiring the privileges needed for a client to acquire a set of privileges the target will understand.
Latest / past specifications:

Current version: 1.0

Past versions: n/a
Contact Information:
Middleware and Related Services PTF    
Related OMG Specifications: CORBA/IIOP, Naming Service, Time Service, CSIv2
Related  Industry Standards: ISO 10646, RFC 2044

Specification Name: Common Object Request Broker Architecture (CORBA/IIOP)
Description: Specification of an architecture for middleware technology called an Object Request Broker that provides interopreability among clients and servers distributed over a heterogeneous environment.

Part 1 - CORBA Interfaces
Part 2 - CORBA Interoperability
Part 3 - CORBA Components
Keywords: asynchronous, callback, COM, context, CORBA, dynamic invocation, dynamic skeleton, fault tolerance, identity, IDL, implementation repository, interceptors, interface, interface repository, interoperability, language binding, messaging, object adapter, object reference, operation, OR, ORB, policy domains, policy object, portable interceptors, portable object adapter, QoS, router administration, routing, security, skeleton, static invocation, thread, ValueBase
Latest / past specifications:

Current version: 3.2

Past versions
Contact Information:
Middleware and Related Services PTF    
Related OMG Specifications: CORBA Component Model, Fault Tolerance, Security, UML Profile for CORBA


Specification Name: CORBA/e
Description: CORBA/e enables the implementation of middleware products that are open, mature, robust, and memory efficient (small footprint); offering high performance and deterministic real-time behavior - key requirements of most DRE systems. CORBA/e consolidates CORBA as the dominant standard for embedded middleware for the foreseeable future. It is further recognized that there are a wide range of capabilities in today’s embedded systems. A key tenet of CORBA/e is the support for "Profiling", a process by which specific subsets of these CORBA specifications can be defined by different end user communities and then standardized through the OMG. This will allow different end user communities to choose the appropriate subset of CORBA features required by any standards that are developed within that working group/task force and then for the vendors to produce highly optimized implementations based on the corresponding CORBA/e specification (Profile).
OMG Cross Reference: Specialized CORBA Specifications


Specification Name: Common Secure Interoperability (CSIv2)
Description: Addresses the requirements of CORBA security for interoperable authentication, delegation, and privileges.
Keywords: authentication, authorization, confidentiality, delegation, privilege, SAS, security, session, transport
Latest / past specifications:
Current version: Chapter 24 of CORBA/IIOP 3.0.3

Past version: Chapter 26 of CORBA/IIOP 2.6
Contact Information:
Middleware and Related Services PTF    
Related OMG Specifications: ATLAS, CORBA/IIOP, Time Service
Related  Industry Standards: IETF ID PKIXAC,  IETF RFC 2246,  IETF RFC 2459, IETF RFC 2743, X.501-93


Specification Name: CORBA Component Model (CCM)
Description: Specification of: a  Component Implementation Definition Language (CIDL);  the semantics of the CORBA Components Model (CCM); a Component Implementation Framework (CIF), which defines the programming model for constructing component implementations; a container programming model  describing how an Enterprise JavaBeans (EJB) component can be used by CORBA clients, including CORBA components; an architecture of the component container as seen by the container provider; how  Component implementations may be packaged and deployed; and definitions of the XML DTDs used by the CORBA Components.
Keywords: CCM, CIDL, CIF, Component Implementation Definition  Language, component model, Component Implementation Framework, container architecture, deployment, DTD, EJB, locality, packaging, policy, XML

Latest / past specifications:

Current version: 3.2

NOTE:  CCM is Part 3 of the CORBA 3.2 specification

Past versions: 3.0  
Related OMG Specifications: CORBA/IIOP, Deployment and Configuration, Lightweight CCM, Quality of Service for CCM, Streams for CCM, UML Profile for CCM, DDS for Lightweight CCM
Related  Industry Standards: Enterprise JavaBeans


Specification Name: CORBA Reflection (RFLEC) 
Description: This specification defines reflective operations for CORBA objects. Such operations provide a way for applications to obtain metadata describing an object’s interface directly from the object itself, rather than requiring the presence of a separate metadata service such as an Interface Repository. This specification provides a general approach to metadata discovery based on object narrowing, and it supports multiple metadata formats in an easily extensible manner.
Keywords: Dynamic Skeleton Interface (DSI), Interface Repository (IFR), introspection, metadata, reflection, reflection provider target object
Latest / past specifications:

Current version: 1.0

Past versions: n/a
Contact Information:
Middleware and Related Services PTF      
Related OMG Specifications: CORBA/IIOP, Deployment and Configuration, XMI
Related  Industry Standards:  


Specification Name: CORBA-FTAM/FTP Interworking (FTAM)
Description: Describes a single set of interfaces that will allow any Operations Support System (OSS) to perform its file management operations on underlying Network Elements regardless of the type of file management mechanism the underlying node is using.
Keywords: File Transfer Client; File Transfer Server; FTAM; FTP;  Network Element; OSS
Latest / past specifications:

Current version: 1.0

Past versions: n/a
Contact Information:
Telecommunications PSIG      
Related OMG Specifications: CORBA/IIOP, Property Service
Related  Industry Standards: IETF RFC 959; IETF RFC 1415


Specification Name: CORBA / TC Interworking and SCCP-Inter ORB Protocol (SCCP)
Description: This specification addresses the interworking between CORBA-based Intelligent Network (IN) applications and the same applications implemented using the existing IN infrastructure.
Keywords: GIOP, GSM, INAP, MAP, MTP,  network, remote operations, OSI ROS,  SCP, signal, SSP, SS7, switching, Transaction Capabilities, Transaction sub-layer
Latest / past specifications:

Current version: 1.0

Past versions: n/a
Contact Information:
Telecommunications PSIG  
Related OMG Specifications: CORBA/IIOP, Life Cycle Service, Naming Service
Related  Industry Standards: ITU-T Rec. Q.1400;ITU-T Rec. Q.1218; ITU-T Rec. Q.771-5; ITU-T Rec. X.680 through 683 (1994) | ISO/IEC 8824-1/2/3/4:1995; ETSI, ETS 300 374-1; ITU-T Rec. X.880 (1994); ITU-T Rec. Q.71


Specification Name: CORBA-WSDL/SOAP Interworking (C2WSDL)
Description: The overall goal of this specification is to provide a natural mapping from IDL to WSDL that is also suitable for a reverse mapping, from the mapped subset of WSDL back to IDL.
Keywords: constructed types, IDL source, interfaces, modules, object references, primitive types, service endpoints, SOAP bindings, value type
Latest / past specifications:

Current version: 1.2.1

Past versions
Related OMG Specifications: CORBA/IIOP, WSDL/SOAP-CORBA Interworking
Related  Industry Standards:   W3C SOAP 1.1, W3C WSDL 1.1, W3C XSD

Specification Name: DDS for Lightweight CCM (dds4ccm)
Description: The overall goal of this specification is to provide a natural mapping from IDL to WSDL that is also suitable for a reverse mapping, from the mapped subset of WSDL back to IDL.
Latest / past specifications:

Current version: 1.1

Past versions: 1.0


Specification Name: Deployment and Configuration of Component-based Distributed Applications (DEPL)
Description: This specification provides middleware mechanisms, methods, and notations for comprehensive automated deployment and configuration support for component-based distributed applications. In particular:
  • Methods and notations for the description of the network topologies, capabilities and properties of heterogeneous distributed processing environments (DPE) for distributed applications.
  • Methods and notations for the specification of configuration and deployment strategies for the deployment process of distributed applications.
  • Specification of interfaces, and middleware mechanisms and services necessary for automated support for the entire deployment process of distributed applications and their configuration management.
Keywords: actor, CCM, component data, component development, component management, configuration, deployment, distributed processing environments (DPE), execution data, execution management, IDL, MDA, metadata, package, PIM,  profile, PSM, target data, target management, XML Schema
Latest / past specifications:

Current version: 4.0

Past versions: n/a
Contact Information:
Middleware and Related Services PTF      
Related OMG Specifications: CORBA Component Model, UML, Property Service
Related  Industry Standards: "Open distributed processing - Reference Model: Overview" (ITU-T X.901); "Open distributed processing - Reference Model: Foundations" (ITU-T X.902); "Open distributed processing - Reference Model: Architecture" (ITU-T X.903); "Open distributed processing - Reference Model: Architectural semantics" (ITU-T X.904)    
Related  Industry Standards:


Specification Name: Fault Tolerance (FT)
Description: Provides robust support for applications that require a high level of reliability, including applications that require more reliability than can be provided by a single backup server. The standard requires that there shall be no single point of failure.
Keywords: causal order, fault management, fault tolerance, logging and recovery management, multicasting,  replication management, virtual synchrony
Latest / past specifications:
Current version:  1.0 Past version: Chapter 23 of CORBA/IIOP 3.0.3
Contact Information:
Real-time PTF  
Related OMG Specifications: CORBA/IIOP, Event Service,  Naming Service, Notification Service, Time Service
 
Specification Name: Firewall Traversal  (FIRE)
Description:

The overall goal of firewall traversal is to provide better accessibility to CORBA application servers when there is a firewall separating a client from a server.
Finalization Information:
Status: 1.0 finalization completing Working Document: 1.0 Beta 2 Specification
 
Specification Name: GIOP Compression (ZIOP)
Description: Defines a compression mechanism for the CORBA GIOP protocol. Such a mechanism provides a way for servers to publish objects that accept compressed requests and for clients to make compressed invocations. 
Latest / past specifications:

Current version: 1.0

Past versions: n/a

Specification Name: Interworking between CORBA and TMN Systems (TMN)
Description: Standard interfaces supporting the interworking between telecommunications management systems based on different  technologies.
Keywords: ASNI, caching, CMIP, CMIS, collections, gateways, OSI, SNMP, systems management, TMN
Latest / past specifications:

Current version: 1.0

Past versions: n/a
Contact Information:
Telecommunications PSIG  
Related OMG Specifications: CORBA/IIOP, Event Service, Life Cycle Service, Naming Service
Related  Industry Standards: X/Open guide number G207; ITU-T (CCITT) Recommendations: X.701, X.710, X.720,  X.721,  X.722,  X.734,  X.735,  X.208,  M.3010

Specification Name: Lightweight Fault Tolerance (LWFT)
Description: LWFT extends the Fault Tolerance CORBA specification with capabilities to support real-time applications by providing predictable recovery times and support for application-defined consistency management. Extensions to CORBA, FT CORBA are specified to enable interoperability between client ORBs and server ORBs in a fault tolerant enabled infrastructure.
Finalization Information:
Status: 1.0 finalization completing Working Document: 1.0 Beta 2 Specification
   


Specification Name: Online Upgrades (ONUP)
Description: Online Upgrades facilitates the safe and orderly upgrading of objects in a manner that is portable across systems and that is interoperable between systems. It is a first step towards a more general online upgrade capability. The specification aims to provide the ability to:
  • Upgrade individual objects, where such upgrades change the implementation of the object but do not change the external interfaces of the object
  • Pause an object, so that it can be upgraded, while allowing the object the opportunity to reach a safe and quiescent state
  • Transfer state from an instance of the old implementation of the object to an instance of the new implementation of the object, with provision for such state transfers where the representations of the old state and the new state are different
  • Resume service using an instance of the new implementation of the object without risk that messages will be lost, misordered or processed twice
  • Allow client objects to continue to use a server object while remaining unaware that the server has been upgraded, and allow server objects to continue to serve a middle-tier client object that also acts as a server while remaining unaware that the client has been upgraded
  • Address objects in such a way that a client can continue to use its existing object reference to access a server after it has been upgraded
  • Rollback an upgrade, prior to the instance of the new implementation becoming operational, if some part of the upgrade fails
  • Revert from an instance of the new implementation to an instance of the old implementation, if operation with the instance of the new implementation proves to be unsatisfactory
  • Perform upgrades on small collections of objects by means of allowing the application to commit and rollback the upgrades explicitly.
Keywords: commit, group management, implementation, object references, object state, portability, pause, pulled upgrade, pushed upgrade, resume, revert, rollback
Latest / past specifications:

Current version: 1.0

Past versions: n/a
Contact Information:
Middleware and Related Services PTF      
Related OMG Specifications: CORBA/IIOP, Real-time CORBA
OMG Cross Reference: Specialized CORBA Specifications
Related  Industry Standards:   


Specification Name: Quality of Service for CCM (QOSCCM)
Description: This specification not only supports the consideration of typical QoS properties like Latency, Throughput, Bandwidth, etc. but also very different kind of QoS properties (non-functional aspects) like reservation of computing power or constraining the frequency of event submission which can be useful for saving battery power of a mobile device. It also concentrates on the introduction of container extensibility mechanisms in order to allow realization of such properties, and does not deal directly with them, since the needs are very disparate and sometimes application specific.
Keywords: Container Portable Interceptor, Extension Container, Negotiation Interface and Flow Details, QoS Enabler 
Latest / past specifications:

Current version: 1.1

Past versions: n/a
Revision  Information:
 (NOTE: 1.1 is the first publication)
Related OMG Specifications: CORBA/IIOP, CORBA Component Model, MOF, UML Profile for QoS
Most recent IPR and Implementation questionnaire responses:  

Specification Name: Streams for CORBA Components
Description: The CORBA Component Model (CCM) reduces the complexity of the development of large distributed applications by defining a component-based programming paradigm where a special runtime construct, the container, manages and controls certain runtime services, like transactions and security. The communication of stream data will be performed by the container. For that reason, communicating containers need a common understanding about the transport of the data stream. This specification defines so called transport profiles that state rules of communication between containers. These profiles are completely independent of the actual data stream type (content) to be communicated.
Keywords: basic stream type, constructed stream type, stream implementation profile, stream port, stream sink, stream source, stream type meta information, value stream type, transport profile
Latest / past specifications:

Current version: n/a

Past versions: n/a
Finalization Information:
Status: 1.0 finalization completing Working Document: 1.0 Beta 2 Specification Contact:
Middleware and Related Services PTF
Related OMG Specifications: CORBA/IIOP, CORBA Component Model
Related  Industry Standards:    

Specification Name: UML Profile for CORBA® (CORP)
Description: Provides a standard means for expressing the semantics of CORBA IDL using UML notation and support for  expressing these semantics with UML tools.
OMG Cross Reference: UML Profile Specifications

Specification Name: UML Profile for CORBA® Component Model (CCMP)
Description: This specification provides a standard means for expressing CCM-based applications (PSMs) using UML notation and thus supporting all kinds of MDA model transformations such PIM-to-PSM and PSM-to-PSM. It is also designed to work with MOF repositories.
OMG Cross Reference: UML Profile Specifications

Specification Name: UML Profile for CORBA®  and CORBA® Component Model (CCCMP)
Description: This specification provides a UML 2 profile that facilitates representation of concepts needed to represent a pure CORBA or CORBA Components PSM. In conjunction with existing OMG specifications, namely UML 2, CORBA, CORBA Components and the MOF 2, this will result in significant benefits to the CORBA and CORBA Components user community and the users of MDA in general.  
NOTE This specification is intended to replace the existing UML Profile for CORBA and UML Profile for CCM specifications.
OMG Cross Reference: UML Profile Specifications

Specification Name: Wireless Access and Terminal Mobility in CORBA (WATM)
Description: Specifies an architecture and interfaces to support wireless access and terminal mobility in CORBA. Version 1.2 incorporates the specification of the GIOP Tunneling Protocol (GTP, which is an abstract, transport-independent protocol defining the message formats for transmitting GIOP messages and for establishing, releasing, and re-establishing the tunnel.
Keywords: access bridge, baseband, Big-Endian, channel, connection-oriented data services, discovery,  fragmentation, GIOP, GTP, handoff, home location agent, Host Controller Interface (HCI), L2CAP, messaging, mobile, multiplexing,  packet, protocol, terminal bridge,  transport, tunneling protocol, wireless
Latest / past specifications:

Current version: 1.2

Past versions
Contact Information:
  Telecommunications PSIG        
Related OMG Specifications: CORBA/IIOP
Related  Industry Standards: WAP-188-WAPGenFormats, Version 15-Aug-2000; WAP-201-WDP, Approved Version 19-February-2000; 
VIVIAN Consortium, GIOP Tunneling over Bluetooth L2CAP, http://www-nrc.nokia.com/Vivian/Public/Html/ltp.html.


Specification Name: WSDL/SOAP-CORBA Interworking  (WSDL2C)
Description: This specification defines a mapping between WSDL specifications, with a SOAP Binding, to a corresponding set of OMG IDL interface specifications. This specification is applicable to the domain of WSDL specifications which use only the constructs which result from the CORBA to WSDL-SOAP specification. This simplifies the mapping, and allows for mapping from a restricted WSDL-SOAP subset to CORBA IDL interfaces. This specification assumes that the CORBA to WSDL-SOAP mapping includes an identifier for the source OMG IDL file in the resulting WSDL specification. The WSDL to IDL translator can key off this identifier to revert to the original IDL specification, rather than performing the translation algorithm specified in this specification..
Keywords: constructed types, IDL source, interfaces, modules, object references, primitive types, service endpoints, SOAP bindings, value type
Latest / past specifications:

Current version: 1.0

Past versions: n/a
Contact Information:
Middleware and Related Services PTF        
Related OMG Specifications: CORBA/IIOP, CORBA-WSDL/SOAP Interworking, Java to IDL Mapping
Related  Industry Standards: W3C SOAP 1.1, W3C WSDL 1.1, W3C XSD

[ top ] [ Index Page ]

Edited by Linda on 10/01/2012

 

 
 
Copyright © 1997-2012 Object Management Group, Inc. All Rights Reserved. For questions about the WEBSITE , please contact webmaster@omg.org.
For TECHNICAL questions, please contact webtech@omg.org. This site is best viewed with Mozilla Firefox or Internet
Explorer versions 6.0 or later or any browser capable of viewing JavaScript and CSS 2.0. The site is using DHTML JavaScript Menu By Milonic.com.