Thursday, 4 July 2013

WebSphere Commerce Application Layers:Part2

Various layers that compose the application architecture:Part2

Business processes
Represent the processes available in WebSphere Commerce divided by business model. 
The business processes are divided into three areas: 
Administrative processes 
Processes that are used to administer a site, a store, or an organization.
Starter stores 
Starter stores contain sample processes that would be followed by customers of the store. Use the processes described in starter stores as a guideline, or a starting point, for site development. Changing or adding a process to a starter store processes will require changes to the site design.
Solution:
A solution describes the high-level view of how all the administrative processes and starter store processes fit within the framework of the overall business model. A solution combines processes into a coherent picture which explains the relationship between the various process groups.
 
Presentation layer

The presentation layer is responsible for displaying results. By default, there are two supported types of presentation layers supported: Web and rich client. For the Web presentation layer the display is rendered using JSP files, whereas, for the rich client the presentation is rendered with Eclipse views and editors implemented using SWT components.
Service layer

The service layer, implemented using OAGIS(Open Applications Group Integration Specification)* messages, is a channel-independent mechanism that can access WebSphere Commerce business logic. The service layer segregates the implementation of business logic such as order and catalog. This segregation permits the underlying implementation to change without requiring that the caller change. All clients, including Web clients and back-end services, go through the service layer to run business logic. The service layer supports two transport mechanisms: local Java binding and Web services.
 
Business logic

The business logic layer is where business rules are implemented independent of the presentation layer. Business logic is implemented using the command pattern. Two types of commands are implemented:
  • controller commands - accessible by the presentation layer and used as a coordinator of tasks.
  • task commands - not accessible by the presentation layer but called from the controller commands. This command type is used to implement business rules.
 
Persistence layer

The persistence layer records the data and operations of the WebSphere Commerce system. The persistence layer represents entities within the commerce domain and encapsulate the data-centric logic required to extract or interpret information contained within the database. These entities comply with the Enterprise JavaBeans specification.
These entity beans act as an interface between the business components and the database. In addition, the entity beans are easier to comprehend than complex relationships between columns in database tables.
 
Database schema
 
WebSphere Commerce database schema, which includes over 600 tables, is designed specifically for e-commerce applications and their data requirements. The database schema supports persistence requirements for the WebSphere Commerce subsystems (Order, Catalog, Member, Marketing, Trading). WebSphere Commerce supports both DB2 and Oracle relational databases. Oracle is not supported on WebSphere Commerce - Express. In addition, to DB2 and Oracle, the development environment also supports Apache Derby.

*  OAGIS is a practical use of XML to enable integration

Wednesday, 3 July 2013

WebSphere Commerce Application Layers :Part1

Various layers that compose the application architecture:Part1


Business models:In WebSphere Commerce represents the purpose of the site in which the WebSphere Commerce product may be used.A business model describes a scenario in which various parties use WebSphere Commerce to achieve their needs.

The Business models provided by WebSphere Commerce are:

B2B:  In a typical B2B direct business, businesses purchase goods or services directly from another business. The selling business can be a wholesaler, a distributor, a manufacturer, or a retailer who sells to buyers from other businesses
B2C:In a typical consumer direct business, customers buy directly from the business, usually a retailer, as shown in this diagram. The business can be a retailer, a manufacturer who sells their goods directly to consumers through their own retail outlet, or any other business that sells goods or provides services directly to consumers. For example, a business that sells to consumers directly through a catalog would be considered a consumer direct business.

Demand chain:A demand chain is composed of the enterprises that sell a business's goods or services. For example, a demand chain may be composed of buyers who initiate the sales transaction, the resellers who sell the manufacturer's goods, and the manufacturer who creates the goods.r a demand chain may be composed of the resellers who sell a manufacturer's goods, the manufacturer who makes the goods, and the distributors who supply the manufacturer's goods to the resellers. Demand chains also support direct sales channels, in which the demand chain owner sells directly to consumers or business partners.

In this example, buyers purchase goods from a manufacturer's resellers (channel partners). Resellers, in turn, obtain the goods from the manufacturer, via the manufacturer's hub.

Demand chain stores:The demand chain owner may create a site with stores for its channel partners, such as resellers or distributors. This reduces the infrastructure costs to the reseller or distributor who may not have the expertise or capital to create and maintain their own site.

Extended Site: A site that allows selling organization to provide unique storefronts for different enterprise customers, different geographical customers.
 The business can customize sites by:
  • geography
  • brand
  • market segment
  • customer
For example, different geographical areas might have unique legal and tax regulations.

WebSphere Commerce common architecture

WebSphere Commerce is multichannel-enabled i.e., can support transactions across various sales channels.That support multiple presentation layers, responsible for displaying results, which decouple control logic from business logic.

The preceding diagram depicts how WebSphere Commerce supports two channels: the Web channel and the sales channel. For the Web channel the presentation is rendered using JSP pages and the Web controller layer uses Struts. For the sales channel, the display uses the Eclipse rich client technology.