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

[Former Member]

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=Evon...

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

http://sappit1:50100/XISOAPAdapter/MessageServlet?senderParty=&senderService=EvonceOSB_PEMP_T&am...

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

[baskar_gopalakrishnan2]

You host webservice on the sender side.. You dont need to create business system for soap. You can use Business service or Business component and maintain the same across environments. You move this component to other environments from dev to QA to prod. This way you maintain the same WSDL URL.

[former_member854360]

Hi ,

It is recommended to use different environmemt for Dev,testing,Production. So your PI server host name and port will be different for every environment.

So URL will differ.

however if you dont want to change Business system Name then go for BUSINESS SERVICE/COMPONENT instead of BUSINESS SYSTEM. It will be same in every environment and also dont need to maintain anything in SLD