Develop > Presentation layer > WebSphere Commerce integration with WebSphere Portal
Customize WebSphere Commerce Portal integration
There are two main approaches to Customizing WebSphere Commerce Portal integration. Using the provided WebSphere Commerce MVCPortlet class (MVC style), and Using WebSphere Portal general programming techniques (Web service style).
- Use the provided WebSphere Commerce MVCPortlet class (MVC style)
The WebSphere Commerce Portlet, MVCPortlet, is a generic implementation of the MVC pattern. It allows you to set up one or more portlets, each with its own configuration, to call various WebSphere Commerce services. The goal of this MVCPortlet is to cleanly separate the model (application logic that interacts with a database) from the view (HTML pages presented to the client) and the controller (instance that passes information between view and model). This programming pattern greatly reduces code redundancy as well as maintaining a consistent behavior across all WebSphere Commerce portlet actions.
- Use WebSphere Portal general programming techniques (Web service style)
In this style of programming, a portlet can invoke the backend Web services provided by WebSphere Commerce or a vendor directly without the need for a client library. Although this model is less restrictive than the previous one, you have to write more code and configuration for any customization logic.
Related concepts
Best practices for designing store pages that contain MVC Portlets
WebSphere Commerce integration with WebSphere Portal
Use WebSphere Commerce services in portlets
Populate data on a portlet JSP file using the WebSphere Commerce foundation tag library
WebSphere Commerce Portal integration architecture
Related tasks
Add or customizing a portlet using the MVCPortlet class
Secure HTTP requests on WebSphere Portal