1. OMG Issue

QOSCCM11 — Dynamic configuration of components

  • Key: QOSCCM11-5
  • Legacy Issue Number: 12430
  • Status: closed  
  • Source: THALES ( Olivier Hachet)
  • Summary:

    Dynamic configuration of components :
    In the Scope section of QoS4CCM specification, the following is mentionned:
    "Dynamic configuration and re-configuration is also an essential point of
    distributed systems, because in order to adapt an application to a specific
    execution environment, one has to be aware that the QoS of the execution
    environment evolves during execution. There is a strong need to be able to
    make on-the-fly adaptation. That is why it is very important to provide an
    architecture, mechanisms, and monitoring concepts that allow dynamic
    adaptation of a running application, explicitly by an administrator, but
    also automatically. The specification addresses this problem domain in the
    context of the CORBA Component Model (CCM) [CCM]."

    For example reading/writing component's attributes or installing or
    uninstalling non-functional properties is necessary. This issue propose to
    address this topic which is not concretly resolved in the current

    To achieve this goal, a small evolution is needed. The existing CCM
    specification allows some application specific means like home user defined
    operations or 'configurator' setting but such mechanisms don't work without
    respectively using home finder or dynamic invocations. The necessity to
    develop applications that can dynamically reconfigure components and get
    knowledge of component configuration in a generic way, bring us to consider
    a new configuration mechanism at runtime to facilitate dynamic adaptation of
    running application.
    We propose to add configuration ability with access of special
    'configurator' implementation using component's home interface. We also
    propose to improve StandardConfigurator to get component configuration.This
    will allow to configure easily non-functional properties at run-time.

  • Reported: QOSCCM 1.0 — Wed, 7 May 2008 04:00 GMT
  • Disposition: Resolved — QOSCCM 1.1
  • Disposition Summary:

    If the component is created dynamically, or configured at runtime, the QoS value needs to be configured either via application specific means or by using configurator. Sections are added to support dynamic adaptation of a running application. This implies the modification of the CCM interface StandardConfigurator to be able to retrieve configuration values. HomeConfiguration interface is also modified to be able to retrieve a configurator.

  • Updated: Fri, 6 Mar 2015 20:54 GMT