Develop > Persistence layer > WebSphere Commerce Web services with JSP pages
Understand the WebSphere Commerce Web service framework
The goals of the WebSphere Commerce Web service framework are:
- To promote structured WSDL descriptions to define the objects used for invoking the service.
- To promote the adoption of industry-accepted standards for service definitions, such as the Open Applications Group Integration Standard (OAGIS), with the intent to achieve greater interoperability with other systems that have adopted the same standards.
- To promote separation between client and server through publishing (that is, publicly defining) the XML schema of the data objects used when invoking the service.
- To promote use of Web service development tools, such as WebSphere Commerce Developer or Rational Application Developer, for developing Web service clients that can communicate with WebSphere Commerce.
The following topics explain how WebSphere Commerce fits into the service provider and service consumer roles:
Web service caching
WebSphere Commerce Web services with JSP pages
WebSphere Commerce as a service consumer
WebSphere Commerce as a service provider
Customize the Web service client invocation XML file
Configure WebSphere Commerce Developer for Web service development
Create a Web service client API for WebSphere Commerce
Customize existing outbound service requests
Deploy an inbound Web service
Enable JMS for Web services
Enable WebSphere Commerce as a service consumer
Enable WebSphere Commerce as a service provider
Modify an inbound Web service
Additional information about Web services
Inbound Web services provided
Service-oriented outbound integration points
WebServicesRouter Web module configuration
Business Object Documents long description