Understanding 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:
- 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.- WebSphere Commerce as a service consumer
WebSphere Commerce Enhancements for version 6 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 JMS for Web services
JMS support for Web services is not enabled when WebSphere Commerce is installed. This is because the JMS resources are required to be set up or the WebSphere Commerce Server will report errors during start up. Enabling Web service over JMS support involves defining the JMS resources, defining a Messaging Listener Port, and deploying a Message Driven Bean.Related concepts
WebSphere Commerce Web services with JSP pages
Business Object Documents long description
Related reference