The application developer for Commerce Enabled Portal will complete the same tasks as the application developer for non portal enabled WebSphere Commerce, with a few additional tasks. As a result, you should follow this roadmap in conjunction with the Application developer information roadmap provided with the base version of WebSphere Commerce.
Recommended reading
Before beginning any application development tasks for Commerce Enabled Portal, review the following information:
- The WebSphere Portal information center, for an understanding of how WebSphere Portal works and more information about working with portals.
- Commerce Enabled Portal
- Commerce Enabled Portal architecture
- Commerce Enabled Portal portlets
- Commerce Enabled Portal development environment
- Commerce Enabled Portal samples
- Application developer information roadmap
- Guidelines for adding portal function to your store
- Adding portal function to your store
Commerce Enabled Portal application development tasks
The application developer completes five main tasks in Commerce Enabled Portal:
Develops storefront pages
The developing storefront pages task of Commerce Enabled Portal is the same as developing storefront pages for the base version of WebSphere Commerce, with a few exceptions in how you develop JSP files.
- For information about developing storefront pages, see JSP page designer.
- Review the information in Guidelines for adding portal function to your store and Adding portal function to your store.
- For specific information about developing JSP files for Commerce Enabled Portal, see Commerce Enabled Portal JSP file guidelines. Also review Commerce Enabled Portal JSP file tag library.
- If you are creating a Commerce Enabled Portal that can be accessed by Wireless Access Protocol (WAP), see Wireless Markup Language (WML) JSP files.
- When Creating store pages that can be cached, review the following Commerce Enabled Portal specific information about caching: Caching in Commerce Enabled Portal.
Develops portlets
The developing portlets task is unique to an application developer working with Commerce Enabled Portal. For a better understanding of portlets, review the information about portlets in the WebSphere Portal information center. For information specific to developing a Commerce Enabled Portal portlet, review the following:
- Commerce Enabled Portal portlets
- Creating a Commerce Enabled Portal portlet
- Synchronized content through dynamic context
Develops store data
Store data for a Commerce Enabled Portal is developed in the same manner as for the base version of WebSphere Commerce. For more information, see Data developer.
Develops store business logic
Store business logic for a Commerce Enabled Portal is developed in the same manner as for the base version of WebSphere Commerce. For more information, see Store programmer.
Integrates with a back-end system
Integration with WebSphere Portal is done through the portlets. For more information see Commerce Enabled Portal portlets. For integration between WebSphere Commerce and other systems, see Integrator. For integration between WebSphere Portal and other systems, see the WebSphere Portal information center.
Samples
For many sites, development begins with modifying one of the samples provided with Commerce Enabled Portal. The samples include a complete set of JSP pages and portlets necessary for a fully-functional Commerce Enabled Portal. The JSP pages and portlets may be modified as necessary for use in your store. For information about the samples, see Commerce Enabled Portal samples. Since the samples provided with Commerce Enabled Portals are based on the starter stores provided with WebSphere Commerce, you can also refer to the topics in the Easy start section.
Tutorials
Complete the tutorial in a sequence. For more information see, Commerce Enabled Portal tutorials.