You need to have a proxy to handle your set-up.
1. It will enable switching to a new PI server.
a. SAP PO migration: You want to be able to move to a new server. You cannot move everything at once, so you have to do it one interface at a time.
b. High reliability system: You want to be able to quickly switch the SOAP server to point to the other server. You may have multiple instances of a PI/PO system; and may be wanting to decide which of the instances to use now.
2. You want flexibility to change the endpoint
3. Use a different port from the one you normally would (http://50000)
4. Create a separate DNS (Domain Name System) name
5. Use SSL (Secure Sockets Layer)
6. Update the endpoint – see SAP https://websmp230.sap-ag.de/sap/support/notes/1583506
7. Use a web dispatcher, Apache reverse proxy or hardware box to dispatch calls to PI
If you already have a standard set-up where you are using the PI’s http port for SOAP traffic, then you have to do some workarounds. You will still have to use that port. You can change the ICM/Web Dispatcher script to forward some of the SOAP calls to the new server you have. It may not be the best way of doing it, but it is feasible. When everything has been moved to the new server, you will be able to create a new proxy server on the old PI server domain name. After this step, you will be able to use that domain name for the new system.
By having a reverse proxy in front of your SAP PI/PO system, you will be able to handle requests. It will always be possible to change the requests to point to the newer server, based on some rules defined by you.