SoapRPC was used for invoking an RPC/Encoded web service and soapHTTP for invoking a Document/Literal web service.
There are no direct replacement services, but in IS 7.1 with the introduction of Web Service Descriptors,
a new service pub.client:soapClient was introduced that would be used to invoke either style (RPC/Encoded or Document/Literal, or even the new RPC/Literal) web services going forward.
So while soapClient is not a direct replacement service for either of the other two old services, it kind of functionally replaces both.
by the way pub.client:soapRPC and pub.client:soapHTTP are still present and functional in the IS 9.9 for backward compatibility.
So, if you have migrated from IS 6.5 to the newer versions of the webMethods. Still the webservices developed in IS 6.5 should function properly.
But if you want to use pub.client:soapRPC service to create webservices on the newer versions of webMethods , then it is an obvious no-no. You should go with the webservice descriptor approach.
#webMethods#B2B-Integration#Integration-Server-and-ESB