WCS interview Questions and Answers.

" Click here "   to download the document 

all the best prepare well for the interview.

Details about Data beans in WCS.

Data Bean :

A data bean is a Java bean that is used within a JSP page to provide dynamic content. A data bean normally provides a simple representation of a WebSphere Commerce entity bean. The data bean encapsulates properties that can be retrieved from or set within the entity bean. As such, the data bean simplifies the task of incorporating dynamic data into JSP pages.

A data bean is activated in one of the following ways:

• by means of the wcbase:useBean tag (recommended)
• by means of the following call:

com.ibm.commerce.beans.DataBeanManager.activate(data_bean, request, response)

where data_bean is the data bean to be activated, request is an HTTPServletRequest object, and response is an HTTPServletResponse object.

Types of data beans :

A data bean is a Java bean that is mainly used to provide dynamic data in JSP pages. There are two types of data beans:

1.       Smart Data Bean.
2.       Command Data Bean.

• Smart data beans :

• A smart data bean uses a lazy fetch method to retrieve its own data.
• Smart data beans that require access to the database should extend from the access bean for the corresponding entity bean and implement the com.ibm.commerce.SmartDataBean interface.
• For example, the OrderItemDataBean data bean extends the OrderItemAccessBean access bean, which corresponds to the OrderItem entity bean.
• Some smart data beans do not require database access. At this case “When database access is not required, the smart data bean should extend the SmartDataBeanImpl class”. 

   Command data bean :

• A command data bean relies on a command to retrieve its data and is a more lightweight data bean.
• Command data beans can also extend from their corresponding access beans and implement the com.ibm.commerce.CommandDataBean interface.

Tutorial Point offline browsing Link for download.

This Post is very much usefull to those who are not able to Browse the Internet for Java preparation Please download the material from this link

"

CliCK here to DOWNLOAD

"

Please leave a comment and follow us for more updates and materials......

Prepare well all the best Friends.

Steps in Publishing The .SAR file.

Publishing Steps for Store Archive (.sar)

· A store archive file (.sar) is a ZIP archive file that contains all the assets necessary to create a store or site. It is primarily used as a vehicle for packaging and delivering stores. You only need to publish a store archive to the WebSphere Commerce Server to create a functioning store or site that you can view, browse, and shop at.

· Store archive files are also used to package and deliver organization structures, predefined user roles, and access control policies necessary to create the environment for your store or site, as well as to package collections of assets used to create a catalog or storefront.

Publishing a Madisons.sar file: The steps are:

The sar file location is WCDE_installdir/starterstores/AddOnFeatures

· Open the Administration Console, selecting the Site option.

· From the Stores Archives menu, select Publish. The Store Archives page displays listing the store archives available for publish. By default, the page displaying composite store archives displays.

· From the View list, select Add On Feature.

· Select MadisonsEnhancements.sar.

· Click Next.

· Select the Madisons-based starter store onto which you want to publish the Madisons enhancements store archive. The Publish wizard must publish the Madisons enhancements store archive on top of the Madisons starter store; no other starter stores are supported. There are three stores:

1. Marketing Store.

2. Catalog Store.

3. Customer facing Store.

4. If you are using a single store setup then choose the same store for all three.

5. If you are using an Extended sites model, choose the appropriate stores that you are using.

· Click Next. The Summary page displays, listing the store archive and parameters selected, and the location to which the store archive is published.

· After reviewing the summary information, click Finish. A confirmation dialog displays, telling you the number of the publishing job. Note the job number for future reference.

· To check the publishing status, click Refresh.

· When the Publish Status column displays Successful, select the corresponding job number; then click Details.

· To launch the published store in a browser, click Launch Store.

· When you have finished viewing the store, bookmark the site, and close the browser.

· Restart the WebSphere Commerce Server.

Commands Present in Order Subsystem.

Some of the commands related to Order Sub-system are:

· com.ibm.commerce.order.commands.OrderDeleteCmd

· com.ibm.commerce.order.commands.OrderCancelCmd

· com.ibm.commerce.order.commands.OrderProfileUpdateCmd

· com.ibm.commerce.order.commands.OrderUnlockCmd

· com.ibm.commerce.order.commands.OrderScheduleCmd

· com.ibm.commerce.order.commands.ScheduledOrderCancelCmd

· com.ibm.commerce.order.commands.ScheduledOrderProcessCmd

· com.ibm.commerce.order.commands.OrderItemAddCmd

