Skip to main content

Jakarta Connectors

Jakarta Connectors is a Jakarta EE specification that defines a standard architecture and contract model for integrating Jakarta EE application servers with enterprise information systems through resource adapters (enterprise integration).

  • Standard architecture for connecting Jakarta EE application servers to enterprise information systems (enterprise integration).
  • Resource adapter contract model between application servers and external systems such as Emergency Response Plan (ERP), Customer Relationship Management (CRM), and legacy platforms (application integration).
  • Support for connection management, transaction management, and security contexts between containers and resource adapters (application infrastructure).
  • Stateful Packet Inspection (SPI) for building pluggable resource adapters that can be deployed and managed within Jakarta EE containers (platform extensibility).
  • Defined interaction patterns for inbound and outbound communication between Jakarta EE components and external systems (integration patterns).

More About Jakarta Connectors

Jakarta Connectors is a specification within the Jakarta EE platform that defines a standard way for Jakarta EE application servers to connect to enterprise information systems (EIS), such as ERP packages, mainframe systems, messaging systems, and other external platforms (enterprise integration). It addresses the integration problem space where Java-based enterprise applications need consistent access to heterogeneous back-end systems under a unified contract.

The specification introduces the concept of a resource adapter, which is a system-level software driver that integrates an EIS into a Jakarta EE environment (application integration). A resource adapter implements a defined set of contracts with the application server, including connection management, transaction management, and security, so that Jakarta EE components can interact with external systems in a container-managed way without embedding vendor-specific integration logic.

Through its system contracts, Jakarta Connectors standardizes how application servers manage connection pooling, association, and lifecycle for connections to external systems (application infrastructure). It specifies how distributed transactions can span both Jakarta EE components and EIS resources using container-managed transaction demarcation (transaction management). It also covers propagation of security identities and credentials between the application server and the resource adapter (identity and access), enabling consistent authentication and authorization semantics across integrated systems.

Jakarta Connectors defines a service provider interface (SPI) that vendors or integrators use to implement pluggable resource adapters that can be deployed into compliant Jakarta EE servers (platform extensibility). These resource adapters are packaged, configured, and managed similarly to other Jakarta EE deployment artifacts, which allows administrators to treat connectivity to different EIS platforms in a uniform way. The SPI also covers interaction patterns for outbound access, where Jakarta EE components call out to an EIS, and inbound access, where an EIS can initiate interactions into the Jakarta EE environment through message inflow (integration patterns).

In enterprise environments, Jakarta Connectors is used to integrate line-of-business systems with Jakarta EE applications running in application servers from multiple vendors (enterprise application platforms). It supports scenarios such as transactional updates across databases and legacy systems, secure access to mainframe transaction monitors, and message-driven processing of events originating in external systems. By codifying integration contracts at the platform level, the specification enables more portable resource adapters and reduces the need for custom, server-specific integration code.

Within a technical taxonomy, Jakarta Connectors is categorized as an enterprise integration specification for application server to back-end system connectivity, focusing on resource adapter architecture, system-level contracts for transactions, security, and connection management, and standardized deployment and management of integration components in Jakarta EE environments.