# Install openliberty-microprofile4 with Homebrew Lightweight open framework for Java (Micro Profile 4). Version 26.0.0.5 via Homebrew; verified 2026-05-18. ## Install ```sh sudo av install brew:openliberty-microprofile4 ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install openliberty-microprofile4 ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:openliberty-microprofile4 - **Package manager:** Homebrew - **Package manager page:** - **Version:** 26.0.0.5 - **Source summary:** Lightweight open framework for Java (Micro Profile 4) - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** EPL-1.0 - **Source archive:** - **Last updated:** 2026-05-18T22:00:18Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - openliberty-microprofile4 (cli) - openliberty-microprofile4 (alias) ## Dependencies - openjdk ## Install behavior - Post-install hook: not defined - Caveats: The home of Open Liberty Micro Profile 4 is: $HOMEBREW_PREFIX/opt/openliberty-microprofile4/libexec - Bottle: available on all ## Freshness - Page generated: 2026-07-08 - Package-manager version: 26.0.0.5 - Package-manager updated: 2026-05-18 - Local data: ok - Upstream repository: https://openliberty.io - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage openliberty-microprofile4 is the Homebrew Open Liberty distribution aimed at Eclipse MicroProfile 4.0 workloads. It packages the same Open Liberty runtime lineage around the MicroProfile API set for cloud-native Java services rather than around the full Jakarta EE platform. ### Project history Open Liberty was open sourced by IBM in 2017 from Liberty, a runtime IBM started in 2012 for small footprint, modular configuration, and flexible Java deployment. The project has since acted as IBM's open implementation base for Jakarta EE and Eclipse MicroProfile and as the foundation for WebSphere Liberty. MicroProfile emerged to standardize APIs common in Java microservices. Open Liberty's `microProfile-4.0` feature combines Liberty support for Eclipse MicroProfile 4.0 for Cloud Native Java and includes capabilities such as Config 2.0, Fault Tolerance 3.0, Health 3.0, Metrics 3.0, OpenAPI 2.0, OpenTracing 2.0, and Rest Client 2.0. ### Adoption history Open Liberty has long used MicroProfile as part of its cloud-native positioning: enterprise Java teams could run a smaller set of service-oriented APIs without enabling a whole Jakarta EE platform. MicroProfile 4.0 aligned with Jakarta EE 8, which made it a useful bridge for organizations already standardized on Java EE 8 APIs while adopting microservice conventions. A MicroProfile-specific package is attractive to developers and operators who care about the exact API bundle available on disk. It separates the microservice profile from Open Liberty's Jakarta EE full-platform and Web Profile packages. ### How it is used In a Liberty server, the MicroProfile 4.0 convenience feature is enabled with `microProfile-4.0` in `server.xml`. That enables CDI, JAX-RS, JSON-B, JSON-P, Servlet, and the MicroProfile APIs used for externalized configuration, health endpoints, metrics, OpenAPI descriptions, fault tolerance, tracing, JWT, and REST clients. Developers use this runtime for local service development, CI checks, and deployment packaging where the application expects MicroProfile 4 behavior. The same Open Liberty ecosystem also offers Maven and Gradle plugins, container images, and IDE tooling for iterative dev mode. ### Why package nerds care This formula is notable because it tracks an API profile, not just an upstream release train. Package managers that expose Open Liberty by MicroProfile level let users install a runtime whose compatibility promise is visible in the package name. It also captures the enterprise Java split between platform profiles and microservice profiles: `openliberty-microprofile4` overlaps with Jakarta EE components but exists for a different operational story. ### Timeline - 2012: Liberty began inside IBM as a lightweight runtime. - 2017: IBM opened Liberty development as Open Liberty on GitHub. - 2021: MicroProfile 4.0 aligned with Jakarta EE 8 and was documented in Open Liberty tutorials and feature references. - Open Liberty documentation defines `microProfile-4.0` as the convenience feature for Eclipse MicroProfile 4.0 for Cloud Native Java. ### Related projects - Related technologies include Eclipse MicroProfile, Jakarta EE 8, Open Liberty's MicroProfile feature family, WebSphere Liberty, and the Open Liberty Maven and Gradle plugins. ### Sources - - - - - - ## Security Notes No matching local secret-handling manifest was found for openliberty-microprofile4. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ${wlp.user.dir}/servers/${wlp.server.name}/server.xml, ${wlp.user.dir}/servers/${wlp.server.name}/bootstrap.properties, ${wlp.user.dir}/servers/${wlp.server.name}/server.env, ${wlp.user.dir}/servers/${wlp.server.name}/jvm.options ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** openliberty-microprofile4 - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Related links - [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [openjdk](https://www.automicvault.com/pkg/brew/openjdk/) - Runtime dependency declared by Homebrew. - [openliberty-jakartaee8](https://www.automicvault.com/pkg/brew/openliberty-jakartaee8/) - Shares the same upstream homepage. - [openliberty-jakartaee9](https://www.automicvault.com/pkg/brew/openliberty-jakartaee9/) - Shares the same upstream homepage. - [openliberty-webprofile8](https://www.automicvault.com/pkg/brew/openliberty-webprofile8/) - Shares the same upstream homepage. - [openliberty-webprofile9](https://www.automicvault.com/pkg/brew/openliberty-webprofile9/) - Shares the same upstream homepage. - [roadrunner](https://www.automicvault.com/pkg/brew/roadrunner/) - Shares av.db curated category or tags: application-server, cli, cloud-infrastructure. - [passenger](https://www.automicvault.com/pkg/brew/passenger/) - Shares av.db curated category or tags: application-server, cli, cloud-infrastructure. - [tomcat](https://www.automicvault.com/pkg/brew/tomcat/) - Shares av.db curated category or tags: application-server, cli, cloud-infrastructure, java. - [tomee-plume](https://www.automicvault.com/pkg/brew/tomee-plume/) - Shares av.db curated category or tags: application-server, cli, cloud-infrastructure, java. ## Combined YAML source View the package source record on GitHub. [combined/openliberty-microprofile4.yml](https://github.com/automic-vault/db/blob/main/combined/openliberty-microprofile4.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph