Error while executing Webservice Model - Depricated one.

[Former Member]

Hi ,

I am trying to execute a webservice through Webdynpro framework . So I have imported the webservice using the Webservice model - Depricated in NWDS 7 SP15 using the local wsdl file.

The Webservice is provided by XI 3.0 SP19.

When i set the parameters for the model and execute, i am getting an excpetion and the message is Server Error.

In the XI worksbench, i see the error is in integration builder and error type is Mapping error.

The Webservice works fine in SOAPUI tool.

I am not able to figure out whether the problem is in my webdynpro code or in WSDL file format or in XI.

Below is my webdynpro java code :

 

try
{
			Request_MI_EmployerPeopleFinderOB_Sync_MI_EmployerPeopleFinderOB_Sync  objMI= new Request_MI_EmployerPeopleFinderOB_Sync_MI_EmployerPeopleFinderOB_Sync();
			
			objMI._setUser("xi_remote");
			objMI._setPassword("good");
			
			Record objRecord =  new Record();
					
			objRecord.setNAMEKEY("1");
			objRecord.setNAMEVALUE("Terri");
			objRecord.setOPTIONVALUE("0");
			objRecord.setFIELDKEY(null);
			objRecord.setFIELDVALUE(null);
		
			DT_EmployerPeopleFinderRequest objActDT = new DT_EmployerPeopleFinderRequest();
		
			
			objDT.setRecord(objRecord);
			
			objMI.setMT_EmployerPeopleFinderRequest(objDT);
			
			wdContext.nodeRequest_MI_EmployerPeopleFinderOB_Sync_MI_EmployerPeopleFinderOB_Sync().bind(objMI);
		
			wdContext.currentRequest_MI_EmployerPeopleFinderOB_Sync_MI_EmployerPeopleFinderOB_SyncElement().modelObject().execute();
		
			wdContext.nodeResponse().invalidate();
	
			wdComponentAPI.getMessageManager().reportSuccess("Execution Done");
  
    
    }  catch (Exception e) {
		wdComponentAPI.getMessageManager().reportException("rfqException="+e.getMessage(),true); 
		
    }

And below is my wsdl file contents :

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

<wsdl:definitions name="MI_Employer_PeopleFinder_OB_Sync" targetNamespace="http://mln.com/xi/employer_people_finder" xmlns:p1="http://mln.com/xi/employer_people_finder" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"><wsdl:types><xsd:schema targetNamespace="http://mln.com/xi/employer_people_finder" xmlns="http://mln.com/xi/employer_people_finder" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:element name="MT_Employer_PeopleFinder_Request" type="DT_Employer_PeopleFinder_Request" /><xsd:element name="MT_Employer_PeopleFinder_Response" type="DT_Employer_PeopleFinder_Response" /><xsd:complexType name="DT_Employer_PeopleFinder_Response"><xsd:sequence><xsd:element name="row" minOccurs="0" maxOccurs="unbounded" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">cc730420485611dda9cde25dac1a5f6b</xsd:appinfo></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element name="NAME" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">cc730421485611ddc0aae25dac1a5f6b</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="WORKPHONE" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">cc730422485611dd9b83e25dac1a5f6b</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="EMAIL" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">cc730423485611dd9bbbe25dac1a5f6b</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="LOCATIONTEXT" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">cc730424485611dda467e25dac1a5f6b</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="ADUSRID" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">cc730425485611dd9c0fe25dac1a5f6b</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="HRID" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">6dcd2b20485711dd9b57e25dac1a5f6b</xsd:appinfo></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType></xsd:element></xsd:sequence></xsd:complexType><xsd:complexType name="DT_Employer_PeopleFinder_Request"><xsd:sequence><xsd:element name="Record" minOccurs="0"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">4c7976b053a911ddbd47f0f2ac1a9870</xsd:appinfo></xsd:annotation><xsd:complexType><xsd:sequence><xsd:element name="NAMEKEY" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">4c7976b153a911dd86b5f0f2ac1a9870</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="NAMEVALUE" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">4c7976b253a911ddc997f0f2ac1a9870</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="OPTIONVALUE" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">4c7976b353a911ddad01f0f2ac1a9870</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="FIELDKEY" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">4c7976b453a911ddb58df0f2ac1a9870</xsd:appinfo></xsd:annotation></xsd:element><xsd:element name="FIELDVALUE" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:annotation><xsd:appinfo source="http://sap.com/xi/TextID">4c7976b553a911ddce71f0f2ac1a9870</xsd:appinfo></xsd:annotation></xsd:element></xsd:sequence></xsd:complexType></xsd:element></xsd:sequence></xsd:complexType></xsd:schema></wsdl:types><wsdl:message name="MT_Employer_PeopleFinder_Request"><wsdl:part name="MT_Employer_PeopleFinder_Request" element="p1:MT_Employer_PeopleFinder_Request" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" /></wsdl:message><wsdl:message name="MT_Employer_PeopleFinder_Response"><wsdl:part name="MT_Employer_PeopleFinder_Response" element="p1:MT_Employer_PeopleFinder_Response" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" /></wsdl:message><wsdl:portType name="MI_Employer_PeopleFinder_OB_Sync"><wsdl:operation name="MI_Employer_PeopleFinder_OB_Sync"><wsdl:input message="p1:MT_Employer_PeopleFinder_Request" /><wsdl:output message="p1:MT_Employer_PeopleFinder_Response" /></wsdl:operation></wsdl:portType><wsdl:binding name="MI_Employer_PeopleFinder_OB_SyncBinding" type="p1:MI_Employer_PeopleFinder_OB_Sync" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"><soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" /><wsdl:operation name="MI_Employer_PeopleFinder_OB_Sync"><soap:operation soapAction="http://sap.com/xi/WebService/soap1.1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" /><wsdl:input><soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" /></wsdl:input><wsdl:output><soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:service name="MI_Employer_PeopleFinder_OB_SyncService"><wsdl:port name="MI_Employer_PeopleFinder_OB_SyncPort" binding="p1:MI_Employer_PeopleFinder_OB_SyncBinding" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"><soap:address location=" http://max-sap23:50000/XISOAPAdapter/MessageServlet?channel=:BusService_Portal_PeopleFinder:Sender_S...; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" /></wsdl:port></wsdl:service></wsdl:definitions>

