Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Web services and WebSphere Commerce
A web service is an interface that describes a collection of operations that are accessible through the network by using standardized XML messaging.
WebSphere Commerce Web services with JSP pages
A Web service is an interface that describes a collection of operations that are accessible through the network by using standardized XML messaging. A Web service is described using a standard, formal XML notation, called a service description. The service description includes all the details necessary to interact with the service, including its message formats (that detail the operations), transport protocols, and location. The interface hides the implementation details of the service, allowing it to be used independently of the hardware or software platform on which it is implemented and also independently of the programming language in which it is written. The foundation for Web services are standards such as simple object access protocol (SOAP), the Web Services Description Language (WSDL), and the Universal Description, Discovery, and Integration (UDDI) registry.
Understanding the WebSphere Commerce Web service framework
The goals of the WebSphere Commerce Web service framework are:
WebSphere Commerce as a service provider
When you enable business operations in WebSphere Commerce as Web services that can be accessed by external systems, WebSphere Commerce becomes the service provider.
Modifying an inbound Web service
To avoid having customization overwritten by future versions of WebSphere Commerce, we do not recommend that you modify existing inbound services. Instead, create a new version of the inbound service based on existing ones.

Modifying an inbound Web service

To avoid having customization overwritten by future versions of WebSphere Commerce, we do not recommend that you modify existing inbound services. Instead, create a new version of the inbound service based on existing ones.

Procedure

Determine the implementation command and mapping file for the inbound Web services.
Extend the existing implementation command if you need to.
Create a new inbound service use the your own implementation command in the CommandMapping section.