This topic describes the terms you may need to understand when you use OceanBase Migration Service (OMS) Community Edition.
| Category | Term | Description |
| Control components | Ghana | The console of OMS Community Edition. |
| CM | The cluster management (CM) service of OMS Community Edition. | |
| Supervisor | The proxy service of OMS Community Edition. Supervisor receives and runs commands from the CM service. | |
| Incremental parsing components | Store | Pulls database clogs, parses the 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 | Light-Connector | Supports data synchronization projects in OMS Community Edition of versions earlier than V3.3.1. |
| Incr-Sync | The incremental synchronization component. It requests incremental data from the incremental pulling component Store, filters the data based on the configured synchronization objects, and synchronizes the log records to the destination instance while ensuring the time series and consistency of transactions. | |
| Full-Import | The full import component. It migrates inventory data of tables in the source database and synchronizes incremental data. | |
| Full-Verification | The full verification component. It verifies all fields of row records in the migrated tables and generates a correction statement for inconsistent data. | |
| 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 Community Edition. |
| InfluxDB | As a time series database service, InfluxDB is deployed in containers and stores the monitoring data of migration projects in OMS Community Edition. |