Client Proxy Question

[Former Member]

Hi all,

Initially, when we have created a client proxy in ECC 5.0 with Oracle on Windows,

we have chosen Local File as the WSDL source. We had the WSDL saved locally.

This way we have generated a Client Proxy in SE80.

Then we created a logical port using LPCONFIG.

Since this the default logical port, we just saved it with all the settings imported

from the WSDL definition.

This way the Client proxy was working fine.

The doubt that I have is, later on, if we want to just change the URL under

call paramters in LPCONFIG to the URL of the WSDL residing on some

other server(Non SAP), will the client proxy work?

Regards,

Vishnu

[Former Member]

>The doubt that I have is, later on, if we want to just change the URL under call paramters in LPCONFIG to the URL of the WSDL residing on some other server(Non SAP), will the client proxy work?

Yes.

[Former Member]

Hi Gaurav,

Thanks for your response.

When I try to use the URL provided by the Client, below is the error that I am getting in dev_rfc0,

ERROR 01:44:52: SOAP Application CL_SOAP_APPLICATION_CLIENT
->IF_SOAP_APPLICATION_CS~EXECUTE_PROCESSING() A SOAP Runtime Core
Exception occurred in method XP_READ_TAG of class CL_SOAP_XP at
position id 1 with internal error id 112 and error text no
extended error message (SOAP_ESERVER) (fault location is 1 ).

Regards,

Vishnu

[Former Member]

In such case please check if binding already exist in wsdl and system is picking it up from wsdl not from lpconfig. If required try to regenerate proxy to reflect correct changes.

Regards,

Gourav

[Former Member]

Hi Gaurav,

Looking at the error below, the binding is happening.

However, there is a return code 503. And SAP is not able to access the

Webservice located at the other server(Non-SAP).

INFO 01:44:43: SOAP SESSION Protocol CL_SOAP_SESSION_PROTOCOL
->IF_SOAP_PROTOCOL~PRE_PROCESS() SOAP Session Protocol
preprocessed

INFO 01:44:43: SOAP Transport Binding CL_SOAP_HTTP_TPBND_ROOT
->IF_SOAP_TRANSPORT_BINDING~SEND() Try to send message ( DEST =
,PATH = ,URL = http://server name:portno/ ,SOAP Action = "ROI_R3
_DF.roiSAPCreateOrder" )

INFO 01:44:43: SOAP Transport Binding CL_SOAP_HTTP_TPBND_ROOT
->IF_SOAP_TRANSPORT_BINDING~SEND() Message sent

INFO 01:44:43: SOAP Transport binding CL_SOAP_HTTP_TPBND_ROOT
->IF_SOAP_TRANSPORT_BINDING~RECEIVE() Try to receive message

INFO 01:44:52: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->HANDLE
_STATUS_CODE() Received return code 503 ( not available )

ERROR 01:44:52: SOAP Message CL_SOAP_MESSAGE->IF_SOAP_MESSAGE
_PART~INIT_FOR_DESERIALIZE() A SOAP Runtime Core Exception
occurred in method XP_READ_TAG of class CL_SOAP_XP at position id
1 with internal error id 112 and error text no extended error
message (SOAP_ESERVER) (fault location is 1 ).

Regards,

Vishnu

[Former Member]

Can you test if you can access new wsdl url from your SAP systems? It is possible that particular url is not accessible from SAP landscape. Test from SOAP UI as well.

Regards,

gourav

[Former Member]

Hi Gaurav,

The test with SOAP UI is succesful.

For some reason SAP is not able to access the webservice with the URL.

SAP's Support guys tell me that there has to be some suffix at the end of the URL.

However my client say's that the given URL is all that is required to access the webservice.

And I am not able to figure out what the problem could be.

Thanks for your time.

Regards,

Vishnu

[Former Member]

Hi,

You don't need any suffix, ask your basis guy if internet communication from SAP system is opened or any proxy/firewall settings need to be changed etc.

You can also test this by creating RFC connection in SM59 for given url, if RFC test is ok then it is working else some configuration need to be changed.

Regards,

Gourav