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.
No comments:
Post a Comment