· com.ibm.commerce.order.commands.OrderItemDeleteCmd

· com.ibm.commerce.order.commands.OrderItemUpdateCmd

· com.ibm.commerce.order.commands.PayResetPMCmd

The tables in Order Sub-system are:

1. Orders

2. OrderMGP: Relation between Order & Member.

3. OrderItem

4. ORDITEMCONF: Relation between order items & order item shipment confirmation.

5. Ffmcenter

6. ORDUSERS: Contains information about users that worked with an order.

7. OrdTax: Represents the total tax for all order items in an order.

a. ORDSTAT: Contains information about the status of an Order Status Update inbound message.

b. ORDISTAT: This table contains information about the items within a single order for an Order Status Update inbound message.

8. SCHORDERS: Contains the entries for scheduled orders.

a. SUBORDERS: Contains subtotals of amounts for all the OrderItems of an Order with the same shipping address.

b. ORDPAYINFO: Holds a name-value pair representing payment information for a particular Order.

c. ORDPAYMTHD: The Order Payment Method table contains order payment or refund methods selected for an order.

Details About Order SubSystem.

ORDER SUBSYSTEM

• Order Sub-system is a component of WCS that provides shopping carts, order capture, order fulfillment, inventory & payment function support.
• An order includes one or more products, billing & shipping addresses, payment details & the total cost including shipping charges & taxes.
• From a customer persective an order is a list of selected products.
• Each product in a list is called an order item.
• From a store perspective an order is a list of order items.
• Orders are associated with a single store.
• An order profile is a special type of order that can be associated with either a store or a store group.
• The order profile holds default information about a customer such as payment information, shipping address, shipping mode & billing address.

Ø There are 4 inventory systems, they are:

1. ATP inventory.

2. Non-ATP inventory.

3. No inventory.

4. External inventory.

ATP Inventory: The ATP inventory model enables you to allocate stock from existing inventory or backorder from expected inventory. You can also obtain an estimated availability time for each order item once it has been added into the shopping cart. The ATP also supports allocating stocks for future order processing.

Non-ATP Inventory: The non-ATP inventory model supports inventory operations that are only based on existing on-hand inventory.

No Inventory: The no inventory model assumes that all products have infinite quantities. When the products in a store are virtual products, digital downloadable products, or electronic assets, such as downloadable images or music.

External Inventory: External inventory is used for Websphere Commerce and some external inventory systems integration. For integration with other inventory systems, you might select ATP, non-ATP, or No-inventory inventory system based on the specific inventory system and integration scenario.

The shipping codes for an order sub-system are:

• A - Payment Authorization requires review.
• B - Backordered.
• C - Payment Authorization complete.
• D - Deposited.
• E - CSR Edit.
• F - Ready for remote fulfillment.
• G - Pending remote fulfillment.
• H - Error in remote fulfillment.
• I - Submitted.
• J - Trashcan.
• L - No inventory.
• M - Either a part or total amount is approved.
• N - Approval denied.
• P - Pending Order.
• Q - Quick order profile.
• R - Released.
• S - Shipped.
• T - Temparory.
• W - Pending approval.
• X - Cancelled.
• Y - Private requisition list.
• Z – Sharable requisition list.

Order Flow Process For Consumer Direct Store

Consumer Direct Order flow Process:

Place an order. A customer or an administrator who has the authority to act on behalf of the customer places an order with the store. Placing an order involves browsing the online catalog, selecting one or more products for the order, and providing billing, shipping, and offline payment information. Once the customer or administrator completes the order checkout, the order moves from P state (pending with products in the shopping cart) to M state (pending payment approval).

Approve payment for the order. Once the order has been placed, the next step is to approve payment for the order, using WebSphere Commerce Payments. Offline payments are automatically approved and the order moves from M state (pending payment approval) to C state (approved and ready to be released to fulfillment).

Release the order to fulfillment.

Create a pick batch for all orders released to the specified fulfillment center. Pick batches must be created for all fulfillment centers, including the channel store. Once you receive the products from the channel store, you can then pick and pack them for delivery to customers. All releases for the selected fulfillment center are placed in one batch; pick slips are created for each pick batch and packing slips are generated for the releases.

View and print pick ticket.

View and print packaging slip.

Pick and pack products specified in the pick ticket and packaging slip. Products specified in the pick ticket are then manually picked from the fulfillment center, and products are packed according to the instructions in the packing slips.

Create package.

