cancel
Showing results for 
Search instead for 
Did you mean: 

WSDL file - Adress Location Isuue

tharaka_fernando
Contributor
0 Kudos

Dear All,

In our SAP <-> Legacy systems, most of the transaction are integrated through WSDL (SOAP to Proxy) in PI. In WSDL file, at the bottom IP address of the SAP PI is used by the Legacy system to call the webservice. Please see below example for a snapshot of a WSDL  file.

..............................

...............................

<service name="SI_AutoSalesOrder_RequestService">

    <port name="SI_AutoSalesOrder_RequestPort" binding="s0:SI_AutoSalesOrder_RequestBinding">

      <soap:address location="http://10.105.12.65:50000/sap/xi/engine?type=entry&amp;version=3.0&amp;Sender.Service=BS_TE_EXAMPLE&amp;Interface=urn%3A%2F%2Fhayleysadvantis.com%2FTE%2Fexample%2FSD%2FIS01%2FAutoSalesOrder%5ESI_AutoSalesOrder_Request" />

    </port>

  </service>

</definitions>

Is there any other method to not use this IP address because the given IP is the Development Server IP (for example).But when this is transported to Production the Legacy System Developers need to change all the WSDL files from their end (IP address) to connect .

And we have a DR (Disaster Recovery) system.

When one server is down the other one is in active status. Under this scenareo Legacy System Developers are not in a position to change the IP address.

What is the Solution for this?

Thank you all in advance.


Accepted Solutions (0)

Answers (2)

Answers (2)

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

there is not. If you need to execute the interface in other instances you need to provide a WSLD with the proper endpoint.

to do this you have two option. create the WSDL in the sender agreement in each instance or change the ADDRESS LOCATION manually, remember you must know the Instance name and Business System.

Regards

Former Member
0 Kudos

Hi Tharu,

The regular process is that you need to provide the WSDL of each instance (i.e. DEV, QA, PROD) separately, since these are different servers (as you mentioned). Thus I assume there is no other possibility to provide different WSDLs with different end point URLs.

Best Regards

H.