Salesforce to ECC Intergration scenario issue

[former_member200386]

Dear Experts,

I am working on one requirement  where SFDC is at sender side ECC at receiver side. I am using soap adapter for sales force  side.(SOAP to RFC scenario)

i have created WSDL file and shared to Sales force team.while they are importing the WSDL they are getting this below error

Error: Failed to parse wsdl: output not defined in binding operation .

Can you please guide me how can i resolve the issue.

Thanks in advance

Pavan

[smavachee]

Refer below links and ask Salesforce guys to look into it as well.

Failed to parse WSDL

Error while parsing the WSDL file at SFDC

Hope it helps.!

Regards,

Sunil

[former_member200386]

Hi Sunil,

Thanks alot for your quick response , i have already gone through that link.  no use

i have a few questions .

1)

my namespace is like this urn:xxxxxxxxx

is this correct?

or i need to create like this http://....xxxxxxxxxx?

2) the design will be like plain SOAP to RFC only or else we need to follow the same  approach 

if sales force is at receiver side, we need to design like belowsession id creation & dynamic url creation)

Regards,

Pavan

[smavachee]

Nothing wrong with namespace. Cross check your ESR once again with reference to below blog..

Integration with Salesforce

Regards,

Sunil

[former_member200386]

Hi Sunil,

I have that document with me. that approach is if sales force is at receiver  side.

but my requirement is Sales force at Sender Side.

Regards,

Pavan

[smavachee]

Oops, got busy with other engagements.

Any way, it will be typical SOAP to RFC Scenario.

Can you cross check WSDL using WSNavigator or any other available tool.

Regards,

Sunil

[former_member200386]

HI Sunil,

Thanks for your response. I have tested the WSDL with Soap UI tool and it is working fine.

but same wsdl is not importing at sales force end.

can you please go through this link once

http://www.salesforce.com/us/developer/docs/apexcode/Content/apex_callouts_wsdl2apex.htm

in this web blog it is mention that sales force apex does not support if wsdl contain multiple ports (wsdl will import through apex classes in salesforce).  i have to ports in WSDL (50000, 50001)Please find my WSDL structure below.

<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:p1="http://SFDCIntegrationPOC" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" name="SI_SFDC_Sender" targetNamespace="http://SFDCIntegrationPOC">

<wsdl:documentation />

<wsp:UsingPolicy wsdl:required="true" />

<wsp:Policy wsu:Id="OP_SI_SFDC_Sender" />

<wsdl:types>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://SFDCIntegrationPOC" targetNamespace="http://SFDCIntegrationPOC">

<xsd:element name="MT_SFDC_Sender" type="DT_SFDC_Sender" />

<xsd:complexType name="DT_SFDC_Sender">

<xsd:annotation>

<xsd:appinfo source="http://sap.com/xi/VersionID">

2b36df0f865c11e2c54d0000007826ca

</xsd:appinfo>

</xsd:annotation>

<xsd:sequence>

<xsd:element name="INPUT" maxOccurs="unbounded">

<xsd:complexType>

<xsd:sequence>

<xsd:element name="PatientId" type="xsd:string" minOccurs="0" />

<xsd:element name="SFDCId" type="xsd:string" minOccurs="0" />

<xsd:element name="PatientStatus" type="xsd:string" minOccurs="0" />

<xsd:element name="TreatingPhysicianName" type="xsd:string" minOccurs="0" />

<xsd:element name="HospitalName" type="xsd:string" minOccurs="0" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

</wsdl:types>

<wsdl:message name="MT_SFDC_Sender">

<wsdl:documentation />

<wsdl:part name="MT_SFDC_Sender" element="p1:MT_SFDC_Sender" />

</wsdl:message>

<wsdl:portType name="SI_SFDC_Sender">

<wsdl:documentation />

<wsdl:operation name="SI_SFDC_Sender">

<wsdl:documentation />

<wsp:Policy>

<wsp:PolicyReference URI="#OP_SI_SFDC_Sender" />

</wsp:Policy>

<wsdl:input message="p1:MT_SFDC_Sender" />

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name="SI_SFDC_SenderBinding" type="p1:SI_SFDC_Sender">

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

<wsdl:operation name="SI_SFDC_Sender">

<soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" soapAction="http://sap.com/xi/WebService/soap1.1" />

<wsdl:input>

<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" />

</wsdl:input>

</wsdl:operation>

</wsdl:binding>

<wsdl:service name="SI_SFDC_SenderService">

<wsdl:port name="HTTP_Port" binding="p1:SI_SFDC_SenderBinding">

<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://alxn-sapxd1.alxn.net:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_SFDC&re..." />

</wsdl:port>

<wsdl:port name="HTTPS_Port" binding="p1:SI_SFDC_SenderBinding">

<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="https://alxn-sapxd1.alxn.net:50001/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_SFDC&r..." />

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

You are saying it will be a typical SOAP to RFC scenario?

it means do i need to follow the same approach we need to follow if sales force at teciver end.

i.e create session id using java mapping, soap look up design etc...?

Thanks in Advance

Pavan

[smavachee]

That is correct Pavan, as you are using multiple bindings, that is a reason even your error indicate.

Can you try with example given..

Regards,

Sunil

[former_member200386]

Hi Sunil,

Thanks for your response i found out the actual reason for this error. Sales force always expects WSDL to be synchronus, i changed my design plan to synchronus , now sales force team are sucessfully importing the wsdl.

Again i am troubling you!!!!

i have seen this thread

http://scn.sap.com/thread/3196104

in this thread the user has also working same requirement as sales force as sender . he faced lot of issues using with SOAP adapter  then he changed the scenario into HTTP to RFC.

suppose i changed the scenario into HTTP to RFC. How sales force team will send the data to PI with out calling WSDL? please help me

Thanks in advance

Pavan

[smavachee]

I will suggest you to stick with SOAP only. Personally I have not been used HTTP with Salesforce in any of my engagements.

Looking into technical aspect of communication, HTTP Adapter is directly connecting to Integration Engine whereas SOAP Adapter connecting via Java based Adapter Framework.

I am not sure about your existing SAP PI version, but looking ahead with migration patchwork in future with PI 7.3 or 31 single stack, will prefer to go ahead with SOAP.

If you are successfully integrated the scenario, don't make it complicated.. . May be for POC purpose you can use HTTP but as of now go ahead with SOAP.

Regards,

Sunil

[rajasekhar_reddy14]

Hi Pavan,

I did SFDC integration in my current project, use SOAP adapter only it works only thing is network compatiblity if SFDC team able to access WSDL then no worries.

Regards,

Raj

[former_member200386]

Hi Raj,

Thanks for your Update. I am  little worried before, after seeing your  post i got the confidence that i can pull off my scenario. 

Please suggest me what kind of design i need to follow if SFDC is at sender side. is it normal SOAP to RFC scenario or do wee need to create a session id ....etc. Please help me

Regards,

Pavan

[former_member200386]

Dear Experts,

Have any one worked on Sales Force integration with ECC ? Sales force as sender side. Quick response appreciated.

Regards,

Pavan