Hitachi Vantara Pentaho Community Forums
Results 1 to 2 of 2

Thread: Web services lookup step: No success on retrieving data from SOAP wsdl

  1. #1
    Join Date
    Aug 2012
    Posts
    4

    Default Web services lookup step: No success on retrieving data from SOAP wsdl

    The webservice that I want to retrieve data from, has the following SOAP input structure:

    Code:
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:str="http://www.webservice.com" xmlns:xsd="http://xml.services.common.webservice.com/xsd">
       <soap:Header/>
       <soap:Body>
          <str:getData>
             <!--Optional:-->
             <str:rec>
                <!--Optional:-->
                <xsd:auth_LoginName>login</xsd:auth_LoginName>
                <!--Optional:-->
                <xsd:auth_Password>password</xsd:auth_Password>
             </str:rec>
             <!--Optional:-->
             <str:param1>1</str:param1>
             <!--Optional:-->
             <str:param2>2</str:param2>
             <!--Optional:-->
             <str:param3>3</str:param3>
          </str:getData>
       </soap:Body>
    </soap:Envelope>
    I built a transformation this way, where the Generate Rows step of course contains the values for param1, param2 and param3:

    Name:  transformation.png
Views: 85
Size:  12.8 KB

    The three tabs of the Webservices lookup step I filled out this way:

    Name:  tab1.jpg
Views: 111
Size:  36.3 KB

    Name:  tab2.jpg
Views: 69
Size:  30.3 KB

    Name:  tab3.jpg
Views: 68
Size:  30.1 KB

    But the XML result file remains empty (although the same request via soapUI gets success!):

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

    Have you any ideas, why?
    I suppose, it has to do with the cascaded rec-structure for "LoginName" and "Password", because PDI can not know the inside names of this rec-container, as long I have no chance to announce it to PDI. How can I fix that?

    Any hints will be welcome, thanks a lot!

  2. #2
    Join Date
    Aug 2012
    Posts
    4

    Default

    Does really no one have an idea? Isn't it a very normal input structure of that web service? I think, there must be a solution!

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.