wcs

In WCS7 is that with an eSpot you can define default content to appear in there without having to create an eSpot. This is useful for just a single piece of content. However if you add multiples (which you are allowed to do) you cannot sequence them at all and it’s because of the tables, which are used. So in case you wanted to know. - When creating new web activity the data is stored in DMACTIVITY, DMELEMENT and DMELEMENTNVP. Recommended content is stored in DMELEMENTNVP as Name ('collateralIdList') Value(COLLATERAL.COLLATERAL_ID ) pairs and DMELEMENTNVP.SEQUENCE is field where sequence is stored. - For marketing spot default content to display in an e-Marketing Spot it is stored in DMEMSPOTDEF table. DMEMSPOTDEF.CONTENT is where the identifier of the content is stored. DMEMSPOTDEF table doesn't have any field where the sequence would be stored/set, which is why you cannot sequence it.

WebSphere Commerce V7.0 Feature Pack 6 , the   announcement   was released on the IBM site a few days ago, but today it is finally available in the IBM software catalog. What’s new? New features available with WebSphere Commerce Version V7.0 Feature Pack 6 include dynamic merchandising, starter store enhancements, and enhancements to business user tools, the Data Load utility, WebSphere Commerce search, and store preview. ·          Improved capabilities to help ensure the most relevant products are offered when shoppers conduct a search ·          The ability to better target shoppers with recommendations based on their current search or navigation point ·          The ability to help business users make changes more easily to catalogs, marketing, and promotions Features: The   mobile integration   has taken a big step forward by using the IBM Worklight platform. There is a reference hybrid Android application included which I’m very excited to take a look at. I’m very

Model-View-Controller design pattern. Display design patterns. Command design patterns. Model-View-Controller design pattern: The model-view-controller (MVC) design pattern specifies that an application consist of a data model, presentation information, and control information . The model (for example, the data information) contains only the pure application data; it contains no logic describing how to present the data to a user. The view (for example, the presentation information) presents the model's data to the user. The view knows how to access the model's data, but it does not know what this data means or what the user can do to manipulate it. Finally, the controller (for example, the control information) exists between the view and the model. It listens to events triggered by the view (or another external source) and executes the appropriate reaction to these events. In most cases, the reaction is to call a method on the model. Since

   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: User. Action. Resource. 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: Groupa

This is to allow for application implementation of the type of optimistic locking that Oracle does at the DB level. It allows lowered levels of locking and not surprisingly is discussed in the info center for both Version 6 (introduced) and Version 7

   Refresh copy helper is to retrieve the fields using primary key like select * from where memberId, and commitCopyhelper is to insert or update fields ( The method refreshCopyHelper() writes to the hash table from the database)

WebSphere Commerce V7.0 Feature Pack 4 includes: ·          Smarter stores optimized for mobile devices ·          Facebook integration allowing shoppers to click and share ·          Programming model enhancements Starter stores optimized for mobile devices ·          Smart phone and tablet starter stores provide rich storefronts for several mobile devices and platforms. They can be deployed on mobile devices and accessed using the mobile Web or as native or hybrid applications. See the What’s new overview of smart phone and tablet starter stores for a complete look at this exciting new functionality: o     What’s new: Smart phone and tablet starter stores with location-based services . The What’s new overview contains information for smart phone and tablet starter stores with location-based services, including: o     The benefits of enabling smart phone and tablet starter stores. o     Related features of Feature Pack 4, such as REST services. o     User role-s

Generally controller command is the main command which we used to call from the JSP to process the request, But task command is used to perform some specific task like for inventory check, price check, these are handled through task commands, so task command are command which perform specific task for controller command. DIFFERENCE - By the above statement we can visualize that Controller command is required to be configure in the struts file, but task command is not required to be configured in struts, rest everything is same in both.

cross-sell A merchant suggests other catalog entries based on an already chosen catalog entry. For example, a merchant can suggest a high-resolution color printer when a digital camera is purchased, or a particular type of batteries when a flashlight is purchased. up-sell A merchant suggests a better catalog entry based on the one selected. For example, a merchant can suggest a higher quality television when a low-end model is selected.

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 representation of a WebSphere Commerce Entity bean. There are 3 types of data beans: 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 t

A process of communicating with Commerce commands in an Ajax fashion without refreshing the page. The response generated in the Command is converted to a JSON ( JavaScript Object Notation). However this is not done using any Ajax framework at the client end. Commands Create a regular command interface and implementation in Commerce. Only difference in writing this AjaxAction based command compared to a regular command is the inclusion of the line at the end of performExecute() method setResponseProperties(rspProp); Here rspProp is the TypedProperty variable in the method. All the data that is required to be sent back to the source (JSP/browser) that called this command should be placed in the TypedProperty variable. Struts Configuration ·          Instead of setting the type of < action-mappings > as BaseAction , it is set to AjaxAction ·          There is no <global-forwards> entry required for this since only data object is got back instead o

In the IBM Rochester lab, the Business Solutions Test (BST) team has implemented IBM's WebSphere Commerce in several of its customer-like scenarios. While doing so, the BST team discovered the importance of the Clean WCS Database (CLNWCSDB) command. Here, I'll explain how to use the command for both WebSphere Commerce Suite Version 5.1 (WCS V5.1) and WebSphere Commerce Version V5.4. Cleaning up unnecessary data in a WebSphere Commerce site can improve performance, decrease the amount of storage needed to host the WebSphere Commerce site, and decrease the amount of time required to do future upgrades and migrations. A number of different tables can be cleaned up, and this cleanup can be done on an individual basis, depending on the needs of the site. If rows need to be deleted from a WebSphere Commerce database, it is important to use the CLNWCSDB command in order to properly handle constraints.   CLNWCSDB works in conjunction with the WebSphere Commerce CLEANCONF tab