HCL Commerce enterprise beans

The persistence layer within the HCL Commerce architecture is implemented according to the JPA component architecture. However, a small number of stateless session beans are used to handle intensive database operations, such as performing a sum of all the rows in a particular column.

Public enterprise beans are used by commerce applications, and can be both used and extended. These public enterprise beans are organized into the following EJB modules:

  • Catalog-ProductManagementData
  • ContentManagement-WorkspaceFlowData
  • Enablement-BaseComponentsData
  • Enablement-RelationshipManagementData
  • Enablement-TicklerData
  • GiftRegistry-BaseComponentsData
  • GiftRegistry-OrderIntegrationData
  • Marketing-CampaignsAndScenarioMarketingData
  • Marketing-CustomerProfilingAndSegmentationData
  • Marketing-ExperimentationManagementData
  • Member-MemberManagementData
  • Merchandising-PromotionsAndDiscountsData
  • Order-OrderCaptureData
  • Order-OrderManagementData
  • WebSphereCommerceServerExtensionsData
  • HCL Commerce Enterprise Trading-AuctionsAndRFQsData

Some of the EJB modules in the preceding list contain session beans. In order to simplify migration in the future, you should not modify a session bean class. If required, you can create a new session bean in the WebSphereCommerceServerExtensionsData EJB module. For more information about creating new session beans, refer to Writing new session beans.

A program that uses enterprise beans must deal with the Java Naming and Directory Interface (JNDI) as well as the home and remote interfaces of enterprise beans. To simplify the programming model, an access bean for each enterprise bean is generated. When creating your own enterprise beans, use the tooling in HCL Commerce Developer to generate this access bean.