3:05 p.m.
I have been developing an connector with version 6.2 and realized I
should be looking forward to version 7.0 so I download some files from
7.0 and started reading up on the changes coming in 7.
While reading the "Teiid 7.0 Installation Guide" I read the following:
Teiid 7.0 installation is entirely different from the previous
versions. Previously Teiid could
be installed as standalone server or embedded server. Starting with
this release Teiid will
need to be installed into a existing JBoss AS installation. Teiid will
be another component
inside the JBoss AS rather than have its own runtime environment. One
disadvantage of this
configuration is Teiid will not support the "embedded" mode in 7.0
version.
I was shocked to find that Teiid will no longer support a stand alone
server installation and must be installed into a JBoss AS environment.
Am I wrong?
--
Charles Simon
Principal Software Engineer
Select Business Solutions, Inc.
35 Nutmeg Drive
Trumbull, CT 06611
http://www.selectbs.com
mailto:charles.simon@selectbs.com
3:40 p.m.
On Mon, 2010-04-05 at 16:05 -0400, Charles Simon wrote:
I was shocked to find that Teiid will no longer support a stand alone
server installation and must be installed into a JBoss AS
environment.
Am I wrong?
You have read correct. Starting with 7.0.M3 (soon to be released) Teiid
needs to be installed in JBoss AS. We support the standalone Teiid
server using the JBoss AS as the host environment. For a end user, it
should be no different from before after the installation. You would
still be able to connect through JDBC as before to access your VDBS.
If you are developing the custom connector, the connectors will be
developed as JCA connectors. From Teiid standpoint the Connector API
itself modified slightly to fit into JCA, Teiid provides the rest of the
implementation for the JCA hooks. The packaging and configuration for
the connector is changed completely from before. Teiid will use RAR
files like any other JCA connector. Take look at the code for one of
supplied connectors in Teiid's svn for a sample.
There are numerous reasons for the shift, you can read them on Teiid's
blog.
Please let us know about your concerns, we will try to answer any
questions your may have.
Thanks.
Ramesh..
3:56 p.m.
Thanks for the fast reply. That leaves me with a question:
Should I be developing a JCA connector that gets added to Teiid or is
Teiid the JCA connector and I still need to be developing using the
Teiid connector API?
Ramesh Reddy wrote:
On Mon, 2010-04-05 at 16:05 -0400, Charles Simon wrote:
> I was shocked to find that Teiid will no longer support a stand alone
> server installation and must be installed into a JBoss AS
> environment.
> Am I wrong?
>
You have read correct. Starting with 7.0.M3 (soon to be released) Teiid
needs to be installed in JBoss AS. We support the standalone Teiid
server using the JBoss AS as the host environment. For a end user, it
should be no different from before after the installation. You would
still be able to connect through JDBC as before to access your VDBS.
If you are developing the custom connector, the connectors will be
developed as JCA connectors. From Teiid standpoint the Connector API
itself modified slightly to fit into JCA, Teiid provides the rest of the
implementation for the JCA hooks. The packaging and configuration for
the connector is changed completely from before. Teiid will use RAR
files like any other JCA connector. Take look at the code for one of
supplied connectors in Teiid's svn for a sample.
There are numerous reasons for the shift, you can read them on Teiid's
blog.
Please let us know about your concerns, we will try to answer any
questions your may have.
Thanks.
Ramesh..
--
Charles Simon
Principal Software Engineer
Select Business Solutions, Inc.
35 Nutmeg Drive
Trumbull, CT 06611
http://www.selectbs.com
mailto:charles.simon@selectbs.com
4:05 p.m.
On Mon, 2010-04-05 at 16:56 -0400, Charles Simon wrote:
Should I be developing a JCA connector that gets added to Teiid or is
Teiid the JCA connector and I still need to be developing using the
Teiid connector API?
Teiid Connector API extends the JCA API. The Teiid runtime uses the
Connector API to communicate with the Teiid Connector. But at the same
time
Teiid Connector *is a* JCA connector.
Here Teiid provides rest of the hooks *to be* a JCA Connector. It needs
to be JCA connector to live in a Container like JBoss AS, so that Teiid
can make use of data sources, connection pooling, security etc.
So, you can keep developing your connector as before. However, before
you can move your connector to 7.0 release you need to
1) update it with latest Connector API from 7.0. One major difference
here is how you define/read configuration properties.
2) it needs be packaged differently. This requires RAR file format.
3) deployed in the environment differently. It is exactly like defining
a Connection Factory/Data Source in JBoss AS.
We are also in process of developing a Eclipse plugin for connector
development, we will have a version of it before 7.0 final release.
Ramesh..
4:52 p.m.
I forgot to mention that my connector has to use the "Dynamic VDB" with
connector supplied Meta data. Will this this be any easier to setup? I
did notice the article that said the DVDB file must have a name
???-vdb.xml, but did not find any specifics on what that files should
contain. Is it the same format as the 6.2 .def file?
I ask this because I had a problem that I ran into while developing with
the 6.2 CDK. It did not support the ability to have connection specific
Meta data. It always used the Meta data the TranslationUtility was
created with to parse the SQL command and the TranslationUtility had to
be created before the ConnectorHost was created, which is needed to
create a connection.
I need to control the Meta data my connector gives to Teiid based on a
connection's userid and password. Is there a way to do that?
Ramesh Reddy wrote:
On Mon, 2010-04-05 at 16:56 -0400, Charles Simon wrote:
> Should I be developing a JCA connector that gets added to Teiid or is
> Teiid the JCA connector and I still need to be developing using the
> Teiid connector API?
>
Teiid Connector API extends the JCA API. The Teiid runtime uses the
Connector API to communicate with the Teiid Connector. But at the same
time
Teiid Connector *is a* JCA connector.
Here Teiid provides rest of the hooks *to be* a JCA Connector. It needs
to be JCA connector to live in a Container like JBoss AS, so that Teiid
can make use of data sources, connection pooling, security etc.
So, you can keep developing your connector as before. However, before
you can move your connector to 7.0 release you need to
1) update it with latest Connector API from 7.0. One major difference
here is how you define/read configuration properties.
2) it needs be packaged differently. This requires RAR file format.
3) deployed in the environment differently. It is exactly like defining
a Connection Factory/Data Source in JBoss AS.
We are also in process of developing a Eclipse plugin for connector
development, we will have a version of it before 7.0 final release.
Ramesh..
--
Charles Simon
Principal Software Engineer
Select Business Solutions, Inc.
35 Nutmeg Drive
Trumbull, CT 06611
http://www.selectbs.com
mailto:charles.simon@selectbs.com
8:43 a.m.
On Mon, 2010-04-05 at 17:52 -0400, Charles Simon wrote:
I forgot to mention that my connector has to use the "Dynamic VDB"
with
connector supplied Meta data. Will this this be any easier to
setup?
No more easier than before.
I
did notice the article that said the DVDB file must have a name
???-vdb.xml, but did not find any specifics on what that files should
contain. Is it the same format as the 6.2 .def file?
Yes, the file name must be in the form ???-vdb.xml, so that VDB deployer
can find the file by pattern matching the name and auto-load. The format
of the file itself is slightly modified. I have updated the examples
section, and wiki documents @ https://community.jboss.org/docs/DOC-15058
Also, in the Teiid's client jar, there is schema file called
"vdb-deployer.xsd" for this.
I ask this because I had a problem that I ran into while developing
with
the 6.2 CDK. It did not support the ability to have connection
specific
Meta data. It always used the Meta data the TranslationUtility was
created with to parse the SQL command and the TranslationUtility had
to
be created before the ConnectorHost was created, which is needed to
create a connection.
With 6.2 CDK, the only way to test is to build the VDB first
and then
test as you are describing above. The Dynamic-VDB does not need this
form of testing, as you can test directly with the Teiid engine.
I need to control the Meta data my connector gives to Teiid based on
a
connection's userid and password. Is there a way to do that?
There is way to
see who is logged in at the connector. Check out
"ExecutionContext" class in the connector API. If you are using
6.2 --> getUser()
7.0 --> getSubject()
to get to the logged in user. As you see in the first call Teiid will
not be able to tell you any group/role information, however 7.0 call
does. In 6.2 you would have to find alternative ways to supply the same.
(see credential map or trusted payload in the reference guide, however
these are non existent in 7.0)
Ramesh..
5148
days inactive
5149
days old
5 comments
2 participants
participants (2)
-
Charles Simon -
Ramesh Reddy