When providing a service for public use, the provider may wish to create and publish an abstraction to the original service to insulate consumers from anticipated changes to the original service. This is done by creating a public SOAP service that points to the original service and publishing the interface for the public SOAP service in place of the original service. This simplifies the task of switching the location of the original service by shifting responsibility for updating services from consumers to the provider. Thus, the change can be accomplished by a single action of the provider, instead of requiring a separate action by every consumer. The change is accomplished by the provider editing the abstracting public SOAP service, then redeploying it. This instantly updates all consumers so that subsequent service requests use the updated service.
Updating Without the Use of an Abstract Service
If an abstracting public SOAP service is not used and an update to the service location or implementation is required, then each consumer of the original service requires updating.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com