macOS - Software Lifecycle - Install DBeaver Community

What the DBeaver Installer does

This Automox Worklet™ automates the download and installation of DBeaver Community Edition on macOS endpoints. DBeaver is a free, open-source universal database management tool that supports virtually any database system including MySQL, PostgreSQL, SQLite, Oracle, SQL Server, MariaDB, and more.

The installation process downloads the DMG file from the Automox software cache, mounts the disk image, copies the application bundle to /Applications using cp with recursive and preserve flags, unmounts the volume, and removes the temporary files. This approach provides a clean installation without user interaction.

Why deploy DBeaver through Automox

Database administrators and developers frequently need to connect to multiple database systems during their work. DBeaver provides a single tool that handles connections to different database types, eliminating the need for multiple vendor-specific clients.

Deploying DBeaver through Automox standardizes the database tooling across your development and operations teams. This provides a consistent experience for SQL editing, data browsing, schema management, and database administration tasks regardless of the underlying database system.

The Automox software cache provides the latest version of DBeaver without requiring users to navigate download pages or handle DMG files manually. Silent installation supports deployment to endpoints regardless of user session state.

How DBeaver installation works

1. Evaluation phase: The Worklet checks if /Applications/DBeaver.app exists on the endpoint. If DBeaver is present, the endpoint is compliant and no action is needed. If DBeaver is missing, the evaluation triggers remediation.

2. Remediation phase: The script downloads the DBeaver DMG from api.automox.com, mounts the disk image silently, copies the DBeaver.app bundle to /Applications using cp -vrp, attempts to unmount the volume (with a retry after 5 seconds if busy), and removes the temporary DMG. A final check confirms the application exists.

DBeaver installation requirements

• macOS 10.15 (Catalina) or later

• Intel or Apple Silicon processor

• Network access to api.automox.com

• Automox agent version 1.42.22 or later

• Java Runtime Environment (bundled with DBeaver)

Expected state after DBeaver installation

After successful remediation, DBeaver Community appears at /Applications/DBeaver.app. Users can launch the application and immediately begin configuring database connections. DBeaver includes its own Java runtime, so no separate JDK installation is required.

You can verify the installation by checking for the application in /Applications or by reviewing the Worklet execution logs. The logs indicate whether DBeaver was freshly installed or already present on the endpoint.

How to validate install dbeaver community changes

1. Run this Worklet on a pilot macOS endpoint and review evaluation output for install dbeaver community.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as exit, else.

4. Validate remediation effects from script operations such as exit, else, curl, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for install dbeaver community. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as exit, else and remediation operations such as exit, else, curl. Use these indicators to verify that endpoint changes match intended policy outcomes.