Ship goods. Ship the order to the customer.

Confirm shipment has been sent.

Confirm Shipment. Once you have verified the shipment on the system, the status of the order changes to Shipped.

Note:

1. Pick Ticket: A printed document containing a list of all the products required to fulfill the releases in a given pick batch.

2. Pick Batch: A group of releases that are managed as a unit in a fulfillment center.

3. Fulfillment Center: Serves as a storage warehouse where products are packed & shipped to customers.

Commerce Exceptions

Class Summary
ECApplicationException	This class defines the exceptions thrown by the WebSphere Commerce Application Server when application errors occur during the processing of business logic.
ECException	This is an abstract base class used for defining exceptions thrown by the WebSphere Commerce Application Server.
ECParameterError	This class is a specialization of the service parameter error that uses an ECMessage to populate the error object.
ECSystemException	This class defines the exceptions thrown by the WebSphere Commerce Application Server when system errors occur during processing.
ExceptionHandler	This class contains methods & helper methods for converting Exception objects to ECException objects and generating ECException objects.
InvalidParameterValueException	This class defines the exception thrown by the WebSphere Commerce Application Server when a parameter error occurs.
ParameterNotFoundException	This class defines the exception thrown by the WebSphere Commerce Application Server when a parameter not provided by the client.

Details about Access Control Policies.

An Access Control Policies authorizes a group of users to perform a set of actions on a set of resources.

An access control policy has 4 elements, they are:

1.User.

2.Action.

3.Resource.

4.Relationship.

User: The Users are the people that use the system. For access control purposes, users must be grouped into relevant access groups.

Action: Actions are the activities that users can perform on the resource.

Resource: Resources are the entities that are protected. A resource group might include business objects like contract or order, or a set of related commands.

Relationship: Relationships are the relationship between the user and the resource. Access control policies may require that a relationship between the user and the resource be satisfied. Each resource class can have a set of relationships associated with it. Each resource can have a set of users that fulfill each relationship.

There are 2 types of access control policies, they are:

1.Groupable standard policies(policy type-2).

2.Groupable template policies(policy type-3).

A groupable standard policy is applied, once, at organizations that subscribe to a policy group that contains the policy.

Groupable template policies are dynamic in nature in that they have an access group that is scoped, when the system is running, to the organization that owns the resource.

The table updated in access control poliies are:

1.ACACTION: Stores actions that are to be performed on the resources in the system.

2.ACPOLICY: Stores all the access control policies in a system.

3.ACRESGRP: Stores all access control resource groups in a system.

4.ACPOLDESC: Stores local specific information for ACPOLICY.

5.ACRELATION: Relation between resources and members in system.

6.ACRESREL: Associates a resource and relationships that it supports.

WebSphere Commerce allows you to determine, through access control, which tasks a particular user, be they customers, buyers, administrators, distributors, manufacturers, or suppliers, can perform in relation to your business.

To facilitate database management and ensure security, access to WebSphere Commerce must be restricted to specific individuals and organizations. The process of restricting access is referred to as access control or authorization. Authorization can be defined as security guidelines that:

1. Allow or deny a user of a system access to the resources managed by a system.
2. Specify what actions the user can perform on each resource.

The authorization model for WebSphere Commerce is based upon the enforcement of access control policies. Access control policies are enforced by the access control Policy Manager. In general, when a user attempts to access a protected resource, the access control policy manager first determines what access control policies are applicable for that user and then, based upon the applicable access control policies, it determines if the user is allowed to perform the requested operation on the given resource.

The Site Administrator manages the access control policies that apply to a site or store.

Details about Beans Present in WCS..

Data Bean

A data bean is a java bean that is used within a jsp page to provide dynamic contect to the jsp page. A data bean normally provides a simple representaion of a WebSphere Commerce Entity bean.

There are 3 types of data beans:

1.Smart databean.

2.Command databean

3. Input data bean

• Smart data bean: When a smart data bean is activated, the data bean manager invokes the data bean's populate method. Using the populate method, the data bean can retrieve all attributes, except attributes from associated objects.
• Command data bean: A data bean implementing the CommandDataBean interface retrieves data from a data bean command. A data bean of this type is a lightweight object; it relies on a data bean command to populate its data. The data bean must implement the getCommandInterfaceName() method which returns the interface name of the data bean command.
• Input data bean: A data bean implementing the InputDataBean interface retrieves data from the URL parameters or attributes set by the view.

