Skip to main content

JCA Container Integration, Why Teiid needs it? - Part 1

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, reliability. How about the usage of current day's POJO based IOC containers, Management APIs and various tools associated with them? Over the past 7~8 years of MetaMatrix/Teiid development all of these features were home grown per customer need. However many of these features were not developed per industry standards since no relevant standards existed at the time nor did customers demand standards compliance. As a result Teiid has ended up with tens and thousands of lines to code to replicate what has become common container functionality. The Teiid Team claims to be experts in the data integration arena and leveraging an alternative runtime platform allows us to maintain a sharper focus.

Not coincidentally the JBoss AS 5 platform, built using the highly extensible and feature rich Microcontainer environment/framework, provides not only a JCA container, but a POJO based service framework with dependency injection, AOP, virtual file system, deployer and management frameworks which are ideal for developing robust software. JBoss AS is also a vibrant and exciting community ready to help with any issues. So, for Teiid we choose Microcontainer as the underlying framework to redesign Teiid's service components and JBoss AS host environment.

This will not only dramatically reduce the code foot print of Teiid, but will leverage a wealth of existing documentation and knowledge around utilizing JBoss AS, Microcontainer, and JCA. We still however did not talk in-depth about the JCA container part of it - that will be coming up in the next article.

Ramesh..

Comments

  1. Nice!
    Can you point me to MC pieces for a quick peek of what you've been doing? :-)

    -Ales

    ReplyDelete
  2. Thanks Ales.

    The work is still in progress, but you can see deployer work here

    http://anonsvn.jboss.org/repos/teiid/branches/JCA/jboss-integration/src/main/java/org/teiid/jboss/deployers/

    http://anonsvn.jboss.org/repos/teiid/branches/JCA/runtime/src/main/java/org/teiid/deployers/

    The Teiid services are also updated as MC pojo beans and that configuration can be seen here

    http://anonsvn.jboss.org/repos/teiid/branches/JCA/build/kit-jboss-container/

    Also, we have been using the management api & profile service to manage these artifacts.

    Ramesh..

    ReplyDelete

Post a Comment

Popular posts from this blog

Teiid Spring Boot 1.7.0 Released

Teiid Spring Boot version 1.7.0 to support Teiid 16.0 has been released. This release is mainly to support the Teiid's latest version.  In this release, the support for OpenAPI code generation based on VDB has been removed as there is no community interest and moreover it was at OpenAPI 2.0, and the industry has moved to 3.0 and beyond. There are no plans to further pursue this feature. VDB maven plugin was also removed, which was intended to be a replacement for the VDB importing feature was to be used when working on OpenShift, however, since it requires the Maven repository and does not completely represent the feature as defined on the WildFly based deployments this is also removed. You can still use the VDB import feature with Teiid Spring Boot, simply define the VDB with your "IMPORT DATABASE" statements and provide the additional files along with the main VDB file. During the start of the application, Teiid Spring Boot will load all the necessary DDL files for the ...

Teiid Spring Boot 1.5.0 Released

I am excited to announce that Teiid Spring Boot version 1.5.0 released today to the maven repository based on Teiid 14.0.0 release. If you have not used Teiid Spring Boot before, it is built on top Teiid Core libraries with developer simplification in mind. It simplifies the deployment model to a single VDB and provides you with executable binary rather than Server like WildFly where you need to deploy your VDBs. The release highlights are * Cassandra Data Source support * Materialization automation * Spring Boot version to 2.2.6 * Keystore/Truststore simplifications that work across the system * SOAP Data Source support * FTP Database Support * A Lot of changes to detect data sources based on their inclusion as dependencies and consistent naming schemes across both Teiid and Teiid Spring Boot. For a full list see this Take look at the various examples in Teiid Spring Boot and take it for test drive let me know if there are any issues or improvements you see. Ramesh...

Teiid Designer 8.3 Beta 1 milestone available

Teiid Designer 8.3 , targeted for release late next month, is focused on bug fixing and improving the integration of the JBoss server and Teiid runtime frameworks. We've released our first milestone, 8.3 Beta1 and it's available from our downloads page via zip archive or update site . Highlights include... Addressed problems re-deploying non-JDBC data sources TEIIDDES-1742 and TEIIDDES-1767   Improved Teiid Configuration tree behavior TEIIDDES-1730 - Add Create Teiid VDB Data Source action to VDB selection TEIIDDES-1835 - Add preview artifact management actions TEIIDDES-1847 - Filter preview artifacts in tree if not tied to current runtime user      TEIIDDES-1814 - Remove Teiid-specific server creation dialog Teiid Designer Team