-
1. Re: Incoming OData connetion doesn't work
rareddy Jun 20, 2019 10:15 AM (in response to dieman.one)How did you install Teiid? What version, you mentioned Red Hat JBoss application Platform" but that does not have Teiid in it.
Ramesh..
-
2. Re: Incoming OData connetion doesn't work
dieman.one Jun 20, 2019 10:54 AM (in response to rareddy)Hi, apology for not including that info.
I installed Teiid as overlay installation on WildFly.
teiid-wildfly-12.1.1-dist
-
3. Re: Incoming OData connetion doesn't work
rareddy Jun 20, 2019 12:49 PM (in response to dieman.one)Sorry, we do not support overlay on EAP versions in community. Teiid only uses the WildFly versions for it. Redhat used to offer EAP based Data Virtualization, but that is no longer available. With some knowledge of EAP and Teiid you can probably do that, but it is beyond community support we can provide for it. Easiest is to try to find above WAR file and move to the "deployments" directory?
You can also try newer spins of Teiid like "teiid-spring-boot" where an Application Server requirement is completely removed, but this is better suited for Java developer.
Ramesh..
-
4. Re: Incoming OData connetion doesn't work
dieman.one Jun 21, 2019 3:52 AM (in response to rareddy)Hi, unfortunately the WAR is not so easy to find as a JAR. I t might be even JBoss-specific?
Could you suggest where to get it?
Can you maybe please suggest an alternative route as well? For me enabling OData connection is a requirement. What would be the best way to arrive at Teiid installation with OData enabled? Should I switch to another JBoss version?
and copy my configuration over?
-
5. Re: Incoming OData connetion doesn't work
dieman.one Jun 21, 2019 5:37 AM (in response to dieman.one)Hi, I just found that there is another Odata-Olingo connector installed on my Teiid, on odata4 context root, and it seems alive!
http://localhost:8080/odata4/vdb1-xml.1/PRISM.cs_std_parent
But eventually I get the following error:
error code "" message "TEIID16022 Unknown Schema or Schema is not visible in VDB"
I am possitive that my VDB name and schema and table are correct - I can query them successfully via JDBC connection.
I found another article related to the same error (no solution):
Is odata4 URL not the way forward? Is there any way to overcome this error?
-
6. Re: Incoming OData connetion doesn't work
rareddy Jun 21, 2019 10:57 AM (in response to dieman.one)The use of "odata4" context is supporting OData V4, earlier versions Teiid also supported V2 at context "odata" which now has been removed.
Try using http://localhost:8080/odata4/vdb1-xml.1/PRISM/cs_std_parent
In OData V4, the schema becomes part of the path, not represented with "." in table name. Each schema is exposed at schema root. Also in order to show up table in odata, the table/view MUST have primary or unique key defined on it.
-
7. Re: Incoming OData connetion doesn't work
dieman.one Jun 21, 2019 11:29 AM (in response to rareddy)Hi, tried that, this resulted in the following error:
<?xml version="1.0" encoding="UTF-8"?>
<error>
<code>null</code>
<message>Cannot find EntitySet, Singleton, ActionImport or FunctionImport with name 'cs_std_parent'.</message>
</error> -
8. Re: Incoming OData connetion doesn't work
rareddy Jun 21, 2019 11:35 AM (in response to dieman.one)What does http://localhost:8080/odata4/vdb1-xml.1/PRISM/$metadat
returns. where PRISM is the name of your model/schema in the VDB. Check the result document and in the <EntityContainer> it will list the entities you can access. If the "cs_std_parent" listed then you can query if not you will see above error. As I mentioned make sure this table has Primary Key in it.