Service Oriented Integration (SOI) - Websphere Commerce Web Services

-
Service Oriented Integration (SOI) - Websphere Commerce Web Services

As part of the WebSphere Commerce transition to SOA, there is an effort to decouple components to allow re-use of WebSphere Commerce business services in other environments besides the WebSphere Commerce application. In order to support this decoupling, the core infrastructure is the first piece that needs to run independently so it can be leveraged in other environments as well. The request handling has changed to create a lightweight runtime environment that new and existing components can use. This lightweight runtime focuses on the processing of business object documents (BODs). This new architecture paves the road to SOA adoption by standardizing on how clients will talk with SOA components.
WebSphere Commerce now provides 4 SOI service modules -- logical groupings of business objects that have been grouped to standardize communication. These service modules are:
Member
Order
Catalog
Contract
The SOI modules ultimately maps to the ControllerCommand. And you would often extend the OOB commands for your custom logic - use EJBs for persistance much as the way as you did in WCS 6.0
( I can see a lot of v6 developers expressing a huge sigh of relief ). Most of the time what the developers struggle is how to map a service to a command name. I have put together a small diagram showing the complete flow - Taking a very common scenario - extending the Registration process to store custom membership attributes.




The sad part is that we may not be able to really see the "actionCode" being used in the method ( registerPerson in this example ) since we do not have the access to the source code ( I narrowed down the command by my past experience in v6 ) - but what IBM is done is help the developer community at large is provide the methodName to CommandName mappings directly in the following link:

 http://pic.dhe.ibm.com/infocenter/wchelp/v6r0m0/index.jsp?topic=%2Fcom.ibm.commerce.component-services.doc%2Fconcepts%2Fcwvcs.htm

 The following is a mapping for the MemberFacadeClient methods and the corresponding URL commands:
Map registerPerson(Map) - UserRegistrationAdd
Map updatePerson(Map) - UserRegistrationUpdate
Map addAddressForPerson(Map) - AddressAdd
Map updateAddressForPerson(Map) - AddressUpdate
Map deleteAddressForPerson(Map) - AddressDelete
Map registerOrganization(Map) - OrgEntityAdd
Map updateOrganization(Map) - OrgEntityUpdate
Map addAddressForOrganization(Map) - AddressAdd
Map updateAddressForOrganization(Map) - AddressUpdate
Map deleteAddressForOrganization(Map) - AddressDelete
If you really want to appreciate the actionCode concept , refer the below method used in the SOITutorialStoreFacadeClient.java 




Tutorial Link
 Tutorial: Creating a WebSphere Commerce web service module (SOI)

Comments

Post a Comment

Popular posts from this blog

Websphere Commerce Data Load using CSV \Websphere Commerce Data Load using XML

-
Websphere Commerce Data Load using CSV \Websphere Commerce Data Load using XML Data can be loaded into WCS tables using data load utility. Data load utility works in the steps as mentioned below. 1.Data Reader The data reader reads the input file, and transforms the input into a data object. Data objects are typically map objects. Eg: CSV data reader \XML Data Reader 2.Business Object Builder The business object builder instantiates the business object and populates it from the data in the data object. Eg:The table object builder 3. Business Object Mediator The business object mediator converts the business object into physical object. The table object mediator is always used with the table object builder. Eg: table-based mediator 4. Data Writer The data writer writes the physical object into the database. This tutorial uses the default data writer to write the generated physical o...
Read more

Websphere Commerce Catalog Subsystem

-
  Websphere Commerce Catalog Subsystem The Catalog Subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries, and any associations or relationships among them.    Master Catalog It is the single catalog that contains all products, items, relationships, and standard prices for everything that is for sale in your store. Every store in the Web Sphere Commerce system must have a master catalog. It is possible to share the master catalog across stores. Master Catalog Restrictions 1)The master catalog must be a proper tree, which means that there are no cycles. e.g.The parent category "Women" has a subcategory "WomenDress". It is important that WomenDress and any of WomenDress's subcategories like tops,jeans etc are not the parent category of "Women" category. 2)A catalog entry or category cannot belong to multiple parent categories in the master...
Read more

Calculation Framework in Websphere Commerce.

-
  OrderCalculateCmd OrderCalculateCmd invokes the Promotion engine. PromotionEngineOrderCalculateCmdImpl implements OrderCalculateCmd class. OrderCalculateCmd is invoked when we add, delete, update or merge item/s in cart. This command calculates the order  total based on the sequence in which calculationUsageId is passed into the command. WebSphere Commerce provides the below predefined calculation usages: Calusage_id    Description -1                         Discount -2                         Shipping -3                         Sales Tax -4          ...
Read more