Probelm while connecting from PI server to BAPI (exposed as webservice)

[Former Member]

hi friends

i exposed BAPI as webservice in R/3 system .

when i am trying to test from tcode wsadmin with

"http://10.136.148.36:8002/wsnavigator/jsps/explorer.jsp?description=WebServiceZZBAPI_USER_GET_DETAIL&name=ZZBAPI_USER_GET_DETAIL&wsdl=http%3A%2F%2Finst50053318.BLR4.SAP.CORP%3A8002%2Fsap%2Fbc%2Fsrt%2Frfc%2Fsap%2FZZBAPI_USER_GET_DETAIL%3Fsap-client%3D001%26wsdl%3D1.1"

its giving reponse when i test it.

if directly opens with Internet Explorer through the following link

"http://inst50053318.blr4.sap.corp:8002/sap/bc/srt/rfc/sap/ZZBAPI_USER_GET_DETAIL?sap-client=001" its showing HTTP 500 - Internal server error in R/3 system.

in PI SERVER i am trying to call this webservice using SOAP adapter with scenario HTTP->SOAP.

i configured the soap adapter using URL "http://inst50053318.blr4.sap.corp:8002/sap/bc/srt/rfc/sap/ZZBAPI_USER_GET_DETAIL?sap-client=001&wsdl=1.1".

nw its giving the respose like " HTTP 500 TIMED OUT ERROR" as wellas showing Application server error".

please suggest me with ur valuable inputs

thanks & regards

Ravi

[Former Member]

HI,

Can u please check the timeout settings from SXMB_ADM .

Refer the belog for more details.

/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

Thnx

Chirag

[Former Member]

hi chirag...

even though i increased the Timed_out parameter value as 80000(previously it was 60000), but

no change in response (still it showing the error).

please go through the respose which given as response in my HTTPCLIENT and please suggest me

accordingly.

Result:

http-Status: 500 Timeout

Payload:

thanks &regards

ravi

[Former Member]

Hello

Check if http://inst50053318.blr4.sap.corp is rechable from XI. in internet explorer try using IP instead of domain name.

Regards

Rajeev

[Former Member]

hello rajiv

no, i am unable to reach the Service through the XI server.

can u please suggest me , what are all the steps i need to follow for connecting the R/3

from my PI server.

thanks & Regards

Ravi

[Former Member]

HI,

Have u maintained the 4 RFC destination and run the SLDCHECK transaction on XI.

DO let me know the result of SLDCHECK.

AI_RUNTIME_JCOSERVER

Points from the Integration Server to the mapping runtime. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used for the mapping runtime, value mapping, and the exchange profile).

AI_DIRECTORY_JCOSERVER

Points from the Integration Server to the Integration Builder. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used to refresh the runtime cache).

LCRSAPRFC

The RFC destination LCRSAPRFC is required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile.

SAPSLDAPI

The RFC destination SAPSLDAPI is required for the connection to the SLD. It is used by the ABAP API.

INTEGRATION_DIRECTORY_HMI

For Cache Updates

Ur HTTP time out problem is repsolved or still u r facing it.

Thnx

Chirag

[Former Member]

result of SLDCHECK in PI server is good.

but i think there is problem with R/3 webservice.

when i am trying to access the soap service through the explorer of my desktop its showing error page.

wsdl of the service i can able to see through the link "http://inst50053318.blr4.sap.corp:8002/sap/bc/srt/rfc/sap/zzbapi_user_get_detail?sap-client=001&wsdl=1.1"

but i cant open the service with "http://inst50053318.blr4.sap.corp:8002/sap/bc/srt/rfc/sap/zzbapi_user_get_detail?sap-client=001;"

please suggest me accordingly'

thnaks & Regards

Ravi

[Former Member]

Hi Ravi,

Did you also try this url..

http://inst50053318.blr4.sap.corp:8002/sap/bc/srt/rfc/sap/zzbapi_user_get_detail

Are you getting the same error?

I think the error could be related to authorization. Not sure which authorization object that could be.

Can you try with a user who has SAP_ALL and see if it works.

Regards,

Sumit

[nikhil_bose]

you are getting error in SOAP Envelope ?

try generating WSDL by document style and i think you are missing the tail part in the url. add &wsdl1.1 to the url. it will do work.

thanks

nikhil

**reward if helpful

[Former Member]

Hi Nikhil,

If you see Ravis message, he can generate the wsdl.

See the link posted by him he has added &wsdl1.1.

Regards,

Sumit

[nikhil_bose]

dear sumit,

"To Err Is Human, To Forgive Divine".

Thanks for your effort anyway.

tell me if the &WSDL1.1 part is avoided, we can still use the WSDL message ? I think, or it really does display a SOAP error.

Could you tell me Mr. summit, where we have to use RPC Style WSDL and Document Style WSDL ?

thanks again,

nikhil