BOD and SOI

-

BOD 


 BOD uses pattern matching and DSL to the enter the database


SOI


 SOI uses controller commands\data beans \access beans.
Two ways to customize SOI : 
1. One way is to take advantage of the UserData hooks within the existing types to pass unstructured      information.
2. The other way is to use the Overlay methodology.

The limitation of this method is UserData provides the ability to pass name-value pairs only.


Overlays, a part of the OAGIS model, extend complex types similar to the inheritance model in Java. Within the Overlay model, you extend your complex type defined within the noun and generate Java code to represent that complex type. More specifically, where you referenced the default WebSphere Commerce version of the complex type, you reference your new version of the complex type and substitute it in. Within the client server framework, when the complex type is sent from the client to the server the business logic retrieves your version of the extended complex type. This model provides another way to add additional information, as it allows you to create structured Java objects to better represent the data that you want to flow from one system to another

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