Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Presentation layer
WebSphere Commerce uses Java Server Pages (JSP) to implement the view layer of the Model-View-Controller (MVC) design pattern. The view layer is in charge of retrieving data from the database through the use of data beans and formatting it to meet the display requirements. The view layers determines whether the request is sent to a browser or streamed out as XML. JSP files present a clean separation between data content and presentation.
WebSphere Commerce integration with WebSphere Portal
You can integrate WebSphere Commerce, a Business Application Service with WebSphere Portal, an Interaction Service. The Interaction Service provides core portal services (WebSphere Portal) that aggregate applications and content and deliver them as role-based applications. The Enterprise Service Bus (ESB) pattern is used for communication, mediation, transformation and integration with external systems. Using an ESB to integrate the Web services exposed from WebSphere Commerce to the WebSphere Portal promotes a loosely coupled design where the ESB manages the interactions styles between the WebSphere Commerce services and the presentation layer. You do not need to alter your presentation layer to support the protocol and format used by the WebSphere Commerce services. Instead, you rely on the ESB to perform tasks such as message transformation and protocol mediation. Neither WebSphere Commerce nor WebSphere Portal needs to change in order to communicate with one another. The ESB is used to act as an interpreter between the two systems and will translate the messages into a format the receiving system understands.
Preparing MVCPortlet for deployment
When development is complete, portlets are packaged into WAR files for deployment to the WebSphere Portal Server.

Preparing MVCPortlet for deployment

When development is complete, portlets are packaged into WAR files for deployment to the WebSphere Portal Server.

Before you begin

Develop, customize, and test your portlet in Rational Application Developer.

Procedure

Open Rational Application Developer.
From the Enterprise Explorer view, right-click the portlet project and select Export > WAR file. The Export wizard opens.
On the WAR Export page, enter the destination directory for the WAR file. A default name for the WAR file is automatically provided, but you can change it.
Do not select the Export Source files check box to exclude source files in the WAR file.
Select the Overwrite existing file to automatically replace an existing WAR file for this project.
Click Finish.