WebSphere Commerce 7 is here!

On Friday WebSphere Commerce v7 GAed and we’ve received some great press. Here are some of the articles below:

InternetRetailer Coverage: IBM’s WebSphere Commerce 7 supports mobile and social commerce

With the WebSphere Commerce 7 e-commerce platform IBM Corp. released yesterday, shoppers can use a synchronized shopping cart across conventional and mobile commerce sites, says Errol Denger, director of business and product strategy for WebSphere Commerce. Retailers can coordinate marketing across web sites, mobile phones and social networks, he adds.

“We’re enabling large and small retailers to deliver an optimal branding experience, whether it’s on the web or mobile commerce device,” Denger says. “This is being driven by our clients who are saying they don’t want their mobile commerce channel to be separate.”

The overall idea, he says, is to help retailers connect with customers however shoppers want to buy online. Shoppers with a web-enabled mobile phone, for example, will be able to browse an online store built on WebSphere Commerce 7, conduct side-by-side product comparisons that a retailer makes available, and make an instant online purchase. Delivery can be to the shopper’s home or, if the retailer has integrated its store systems into its e-commerce platform, for pickup at a store. Shoppers would also be able to use their mobile phones to check the availability of desired inventory in the retailer’s nearest store and upload directions before opting for in-store pickup.

WebSphere Commerce 7 also supports new levels of personalized marketing, Denger says. For example, retailers will be able to use it to design merchandising and marketing campaigns that make product offers based on such behavior as the average number of product reviews a shopper is known to post each month. Shoppers who are prolific review writers have been known to spend more online than shoppers who don’t write reviews, Denger notes, making them prime candidates for a retailer’s offers.

In another example, he says, an offer could be triggered by the type of social networking site a shopper was on before arriving at a retail site. If a shopper came from a Facebook or Google search page about Harley-Davidson touring-style motorcycles, for instance, a retailer using WebSphere Commerce 7 could present her with a customized landing page based on the particular interests expressed on that Facebook or Google page.

Although other e-commerce technology companies are integrating mobile commerce into their platforms, IBM stands out with a platform that also strongly integrates with store point-of-sale terminals and kiosks, says Nikki Baird, managing partner with research and advisory firm Retail Systems Research LLC. “When enabling a cross-channel strategy, WebSphere Commerce can now better become a cornerstone in a multi-leg strategy,” she says.

IBM is still in the early stage of cross-channel technology development, the company says. In June it announced a five-year, $100 million research initiative to improve mobile commerce services worldwide. “Advancements in mobile devices are reshaping the way customers interact with brands, expanding beyond mere information exchange to true online commerce,” IBM said in announcing WebSphere Commerce 7. “Increasingly, the beneficiaries of this growth are online retailers.”

Other Coverage:





Allan xu's Blog: WebSphere Commerce Acceleator customization

Two scenarios of customizing Accelerator
Create a dynamiclist in Accelerator:

1. Update instance.xml to add entry of new resources.xml

locate \WC\xml\config\wc-server.xml, search
<ToolsGeneralConfig DTDPath=”tools/common;tools/devtools;tools/bi;tools/catalog;schema/xml;sar” XMLCacheSize=”0″ XMLPath=”tools;tools/devtools;WEB-INF/xml/tools;WEB-INF” developmentMode=”false”

you can udpate developmentMode to true, this allows the xml/properties files being refreshed in run time.

Assume we add codes into “custom” folder, then add new line like this:

<resourceConfig file=”custom/resources.xml”/>

2. Create resources.xml in \WC\xml\tools\custom location.

the custom must match #1 “custom”. sample resources.xml

<!DOCTYPE resourceConfig SYSTEM “../common/Resources.dtd”>

<!– Operational Time Tools specific model extensions –>
<resourceConfig >

<resource nameSpace=”custom”>

<!– resource bundle file mappings –>

bundle=”com.ibm.commerce.tools.sears.properties.customRB” />

<!– XML file mappings –>

file=”custom/customXMLr.xml” />



name space is defined as “custom”, then the resource bundle can be referenced as custom.customRB.

3. Create menu

Locate this file: WC\xml\tools\common\CommerceAcceleratorMHS.xml

depends on what type of your store, you may have to find the right xml file.

Run “select store_id,storetype from store where store_id=xxx” to find out what store type is.

