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.

Types of SUBSYSTEMS IN WCS.

Types of SUBSYSTEMS IN WCS.

• Catalog Subsystem.

• Order Subsystem.

• Trading Subsystem.

• Merchandising Subsystem.

• Marketing Subsystem.

• Member Subsystem.

• Payment Subsystem.

Difference between V6 and V7

Order trash can feature disabled by default
In WebSphere Commerce Version 7, the order trash can feature is disabled by default. In WebSphere Commerce Version 6, the default owner for deleted orders was -1002. In Version 7, the default owner for deleted orders is now -1006 (a guest user).
Changed functionality
Changed functionality typically involves changes in default values or an outcome different from what would have occurred in previous releases. For example, a default parameter might use one value in WebSphere Commerce Version 6 and a different value in WebSphere Commerce Version 7.
Madisons starter store replaces the consumer direct sample store
The Madisons starter store is the new store that replaces the consumer direct sample store in the previous release. The Madisons starter store uses Rich Internet Application (RIA) technologies such as Asynchronous JavaScript and XML (AJAX) and Dojo widgets to provide customers with an interactive and rich shopping experience. RIA technologies help to improve order conversion rates and reduce shopping cart abandonment. The store can be used as a standalone store using the consumer direct business model or as an asset store in Extended Sites or Demand Chain business models.
The Madisons starter store provides all the pages and features necessary for a functioning consumer direct online store. It is packaged with WebSphere Commerce as a store archive. It contains a full set of consumer direct features, including user registration, catalog browsing, promotions, and targeted marketing. The store contains rich interactions, including the product quick info pop-up window, product fast finder, mini shopping cart, and a streamlined checkout flow.
The store is fully accessible and translated into group one languages, supporting locale-specific bidirectional languages. Technological features include search engine optimization, support for multiple Web browsers and platforms, and options to accommodate a variety of flows, depending on customer needs.
In WebSphere Commerce Version 7, the Madisons starter store includes the store locator, inventory availability, and buy online, pickup in-store capabilities.
Apache Derby replaces Cloudscape database support
WebSphere Commerce Version 7 supports Apache Derby instead of Cloudscape. IBM has dropped support for the Cloudscape database. If you are using IBM Cloudscape it is recommended that you upgrade to the recent release of Apache Derby.
DB2 loop-back configuration has been removed on Unix platforms
DB2 loop-back configuration has been removed from Unix platforms. The DB2 loop-back configuration was implemented as a workaround due to a DB2 limitation. This limitation has been resolved with the new DB2 JCC type 4 connection type.
Oracle database character set has been changed from UTF8 to AL32UTF8
WebSphere Commerce has moved to the AL32UTF8 character set to align with the Oracle database recommendations. If you are using a WebSphere Commerce Version 6 Oracle database, you must migrate your database character set to use AL32UTF8.
Workspace Administration Tool
The Workspace Administration tool is deprecated for WebSphere Commerce Version 7 Feature Pack 3. This feature was used to manage workspaces and workspace-related activities.
Recommended action:
The Workspace Management tool, replaces all of the workspace management features in the Workspace Administration Tool. It is recommended that you use the Assets tool in the Management Center to manage your workspaces. However, if you have business reasons to continue using the Workspace Administration Tool, you can re-enable it.

Versions of WCS & Consoles present in RAD

Versions:

They were 3 versions of wcs they are: 5.6, 6 and 7.

• In 5.6 there is no implementation of struts.
• The main difference between 5.6 and 6, the view command in V5.6 is replaced with Struts.
  
• In 6 there was no social and mobile commerce and in 7 these both were implemented.
• 7 provides multichannel precision marketing etc.

Consoles:

They were 5 consoles in wcs they are:

1. Management Center: Manages data related to stores.

2. Accelerator: It is related to marketing, merchandising, catalog management etc.

3. Organization Administration Console: Creates users & assign roles and categorize users based

into a group.

4. Workspace Administration Console: Managing business sites like adding products, site up, site

down etc.

5. Administration Console: Store publishing, registries etc.

WCS EDITIONS

WCSEDITIONS:  There were 3 editions of WCS they are:

     1  Express.
     2 Professional.
     3 Enterprise.
 

Express: Express meets the needs of small and medium sized businesses. It provides full consumer direct support and simple business direct support.

Professional: It meets the needs of most consumer direct businesses. It includes features such as workspaces.

Enterprise: It offers online commerce and collaboration with traditional and new customers and partners through management of online trading relationships. It also provides B2B commerce functions, including accounts, contracts, and request for quotes, purchase orders, requisition lists and approvals.

Types of WCS

There were 2 types of wcs they are:

1. WCS Server.
2. WCS Developer.

WCS Server: It is used throughout the world.

WCS Developer: It is installed by the individual user in his/her system.

what is IBM WebSphere Commerce...?

IBM WebSphere Commerce is a platform framework for e-commerce, including marketing, sales, customer and other functionality in a tailorable, integrated package.WebSphere Commerce is a customizable, scalable and high availability solution built on the java- javaEE platform using open standards, such as XML, and Web services.