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 consumer
WebSphere Commerce provides features and integration scenarios that enable WebSphere Commerce to act as a service consumer, especially with order management systems (OMS) and enterprise resource planning systems (ERP).
Enabling WebSphere Commerce as a service consumer
WebSphere Commerce can consume a business operation defined by an external system as a Web service. In this scenario, WebSphere Commerce acts as the service consumer to an external system.

Enabling WebSphere Commerce as a service consumer

WebSphere Commerce can consume a business operation defined by an external system as a Web service. In this scenario, WebSphere Commerce acts as the service consumer to an external system.

Procedure

Identify an external system with business logic that WebSphere Commerce needs to consume.
- If not already provided, create a Web service on the external system to provide the business logic. WebSphere Commerce uses a Web Service Definition Language (WSDL) that is based on the OAGIS WSDL to make outbound service requests to external systems.
- If the external system does not use the same WSDL, but has an existing service API defined, mediation is required to transform outbound service requests and responses between the two formats.
Customize the Web service client invocation XML file.
Create a Web service client API for WebSphere Commerce to construct the outbound message.
Identify the business process (task commands or controller commands) within WebSphere Commerce that consume the service. Use Service-oriented outbound integration points as a reference. The task command should call the client API to send the message.