Skip to Content
0
Former Member
Aug 04, 2011 at 11:44 AM

Sender SOAP Adapter - how to avoid changes of URL for diferent environments

108 Views

Dear experts,

we have a concern with transports of PI objects in our environment.

Situation:

When we transport SOAP Sender objetcs in PI from Dev to Test the URL (Endpoint) changes automatically the hostname and the business system (target system in SLD). For example:

In Development to call the Web Service (Sender SOAP Adapater):

http://sappid1.evonceib.local:50100/XISOAPAdapter/MessageServlet?senderParty=&senderService=EvonceOSB_PEMP_D&receiverParty=&receiverService=&interface=PEMP_PagadoresMaintain_Async_Out_WS&interfaceNamespace=urn%3Aonce%3Asppemp%3Amanagedatosdepagadorpa_in_pemp

In Test to call the Web Service (Sender SOAP Adapater):

http://sappit1:50100/XISOAPAdapter/MessageServlet?senderParty=&senderService=EvonceOSB_PEMP_T&receiverParty=&receiverService=&interface=PEMP_PagadoresMaintain_Async_Out_WS&interfaceNamespace=urn%3Aonce%3Asppemp%3Amanagedatosdepagadorpa_in_pemp

Problem:

The consuming side only wants to have one endpoint and don't want to touch the development when transporting the consumer. Generally to find a work around via DNS aliases for the hostname should solve the prefix of the URL, but how to handle the difference of Business Systems senderService=EvonceOSB_PEMP_D and senderService=EvonceOSB_PEMP_T in the URL?

In the SLD I can not maintain two BS with the same name, when I do not define a transport target the import fails.

So anybody has an idea how to get exactly the same URL for diferent environments?

Thank you in advance,

Best Regards,

Karsten Blankenstein