cancel
Showing results for 
Search instead for 
Did you mean: 

WebServices: Reuse of SAP XI 3.0 WSDLs with SAP PI 7.x

Former Member
0 Kudos

Hi,

interesting question...

when migrating from an SAP XI 3.0 system to SAP PI 7.x (by installing a new PI and migrating the data to the new instalation)

is it possible to reuse the published WSDLs from XI?

Is it enough to simply provide the new address of the system to partners?

Or is it required to generate a new WSDL and send this to partners.

When I compare a WSDL from the old XI system with one from another PI there are some diferences in the location identifiers...

XI:

location="http://111.111.11:50500/XISOAPAdapter/MessageServlet?

channel=:PX0:CC_ORDER_CREATE_SOAP_SENDER"/>

PI:

location="http://test01.global.test.com:50220/XISOAPAdapter/MessageServlet?senderParty=&senderService=INTEGRATION_SERVER_PD0&

receiverParty=&receiverService=&interface=MI_PURCHORDER_CREATE&

interfaceNamespace=http%3A%2F%2Fwww.test.com%2Fexternal%2Finterfaces"

What I identify is that XI url provides a channel but no message interface!

I would expect there are no changes to the mesge itself!

Ideas an comments are welcome!

Thank you!

Best regards

Dirk

Accepted Solutions (1)

Accepted Solutions (1)

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi,

If you are not changing message interface name and no changes in WSDL structrues then you can use same stuff, only in port detials/Host details will wary.

I suggest you to publish sender agremennts in Service registry in PI 7.1 system instead of genarating manually.

checkout below blog

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23725

Regards,

Raj

Answers (2)

Answers (2)

former_member184681
Active Contributor
0 Kudos

Hi Dirk,

In general, this is one of the reasons why ESR (Development) and ID (Configuration) are separated in PI. In case nothing changes in the development part, you wouldn't have to worry about generating new .wsdl files. I also know from my experience that 3rd parties responsible for sender/receiver systems might prefer changing connection details like URL manually instead of importing the .wsdl file again. So as far as I know, it is enough if you provide them with proper URL for the WS calls.

Hope this helps,

Greg

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Though there is no changes in service definition in terms of structure, Still I might want you to create WSDL using the sender agreement and pass it to the partners. During WSDL creation the wsdl url location is identified and added in the wsdl. If you dont want to create wsdl then pass the new url address. If the port number or instance or anything changed then you might have to take those changes too.

Example if your new installation instance number is 01 then port becomes 50100