[
https://jira.jboss.org/jira/browse/TEIID-838?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-838.
--------------------------------
Resolution: Done
By copying the VDB into "deploy" directory of the runtime, the VDB will be
deployed automatically. User can also use Admin API, or JOPR based plugin to deploy a
VDB.
If the VDB has no validation errors it will be deployed. If the VDB has incomplete binding
associations, then it will deployed but will be in the "inactive" state. If
fully configured then it will be in the "active" state. The VDB MUST have
".vdb" extension.
All the above rules apply for the "dynamic" vdb also, except the file extension
MUST be "-vdb.xml".
It is possible to supply the connector bindings in the same VDB file using a
"-ds.xml" file, however this is not a requirement to have them inside the VDB.
If the same named VDB file overwrites the previous VDB file, then old VDB is replaced
with new one. No AUTOMATIC VERSION updates on the VDB as before are supported. If user
needs this functionality they need to supply the VDB in different file name with correct
version information.
Runtime discovery of VDBs
-------------------------
Key: TEIID-838
URL:
https://jira.jboss.org/jira/browse/TEIID-838
Project: Teiid
Issue Type: Sub-task
Components: Server
Affects Versions: 7.0
Reporter: Steve Jacobs
Assignee: Ramesh Reddy
Fix For: 7.0
Teiid server should be able to discover VDBs at runtime and automatically load them to
the extent possible - i.e. if the server is not configured to require entitlements and all
connectors are running, the server should load the VDB as a new version and allow queries.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira