Explore topic-wise InterviewSolutions in .

1. Identify the business logic that you want to expose as a WEB service.
2. Identify the CONTROLLER command that represents this business logic. If it is not available, then create a new controller command. You can write new commands to call a COLLECTION of existing commands.
3. Identify the mandatory and OPTIONAL PARAMETERS that this command requires.
4. Create a WSDL description for the Web service.
5. Register the WSDL description.
6. Write a JSP page to compose a response.
7. Deploy the service. This includes the deployment of related files and resources. In case of a new command, you must deploy and register it in the WebSphere Commerce command registry.

Pending , SCHEDULE, Submit , Pending PAYMENT Approval , Payment authorization complete , Approve , CSR Edit , CSR Submit , Release , Shipment, Backordered , Order TRANSFERRED , CANCEL , Close.

Pending , Schedule, Submit , Pending Payment Approval , Payment authorization complete , Approve , CSR Edit , CSR Submit , Release , Shipment, Backordered , Order Transferred , Cancel , Close.

• PostOrgEntityAddCmd
• PostOrgEntityUpdateCmd
• CheckUserInMemberGroupCmd
• LogonCmdImpl
• DBAuthenticationCmd
• LDAPAuthenticationCmd
• LogoffCmd

It is used for STORING data type of attribute VALUES. Valid values: INTEGER, STRING, FLOAT, DATETIME, FREEFORM or BIGINT.

It is used for storing data type of attribute values. Valid values: INTEGER, STRING, FLOAT, DATETIME, FREEFORM or BIGINT.

OPTCOUNTER is the field used in all tables for Optimistic locking. Whenever a client updates a record in the table , WCS increments the OPTCOUNTER for that table so that this value can be COMPARED in case the other client try to update it to see if SOMEONE ELSE updated it in the duration between its retrieval and update.

OPTCOUNTER is the field used in all tables for Optimistic locking. Whenever a client updates a record in the table , WCS increments the OPTCOUNTER for that table so that this value can be compared in case the other client try to update it to see if someone else updated it in the duration between its retrieval and update.

UTILITIES provided by WCS for PREPARING and loading DATA into WCS Database.

Utilities provided by WCS for preparing and loading data into WCS Database.

We can WRITE the code to CALL access BEAN in the populate () method.

We can write the code to call access bean in the populate () method.

Helper class is a UTILITY class that can be USED without prior CODING and it REDUCES code redundancy.

Helper class is a utility class that can be used without prior coding and it reduces code redundancy.

FULFILLMENT centers are used by stores as WAREHOUSES for shipping and receiving centers. One store can have MULTIPLE fulfillment centers associated with it.

Fulfillment centers are used by stores as warehouses for shipping and receiving centers. One store can have multiple fulfillment centers associated with it.

Master Catalog is a CENTRALIZED location to manage stores. Everything that is REQUIRED for the store is present in master catalog. It is a single catalog that CONTAINS products, ITEMS, relationships and prices that is required for sale in the store.

Master Catalog is a centralized location to manage stores. Everything that is required for the store is present in master catalog. It is a single catalog that contains products, items, relationships and prices that is required for sale in the store.

The ORDER will be blocked by calling task command NotifyBlockCmd or the CONTROLLER command BlockNotifyCmd. When the order is blocked, the value of BLOCKED column in the ORDERS table will be 1 (means the order is blocked).

The order will be blocked by calling task command NotifyBlockCmd or the controller command BlockNotifyCmd. When the order is blocked, the value of BLOCKED column in the ORDERS table will be 1 (means the order is blocked).

The SHIPPING and billing address of the CUSTOMER are stored in the ADDRESS table. There are two RECORDS in this table - one is for shipping and other is for billing ADDRESSES. The ADDRBOOK_ID is the foreign KEY in the ADDRESS table. The ADDRESSTYPE will be S for shipping , B for billing and SB for both shipping and billing.

The shipping and billing address of the customer are stored in the ADDRESS table. There are two records in this table - one is for shipping and other is for billing addresses. The ADDRBOOK_ID is the foreign key in the ADDRESS table. The ADDRESSTYPE will be S for shipping , B for billing and SB for both shipping and billing.

This FILE RETRIEVES and prepares the JSP page PATH, file path and resource bundle path which are used by other JSP’s. The EnvironmentSetup.jsp INCLUDES most commonly used attributes such as storeDir, jspDir, includeDir, bundleDir, ETC.

This file retrieves and prepares the JSP page path, file path and resource bundle path which are used by other JSP’s. The EnvironmentSetup.jsp includes most commonly used attributes such as storeDir, jspDir, includeDir, bundleDir, etc.

CommandContext is the interface in WEBSPHERE COMMERCE, which contains session and user information and set in the CONTROLLER command before the execute METHOD is called.

CommandContext is the interface in WebSphere Commerce, which contains session and user information and set in the Controller command before the execute method is called.

UserRegistrationAddCmd for adding the USER. This will insert the DATA into tables 

- USERS

- USERREG

- USERPROF

- USERDEMO

- ADDRESS

UserRegistrationUpdateCmd for updating the user profile.

LogOffCmd for LOGGING out.

Customized Controller Commands in GOSP are GOSPNCIMHandShakeCmd used for authenticating the user, by HAND shaking with NCIM. This command will search for user authentication token, if the authentication token is available, then the user will be ALLOWED to sign on. 

GOSPNCIMUserRegistrationFormCmd used for creating the registration form for the user.

UserRegistrationAddCmd for adding the user. This will insert the data into tables 

- USERS

- USERREG

- USERPROF

- USERDEMO

- ADDRESS

UserRegistrationUpdateCmd for updating the user profile.

LogOffCmd for logging out.

Customized Controller Commands in GOSP are GOSPNCIMHandShakeCmd used for authenticating the user, by hand shaking with NCIM. This command will search for user authentication token, if the authentication token is available, then the user will be allowed to sign on. 

GOSPNCIMUserRegistrationFormCmd used for creating the registration form for the user.

WebSphere Commerce performs all CALCULATIONS for one calculation usage at a time. The order of calculation usages is STORED in the SEQUENCE column of the STENCALUSG database table. The entries in this table are INITIALLY populated with information from wcs-bootstrap.xml.

WebSphere Commerce performs all calculations for one calculation usage at a time. The order of calculation usages is stored in the SEQUENCE column of the STENCALUSG database table. The entries in this table are initially populated with information from wcs-bootstrap.xml.

Asset stores are collections of SHARABLE resources that can be USED in other stores. An asset STORE is typically composed of the assets that can be used by stores, but is in itself not a functional store and does not CONDUCT BUSINESS transactions.

Asset stores are collections of sharable resources that can be used in other stores. An asset store is typically composed of the assets that can be used by stores, but is in itself not a functional store and does not conduct business transactions.

Database tables are open for read/write over entire network for all users/sessions. It results in INCREASED throughput but results in the loss of UPDATES during parallel ACCESS.

For example:-

1. User X reads a record
2. User y reads the same record
3. User x updates that record
4. User y updates the same record

User y has now over-written the CHANGES that User x made.

Database tables are open for read/write over entire network for all users/sessions. It results in increased throughput but results in the loss of updates during parallel access.

For example:-

User y has now over-written the changes that User x made.

ATTRIBUTE "COLOR" will be stored as a record in tables ATTR and ATTRDESC. All POSSIBLE values for this attribute will be stored in tables ATTRVAL and ATTRVALDESC. Association between Attribute , Attribute VALUE and CATENTRY will be stored in CATENTRYATTR table.

Attribute "color" will be stored as a record in tables ATTR and ATTRDESC. All possible values for this attribute will be stored in tables ATTRVAL and ATTRVALDESC. Association between Attribute , Attribute Value and Catentry will be stored in CATENTRYATTR table.

It's an ACCESS BEAN RELATED to STORE Table.

It's an access bean related to Store Table.

In B2C CUSTOMER can access STORE DIRECTLY and make online purchases whereas In B2B , Its the store BUSINESS between organizations.

In B2C customer can access store directly and make online purchases whereas In B2B , Its the store business between organizations.

All the MARKETING SPOT that is created in the APPLICATION will have record in the EMSPOT table. EMSPOT table consists of EMSPOT_ID, STORE_ID, NAME, DESCRIPTION and USUAGETYPE ESMAPOBJ table consists of MAPPING between ESMAPOBJ_ID and the OBJECT_ID.

All the Marketing spot that is created in the application will have record in the EMSPOT table. EMSPOT table consists of EMSPOT_ID, STORE_ID, NAME, DESCRIPTION and USUAGETYPE ESMAPOBJ table consists of mapping between ESMAPOBJ_ID and the OBJECT_ID.

The CATENTRY_ID is the foreign key in the ORDERITEMS table and OICOMPLIST table. The CATENTRY_ID is the primary key in the CATENTRY table. The relationship of the parent and child CATENTRY_ID can be DEFINED in CATENTREL table. The CATENTRYTYPE_ID can be Product Bean, Item Bean, Package Bean, Bundle Bean, DynamicKitBean and CatalogEntryBean. The CATENTDESC contains all the DESCRIPTIVE INFORMATION for the CATENTRY_ID and the CATENTRY_ID is the primary key in the table.

The LISTPRICE contains the pricing information of the CATENTRY_ID. The OFFER table contains the OFFER_ID of the CATENTRY_ID. The OFFERPRICE table contains the offer price of the CATENTRY_ID and the OFFER_ID is the primary key.

The CATENTRY_ID is the foreign key in the ORDERITEMS table and OICOMPLIST table. The CATENTRY_ID is the primary key in the CATENTRY table. The relationship of the parent and child CATENTRY_ID can be defined in CATENTREL table. The CATENTRYTYPE_ID can be Product Bean, Item Bean, Package Bean, Bundle Bean, DynamicKitBean and CatalogEntryBean. The CATENTDESC contains all the descriptive information for the CATENTRY_ID and the CATENTRY_ID is the primary key in the table.

The LISTPRICE contains the pricing information of the CATENTRY_ID. The OFFER table contains the OFFER_ID of the CATENTRY_ID. The OFFERPRICE table contains the offer price of the CATENTRY_ID and the OFFER_ID is the primary key.

Bootstrap files are XML files which WebSphere Commerce USES during INSTANCE CREATION to populate database tables with information after the schema has been CREATED.

Once the data has been loaded, you can see the preloaded information in the table. These files are used to retrieve information about the specific data, such as calculation codes and pricing policies.

Bootstrap files are XML files which WebSphere Commerce uses during instance creation to populate database tables with information after the schema has been created.

Once the data has been loaded, you can see the preloaded information in the table. These files are used to retrieve information about the specific data, such as calculation codes and pricing policies.

Command can throw two TYPES of exceptions:

ECApplicationException: This exception is thrown; if the error is RELATED to USER input and it always fail. When the user ENTERS invalid parameter, this exception is always thrown. When this exception is thrown, the solution controller does not retry the command, even if the command is specified as retriable. 

ECSystemException: This exception is thrown if a runtime exception or any WebSphere configuration error occurs. Examples of this exception are Remote Exception, Create Exception or other EJB exceptions. When this exception is thrown, the solution controller retries the command if the command is retriable and the exception was caused by either a DATABASE dead lock or database rollback.

Command can throw two types of exceptions:

ECApplicationException: This exception is thrown; if the error is related to user input and it always fail. When the user enters invalid parameter, this exception is always thrown. When this exception is thrown, the solution controller does not retry the command, even if the command is specified as retriable. 

ECSystemException: This exception is thrown if a runtime exception or any WebSphere configuration error occurs. Examples of this exception are Remote Exception, Create Exception or other EJB exceptions. When this exception is thrown, the solution controller retries the command if the command is retriable and the exception was caused by either a database dead lock or database rollback.

DataBean's implement more caching than a AccessBean, so POTENTIALLY REDUCE calls to the database. 

DataBean's are appropriate for use in the JSP pages that make up the site / WEB application as the number of instances is likely to be low and it should HELP control the number of transactions hitting the database.

AccessBean's are MUCH less memory intensive, so can be more appropriate to looping processes etc.

DataBean's implement more caching than a AccessBean, so potentially reduce calls to the database. 

DataBean's are appropriate for use in the JSP pages that make up the site / web application as the number of instances is likely to be low and it should help control the number of transactions hitting the database.

AccessBean's are much less memory intensive, so can be more appropriate to looping processes etc.

No, a TASK COMMAND is not set up to handle web requests directly.

No, a task command is not set up to handle web requests directly.

ACPEXTRACT EXTRACTS the ACCESS control POLICY and access group information in the DATABASE and generates files that capture the information in XML format.

acpextract extracts the access control policy and access group information in the database and generates files that capture the information in XML format.

acpnlsload loads the XML FILES containing the display names and descriptions, into the APPROPRIATE DATABASES.

acpnlsload loads the XML files containing the display names and descriptions, into the appropriate databases.

ACUGLOAD is the UTILITY to LOAD the USER access group in the appropriate database.

acugload is the utility to load the user access group in the appropriate database.

It is not necessary to ENTER data in the CMDREG table, but an ENTRY should be MADE in the struts-config.xml. The controller command can be registered in the CMDREG table by xml and SQL query.

It is not necessary to enter data in the CMDREG table, but an entry should be made in the struts-config.xml. The controller command can be registered in the CMDREG table by xml and SQL query.

The catalog subsystem or Catalog Management provides ONLINE catalog navigation, PARTITIONING, categorization, and associations. In addition, the catalog subsystem includes support for personalized interest lists and custom catalog DISPLAY pages. The catalog subsystem contains all LOGIC and data relevant to an online catalog, including catalog groups (or categories), catalog entries, and any associations or relationships among them. 

Tables USED for Catalog subsystem

1. CATENTRY
2. CATENTREL

The catalog subsystem or Catalog Management provides online catalog navigation, partitioning, categorization, and associations. In addition, the catalog subsystem includes support for personalized interest lists and custom catalog display pages. The catalog subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries, and any associations or relationships among them. 

Tables used for Catalog subsystem

1. CATENTRY
2. CATENTREL

The MARKETING subsystem is a component of the WebSphere Commerce Server, and provides numerous marketing concepts to your site, designed to increase brand AWARENESS, and to attract and retain customers. Components of the marketing subsystem provide functionality to create marketing campaigns, INCLUDING customer SEGMENTS and ADVERTISING; and e-mail activities.

Various components are:

1. Promotions
2. Auctions
3. eSpots
4. e Mail Campaigns
5. Hubs and Extended sites for affiliates

The Marketing subsystem is a component of the WebSphere Commerce Server, and provides numerous marketing concepts to your site, designed to increase brand awareness, and to attract and retain customers. Components of the marketing subsystem provide functionality to create marketing campaigns, including customer segments and advertising; and e-mail activities.

Various components are:

1. Promotions
2. Auctions
3. eSpots
4. e Mail Campaigns
5. Hubs and Extended sites for affiliates

A SMART data bean uses a LAZY fetch method to RETRIEVE its own data. This type of data bean can provide better performance in situations where not all data from the access bean is required, since it RETRIEVES data only as required.

A smart data bean uses a lazy fetch method to retrieve its own data. This type of data bean can provide better performance in situations where not all data from the access bean is required, since it retrieves data only as required.

A retriable COMMAND is a CONTROLLER command that can re-execute itself after ENCOUNTERING a system-level EXCEPTION during the command EXECUTION.

A retriable command is a controller command that can re-execute itself after encountering a system-level exception during the command execution.

Fulfillment CENTER or Delivery Center is the STORE or warehouse from where the actual delivery of merchandise TAKES PLACE.

Fulfillment center or Delivery Center is the store or warehouse from where the actual delivery of merchandise takes place.

