web service problem (Timeout)

[Former Member]

hello

i hope this is the right category to post my problem

i want to use the service "customerCRMChangeRequestConfirmation_In"

but i get this error message: "Error getting response; java.net SocketTimeoutException: Read timed out.

on my search to fix this problem i found the SAP Note 826419.

with following advice:

===========================================================================================

Version NW 7.10

• Using NetWeaver Administrator

o For standard Web service deployable proxy:

1. Open SAP NetWeaver Administrator in a browser: http:// "Web Services Administration".

3. Choose "Proxy Definitions by Name" and click "GO".

4. Select the proxy you want to configure.

5. Choose the "Configuration" tab.

6. Choose the "Logical Ports" tab.

7. Select the logical port you want to configure and choose "Edit".

8. Choose the "Transport Settings" tab.

9. Edit the "Max wait-time for HTTP response (in milliseconds)" field.

10. Click "Save" to save the settings.

============================================================================================

but in my Transport Settings are no "May wait-Time for HTTP response-field"

what is the problem? i have an SAP CRM IDES System with Netweaver 7.1

do I need to install an sp?

I also found this solution for my read time out problem:

http://wiki.sdn.sap.com/wiki/display/TechTSG/%28WSR%29Problems-P01

but this solution with "Visual Administrator" is for java stack, right?

thank you for your help!

kind regards

sven möller

[Former Member]

Hi Trevor

i doing my internship at sybase an sap company.

so i work with an sap crm ides system which was installed by me.

my exercise is to develop a mobile applikation with sap web services. the software for this is sup (sybase unwired platform).

i'm testing my services with the "soapUI" tool.

the service "CustomerCRMByIDQueryResponse_In" worked but the service to Change a Customer gets this time out exception.

[Former Member]

Hi Sven,

There could be several reasons for this timeout but seeing as this is an IDES System things should generally work fine (it's not always the case though).

I would suggest increasing the socket timeout on SoapUI & then test the webservice again. If you are unsure of how to do this just Google 'SoapUI Test Case Socket Timeout' or something similar. You first need to create a test suite/case & then you can control the socket timeout on SoapUI.

Just in case, I would also check that the webservice service is configured correctly by launching transaction code SOAMANAGER from the IDES CRM & searching for this service (look for the change customer service under service providers). Just verify that all endpoint configuration is correct.

I would also verify if you have the necessary authorizations (for your IDES login user) to change a customer.

Lastly, I would setup a trace/recording using the ICF Recorder for your IDES login user (Google 'SAP ICF Recorder' for correct usage). Turn on the recorder to trace your incoming request in IDES & trace the outgoing response from IDES.

You could also try viewing Transaction Codes ST11 & ST22 that trace incoming requests into the IDES Application Server. This may highlight any authorization related issues.

Best Regards, Trevor