In eSite, the store type is MHS.

  • B2C = Consumer direct
  • BBB = Basic B2B direct
  • B2B = B2B direct
  • CHS = Channel hub
  • CPS = Catalog asset store
  • RHS = Consumer direct reseller store
  • BRH = B2B reseller store
  • RPS = Consumer direct reseller storefront asset store
  • BRP = B2B reseller storefront asset store
  • DPS = Distributor asset store
  • DPX = Distributor proxy store
  • SCP = Supplier hub
  • SPS = Supplier asset store
  • SHS = Supplier hosted store
  • HCP = Hosting hub
  • PBS = Store directory
  • MHS = Consumer direct hosted store
  • BMH = B2B hosted store
  • MPS = Consumer direct hosted storefront asset store
  • BMP = B2B hosted storefront asset store.

Open above xml file, follow the existing pattern, create the menu / node accordingly.

Notice “users” define the user access control.

In this example, we create a new sub menu called “process pending order” under “Operation” menu.

search for ” <menuitem ” , and <node url=””/>

under this separator, we create a new node, add below codes:


<node name=”pendOrder”
users=”cusRep cusSup opMgr seller”/>

where name=”pendOrder”, you need register this name in properties: WC\properties\com\ibm\commerce\tools\properties\mccNLS.properties . at the end of file, add:

” pendOrder = process the pending order. ”

this will be showing in the Accelerator as node name. Add locale properties as needed.

url , is the URL when you click on this sub menu (node). This URL will open a dynamic list view, which contents are displaying with the result of view: CustomLandingView. we will create this view later.

users is the access control of the list of allowed users

4. resourceXML file (customXML.xml)

in #2, the resource config file define resourceXML, “custom/customXML.xml”,

create this file at WC\xml\tools\custom\resourceXML

The resourceXML defines a type of panel, like dynamci list, wizard, dialog, etc. Base on what panel you requried, create related xml files.

<!DOCTYPE action SYSTEM “../common/List.dtd”> will determine the type by the dtd. The dtd files can be found in WC\xml\tools\common folder.

in #3, it defines the url of the button to “NewDynamicListView?ActionXMLFile=custom.customXML”, the page will load the dynamic view, then render the page/buttons base on the ActionXMLFile (custom.customXML).



<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE action SYSTEM “../common/List.dtd”>

<action resourceBundle=”custom.customRB”

<parameter listsize=”10″
<scrollcontrol title=”theTitle”
display=”false” />

<controlpanel display=”true” />

users=”cusRep cusSup opMgr seller siteAdmin” />
users=”cusRep cusSup opMgr seller siteAdmin” />
users=”cusRep cusSup opMgr seller siteAdmin” />

<jsFile arc=”/wcs/javascript/tools/common/Util.js” />
<jsFile arc=”/wcs/javascript/tools/common/DateUtil.js” />


where resourceBundle=”custom.customRB” defines the resourcebundle created in next #4.

ActionXMLFile=”custom.customXML” points to the resourcesXML,

scrollControl display=”false” actually turnning off the scroll control

<button> section defines all the buttons.

