Service binding

The service binding resides between the client library and the services. It provides the transport mechanism to pass data, using service data objects (SDOs), between the client and the service. This transport mechanism can be Web services or local Java binding.

 

Service Data Objects

SDOs are an implementation of the value object pattern. SDOs are used to hold data, and have methods to get and set this data. Additionally, they are able to serialize and deserialize themselves based on the transport mechanism, and keep a history of the changes they have undergone. In WebSphere Commerce, the benefit of using SDOs is that they start on the client side, in their Java form, serialize themselves to XML for transportation through Web services, and then deserialize themselves back into a Java object on the WebSphere Commerce Server. You do not need to transform input and output data for every stage of the processing lifecycle of a request, because the SDOs can change forms depending on where they are being used.

 

Transport types

There are two types of binding between the client library and the component facade implementation.

Local enterprise bean

The local enterprise bean connects the client to the component facade implementation in the local JVM. When the client and component facade implementation are deployed within the same application, the client should communicate with the component facade implementation though a local EJB call. The client uses the component facade's local enterprise bean to invoke the method that matches the intended service.

Web services

The Web service connects the client to the component facade implementation remotely. When the client and component facade implementation are deployed in separate applications, the client sends the service request using Web services as the transport layer. Because the client and component facade implementation are distinct applications, the Web service security is used for authorization.

Related Concepts

Service Data Objects (SDO)
WebSphere Commerce services functional architecture
6.0.0.1WebSphere Commerce use of Open Applications Group (OAGIS) messaging
WebSphere Commerce service module