Attributes defined in this interface can be used as primary key fields to fetch additional data. When a JSP page is invoked, the generated JSP servlet code populates all the attributes that match the URL parameters, and then activates the data bean by passing the data bean to the data bean manager. The data bean manager then invokes the data bean's setRequestProperties() method (as defined by the com.ibm.commerce.InputDataBean interface) to pass all the attributes set by the view.

Access Bean

WCS commands interact with access beans rather than directly with the entity beans. Access beans behave like Java beans, & hide all enterprize bean-specific programming interfaces from the client.

Types of Access beans are:

1. Copy Helper methods.

2. Finder methods.

3. EJB methods.

There are 2 types of Copy Helper methods:

1. refreshCopyHelper()

2. commitCopyHelper()

refreshCopyHelper(): refresh copy helper is treated as "find for update” and it locks that particular row unless or until you are done with entire transaction. So you read something with refreshcopyHelper and you keep doing n no of things and when you are finally done then only these locks are released.

refreshCopyHelper reads the database to update the access bean.

commitCopyHelper(): commitCopyHelper() takes the current state of the access bean and updates the database with it.

Updates the database with the contents of the access bean.

Entity Bean: The persistence layer within the WebSphere Commerce architecture is implemented according to the EJB component architecture.

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. One advantage of using entity beans is that developers can utilize the EJB tools provided in WebSphere Commerce Developer. These tools allow developers to define Java objects and their database table mappings. The tools automatically generate the required persisters for the entity beans. Persisters are Java objects that persist Java fields to the database and populate Java fields with data from the database.

WebSphere Commerce V7 Multi-Channel Precision Marketing Overview

Multi-channel precision marketing is an integrated solution to handle on-going dialogs with customers, over time, across channels as customers’ behaviors change. By presenting targeted offers and customized promotions at the individual shopper level, WebSphere Commerce Version 7.0 enables companies to design and fine tune on-line shopping flows, content and e-marketing messages that resonate with the target audience, and help to make the brand stand out over the competition.

Key Features.

• Dialog activity builder for defining and managing triggers and actions.
• Dynamically assign and reassign shoppers to and from segments.
• Deliver marketing messages via SMS.
• Support for advanced promotions including promotions based on product attributes, and caps on discount amount.
• Provide choice of awards.
• Best deal support.
• Build precision marketing customer “dialogs” quickly with best-in-class business user tooling.

Key Benefits.

• Help increase customer satisfaction and loyalty.
• Improve customer experience with personalization.

Detailed Version of "eSpots and cSpots"

eSpots(e-Marketing Spots)
ESpots are specific defined areas on a JSP page whose content can be dynamically configured based on rules. eSpots reserve space on your store pages in which content displays. Use for marketing activity. Add email activity (send promotional mails for selected group in specified time), web activity(start,end date,priority,status).

For calling e-marketing spot use below jsp

< c : import url="${jspStoreDir}include/eMarketingSpotDisplay.jsp">

< / c:import>


c-Spots (Content Spot )
-atleast one content is mandatory -
-can be scheduled with start/end date
-call the content spot name in jsp to display the attached content

For calling c-spot use below jsp

< c:import url="../Snippets/Marketing/Content/ContentSpotDisplay.jsp">
< c: param name="spotName" value="mycontent1" />
< c:param name="substitutionValues" value="{spotname},${spotName}"/>
< c:param name="substitutionValues" value="{myname},${name}"/>
< c:param name="substitutionValues" value="{myid},${id}"/>
< c:param name="substitutionValues" value="{mycomment},${comment}"/>

< / c:import>

Steps to install WCS7.0

Step 1. Install IBM Install Manager 1.4 or above
Step 2. Install RAD using Install Manager
Step 3. Intall WAS using Install Manager
Step 4. Apply latest fixes of RAD and WAS
Step 5. Install WCS 7.0
Step 6. Run setupPlugins.bat and setup.bat

WebSphere Commerce -Member Subsystem

WebSphere Commerce Member Subsystem:
Business logic in the Member subsystem provides member registration and profile management services
Member Subsytem: A top view

User Registration Flow:

User type :

• S(Site administrator )
• A(Administrator)
• G(Guest user)
• R(Registered User)

Table:

• USERS,USERREG,USERREPROF,USERDEMO,
• BUSPROF
• MEMBER,MBRATTR,MBRATTRVAL
• MBRREL
• MBRROLE
• MBRGRP,MBRGRPTYPE,MBRGRPMBR,MBRGRPUSG
• ORGENTITY
• ADDRESS

