SOAP service

This space is made available to users of Open Patent Services (OPS) web-service and now also to users of EPO’s bulk data subscription products such as 14. EPO worldwide bibliographic database (DOCDB), 14.11 EPO worldwide legal status database (INPADOC), 14.12 EP full text data, 14.1 EP bibliographic data (EBD)and more.

Users can ask each other questions, exchange experiences and solutions, post ideas. The moderator will use this space to announce changes or other relevant information.
Post Reply

ashleeninan
Posts: 10
Joined: Mon Jan 06, 2014 3:45 pm

SOAP service

Post by ashleeninan » Tue Jan 07, 2014 9:03 am

Hi,
Since the OPS SOAP service has been moved to version 3.1, I am not getting any response for family retrieval. I am getting a 403 Forbbiden.
The url that I am using is below
h t t p [colon slash slash]ops[dot]epo[dot]org[slash]3[dot]0[slash]soap-services[slash]family-retrieval

Can someone help me understand what needs to be changed to migrate the client code from 3.0 version to 3.1 for SOAP? Thanks.


EPO / OPS Support
Posts: 1027
Joined: Thu Feb 22, 2007 5:32 pm

Re: SOAP service

Post by EPO / OPS Support » Tue Jan 07, 2014 11:40 am

I wrote to you on that as well. It's all in documentation on our website and you need to register to new 3.1 version first and only after activating your account you can add your apps and create a token. Again, it's all in the documentation.

Kind regards,

OPS support


ashleeninan
Posts: 10
Joined: Mon Jan 06, 2014 3:45 pm

Re: SOAP service

Post by ashleeninan » Wed Jan 08, 2014 8:18 am

Hi,

Yes and thanks.
We have received your mail.
We will have it to be planned to migrate to REST service as soon as possible.
But since for time being till we have the REST based version of application developed/migrated we will be consuming SOAP based ops web service in our application,if we do the registration, is the Authentication and Access tokens is required for SOAP service or is it only for REST service?(As we see the document -OPS version 3.1 documentation - version 1.2.10 deals all with the rest service)

Thanks


EPO / OPS Support
Posts: 1027
Joined: Thu Feb 22, 2007 5:32 pm

Re: SOAP service

Post by EPO / OPS Support » Wed Jan 08, 2014 10:18 pm

You need to register for v.3.1 no matter if you use REST or SOAP. The only reason why we mention ony REST in OPS documentation is that we don't update legacy SOAP for over a year now, as you can see on our website. This is also the reason why we recommend that our users use ony REST. Appart of not updating SOAP we also offer less services via SOAP.

Kind regards,
OPS support


ashleeninan
Posts: 10
Joined: Mon Jan 06, 2014 3:45 pm

Re: SOAP service

Post by ashleeninan » Fri Jan 10, 2014 4:12 am

Thanks
When we try to update the SOAP wsdl -http://ops.epo.org/wsdl/ops.wsdl in our application we see that it still points to 3.0.Is it because it has not updated or or the WSDL for SOAP has changed.Please confirm the WSDL for SOAP we need to use for time being

<wsdl:service name="OPSBiblioRetrievalService">
<wsdl:port name="BiblioRetrievalPort" binding="tns:BiblioRetrievalBinding">
<soap:address location="/3.0/soap-services/biblio-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSBiblioSearchService">
<wsdl:port name="BiblioSearchPort" binding="tns:BiblioSearchBinding">
<soap:address location="/3.0/soap-services/biblio-search"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSClaimsService">
<wsdl:port name="ClaimsPort" binding="tns:ClaimsBinding">
<soap:address location="/3.0/soap-services/claims-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSDescriptionService">
<wsdl:port name="DescriptionPort" binding="tns:DescriptionBinding">
<soap:address location="/3.0/soap-services/description-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSFulltextInquiryService">
<wsdl:port name="FulltextInquiryPort" binding="tns:FulltextInquiryBinding">
<soap:address location="/3.0/soap-services/fulltext-inquiry"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSEquivalentsInquiryService">
<wsdl:port name="EquivalentsInquiryPort" binding="tns:EquivalentsInquiryBinding">
<soap:address location="/3.0/soap-services/equivalents-inquiry"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSDocumentInquiryService">
<wsdl:port name="DocumentInquiryPort" binding="tns:DocumentInquiryBinding">
<soap:address location="/3.0/soap-services/document-inquiry"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSDocumentRetrievalService">
<wsdl:port name="DocumentRetrievalPort" binding="tns:DocumentRetrievalBinding">
<soap:address location="/3.0/soap-services/document-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSFamilyService">
<wsdl:port name="FamilyPort" binding="tns:FamilyBinding">
<soap:address location="/3.0/soap-services/family-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSFamilyAndBiblioService">
<wsdl:port name="FamilyAndBiblioPort" binding="tns:FamilyAndBiblioBinding">
<soap:address location="/3.0/soap-services/family-and-biblio-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSFamilyAndLegalService">
<wsdl:port name="FamilyAndLegalPort" binding="tns:FamilyAndLegalBinding">
<soap:address location="/3.0/soap-services/family-and-legal-retrieval"/>
</wsdl:port>
</wsdl:service>

<wsdl:service name="OPSFamilyAndLegalAndBiblioService">
<wsdl:port name="FamilyAndLegalAndBiblioPort" binding="tns:FamilyAndLegalAndBiblioBinding">
<soap:address location="/3.0/soap-services/family-and-legal-and-biblio-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSLegalService">
<wsdl:port name="LegalPort" binding="tns:LegalBinding">
<soap:address location="/3.0/soap-services/legal-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSLegalAndBiblioService">
<wsdl:port name="LegalAndBiblioPort" binding="tns:LegalAndBiblioBinding">
<soap:address location="/3.0/soap-services/legal-and-biblio-retrieval"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="OPSNumberService">
<wsdl:port name="NumberServicePort" binding="tns:NumberServiceBinding">
<soap:address location="/3.0/soap-services/number-service"/>
</wsdl:port>
</wsdl:service>


EPO / OPS Support
Posts: 1027
Joined: Thu Feb 22, 2007 5:32 pm

Re: SOAP service

Post by EPO / OPS Support » Fri Jan 10, 2014 9:41 am

Dear user,

Just change 3.0 with 3.1 and you can use it!! As said before, SOAP is a legacy, we don't really update documentation for SOAP any longer and that is the reason why I suggested few times already that you think of migrating to REST so that you can use OPS and all its services in a proper way.

Kind regards,

OPS support


Post Reply