Question Re: Successfactor Login interface error in Technology Q&A

Successfactor Login interface error

Muniyappan — Mon, 27 Jul 2015 11:11:43 GMT

Hi,

I am using PI 7.4 single stack to integrate successfactor and ECC.

when i am using soap axis channel SFSF_Soap_Adapter_Axis_Login_Response, i am not getting the response. it is throwing below error.

###########################################################################################

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

-<SAP:Error SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>

<SAP:P1>200</SAP:P1>

<SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2>

<SAP:P3/>

<SAP:P4/>

<SAP:AdditionalText>--SAP_bae6e5b3-344a-11e5-a1f3-0000006e6e1e_END Content-ID: <soap-bae3bf0c344a11e5a4c90000006e6e1e@sap.com> Content-Type: text/xml; charset=utf-8 Content-Disposition: attachment;filename="soap-bae3bf0c344a11e5a4c90000006e6e1e@sap.com.xml" Content-Description: SOAP <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging><sap:DynamicConfiguration xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Record namespace='http://sap.com/xi/System/HTTP' name='SetCookie'>BIGipServerP_PERFORMANCEMANAGER012.SUCCESSFACTORS.EU-80=!Qb35bxWVQClJSaPehJNTD7EYqYeaC51zB0C93QiJUqh3h7XbikKac2THNei6/tgJy0vaPTBCjvAyQzE=; path=/; HttpOnly, JSESSIONID=6886020214A518D2481773B7539A7D95.DC12BIZXSFAPI01; Path=/sfapi</sap:Record></sap:DynamicConfiguration><sap:System xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Record namespace='/xmlvalidation' name='SYNC_RESPONSE_BEFORE_MAPPING'>1</sap:Record></sap:System><sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Hop timeStamp='2015-07-27T10:30:55Z' wasRead='false'><sap:Engine type='BS'>EDV311</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>55b52c99-3d54-1da6-e100-0000ac14650e</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2015-07-27T10:32:03Z' wasRead='false'><sap:Engine type='AE'>af.pid.nakpidv1</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>55b52c99-3d54-1da6-e100-0000ac14650e</sap:MessageId></sap:Hop><sap:Hop timeStamp='2015-07-27T10:32:07Z' wasRead='false'><sap:Engine type='AE'>af.pid.nakpidv1</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>bad7e494-344a-11e5-c0e0-0000006e6e1e</sap:MessageId></sap:Hop></sap:HopList><sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' versionMajor='3' versionMinor='1' SOAP:mustUnderstand='1'><sap:MessageClass>ApplicationResponse</sap:MessageClass><sap:ProcessingMode>synchronous</sap:ProcessingMode><sap:MessageId>bad7e494-344a-11e5-c0e0-0000006e6e1e</sap:MessageId><sap:RefToMessageId>55b52c99-3d54-1da6-e100-0000ac14650e</sap:RefToMessageId><sap:TimeSent>2015-07-27T10:32:07Z</sap:TimeSent><sap:Sender><sap:Party agency='http://sap.com/xi/XI' scheme='XIParty'></sap:Party><sap:Service>BC_SFSF</sap:Service></sap:Sender><sap:Receiver><sap:Party agency='http://sap.com/xi/XI' scheme='XIParty'></sap:Party><sap:Service>EDV311</sap:Service></sap:Receiver><sap:Interface namespace='http://sap.com/xi/SFIHCM01'>SFSFSessionHandlingLoginQueryResult_Out</sap:Interface></sap:Main></SOAP:Header><SOAP:Body><sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink'><sap:Payload xlink:type='simple' xlink:href='cid:D7B3B5D60B3F3138A68E32077514C9F7'><sap:Name>document-0</sap:Name><sap:Description>unspecified document</sap:Description><sap:Type>Application</sap:Type></sap:Payload></sap:Manifest></SOAP:Body></SOAP:Envelope> --SAP_bae6e5b3-344a-11e5-a1f3-0000006e6e1e_END Content-ID: <D7B3B5D60B3F3138A68E32077514C9F7> Content-Disposition: attachment;filename="document-0.xml" Content-Type: text/xml; charset=utf-8 Content-Description: document-0 <?xml version="1.0" encoding="UTF-8"?> <ns1:loginResponse xmlns:ns1="http://sap.com/xi/SFIHCM01"><result><sessionId>$Version=0; BIGipServerP_PERFORMANCEMANAGER012.SUCCESSFACTORS.EU-80=!Qb35bxWVQClJSaPehJNTD7EYqYeaC51zB0C93QiJUqh3h7XbikKac2THNei6/tgJy0vaPTBCjvAyQzE=; $path=/,$Version=0; JSESSIONID=6886020214A518D2481773B7539A7D95.DC12BIZXSFAPI01; $Path=/sfapi</sessionId><msUntilPwdExpiration>2009135746</msUntilPwdExpiration></result></ns1:loginResponse> --SAP_bae6e5b3-344a-11e5-a1f3-0000006e6e1e_END-- </SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace=""/>

<SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.) </SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

###########################################################################################

it is going into above error but it has the proper response in the additional text(session ID.JPG)

if i take above response and test it in log out interface,it is also failing with same error but it has correct response in the additional text.

--SAP_7a8687f0-344b-11e5-9e28-0000006e6e1e_END Content-ID: <B9E6A2B3FDDB7AE0BF1567C6700D5401> Content-Disposition: attachment;filename="document-0.xml" Content-Type: text/xml; charset=utf-8 Content-Description: document-0 <?xml version="1.0" encoding="UTF-8"?> <ns1:logoutResponse xmlns:ns1="http://sap.com/xi/SFIHCM01"><result>true</result></ns1:logoutResponse> --SAP_7a8687f0-344b-11e5-9e28-0000006e6e1e_END

is there any change required in channel SFSF_Soap_Adapter_Axis_Login_Response? did anyone have this error before?

unfortunately i am not able to monitor the messages in PI().

Regards,

Muni

Re: Successfactor Login interface error

Muniyappan — Mon, 27 Jul 2015 11:15:33 GMT

i get totally different result if i use normal soap channel for login.

logout interface with some random text for session id.

This is confusing. if correct session id given it is failing, for wrong session id interface is working.

i think i can rule out role assignment,rfc configuration,password as for soap channel interface is working.

Re: Successfactor Login interface error

former_member183908 — Mon, 27 Jul 2015 12:42:50 GMT

what response do you get if you test using SOAP UI?


when i am using soap axis channel SFSF_Soap_Adapter_Axis_Login_Response, i am not getting the response. it is throwing below error.

Are using SFSF receiver adapter from SAP?

Thanks

Re: Successfactor Login interface error

Muniyappan — Mon, 27 Jul 2015 14:01:32 GMT

No. i am using SOAP axis adapter.

initially i was using soap adapter. but it did not give correct response. after checking thread i changed soap to soap axis adapter for login interface.

Re: Successfactor Login interface error

Muniyappan — Tue, 28 Jul 2015 05:28:39 GMT

i have done small test. changed sender soap adapter xi protocol to soap. tested with wsnavigator. i am able to get the response.

soap adapter-->PI-->successfactor(Axis)

not able to install soap ui(auth issues), else i could have checked with soap ui also.

seems something missing in ECC side. initially we got error. and required to implement note (1819457 - XI Runtime: @versionMinor has incorrect value 001)

basis has implemented only few notes(red color).

SAP Note 1459464 "Optimization: HTTP 202 instead of
synchronous acknowledgment"
SAP Note 1488164 "XI runtime: Proxy call of Release 6.20"
SAP Note 1561170 "XI runtime: 6.20 proxy call with
HTTP_STATUS_CODE_NEQ_OK"
SAP Note 1378872 "XI message version is not accepted"
SAP Note 1763020 "XI Runtime: HTTP 202 for 3.1 log with AFW"
SAP Note 1590166 "XI runtime: Application acknowledgement in
receiver system"
SAP Note 1570897 "Packaging and application acknowledgment:
No XI response"