Commands:
UserRegistrationAddCmd

• PreUserRegistrationAddCmd
• Update USERS.REGISTERTYPE='R' from 'G'
• Create new record in USERREG
• Create new records in USERPROF,BUSPROF,USERDEMO
• Create new record in ADDRESS with unique nickname
• AuthenticationPolicyCmd
• ProcessPaymentMemberCmd
• ProcessPolicyTypeCmd
• AuditUserRegistrationCmd
• UserRegistrationRoleAssignCmd
• PostUserRegistrationAddCmd

AddressAdd

• Address type-S, B, SB(i.e.Shipping=S, Business=B, Shipping & Business=SB)
• isPrimary -0,1
• Address Status : P(permanent),T(Temporary)
• Unique nickname
• AddressBook

AddressDelete: status = T (from P)
AddressCheck:Check user has atleast one P address
AddressUpdate : Nick name cannot be updated

WebSphere Commerce business models

• Direct sales
• Consumer direct (B2C)
• Business to business direct (B2B)

• Scalable direct sales
• Extended Sites

• Value chain
• Demand chain
• Supply chain

Description about Controller Command.

The abstract class and interface are both found in the com.ibm.commerce.command package.


A new controller command should extend the abstract controller command class ( com.ibm.commerce.command.ControllerCommandImpl). When writing a new controller command, you should override the following methods from the abstract class:

isGeneric()
In the standard WebSphere Commerce implementation there are multiple types of users. These include generic, guest, and registered users. Within the grouping of registered users there are customers and administrators.
The generic user has a common user ID that is used across the entire system. This common user ID supports general browsing on the site in a manner that minimizes system resource usage. It is more efficient to use this common user ID for general browsing, since the Web controller does not need to retrieve a user object for commands that can be invoked by the generic user.
The isGeneric method returns a Boolean value which specifies whether the command can be invoked by the generic user. The isGeneric method of a controller command's superclass sets the value to false (meaning that the invoker must be either a registered customer or a guest customer). If your new controller command can be invoked by generic users, override this method to return true.
You should override this method to return true if your new command does not fetch or create resources associated with a user. An example of a command that can be invoked by a generic user is the ProductDisplay command. It is sensible to allow any user to be able to view products. An example of a command for which a user must be either a guest or registered user (and hence, isGeneric returns false) is the OrderItemAdd command.
When isGeneric returns a value of true, the Web controller does not create a new user object for the current session. As such, commands that can be invoked by the generic user run faster, since the Web controller does not need to retrieve a user object.

isRetriable()
The isRetriable method returns a Boolean value which specifies whether the command can be retried on a transaction rollback exception. The isRetriable method of the new controller command's superclass returns a value of false. You should override this method and return a value of true, if your command can be retried on a transaction rollback exception.
An example of a command that should not be retried in the case of a transaction exception is the OrderProcess command. This command invokes the third party payment authorization process. It cannot be retried, since that authorization cannot be reversed. An example of a command that can be retried is the ProductDisplay command.
setRequestProperties(com.ibm.commerce.datatype.TypedProperty reqParms)

The setRequestProperties method is invoked by the Web controller to pass all input properties to the controller command. The controller command must parse the input properties and set each individual property explicitly within this method. This explicit setting of properties by the controller command itself promotes the concept of type safe properties.

validateParameters()
The validateParameters method is used to do initial parameter checking and any necessary resolution of parameters. For example, it could be used to resolve orderId=*. This method is called before both the getResources and performExecute methods.

getResources()
This method is used to implement resource-level access control. It returns a vector of resource-action pairs upon which the command intends to act. If nothing is returned, no resource-level access control is performed.

performExecute()
The performExecute method contains the business logic for your command. It should invoke the performExecute method of the command's superclass before any new business logic is executed. At the end, it must return a view name.

Important Commands & DataBeans present in Catalog Subsystem

Commands--
StoreCatalogDisplayCmdImpl-
This command sets the view task that will display the Catalogs available to browse in the current Store.

TopCategoriesDisplayImpl-
This command sets the view task that will display the root Categories in a specified Catalog.

CategoryDisplayCmdImpl-
retrieves the configured display page for the specified category in the specified catalog.

ErrorMissingAttributeCmd-
This error task command is set when a Product to Item resolution fails due to missing product attributes.