Please help to solve this problem.

Thanks,

Aditya Metukul

Edited by: aditya metukul on Aug 9, 2008 2:54 AM

Edited by: aditya metukul on Aug 9, 2008 2:55 AM

[Former Member · Accepted solution]

Hello Aditya,

it is very hard to tell were the problem is from your information.

In cases like these I use SoapUI to do the following:

Test your WebDynpro by creating a so called MockService that immitates the response that you expect. By setting the mock service as destination you can see what exactly is sent to XI by your wd app.

If you have done the above you know whether it is in XI or in your WD code. I guess, it is an XI problem as I would expect mapping problems to occur there rather.

Kind regards

Matthias

[Former Member · Accepted solution]

Hi Matthias,

Thanks for the Response.

Please let me know how to create a Mock Service for webdynpro application url in SOAPUI client.

I just saw the option of creating the MockService for the imported WSDL file. Not sure how to go about for Webdynpro appplication URL say [ http://max-sap49:50000/webdynpro/dispatcher/local/TestWd/Testapplication?SAPtestId=1];

I feel the problem lies in the WSDL object hierarchy level for input paramenteres. Usually in most of the webservices or RFCs there will be only level 2 but in our case the level is 3.

e.g. : Request_MI_EmployerPeopleFinderOB_Sync_MI_EmployerPeopleFinderOB_Sync

DT_EmployerPeopleFinderRequest

Record

NameKey

Name Value

OptionValue

FieldKey

FieldName

Still now i couldn't find the root cause. Everything looks fine when tested through soap ui tool.

The problem is really strange. I tired with all the possibilities.

Anyways thanks for the help.

Regards,

Aditya Metukul

[Former Member · Accepted solution]

Hello Aditya,

I think you missunderstood me:

You create a Mockservice to immitate your XI Service. You already imported the WSDL so generating the MockService should be straight forward. Then you connect your WD App to the mock service instead of the real one. By that you see exactly what is in the request sent by the WD App. The MockService sends a response in any case and you can see how wd deals with it.

I hope it helps,

Matthias

[Former Member · Accepted solution]

Hi Matthias,

I tried creating mock service in SOAPUI for the existing, but i am not sure whether i am doing it right.

Please give instructions to create mockservice on the existing WSDL imported in SOAPUI.

My webdynpro application url is http://max-sap49:50000//webdynpro/dispatcher/local/TestWd/Testapplication

The node on which MockService to be created in SOAPUI is MI_Employer_PeopleFinder_OB_Sync

And how to see what is sent to XI by webdynpro application ?

Thanks,

Regards,

Aditya Metukul

[Former Member · Accepted solution]

The Root cause was becuase of mismatch in tag names in WSDL and the Response SOAP message.

Once we renamed the tag name in WSDL according to the SOAP message tag names. It worked.

Thanks,

Regards,

Aditya Metukul