Info |
---|
This page is under development |
Overview- The Component registry is a centralised database of registered components and services, which supports multiple management protocols and data models, such as SNMP and TR-069 with TR-181.
- The Component Registrar(CR) in RDK-B Architecture section gives an overview of CCSP Component Registrar, what it contains and illustrates how it is used by other internal components and client applications.
- The “Component Registrar” works like an internal name server.
- Allows other components to register the internal data model objects that they support and the DBuspath used to reach these objects
- Component Registrar provides this information , when other components need to determine what features are available in a particular software build and discover how to access these features
- Through these capabilities, this mechanism provides a flexible way to build a software system that can use any number of software components, allows components to discover what features are available and how to access these features
- Maintains the status and health of all registered components
...
- When a component needs to interact with an object it first asks Component Registrar for a bus address for the object.
- Component Registrar responds with the object address (if the object exists in this software build), hence the object can be accessed.
draw.io Diagram |
---|
diagramName | CCSPcr.drawio |
---|
revision | 1 |
---|
|
Gliffy Diagram |
---|
macroId | bf0b03e9-33e2-46be-93c2-8c24de84d238 |
---|
name | CCSPcr |
---|
pagePin | 2 |
---|
|
APIs
Some of the APIs supported by Component Registrar:
...
Example of registering PAM component
draw.io Diagram |
---|
|
Gliffy Diagram |
---|
macroId | e0f888b6-5000-4811-89ac-4b5b0844d219 |
---|
name | PandM_Comp_Reg_In CcspCR.drawio |
---|
pagePinrevision | 21 |
---|
|