Keywords: doc

Next: ORB Up: No Title Previous: The MICO Binder (CORBA

# Implementation Overview

This chapter gives you an overview of how MICO implements the CORBA 2 specification, the implementation components it consists of and how those components are being used.

A CORBA 2 implementation consists of the following logical components:

- the Object Request Broker (ORB) provides for object location and method invocation.
- the interface repository stores runtime type information.
- one or more object adapters which form the interface between object implementations and the ORB; at least the Basic Object Adapter (BOA) has to be provided, part of which is the implementation repository that stores information about how to activate object implementations.
- the IDL compiler generates client stubs, server skeletons and marshalling code from a CORBA IDL according to the supported language mappings.

Each of these logical components has to be mapped to one or more implementation components, which are described in the next sections.

- ORB
  - ORB Initialization
  - Obtaining Initial References
- Interface Repository
- BOA
  - BOA Initialization
  - BOA Daemon
  - Implementation Repository
    - Listing All Entries
    - Details For One Entry
    - Creating New Entries
    - Deleting Entries
    - Forcing Activation of an Implementation
    - Examples
  - Activation Modes
    - Activation Mode Shared
    - Activation Mode Persistent
    - Activation Mode Unshared
    - Activation Mode Per Method
    - Activation Mode Library
  - Making Objects Persistent
  - Migrating Objects
- POA
  - Architecture
  - Policies
  - Example
  - Using a Servant Manager
- IDL Compiler
- Compiler and Linker Wrappers
  - Examples