Event Portal in Sovereign Home Cloud¶
Event Portal is part of Sovereign Home Cloud. It runs inside the control plane alongside the Cloud Console. Use it to design, document, and govern your event-driven architecture: application domains, schemas, events, applications, Event APIs, and Event API Products, with versions and lifecycle states.
Note: In Early Access, Event Portal connects to your event broker services only through an Event Management Agent you deploy yourself. See Pushing Configuration to Event Broker Services and Differences from Solace Cloud.
What You Can Do¶
| Area | What's available |
|---|---|
| Designer | Application domains, schemas, enumerations, events with topic addresses, applications, Event APIs, and Event API Products, with versions and lifecycle states |
| Designer graph | The graph of how applications and events connect, including across application domains |
| Event access requests | Requests to consume an event owned by another application domain, reviewed and approved in Designer |
| Catalog | Search across every object type |
| KPI Dashboard | Reuse and adoption metrics for the organization |
| Import and export | Application domains as JSON, to move designs between organizations or installations |
| AsyncAPI | Download an application version as AsyncAPI 2.5.0 or 3.0.0, in JSON or YAML |
| REST API | The Event Portal REST API, on your own hostname. See Using the REST API |
| Runtime | Configuration push to your event broker services and scans of what runs on them, through a self-managed Event Management Agent. See Pushing Configuration to Event Broker Services |
Getting Started walks through a first design using these features.
What Isn't Available in Early Access¶
- The cloud-managed Event Management Agent. Deploy the agent yourself instead; see Pushing Configuration to Event Broker Services.
- The AI Design Assistant.
- Micro-integrations.
- Email notifications, for example when someone requests access to an event.
Differences from Solace Cloud lists every difference and limitation.
How Event Portal Runs¶
Event Portal adds nothing to install or operate on its own. It uses the same data stores as the rest of the control plane:
| Dependency | What Event Portal uses it for |
|---|---|
| PostgreSQL | All Event Portal data, in the maas_ep_core database |
Encryption key (VAULT_LOCAL_KEY) |
Encrypting sensitive values in the database |
| OpenSearch | The Catalog search index, kept up to date by the control plane's search service |
| Event broker | Communication between Event Portal and the other control-plane services. Event Portal doesn't start without it. |
Event Portal doesn't use the object store. Its data is covered by the database and key backups in Backup and Restore.
Accessing Event Portal¶
Users reach Event Portal from the Cloud Console, on your console hostname. Each user belongs to an organization, and the Ops UI administrator creates organizations and their users: Sovereign Home Cloud sends no email, so there are no emailed invitations.
Every Event Portal feature package is on for an organization that has Event Portal. There is no billing, so there is nothing to purchase.