Message Ops is the Particle Horizon operator console and REST API for working with Solace durable queues and dead message queues (DMQs). These pages describe Message Ops 1.7.1. The portal groups patch releases under the 1.7 documentation line.
Use it to inspect queues, find messages, review metadata and authorized payloads, resubmit copies, move or delete selected messages, schedule operations and investigate outcomes through jobs and audit records. The web application and integrations use the same API and permission checks.
Start here
- Users: Sign In and Profile, then Queues and Messages.
- Application administrators: Application Setup, Users, Roles and Settings and Manage Environments.
- Infrastructure operators: Software Intake, Azure Installation and Configuration Reference.
- Integrators: Service Accounts and API Reference.
Concepts and architecture
An environment is a saved broker connection. A Message VPN selects a broker namespace; a queue selects the messages within it. Select an environment and VPN in the sidebar before browsing queues. An environment group lets administrators grant a role across several environments.
A message reference is a temporary handle to a browsed message, not a stored copy or reservation. An operation job tracks asynchronous work and item-level outcomes. A schedule submits an operation later using a saved template and the current execution owner’s permissions. An accepted request is not a successful broker operation.
| Component | Responsibility |
|---|---|
| Web | Browser interface, served by nginx; forwards API requests through the same public HTTPS origin. |
| API | Authentication, authorization, validation, configuration, durable requests and results. |
| Worker | Queue browsing, message mutations, schedules and inventory refresh. |
| PostgreSQL | Configuration, encrypted credentials, references, jobs, audit, sessions and the job queue. |
| Solace broker | Source of truth for messages; access is mediated by the API/Worker. |
Production uses Azure Container Apps and Azure Database for PostgreSQL Flexible Server 16. Applications pull approved prebuilt images from your Azure Container Registry. The API has internal ingress and Worker has no ingress. Your browser connects to Web; users do not receive the broker credentials.
Operational boundaries
A move publishes and waits for broker acknowledgement before deleting the source; it is not an atomic broker/database transaction. Timeouts, partial failures, cancellation and restore can require reconciliation before retrying. Search is bounded and messages can change while it runs. See Jobs and Reports and Upgrade and Recovery.
A valid installation license, scoped roles, queue policies and deployment safety controls govern access. Payload access and unmasked content require separate permissions. There is no supported production Docker Compose, Kubernetes or source-build installation in this release.