Design issue...

[Former Member]

XI Xperts,

<b>Note :</b> Though it would appear to be more of an ABAP design issue, the same is going to have a runtime effect on one of my XI scenarios, hence posting in XI forum :).

I have a custom RFC developed on ABAP stack of XI server. This RFC will be transported from DEV to QA / PROD in due course.

I access this RFC from Java code by exposing the RFC as a web service. When looked into the details of the generated WSDL, I could see that the hostname and relevant details of the DEV server are a part of the WSDL as below

<soap:address location="http://<b><HOSTNAME></b>:8008/sap/bc/srt/rfc/sap/<RFC_NAME_WSD>?sap-client=<b>010</b>" />

I generated a deployable proxy from this WSDL and and using it and everything works absolutely fine on DEV.

For sure I can't transport the deployable proxy as it is because it is generated from a WSDL pointing to DEV.

So the question here is :

1. Can I modify the the WSDL and make it

<soap:address location="http://<b>localhost</b>:8008/sap/bc/srt/rfc/sap/<RFC_NAME_WSD>?sap-client=<b>010</b>" /> and then generate deployable proxy from it?

Any issues foreseen with this?

<b>The Java code that accesses this could be an adapter module [may be on central / de-central AE] or a Java Proxy.</b>

2. Any other alternatives if anybody has tried?

Regards,

Amol

Message was edited by:

Amol Joshi

[Former Member]

Hello Amol ,

Yes u can modify the WSDL locatrion host address with u r host and port name along with the respective client value . It will work on the other server too.

Regards,

Keith