Skip to Main Content

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

How to consume a simple web service in 11g PL/SQL?

user12240205Oct 30 2015 — edited Nov 11 2015

Our PEGA team has created a simple web-service in SOAP. We want to call this from a PL/SQL procedure.

I wend through this thread:

Problem is, I am unable to figure out what to replace to looking at the WSDL for my web-service. This web-service was developed by us but by somebody else.

The problem is in this area:

soap_request:= '<?xml version = "1.0" encoding = "UTF-8"?>'||
                   '<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">'||
                   '  <SOAP-ENV:Body>'||
                   '    <m:DownloadRequest xmlns:m="http://www.website.net/messages/GetDetails">'||
                   '      <m:UserName>'||p_username||'</m:UserName>'||
                   '      <m:Password>'||p_password||'</m:Password>'||
                   '    </m:DownloadRequest>'||
                   '  </SOAP-ENV:Body>'||
                   '</SOAP-ENV:Envelope>';
    http_req:= utl_http.begin_request
              ( 'http://www.website.net/webservices/GetDetailsService.asmx'
              , 'POST'
              , 'HTTP/1.1'
              );

The WS we call has 4 input parameters: ArgusCaseID, ArgusInstanceID, ClientID, EventDescription, PegaCaseID.

The response will be: Status

My question is: What to replace for the "m" tags in the soap_request  and http_req above? i.e. the RED ones above.  i.e. the Red ones. I can insert the input parameters like done for UserName and Password. But I can't figure out what to replace for the DownloadRequest and http://www.website.net/messages/GetDetails and   http://www.website.net/webservices/GetDetailsService.asmx.

_________________________________________________________________________________________________________________________________________________________________

The WSDL for the web service is given below:

<?xml version="1.0" encoding="UTF-8"?>

<definitions targetNamespace="urn:PegaRULES:SOAP:ArgusToPegaFeeds:Services" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:nslt1="urn:PegaRULES:SOAP:ArgusToPegaFeeds:Services" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="urn:PegaRULES:SOAP:ArgusToPegaFeeds:Services" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/">

  <types>

    <schema elementFormDefault="unqualified" targetNamespace="urn:PegaRULES:SOAP:ArgusToPegaFeeds:Services" xmlns="http://www.w3.org/2001/XMLSchema"><complexType name="WakeUpArgusEventProcessingRequesttype"><sequence><element name="ArgusEventRequest"><complexType><sequence><element name="ArgusCaseID" type="xsd:string"/><element name="ArgusInstanceID" type="xsd:string"/><element name="ClientID" type="xsd:string"/><element name="EventDescription" type="xsd:string"/><element name="PegaCaseID" type="xsd:string"/></sequence></complexType></element></sequence></complexType><element name="WakeUpArgusEventProcessingRequest" type="tns:WakeUpArgusEventProcessingRequesttype"/><complexType name="WakeUpArgusEventProcessingResponsetype"><sequence><element name="ArgusEventResponce"><complexType><sequence><element name="Status" type="xsd:string"/></sequence></complexType></element></sequence></complexType><element name="WakeUpArgusEventProcessingResponse" type="nslt1:WakeUpArgusEventProcessingResponsetype"/></schema>

  </types>

  <message name="WakeUpArgusEventProcessingResponse">

    <part name="WakeUpArgusEventProcessingResponse" element="nslt1:WakeUpArgusEventProcessingResponse">

    </part>

  </message>

  <message name="WakeUpArgusEventProcessing">

    <part name="WakeUpArgusEventProcessingRequest" element="nslt1:WakeUpArgusEventProcessingRequest">

    </part>

  </message>

  <portType name="ServicesType">

    <operation name="WakeUpArgusEventProcessing">

      <input message="nslt1:WakeUpArgusEventProcessing">

    </input>

      <output message="nslt1:WakeUpArgusEventProcessingResponse">

    </output>

    </operation>

  </portType>

  <binding name="ServicesBindingSOAP" type="nslt1:ServicesType">

    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

    <operation name="WakeUpArgusEventProcessing">

      <soap:operation soapAction="urn:PegaRULES:SOAP:ArgusToPegaFeeds:Services#WakeUpArgusEventProcessing"/>

      <input>

        <soap:body use="literal"/>

      </input>

      <output>

        <soap:body use="literal"/>

      </output>

    </operation>

  </binding>

  <binding name="ServicesBindingSOAP12" type="nslt1:ServicesType">

    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

    <operation name="WakeUpArgusEventProcessing">

      <soap12:operation soapAction="urn:PegaRULES:SOAP:ArgusToPegaFeeds:Services#WakeUpArgusEventProcessing"/>

      <input>

        <soap12:body use="literal"/>

      </input>

      <output>

        <soap12:body use="literal"/>

      </output>

    </operation>

  </binding>

  <service name="ServicesService">

    <port name="ServicesPortSOAP" binding="nslt1:ServicesBindingSOAP">

      <soap:address location="https://telerx-ptdev.pegacloud.com:443/prweb/PRSOAPServlet/SOAP/ArgusToPegaFeeds/Services"/>

    </port>

    <port name="ServicesPortSOAP12" binding="nslt1:ServicesBindingSOAP12">

      <soap12:address location="https://telerx-ptdev.pegacloud.com:443/prweb/PRSOAPServlet/SOAP/ArgusToPegaFeeds/Services"/>

    </port>

  </service>

</definitions>

This post has been answered by PeterValencic on Nov 2 2015
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Dec 9 2015
Added on Oct 30 2015
17 comments
13,814 views