Teiid SOAP interface?

[serff]

I've walked through the basic getting started guide, so I think I understand how Teiid exposes an interface via JDBC, but I can't find any documentation explaining how Teiid exposes a SOAP/WebService interface to the data. Can someone point me to the right place, or explain how Teiid does this?

Thanks!

[rareddy]

The SOAP interface is currently not supported using the Teiid Embedded. It is only supported using the Teiid Server. Teiid Server currently not available and you can track the progress at

https://jira.jboss.org/jira/browse/TEIID-259

Using the Teiid Designer, you can model a web service, and deploy the model in a VDB to a Teiid Server. Teiid additionally will supply a SOAP WAR file, which can be deployed to a application server such JBoss AS. Once this WAR file is deployed and configured correctly, then end user applications can submit the web service requests to application server, which in turn communicate with Teiid Server to build the correct response back to the calling application based the model originally created. It also has facilities to look up the WSDL for the web service you deployed.

Thank you.

[tejones]

Using the Teiid Designer, you can import WSDL into a Relational or a Web Service Model.
See:
http://docs.jboss.org/teiid/designer/6.0/user-guide/importers-chapter.html#wsdl-to-relational-import-section
and
http://docs.jboss.org/teiid/designer/6.0/user-guide/importers-chapter.html#wsdl-to-web-service-import-section
for details.

[serff]

Great, thanks for the info Ramesh and tejones, I'll track the issue in JIRA. We'll be much more interested in the product once there is a server version. Do you have a timeframe for release?

[rareddy]

Our next release is 6.1.0 which in last week of May, we are planning this is in 6.2.0, which may be in July/August, but we may have snapshot before that.

Ted, what are the technical difficulties to make SOAP supported using Embedded?

[tejones]

Sounds like "Dimension" revisited? :-)

We would need to override the connection logic to connect using the embedded URL. May be worth considering as an alternative to a server/SOAP implementation.

[rareddy]

Is this connection configuration in "web.xml" or some external properties file? Can it be tied to a JNDI name (data source)?

[tejones]

Yes and no... the URL is built based on server/port/vdb information passed in OR specified in the web.xml. However, the format of the URL is specified in the code (in the VDB resource servlet in the case of WSDL resource retrieval and in the connection pool logic in the case of the execution of the data service). Code changes would be required to override this.

[rareddy]

Seems like we need a third option and/or remove the web.xml based configuration to specify only the JNDI name, so that the connection specific information is external to the SOAP WAR.

[tejones]

Right, I will log a Jira. The connection pool is using the JDBCUtil class to build the URL so that logic will need to change. Perhaps an intermediate utilitiy class to build the URL based on the desired connection type (JDBC, JNDI, etc.). I think we need to avoid adding more configuration to the web.xml so a property file seems the better way to go.

[rareddy]

Cool, agree. Log a JIRA and please post it here, any design specific issues we can discuss on the JIRA forum.

[rareddy]

Cool, agree. Log a JIRA and please post it here, any design specific issues we can discuss on the JIRA forum.

[tejones]

Logged as: https://jira.jboss.org/jira/browse/TEIID-497