Object Management Architecture (OMA)

The OMA is composed of objects, defined in terms of an object-oriented interface. The actual implementation of the component does not need to be object oriented. Interaction is done using object-oriented interfaces. Interfaces to non-object-oriented and legacy systems can be developed using object-oriented wrappers or adapters. Objects can be both clients (requesters of service) and servers responding to a request.

The OMA is composed of four component categories:

Object Request Broker (ORB) - It is a communication infrastructure that allows or facilitates object communication. The ORB relays object requests across distributed heterogeneous computing environments.
Object Services - Object services are low-level system type services (object persistence, transaction capabilities, security, etc..). This collection of system-oriented services allows application developers to construct applications without having to 'reinvent the wheel'. Support for object services must be supported by all ORB environments and platforms.
Common Facilities - Common facilities are high-level, application-oriented services ( such as mail and printing facilities). Unlike Object Services, support for common facilities is discretionary.
Application Objects - Application objects are developers programs, legacy systems and commercial software. These objects make use of the other three component categories.