Part of the order that needs to be SHIPPED to a particular ADDRESS. There could be an Order where different portions needs to be DELIVERED to different addresses. Each PORTION in such case is a suborder.

Part of the order that needs to be shipped to a particular Address. There could be an Order where different portions needs to be delivered to different addresses. Each portion in such case is a suborder.

It's the STORE ARCHIVER that HOLDS the store Assets in the compressed FORM.

It's the Store Archiver that holds the store Assets in the compressed form.

Attribute DICTIONARY is a set of common attributes that can be reused by multiple PRODUCTS. 

The attribute dictionary provides a central place to manage SHARED attributes, with the following features:

• The ability to standardize attributes.
• The ability to easily compare attributes shared by products and SKUs.
• The ability to QUICKLY CHANGE attributes in one place to affect all catalog entries.

Attribute dictionary is a set of common attributes that can be reused by multiple products. 

The attribute dictionary provides a central place to manage shared attributes, with the following features:

Asset stores are COLLECTIONS of sharable RESOURCES (BUSINESS ARTIFACTS, business PROCESSES and storefront assets) that can be leveraged in other stores. 

Asset stores are collections of sharable resources (business artifacts, business processes and storefront assets) that can be leveraged in other stores. 

By specifying XSiteScriptingProtection WITHIN wc-server.xml. Prohibited characters and attributes are SPECIFIED within XSiteScriptingProtection to protect the APPLICATION from any XSS attach.

By specifying XSiteScriptingProtection within wc-server.xml. Prohibited characters and attributes are specified within XSiteScriptingProtection to protect the application from any XSS attach.

We can see , monitor and can even CHANGE dynacache MANUALLY but for that we need to INSTALL a seperate APPLICATION PROVIDED by WCS.

We can see , monitor and can even change dynacache manually but for that we need to install a seperate application provided by WCS.

Dynacache in WCS is the OBJECT cache. INSTEAD of creating OBJECTS again and again , the store objects are rendered on the basis of MATCHED rules. Caching rules are stored in a configuration file called cachespec.xml.

Dynacache in WCS is the object cache. Instead of creating objects again and again , the store objects are rendered on the basis of matched rules. Caching rules are stored in a configuration file called cachespec.xml.

eSpot is the MECHANISM in WCS to schedule and display DYNAMIC CONTENT. Content management for these SLOTS are done through Accelarator.

eSpot is the mechanism in WCS to schedule and display dynamic content. Content management for these slots are done through Accelarator.

Hub and Extended sites /stores are USED in case of selling through partners and affiliates. Hub is the central site around which extended stores are created by/for the respective partner / affiliate. STORE owner performs the extended site ADMINISTRATIONS whereas overall CONTROL over merchandise remains with the site.

Hub and Extended sites /stores are used in case of selling through partners and affiliates. Hub is the central site around which extended stores are created by/for the respective partner / affiliate. Store owner performs the extended site administrations whereas overall control over merchandise remains with the site.

B2C business deals with selling merchandise DIRECTLY to consumers WHEREAS B2B business deals with selling / COORDINATION with other businesses ( partners , distributors , affiliates etc ) for selling merchandise.

B2C business deals with selling merchandise directly to consumers whereas B2B business deals with selling / coordination with other businesses ( partners , distributors , affiliates etc ) for selling merchandise.

Product refer to CATEGORY of Items and HENCE can't be ASSOCIATED to a particular Stock keeping unit. Items can only be targeted while creating promotions.

Product refer to category of Items and hence can't be associated to a particular Stock keeping unit. Items can only be targeted while creating promotions.

SKU is Stock KEEPING UNIT. ITEMS are referred to as SKU as they are the NARROWEST identifier for which business needs to track quantity.

SKU is Stock keeping unit. Items are referred to as SKU as they are the narrowest identifier for which business needs to track quantity.

This table records the changes to PRODUCT or category INFORMATION in the database. This is referred by WCS for invalidating DYNACACHE.

This table records the changes to product or category information in the database. This is referred by WCS for invalidating dynacache.

MVC, DISPLAY DESIGN and COMMAND.

MVC, Display Design and Command.