Sample assets for the catalog programming model
The catalog programming model sample assets and directory structure are enabled with the WebSphere Commerce starter store enhancements feature.
Using the catalog programming model sample assets
Sample updated storefront JSP files are provided to aid in the understanding of how to use and customize the new storefront services. As the catalog programming model uses the WebSphere Commerce search framework, search-based navigation must be enabled in starter stores to use the SOA services.
To
enable the catalog programming model sample assets and directory structure,
you must perform the following tasks:
- Enabling starter store enhancements
- Publishing the Madisons enhancements store archive
- Enable Search-based navigation in the Madisons starter store
- Copy the sample JSP file assets into the Madisons starter store
directory structure, replacing the existing files with the catalog
programming model sample files.The sample JSP file assets are located in the following directory:
WCDE_installdir/components/store-enhancements/samples/SOACatalogStorefrontServices/stores
Sample JSP file assets
The sample JSP file
assets and the usage of the assets are listed in the following table.
Note: The
sample JSP file assets do not provide full storefront coverage. The
JSP file assets do not contain sample assets for the following storefront
locations for the Madisons and Elite starter stores:
- Quick Info
- Shopping Cart and Shopping Cart Flow
- Mini-Shopping Cart
- Bread Crumb Details
- Order status and order details (in My account)
- Gift registry
- Requisition list (Elite only)
- Saved orders (Elite only
| JSP file | Usage |
|---|---|
|
These main product display JSP files call the new service using the IBM_Store_All access profile. |
|
The product compare JSP files calls the new service using the IBM_Store_Details access profile. |
| CatalogAttachmentAssetsDisplay.jsp | The attachment display JSP file uses the site map. |
| CatalogEntryAttachmentAssetsDisplay.jspf | The JSP file calls the service using the IBM_Store_CatalogEntryAttachments access profile to return attachments for the product display attachments tab. The name, short description and long description displayed in the JSP file comes from the attachment target table (meta data) instead of the relationship table. |
|
The product display JSP files use the new noun passed in from the calling JSP file. These JSP files display all the main elements of the product display including price, merchandising, components, attachments and attributes on the product display page. |
| AttachmentImagesDisplay.jspf | The JSPF file adds angle view images to the product display JSP files. |
| MerchandisingAssociationsDisplay.jsp | The merchandising display JSP file uses the new service noun passed in from the calling JSP file. This JSP file displays merchandising information on the product display page. |
| CatalogEntryPriceDisplay.jspf | The price display JSPF file uses the new service noun passed in from the calling JSP file. This JSP file displays pricing information on the product display page. |
|
The contract price JSP files use the new service noun passed in from the calling JSP file to display contract information in the Elite starter store. These files display contract and pricing information on the product display page. |
|
These JSP files use the new service noun to display information on the starter store pages. |
Store functions
The following store functions
use the Catalog programming model services:
- Search Engine Optimization (SEO)
- Dynamic kit integration with Sterling Configurator