Developing > Persistence layer > WebSphere Commerce integration with WebSphere Portal > Customizing WebSphere Commerce Portal integration

---

 

Using 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.

Create a JSR portlet is beyond the scope of the WebSphere Commerce documentation. See Rational Application Developer online help for detailed instructions on how to create a new portlet implementation class and other available portlet APIs provided by the WebSphere Portal product.

• 
  WebSphere Commerce Portal integration tracing and logging
  Portlets can write message and trace information to log files, which are maintained in the WebSphere Portal server's log directory. The log files help the portal administrator investigate portlet errors and special conditions; they also help the portlet developer test and debug portlets.

Last updated: 25 November 2009