I haven't checked in code yet, but here's what I've got working locally. 1) Wired the Modeling > Deploy "VDB" action (and DND VDB from Explorer to Teiid server) to our ExectionAdmin. The deployment appears be successful to a point where there are Jboss "Translator" checks and it fails because the VDB's don't have translator info in them. Hoping that when VDB work is complete, this will just work. 2) Created Modeling > "Create Data Source" and "Delete Data Source" actions (maybe temporary actions) which extract Connection Profile from selected source model, creates JNDI name and creates a Teiid Data Source if it doesn't exist. Verifies the mechanics of storing connection info in models and using it create Teiid DS artifacts when necessary. 3) On start-up, the ExecutionAdmin now has the smarts to search workspace for physical models and determine if models have matching JNDI names on the default Teiid server. This is a little tricky because we only get Data Source Names (JNDI) from Teiid API and can't get any properties to determine if the DS connection properties (i.e. type, URL, etc) match the Connection Profile info in a model. Based on our workspace logic to "clean-up" preview VDB artifacts on user events (close project, exit Designer, etc...) we are intending to NOT need to know anything more than the DS names. 4) Data Sources are now showing up in the Teiid server view, along with the available Translators. I'm currently providing a display name == model name instead of showing the actual generated JNDI because it'll be ugly and look something like: 8d9b22ab-f4ab-48c0-a6cd-b4d4501b81a5__TestProject_B.TestFolder.BooksSQL_B. User will see "BooksSQL_B" Rest of team: John Doyle is working on providing hooks to Preview Data using DTP Transient connection profiles and Eclipse's "Run" action paradigm. Result will be Select Relational Table, right-click "Preview Data". If info missing "i.e. need to select Connection Profile" or Translator, then user is query'd. Then results view is opened to view .... the results. Dan Florian is working on the Teiid artifact management framework to make the Preview Data work. Since querying data, is really executing queries on a deployed VDB, Designer is utilizing the "merge VDB" capabilities to deploy atomic VDBs (one model per VDB) and use the merge logic for "dependencies". There is also a fair amount of logic required to coordinate these steps and keep the Teiid deployed artifacts in sync with basic Eclipse workspace operations (Open/Close Project, Delete/Move Model, Save Model, etc..). In addition there are additional process/steps to perform when user changes Default Teiid server. John Verhaeg is working on the necessary changes/fixes to the VDB model and VDB Editor framework to be compatible with Teiid API, VDB schema. Barry