This topic describes the terms you may need to understand when you use OceanBase Migration Service (OMS) Community Edition.
| Classification | Term | Description |
| Control components | Ghana | The console of OMS Community Edition. |
| CM | The cluster management (CM) service of OMS. | |
| Supervisor | The proxy service of OMS. Supervisor receives and runs commands from the CM service. | |
| Incremental parsing components | Store | Pulls and parses database clogs, and stores the parsed clogs in a unified format. Downstream applications can consume incremental data of different databases from stores in a consistent manner. |
| LogProxy | The log proxy of OceanBase Database. | |
| Framework components | Connector | Supports full and incremental synchronization in OMS Community Edition V3.3.1-CE and later. |
| Light-Connector | Supports data synchronization projects in OMS Community Edition of versions earlier than V3.3.1-CE. | |
| JDBCWriter | Supports data migration projects in OMS Community Edition of versions earlier than V3.3.1-CE. | |
| Checker | Supports data validation in OMS Community Edition of all versions and full data migration in OMS of versions earlier than V3.3.1-CE. | |
| Others | MetaDB | As a service provided by OceanBase Database, MetaDB is deployed in containers, with a built-in proxy to support direct access to OceanBase Database. MetaDB stores metadata from OceanBase products such as OceanBase Cloud Platform (OCP), OceanBase Developer Center (ODC), and OMS. |
| InfluxDB | As a time series database service, InfluxDB is deployed in containers and stores the monitoring data of migration projects in OMS Community Edition. |