Teiid

Reason # 4 JBoss Microcontainer JBoss Microcontainer (MC) is at the core of JBoss AS and provides many essential services needed in developing any enterprise software application. Teiid utilizes MC, through several of its key sub-frameworks, to manage services and configuration/deployment artifacts. Service Framework: Prior releases of Teiid defined their own service framework(s). These legacy frameworks each had essential flaws - such as not being flexible in defining new services, not providing dependency management, or cumbersome/non-existent configuration management. Teiid in the 6.x releases used " google-guice " for dependency management between services with homegrown configuration management. The service lifecycle was explicitly managed through admin api methods. MC provides a POJO based service framework with IOC style dependency injection and full lifecycle management. A simple XML based configuration can your POJO based services along with their state and depende...

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...

Due to Eclipse packaging and project version dependencies, Teiid Designer 6.2 was not compatible with Eclipse 3.5 . This required updating to newer versions of Eclipse EMF and UML2 projects which resulted in some minor code changes. So this 6.3 release keeps Teiid Designer in sync with Eclipse. Note that the embedded version of Teiid remained the same within Designer, namely Teiid 6.2. Visit our download page for more details. Next our team will focus on a Teiid Designer 7.0 release which will provide tooling changes required to keep pace with Teiid 7.0 release. Barry LaFond Teiid Designer Project

A huge architectural change for the Teiid runtime is upcoming up in Teiid 7.0 release. Teiid is being integrated into a JCA container - JBossAS 5.1.0 GA . In this new platform you can expect all the data integration features of Teiid with power and flexibility of JBossAS . If you are thinking, Teiid is a relational data integration engine what does it has to do with a JEE container? This has little do with Web technologies. It is all about JCA ( Java Connector Architecture ) and the advanced development features of JBossAS . Let me explain each reason in a multi-part series of articles. Reason 1: Right ingredients. Integrate with modules designed by the domain experts. Even though Teiid is a data integration engine, the inner runtime workings of Teiid apart from the command parsing, relational planner and optimization engine are much more similar to any enterprise server application. Like security, user management, resource management, log management, caching, availability, scalability...

Just in time for Thanksgiving we're proud to announce Teiid 7.0 M1 is available. This milestone of 7.0 adds support for order by expressions, updatable temp tables, arbitrary quoted identifiers, and h2/hsql translators. Also JDBC DatabaseMetaData and the system tables have been revamped, and there's a host of other fixes. Before rushing off for the download, you should know Teiid 7.0 does not yet have a corresponding Teiid Designer release - it should be available within two weeks. You can of course still use Teiid 7.0 through the dynamic VDB feature. Existing VDBs from older Designer releases may still work with 7.0 - see TEIID-145 and TEIID-871 - for compatibility issues. Also while milestone 1 uses the same directory structure/installation procedure as Teiid 6.2, subsequent milestones will dramatically change the deployment procedure for Teiid. Be sure to vote/comment on remaining issues you want to see addressed in the 7.0 release.

The Teiid project team is excited to announce the release of version 6.2.0 - available for download here . The 6.2 release adds significant features in ease of use and enterprise readiness. It's never been easier to integrate your disparate enterprise data sources . Dynamic VDB An often requested feature, with a dynamic VDB data can be integrated between multiple sources very quickly without explicitly constructing a VDB using Teiid Designer . Check out a new example (dynamicvdb-portfolio) in the Teiid download, and read this blog for more info. Introducing Teiid Server In the prior releases of Teiid only an embedded deployment mode was offered. This meant the Teiid instance could not be shared among multiple clients. Now with Teiid server, you can run a standalone Teiid process and connect remotely over a highly scalable and configurable socket transport. Look here for installation instructions and how to connect to a server . Security Multiple facets of security were added t...