do we need to implement remaining notes also(1459464,1561170,1590166,1570897)? please suggest.

Thanks,

Muni.

Re: Successfactor Login interface error

former_member183908 — Tue, 28 Jul 2015 06:36:05 GMT

Muni,

is other proxy interfaces are working fine without any issues and what are the versions of ECC and PI?

Thanks

Re: Successfactor Login interface error

Muniyappan — Tue, 28 Jul 2015 08:21:42 GMT

this is the first time interface is developed.

it is ECC 6.0 and PI 7.4 single stack sp 8.

when implemented note 1784054 getting below error after following

Regards,

Muni

Re: Successfactor Login interface error

former_member183908 — Tue, 28 Jul 2015 08:48:46 GMT

looks like some problem with the runtime components of SAP ECC which can't make proxy call to PO

what is the Eh level and SAP APPL and BASIS components?

In your second posting looks like you captured screen shots testing client from SPROXY in that case were you able to see any messages in SXMB_MONI in SAP ECC?

Thanks

Re: Successfactor Login interface error

Muniyappan — Tue, 28 Jul 2015 09:14:46 GMT

below is the component info.

i am not able to see the successful messages in sxmb_moni. i dont have access to soamanager to see messages as suggested in SOAP to SOAP scenario: XML messages not visible... | SCN

only error messages are present.

Re: Successfactor Login interface error

former_member183908 — Tue, 28 Jul 2015 09:42:56 GMT

i think this might be the problem your SAP PO is on 7.4 which is Netweaver 740 and SAP Basis in ECC is 700.if SAP notes does not help i would suggest to log a call with SAP or check with Basis team who has experience in this area for instance if you are still with Honeywell check with AERO basis team.we had a discussion on this about upgrading ECC 6 EH5 to EH7 which needs a mandatory PI upgrade to 740 to have sync in both ECC and PI proxy runtime environments.This was recommended by SAP before our upgrade.

i am not able to see the successful messages in sxmb_moni.

what do you mean by this were you able to see error messages in MONI?

check the SXMB_ADM parameters enabled for the logging of messages in MONI it can be either syn/asyn

Thanks

Re: Successfactor Login interface error

Muniyappan — Tue, 28 Jul 2015 09:59:51 GMT

I will have to log a call with SAP.Thank you pavan for your help.

logging is enabled. but no luck.

Thanks.

Re: Successfactor Login interface error

former_member183908 — Tue, 28 Jul 2015 10:13:24 GMT

good luck Muni and please update this thread with your findings.

Thanks

Re: Successfactor Login interface error

Muniyappan — Thu, 06 Aug 2015 11:31:52 GMT

I could see that issue was with dynamic header SetCookie is length more than 200. That is why it is failing in ECC. Same error did not happen in PI as it is in latest version and SP.


sap:DynamicConfiguration xmlns:sap=&#39;http://sap.com/xi/XI/Message/30'SOAP:mustUnderstand=&#39;1&#39;><sap:Record namespace=&#39;http://sap.com/xi/System/HTTP'name=&#39;SetCookie&#39;>BIGipServerP_PERFORMANCEMANAGER012.SUCCESSFACTORS.EU-80=!Qb35bxWVQClJSaPehJNTD7EYqYeaC51zB0C93QiJUqh3h7XbikKac2THNei6/tgJy0vaPTBCjvAyQzE=; path=/; HttpOnly, JSESSIONID=6886020214A518D2481773B7539A7D95.DC12BIZXSFAPI01; Path=/sfapi</sap:Record></sap:DynamicConfiguration>

Using Adapter-Specific Message Attributes in the Message Header - SAP NetWeaver Process Integration - SAP Library

Told the same to SAP support.SAP suggested to implement note #2028742 - XI runtime: Enhancing the dynamic header for Success Factors.

Now interface is working fine.

It would have been much better if the ECC error gives proper error description.

Thanks Pavan for your help.

Regards,

Muni

Re: Successfactor Login interface error

former_member183908 — Thu, 06 Aug 2015 11:35:47 GMT

Thanks for the update Muni really appreciate it

Thanks