name is the propeties key of button name, properites is the custom.customRB points to.(#4)

action = define the javascript associate with this button, use “basefrm.xxx()” . basefrm is system default. the function will be created inside the jsp files or js files whichever uses this xml as resource xml.

again, users defines the access control.

the jsFile are mandatory.

5. Create properties (customRB)

create customRB.properties (locale properites if needed) in folder WC\properties\com\ibm\commerce\tools\custom\properties\

inside the properties, you need define all the keys that you are going to use for buttons/links, etc

6. Create tools controller command and view

the jsp can be created in


add into \WEB-INF\struts-config-migrate.xml for the view/URL entries. (CustomLandingView)

insdie the jsp file, which will be shown in the main content of the dynamic list, you need add :


<%@include file=”../common/common.jsp”%>


CommandContext cmdContextLocale = (CommandContext) request.getAttribute(ECConstants.EC_COMMANDCONTEXT);
Locale jLocale = cmdContextLocale.getLocale();
Integer langId = cmdContextLocale.getLanguageId();
Integer storeId = cmdContextLocale.getStoreId();
String currency = cmdContextLocale.getCurrency();

//use below to load your properties file. Hashtable pendOrderRB = (Hashtable) ResourceDirectory.lookup(“custom.customXML”, jLocale);

<SCRIPT SRC=”/wcs/javascript/tools/common/dynamiclist.js”></SCRIPT>
<SCRIPT SRC=”/wcs/javascript/tools/common/Util.js”></SCRIPT>

function onLoad () {

// This will load the frames parent.loadFrames();

function findPendingOrders(){
// CustomCommandURL’ is the ToolsCommandController returns a redirect URL to show in currect content.

// the returned view must define simliar to this file style to loadFrames,

top.setContent(‘<%=UIUtil.toJavaScript((String) pendOrderRB.get(“report”))%>’,’/webapp/wcs/tools/servlet/NewDynamicListView?ActionXMLFile=custom.customXML&cmd=CustomCommandURL’,false)
function print() {



<!–your layout –>


// This will render the buttons// Mandatory parent.afterLoads(); </script>


You can use JSTL tag lib in your jsp files.

Add “list All Address” function under Operation/Customer/Address button

1. Locating the modification place

1.1. Find the resourceXML. Locate CommerceAcceleratorMHS.xml , Operations ->find customer, get URL, find XMLFile=csr.shopperSearchB2C. From this we know the name space is “csr”.

<node name=”findCustomers”


users=”cusRep cusSup opMgr seller”/>

1.2. Open WC\xml\tools\csr\resources.xml (notice the namespace csr) . Locate shopperSearchB2C (we get from 2 steps before), find

<resourceXMLfont-weight: bold;”>shopperSearchB2C” file=”csr/ShopperSearchDialogB2C.xml” />

csr/ShopperSearchDialogB2C.xml is located under wc\xml\tools\

Inside this xml, located the “search” panel. Because we know at Accelerator, you have to click search button to go in the panel that we are going to modify. Check its URL, which is ShopperSearchB2C.

  • · Open struts-config.xml, locate this link ShopperSearchB2C. path=”/tools/csr/ShopperSearchB2C.jsp”>
  • · Open this file under CommerceAccelerator\WebContent\tools\csr
  • · Inside the file, you will find :

var url = “/webapp/wcs/tools/servlet/NewDynamicListView”;

var urlPara = new Object();



  • · From this we learn: it opens a dynamicList, using resourceXML csr.shopperListB2C, and command to call is ShopperListB2C.

Now, open open the xml base on “csr.shopperListB2C” .

  • · Now open resources.xml file again, find csr.shopperListB2C.


file=”csr/ShoppersActionsB2C.xml” />

Open struts-config.xml file again, locate URL “ShopperListB2C”,

find name=”ShopperListB2C” path=”/tools/csr/ShopperListB2C.jsp”>

  • · Now open resource xml ShoppersActionsB2C.xml at wc\xml\tools\csr, locate button “change”, find its action = “basefrm.changeCustomerInfo()”.

At ShopperListB2C.jsp find the javascript function changeCustomerInfo() definition.

function changeCustomerInfo(id) {

if (id == null && parent.buttons.buttonForm.changeButton.className==’disabled’) {



if (id == null) {

id = parent.getSelected();



// The following url will not contains NLS data

top.setContent(getNotebookTitle(), ‘/webapp/wcs/tools/servlet/NotebookView?XMLFile=csr.shopperNotebook&shrfnbr=’+id+’&locale=<%=cmdContext.getLocale().toString()%>’,true);



The top.setContent() is where to render the page.

It is opening a notebook, with resourceXML called “csr.shopperNotebook”, not we need use resources.xml file again to locate this resource xml file.


file=”csr/ShopperGetProperties.xml” /&gt;

2. Modification:

2.1. Now, finally, at this “ShopperGetProperties.xml” we will find the panel definition where we are going to edit.





helpKey=”MC.optoolsCSR.shopperGetPropertiesAddressPanel.Help” />




helpKey=”MC.optoolsCSR.shopperGetPropertiesContactPanel.Help” />





helpKey=” ” />

this will add a button between Address and Contact.

2.2. Add custom properties

Open resource bundle by looking for ShopperActionB2C.xml, resourceBundle=”csr.userNLS”, to open



listAllAddress = All Addresses

this will display as the button label.

2.3. Create a new view ListAllAddressView by creaeting jsp CommerceAccelerator\WebContent\tools\Sears\ListAllAddressDisplay.jsp

And define in struts-config-ext.xml

<forward className=”com.ibm.commerce.struts.ECActionForward” name=”ListAllAddressView” path=”/tools/Sears/ListAllAddressDisplay.jsp”>

<set-property property=”resourceClassName” value=”com.ibm.commerce.tools.command.ToolsForwardViewCommandImpl”/>


<action path=”/ListAllAddressView”>

<set-property property=”https” value=”0:1″/>


Create Access Control for the new view

insert into acaction (acaction_id, action) values ((SELECT MAX(acaction_id) + 1 from acaction), ‘ListAllAddressView’);

insert into acactactgp (acactgrp_id, acaction_id) values ((select acactgrp_id from acactgrp where groupname=’CustomerServiceRepresentativeViews’),(select acaction_id from acaction where action=’ListAllAddressView’));