SOAP interface for DataAPI
-
- Posts: 13
- Joined: Mon May 01, 2006 10:27 am
SOAP interface for DataAPI
The March 2008 newsletter said that the SOAP API for the DataAPI was available. if so, I did not see that in the manual at all. Is the SOAP interface available yet? Thanks
SOAP interface for DataAPI
Sorry, it has not quite been released yet. There have been some delays, but we expect to have it available in an update soon. I'll make note here when it's available.
-
- Posts: 256
- Joined: Sat Oct 08, 2005 12:40 pm
SOAP interface for DataAPI
It looks like the Soap interface is active on our appliances.
Can we already use it?
The documentation does not explain how to use the 'additional field' feature with the SOAP interface.
Can you tell me how this works?
Can we already use it?
The documentation does not explain how to use the 'additional field' feature with the SOAP interface.
Can you tell me how this works?
SOAP interface for DataAPI
> It looks like the Soap interface is active on our
> appliances. Can we already use it?
There are two different SOAP APIs, a searching API and a dataload API. The searching API has been distributed in a previous update as a pre-release and is usable. The final release is eminent, and it's unlikely there will be major changes between now and then.
> The documentation does not explain how to use the
> 'additional field' feature with the SOAP interface.
> Can you tell me how this works?
It's similar to how the XML output works - each <Result> has an element for each additional field, where the element name is the Additional Field's name. This is what the <xsd:Any> is for in the WSDL, as the WSDL cannot define what elements may appear.
> appliances. Can we already use it?
There are two different SOAP APIs, a searching API and a dataload API. The searching API has been distributed in a previous update as a pre-release and is usable. The final release is eminent, and it's unlikely there will be major changes between now and then.
> The documentation does not explain how to use the
> 'additional field' feature with the SOAP interface.
> Can you tell me how this works?
It's similar to how the XML output works - each <Result> has an element for each additional field, where the element name is the Additional Field's name. This is what the <xsd:Any> is for in the WSDL, as the WSDL cannot define what elements may appear.
-
- Posts: 13
- Joined: Mon May 01, 2006 10:27 am
SOAP interface for DataAPI
Where would one find the WSDL (assuming this is now available as suggested by the email above)?
SOAP interface for DataAPI
on your appliance, the wsdl for the search API is available at:
/texis/ThunderstoneSearchService/describe.wsdl
/texis/ThunderstoneSearchService/describe.wsdl
-
- Posts: 1
- Joined: Wed Apr 30, 2008 3:57 am
SOAP interface for DataAPI
>It's similar to how the XML output works - each
><Result> has an element for each additional field,
>where the element name is the Additional Field's name.
>This is what the <xsd:Any> is for in the WSDL, as the
>WSDL cannot define what elements may appear.
Is there a way to use Additional fields in the Search Request instead of filtering in the searchResponse ?
I mean using it like in a search url with the parameter "&af1eq=X".
><Result> has an element for each additional field,
>where the element name is the Additional Field's name.
>This is what the <xsd:Any> is for in the WSDL, as the
>WSDL cannot define what elements may appear.
Is there a way to use Additional fields in the Search Request instead of filtering in the searchResponse ?
I mean using it like in a search url with the parameter "&af1eq=X".
SOAP interface for DataAPI
> Is there a way to use Additional fields in the Search
> Request instead of filtering in the searchResponse ?
> I mean using it like in a search url with the parameter
> "&af1eq=X".
That capability does not currently exist with the SOAP search API, but we expect to have it added soon.
> Request instead of filtering in the searchResponse ?
> I mean using it like in a search url with the parameter
> "&af1eq=X".
That capability does not currently exist with the SOAP search API, but we expect to have it added soon.
-
- Posts: 13
- Joined: Mon May 01, 2006 10:27 am
SOAP interface for DataAPI
The WSDL for the search API does not look quite right. You have a group with nothing underneath it.
xsd:element name="search">
−
<xsd:complexType>
−
<xsd:sequence><xsd:group ref="tns:commonRequest"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
xsd:element name="search">
−
<xsd:complexType>
−
<xsd:sequence><xsd:group ref="tns:commonRequest"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
-
- Posts: 13
- Joined: Mon May 01, 2006 10:27 am
SOAP interface for DataAPI
Please disregard the previous post. I see that this is a group item previously defined.
Is there documentation available for this? I would like to know how to get the next page of results.
Thanks, Tom
PS Is the DataLoad API available as a service yet?
Is there documentation available for this? I would like to know how to get the next page of results.
Thanks, Tom
PS Is the DataLoad API available as a service yet?