Teiid

The Teiid project is being integrated to run inside a JCA container. In earlier posts I gave two compelling reasons for the move. Reason # 1 Reason #2 Today we examine #3 Reason 3: Security Security is vitally important for any enterprise application. This is especially true for Teiid as there are typically strict organizational rules governing access to data sources. At a high level Teiid allows for a customizable user authentication/authorization system. There are pre-defined system administrative roles and data authorization roles can be defined for each virtual database (a.k.a. entitlements, or data roles) to govern access at a granular level. Teiid 6.2 (and earlier) Security Features Teiid 6.2 provided a Membership API to define customizable security domains from which to obtain authentication and authorization information. Teiid shipped with implementations of LDAP and File based membership domains. Security at the connector level was supported, static credentials, client pass

Continuing from our earlier discussion " JCA Container Integration, Why Teiid needs it? Part 1 ", here we will discuss the next reason. Reason 2: JCA API What is the JCA API? From the spec site ( J2EE Connector architecture ): JCA defines a standard architecture for connecting the J2EE platform to heterogeneous EIS systems. Examples of EIS systems include ERP, mainframe transaction processing, database systems, and legacy applications not written in the Java programming language. By defining a a set of scalable, secure, and transactional mechanisms, the J2EE Connector architecture enables the integration of EISs with application servers and enterprise applications. What is a Teiid Connector? Teiid connectors also connect to heterogeneous EIS systems, but they implement a Teiid specific Connector API to: Consume commands from the Teiid engine in SQL command object form and translate them into native commands to query and update enterprise sources. Deliver resultant data in a t