[
https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-472:
---------------------------------------
Teiid VDB documentation states:
*Source Element*
A source is a named binding of a translator and connection source to a model.
* name
** The name of the source to use for this model. This can be any name you like, but will
typically be the same as the model name. Having a name different than the model name is
only useful in multi-source scenarios. In multi-source, the source names under a given
model must be unique. If you have the same source bound to multiple models it may have the
same name for each. An exception will be raised if the same source name is used for
different sources.
* translator-name
** The name or type of the Teiid Translator to use. Possible values include the built-in
types (ws, file, ldap, oracle, sqlserver, db2, derby, etc.) and translators defined in the
translators section.
* connection-jndi-name
** The JNDI name of this source's connection factory. There should be a corresponding
"-ds.xml" file that defines the connection factory in the JBoss AS. Check out
the deploying VDB dependencies section for info. You also need to deploy these connection
factories before you can deploy the VDB.
So a multi-source binding elements would look something like the following ?
<source translator-name="sqlserver"
connection-jndi-name="Customer_Accounts"
name="Customer_Accounts_1"/>
<source translator-name="mysql"
connection-jndi-name="Customer_Accounts"
name="Customer_Accounts_2"/>
<source translator-name="sqlserver"
connection-jndi-name="Customer_Accounts"
name="Customer_Accounts_3"/>
Support multi-source bindings
-----------------------------
Key: TEIIDDES-472
URL:
https://issues.jboss.org/browse/TEIIDDES-472
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.3
Reporter: John Verhaeg
Assignee: Barry LaFond
Fix For: 8.1
Probably need a framework somewhat similar to data roles, but at a model level, to manage
these bindings such that they can be validated against or selected when editing a
transformation.
The VDB and its editor then need to be modified to support capturing this information and
tying it to appropriate translators and JNDI names.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira