Apache OpenMeetings

Apache OpenMeetings is a Java‑centric, self‑hosted groupware platform that bundles video conferencing, instant messaging, whiteboard, and collaborative document editing into a single web‑based solution. Built on the Jakarta EE stack (Tomcat 11), it leverages Apache Maven for modular builds and relies on Java SE 17 at runtime. The core of its real‑time media handling is powered by the Kurento Media Server, exposing WebRTC capabilities through a REST/SOAP API. From a developer standpoint, OpenMeetings presents itself as an extensible web application with a clean separation between the front‑end (React/Thymeleaf, FullCalendar v6) and back‑end services.

Key Features

• Real‑time media – WebRTC video/audio streams, screen sharing, and recording (MP4 export).
• Collaboration tools – Shared whiteboard, live document editing via the Apache OpenOffice engine.
• Calendar & scheduling – Fullcalendar integration, automatic email invitations, and room management.
• Messaging – Private chat, contact lists, and group notifications.
• File management – Per‑room file explorer with private/public drives, LDAP/AD connectors for user provisioning.

Technical Stack

• Language & Runtime: Java 17, Jakarta EE 10.
• Application Server: Apache Tomcat 11 (embedded or external).
• Build Tool: Maven 3.8+ with multi‑module project structure (openmeetings-server, openmeetings-webapp, etc.).
• Database: Supports MySQL, PostgreSQL, MariaDB; schema migration via Flyway.
• Media: Kurento Media Server (Java API) for transcoding, recording, and WebRTC signaling.
• Front‑end: Thymeleaf templates + React components, FullCalendar v6 for scheduling UI.
• Messaging: Apache ActiveMQ or RabbitMQ can be plugged in for message brokering.

Core Capabilities & APIs

• REST/SOAP: Exposes endpoints for room creation, user management, file operations, and media control.
• Webhooks: Custom event callbacks for meeting start/end, recording completion, or chat messages.
• Plugin Architecture: OSGi‑style modules allow developers to inject custom services (e.g., a new chat backend or analytics collector).
• LDAP/AD Integration: Built‑in connectors for single sign‑on and group synchronization.
• VoIP/Asterisk Module: Bridges SIP trunks to the web‑based meeting rooms.

Deployment & Infrastructure

OpenMeetings can run on any JVM‑capable host. The distribution ships a pre‑built WAR for Tomcat or an executable tarball that bundles the server and a lightweight embedded Jetty/Tomcat instance. For production, it is recommended to:

• Use Docker: Official Dockerfiles are available; containers expose ports 8080 (HTTP) and 8443 (HTTPS).
• Scale horizontally: Each instance is stateless except for the database and media server; a shared storage (NFS, S3) is required for recordings.
• Use Kubernetes: Helm charts are under active development; operators can manage deployments, secrets, and persistent volumes.

Integration & Extensibility

Developers can extend OpenMeetings through:

• Custom modules: Add new REST endpoints or modify existing services by contributing to the Maven modules.
• WebSocket hooks: Intercept media streams or chat messages in real time.
• External authentication providers: OAuth2, SAML via the built‑in security framework.
• Third‑party APIs: Integrate with Microsoft Teams, Slack, or Zoom using the provided SDKs.

Developer Experience

• Documentation: The project offers a comprehensive website, API docs (Swagger), and detailed build guides.
• Community: Active mailing lists, JIRA tracker, and a Slack channel provide timely support.
• Testing: Unit tests use JUnit5; integration tests run against an embedded Tomcat.
• Licensing: Apache 2.0 guarantees no vendor lock‑in and full source freedom.

Use Cases

• Enterprise Intranet: Deploy a self‑hosted video platform with LDAP integration for internal meetings.
• Educational Platforms: Combine whiteboard and collaborative editing for remote classrooms.
• Remote Work Toolchains: Embed OpenMeetings into existing web portals, exposing APIs for custom dashboards.
• Telehealth: Use secure video rooms with recording compliance and patient file sharing.

Advantages

• Performance: Native Java implementation with efficient WebRTC handling via Kurento.
• Flexibility: Full control over data, compliance with GDPR or HIPAA through self‑hosting.
• Cost: Free under Apache 2.0; no subscription fees unlike SaaS alternatives.
• Extensibility: Modular architecture allows incremental feature addition without touching the core.

In summary, Apache OpenMeetings offers developers a robust, extensible platform for real‑time collaboration that can be tailored to specific organizational needs while remaining fully open source and self‑hosted.