ErrorProductAttributeCmd-
This error task command is set when a Product to Item resolution fails due to incorrect product attributes

ProductDisplayCmdImpl-
This command retrieves the configured Display Page for the specified CatalogEntry which will in turn be launched in order to
display information about the CatalogEntry.This command first ensures that the CatalogEntry specified by the
ProductId can be displayed in the current store, if published, and is not marked for delete.

ResolveSkuCmd-Certain catalog entries may need further processing before being added to an order.
An example is resolving a product into an item through SKU resolution, performed by the ResolveSkuCmd task command.


DataBeans--
StoreDataBean--extends StoreAccessBean ->salesCatalogs()
CatalogDataBean-extends CachedCatalogAccessBean ->getTopCategories()
CategoryDataBean-extends CachedCatalogAccessBean ->getSubCategories()
CatalogEntryDataBean-extends CachedCatalogEntryAccessBean
ProductDataBean-extends CachedProductAccessBean

Management Centre vs Commerce Accelerator

1.For promotions and espot configurations, which is a better approach - management center or accelerator?

• Considering the management center's design, its complex structure takes more time in implementing new modifications as compared to accelerator modifications.

2.We can view the status what change's we did in Management Center, If we did any wrong it shows an error, but in Accelerator the error is not shown.

3.Management center provides a rich UI with features like drag and drop. There is a possibility that in some future releases Commerce Accelerator may be removed. With current release it is not possible as it is tightly coupled with the framework.

4.For an end user perspective Management Center will be the preferred tool. Being a flash based tool it is slow but very user friendly.

5.Management Center, It's sometimes slow but it provides more usability such as drag and drop,etc which makes it a favorite tool for the business user.

=============

• Accelerator
• Create content spot and schedule
• Management Center
• Moving forward, no separate object for content spots, will be phased out
• Content spot was originally created for performance reasons,
• New caching of e-spots eliminates need for content spots
• Now, changing from static (content spot) to dynamic (e-spot) content does not require change in code/jsp
• Previous in Management Center – Campaign, Web Activity, Marketing Experiment, Email Activity, Promotion, Content
• New in Management Center – Customer Segment, e-Spot, Dialog Activity

Important Tables & URLS present in Catalog Subsystem

Tables
STORECAT -store to catalog
CATTOGRP -catalog to group
CATGRPREL -group to group
CATGPENREL -group to parent
CATENTREL -group to praent
CATENTREL -parent to item

URLS---
StoreCatalogDisplay
TopCategoriesDisplay
CategoryDisplay
ProductDisplay

Detailed Description of Catalog Subsystem

CatalogSubsystem

The catalog subsystem is a component of theWebSphere Commerce Server that provides online catalog navigation,partitioning, categorization, and associations. The catalog subsystem containsall logic and data relevant to an online catalog, including catalog groups (orcategories), catalog entries, and any associations or relationships among them.

Catalogentries classification:

· Products.

· Items.

· Packages.

· Bundles.

· Dynamic or static kit.

PRODUCT and ITEM:
An item is a tangible unit of merchandise that has a specific name, partnumber, and price. For example, a 15 inch hammer with a wooden handle (partnumber 15) is an item.
A product, however, is a group of items that exhibit the same attributes.For example, a hammer is a product, while the 15 inch hammer with a woodenhandle is an item. The attributes of this product are "handle type"and "size," which are defined by the corresponding attribute values, wooden and 15 inch.
To distinguish products and items, keep in mind that a product cannot bepurchased, while an item can potentially be purchased.

PACKAGEand BUNDLE:

Packages and bundlesare groupings of catalog entries used for promotional purposes.

A bundle is acollection of catalog entries that allow customers to buy multiple items withone click. A bundle can be agrouping of items, or a combination of products, items, and fully resolvedpackages. The bundle is decomposed into separate orderableSKUs that are added individually to the shopping cart.

Unlike bundles, apackage is an atomic collection of catalog entries. Viewed in similar ways as aproduct, you cannot decompose ormodify a package during navigation or after the package has been placed in theshopping cart. For example, a computer package might contain a specific centralprocessing unit, monitor, and hard drive that cannot be sold separately.

Dynamic kit and Static kit

A dynamic kit is a typeof catalog entry which can be dynamically configured by the customer.
This configuration (or grouping) of products is based on the customer'srequirements and is sold as a single unit.

A static kit is a groupof products that are ordered as a unit. The information about the productscontained in a static kit is predefined and controlled within WebSphereCommerce.