[teiid-commits] teiid SVN: r3272 - branches/7.4.x/build/kits/jboss-container/teiid-examples/jca.

[teiid-commits at lists.jboss.org]

Author: van.halbert
Date: 2011-06-27 10:23:19 -0400 (Mon, 27 Jun 2011)
New Revision: 3272

Added:
   branches/7.4.x/build/kits/jboss-container/teiid-examples/jca/teiid-jdbc-template-ds.xml
Modified:
   branches/7.4.x/build/kits/jboss-container/teiid-examples/jca/readme.txt
Log:
Teiid-1658 added the Teiid JDBC template and updated the readme

Modified: branches/7.4.x/build/kits/jboss-container/teiid-examples/jca/readme.txt
===================================================================
--- branches/7.4.x/build/kits/jboss-container/teiid-examples/jca/readme.txt	2011-06-24 19:40:55 UTC (rev 3271)
+++ branches/7.4.x/build/kits/jboss-container/teiid-examples/jca/readme.txt	2011-06-27 14:23:19 UTC (rev 3272)
@@ -3,6 +3,28 @@
     LDAP
     SalesForce
     Web Services (for ws-security see Admin Guide)
+    ODBC
+    OLAP
+    Mondrian
+    Ingres
+    Intersystems Cache
+    Teiid JDBC template
 
-JDBC Users: Please see the examples in the "<jboss-as>/docs/examples/jca" directory for creating data source configuration 
-files for any type of relational database. These examples demonstrate creating both "local" and "xa" data sources.
+JDBC Users: Please see the examples in the "<jboss-as>/docs/examples/jca" directory for creating data source configuration files for any type of relational database. These examples demonstrate creating both "local" and "xa" data sources.
+
+
+---------
+
+When server applications wants to obtain their Teiid jdbc connection from the server connection pool, then Teiid needs to be deployed as a datasource.   
+
+We have provided a datasource -ds.xml template file to assist in the Teiid datasource deployment.   
+
+To deploy, using the template, do the following:
+
+1.	make a copy of the teiid-jdbc-template-ds.xml file
+2.	edit the file and replace "(vdb)" with the name of your vdb that you will be accessing, updating the user and password accordingly.
+3.	then copy the new -ds.xml file to the deploy directory of the profile you will be using.
+
+Your application should be able to obtain a jdbc connection from the connection pool using the JNDI name defined in the -ds.xml file.  
+By default, it called "TeiidDS".     If you have changed it, then your application will need to refer to it by the new name.
+

Added: branches/7.4.x/build/kits/jboss-container/teiid-examples/jca/teiid-jdbc-template-ds.xml
===================================================================
--- branches/7.4.x/build/kits/jboss-container/teiid-examples/jca/teiid-jdbc-template-ds.xml	                        (rev 0)
+++ branches/7.4.x/build/kits/jboss-container/teiid-examples/jca/teiid-jdbc-template-ds.xml	2011-06-27 14:23:19 UTC (rev 3272)
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!--                                                                       -->
+<!--  This is template that can be used to deploy Teiid                    -->
+<!--  as a datasource.                                                     -->
+<!-- ===================================================================== -->
+
+<!-- See http://www.jboss.org/community/wiki/Multiple1PC for information about local-tx-datasource -->
+<!-- ==================================================================== -->
+<!--  Datasource template for Teiid										-->
+<!--  To use:															-->
+<!--		-	Replace (vdb) in the url with your vdb name				-->
+<!--		-	Place the file in the deploy directory					-->
+<!-- ==================================================================== -->
+
+
+<datasources>
+  <local-tx-datasource>
+    <jndi-name>TeiidDS</jndi-name>
+    <connection-url>jdbc:teiid:(vdb)@mm://localhost:31000</connection-url>
+
+    <driver-class>org.teiid.jdbc.TeiidDriver</driver-class>
+    <user-name>user</user-name>
+    <password>user</password>
+
+      <metadata>
+         <type-mapping>jdbc</type-mapping>
+      </metadata>
+  </local-tx-datasource>
+
+</datasources>