OEM Satellite
Ingest the hosts, databases and targets managed by Oracle Enterprise Manager into the CMDB — read-only, from the OEM Management Repository.
Oracle Enterprise Manager
OEM targets brought into the CMDB
- Hosts monitored by Oracle Enterprise Manager
- Database instances & pluggable databases (PDBs)
- Each target rolled into the CMDB as a managed asset
- Target metrics from the Management Repository
- On-premise and public-cloud OEM deployments, including OCI
- Read from the Management Repository — never the targets directly
Deploy alongside your OEM server
Run the OEM Satellite as a Docker container or install it on any supported Linux host — ideally within the same network as the OEM monitoring server, so all data stays inside the customer’s network boundary.
Docker image
Pull the public CMDB-360 OEM Satellite image from Docker Hub and run it on any host that already has Docker installed.
Universal Installer
Install on any Oracle Linux 8/9 or Ubuntu 20.04/22.04 host (ARM or x86_64) with the graphical Installer or the non-interactive AutoInstaller for scripted setups.
We recommend deploying the Satellite within the same IP space as the OEM monitoring server so sensitive data stays inside the customer’s network boundary — though it can run anywhere that can reach OEM and has outbound access to the Base Station. Minimum footprint: 1 vCPU, 4 GB RAM, 10 GB disk, and no inbound ports are required.
A simple two-step setup
When you deploy with the Installer or AutoInstaller, configuration is handled for you. Otherwise the on-instance tools walk you through two steps.
1 · Connect to the Base Station
Using the AdminTool, point the Satellite at your MSP’s CMDB-360 Base Station with its URL and the unique access token issued for the Satellite. These are held in an encrypted config.yml, then services are restarted.
2 · Connect to OEM
Run the ConfigTool and enter your OEM host URL (without the trailing /em) and a read-only OEM user and password. The Satellite queries the OEM Management Repository over the OEM REST API.
One prerequisite: enable repository SQL queries on the OEM server with a single property — emctl set property -name oracle.sysman.db.restfulapi.executesql.repository.query.enable -value true. The Satellite needs only read-only access, and you can disable any target type or the on-demand detail channel from the scheduler.
How the OEM Satellite protects data
The OEM Satellite runs inside the customer’s network and never touches OEM targets directly — it reads only from the OEM Management Repository over the REST API and sends non-sensitive rosters to the CMDB-360 Base Station. Detailed information is streamed on demand and only while a user is viewing a record, so nothing proprietary is stored outside the environment.