payara mit Homebrew installieren

Projektlinks

• Homepage
• Paketmanager-Seite

Befehle und Aliase

• letsencrypt.py

Projektgeschichte

Payara Server began in 2014, derived from GlassFish 4.1 after commercial support for GlassFish changed. It was developed as a compatible application server with continued fixes, features, and production support.

The project subsequently evolved with newer GlassFish generations and the Java EE-to-Jakarta EE transition. Payara Server now describes itself as an open-source middleware platform for Jakarta EE and MicroProfile applications deployed on premises, in cloud environments, or in hybrid environments.

Payara Micro complements the full server with a lightweight runtime for command-line, containerized, and embedded deployments, while Payara Server retains domain administration and full application-server workflows.

Adoptionsgeschichte

Payara Server was positioned as a supported, production-oriented successor for GlassFish users while retaining familiar Java EE administration and deployment concepts.

Its scope broadened with Jakarta EE, MicroProfile, cloud, container, and hybrid deployment support. The project is available as a community edition, while Payara also provides commercially supported enterprise distributions.

For application teams, its GlassFish lineage reduced migration friction; for operators, Payara added a maintained release and support model around the familiar domain-based server architecture.

Wie es verwendet wird

Developers deploy WAR and EAR applications to Payara Server, administer domains with `asadmin` or the administration console, and configure resources in the domain model.

Operators use `domain.xml` as the central domain configuration, with adjacent logging and environment configuration files. Clusters, instances, data sources, security settings, and application deployments are managed through the server's administration facilities.

Payara Micro is used when the same ecosystem is needed in a smaller command-line or container-oriented runtime.

Warum Paket-Nerds sich dafür interessieren

Payara is notable because it packages a large standards-driven Java runtime whose behavior is shaped by Jakarta EE compatibility, MicroProfile support, domain configuration, Maven artifacts, container images, and the GlassFish code lineage.

Its packaging history also captures the enterprise-Java transition from Java EE to Jakarta EE and the practical difference between an upstream reference implementation and a production-focused downstream distribution.

Zeitleiste

• 2014: Payara Server began as a project derived from GlassFish 4.1.
• 2015: The early Payara 4 line followed GlassFish-style versioning and compatibility.
• 2018: Payara Server 5 adopted the GlassFish 5 and Java EE 8 generation.
• Jakarta EE era: Payara evolved its platform around Jakarta EE, MicroProfile, containers, and cloud deployment.

Related projects

• Eclipse GlassFish is the upstream lineage and closest migration reference point.
• Jakarta EE and Eclipse MicroProfile define the principal application-platform APIs implemented by Payara.
• Payara Micro is the lightweight runtime in the broader Payara Platform.

Quellen

• https://docs.payara.fish/
• https://docs.payara.fish/community/docs/5.2021.8/README.html
• https://github.com/payara/Payara
• https://www.payara.fish/products/payara-server/