To enable the attribute dictionary and non attribute dictionary attribute functionality concurrently

1. witch the implementation of ResolveSkuCmd to ResolveSkuAllCmdImpl in CMDREG table:

a. Open a respected database command window.
b. Run the following SQL command:

SQL> update cmdreg set classname='com.ibm.commerce.catalog.commands.ResolveSkuAllCmdImpl' where interfacename ='com.ibm.commerce.catalog.commands.ResolveSkuCmd';

2. To enable the attribute dictionary only, switch the implementation of ResolveSkuCmd to ResolveSkuNewCmdImpl in the CMDREG table:

a. Open a respected database command window.
b. Run the following SQL command:


SQL> update cmdreg set classname='com.ibm.commerce.catalog.commands.ResolveSkuNewCmdImpl' where interfacename ='com.ibm.commerce.catalog.commands.ResolveSkuCmd';

c. Customize the Catalogs tool to hide the local attribute table to prevent users from using the table to create a new attribute in the legacy table.

Note: To change the ResolveSkuCmd implementation for one store, you create a new row in the CMDREG table with the STOREENT_ID set to the store ID. If you set the STOREENT_ID to "0", the command applies to all the stores.


There are two types of attribute. Determine type of attribute you want to add

i. Allowed value attribute
ii. Assigned value attribute

Note: Supported data types : Text (STRING), Whole number(INTEGER) and Decimal Number(FLOAT)

To enable the attribute dictionary and non attribute dictionary attribute functionality concurrently

1. witch the implementation of ResolveSkuCmd to ResolveSkuAllCmdImpl in CMDREG table:

a. Open a respected database command window.
b. Run the following SQL command:

SQL> update cmdreg set classname='com.ibm.commerce.catalog.commands.ResolveSkuAllCmdImpl' where interfacename ='com.ibm.commerce.catalog.commands.ResolveSkuCmd';

2. To enable the attribute dictionary only, switch the implementation of ResolveSkuCmd to ResolveSkuNewCmdImpl in the CMDREG table:

a. Open a respected database command window.
b. Run the following SQL command:


SQL> update cmdreg set classname='com.ibm.commerce.catalog.commands.ResolveSkuNewCmdImpl' where interfacename ='com.ibm.commerce.catalog.commands.ResolveSkuCmd';

c. Customize the Catalogs tool to hide the local attribute table to prevent users from using the table to create a new attribute in the legacy table.

Note: To change the ResolveSkuCmd implementation for one store, you create a new row in the CMDREG table with the STOREENT_ID set to the store ID. If you set the STOREENT_ID to "0", the command applies to all the stores.


There are two types of attribute. Determine type of attribute you want to add

i. Allowed value attribute
ii. Assigned value attribute

Note: Supported data types : Text (STRING), Whole number(INTEGER) and Decimal Number(FLOAT)

Solr Re-indexing steps WCS 7

Pre-requests: you need to have V7 FEP2+.

IBM WCS is now a fully operational search engine. the product now includes Lucene Solr as the interal search engine, also incorporates industry best practices.


Once you get the latest database, follow these steps to re-index the products.

1. Install "WebSphere Commerce Developer Enterprise" version 7
2. Update "WebSphere Commerce Developer Enterprise" to version 7.0.0.5
3. Stop Server
4. Enable the Store Enhancement Features
1. cd WCDE_installdir\bin
2. enableFeature.bat -DfeatureName=store-enhancements
5. Publish the Madisons Feature Pack Store Archive:
1. Publish Madisons-FEP.sar
6. Enable the Solr foundation
1. cd WCDE_installdir\bin
2. enableFeature.bat -DfeatureName=foundation [DsolrHome=C:\IBM\WCDE_ENT70\search\solr\home]
7. Setup the Search Index: (WC Server must be Stoped)
1. cd 'WCDE_installdir'\components\foundation\subcomponents\search\bin
2. setupSearchIndex.bat -masterCatalogId 10001 -instance WCDE_ENT70 -dbuser db2admin -dbuserpwd db2admin [-solrhome C:\IBM\WCDE_ENT70\search\solr\home]
3. To see log file : \WCDE_ENT70\components\foundation\subcomponents\search\log\wc-search-index-setup.log
4. Once successfully completed the status code could be : Program exiting with exit code: 0
8. Preprocess the Search index: (Run the di-preprocess.bat file against the search index, again server stopped at this point)
1. cd WCDE_installdir\bin
2. di-preprocess.bat C:\IBM\WCDE_ENT70\search\pre-processConfig\MC_10001\DB2\ [-fullbuild true] [-localename en_US]
9. Test the current Solr index to ensure that a request can be recognized: (Server should be started)
1. http://host_name/solr/Default/select?q=*%3A*
10. Build out the index (first make sure to start the WC server):
1. cd WCDE_installdir\bin
2. di-buildindex.bat -masterCatalogId 10001 
11. Test the indexed Solr index to ensure results are returning:
1. http://localhost/solr/MC_10001_CatalogEntry_en_US/select?q=catentry_id:10251
12. Enable the store to display the search breadcrumb and faceting filters:
1. Open Management Center
2. Click "Management Center Tools" menu and select "Store Management"
3. Select the "Madisons" store and click the "Catalog" tab
4. check "Search-based navigation"
5. click Save
13. Test live on the starter store:
1. http://localhost/webapp/wcs/stores/servlet/Madisons/index.jsp
2. http://localhost/webapp/wcs/stores/servlet/en/eliteesite/home

Deleting order items and requisition lists

When a user deletes an order item or requisition list item the table rows representing those items are removed from the database. If enabled, these rows are updated to belong to the trashcan. You can clear the trashcan by running the OrderTrashCanClear scheduled job which will delete the rows, or by using the Database Clean up utility. This feature is disabled by default.

It is highly recommended that you clean your database of order items both before you enable the OrderTrashCan feature, and periodically afterwards. Order item deletion is a common operation, and as a result, a large number of deleted order items can build up in the ORDERITEMS table.

1. Open wc-sever.xml configuration file
2. Within the file, the text can be put next to "ExpectedInventorySynchronize" element.


TrashCanRequisitionListSegmentLen="30"
TrashCanOrderItemSegmentLen="50"
TrashCanEnabled="true"/>

This setting deletes order item entries from the ORDERITEMS table. If TrashCanEnabled is set to "true", when a user deletes an order item or requisition list item, the table rows representing those items are not deleted from the database. Instead, the items are updated to belong to the trashcan.

Disable Access Control Policy WCS (Developent)

Developer while creating new Views commands controllers is to define the access control policy, Although it is a must have step for security reasons, I have always wondered why we need to do this during development time, Just to test and views without having to create the policies during development. Well yes, It's possible with a simple configuration.

In toolkit, navigate to your instance.xml file, on WCS 7 , this will be typically located in
D:\IBM\WCDE_ENT70\workspace\WC\xml\config\wc-server.xml



In toolkit, navigate to your instance.xml file, on WCS 7 , this will be typically located in
D:\IBM\WCDE_ENT70\workspace\WC\xml\config\wc-server.xml

you have to find xml elemented named "Instance

AccessControlUnitTest="true"

and place above attribute with value immediately after "Instance" Elements

Save and restart your test server, from now on any controller and view command that you create will not require a acppolicy to be loaded.

Configuring tracing and logging for the loading utilities

you can configure an additional message log file, messages.txt, and a trace file, traces.txt, for the loading utilities. This can be helpful in getting more information to help determine any problems you may encounter.

1. Open the following in a text editor:

WC_installdir/xml/loader/WCALoggerConfig.xml

Note: There are two locations of the WCALoggerConfig.xml file. WCDE_installdir/xml/loader/WCALoggerConfig.xml is used by the loader utilities when run from the command line, and the file WC_installdir/instances/ instance_name/xml/loader/WCALoggerConfig.xml is used by the loader utilities in the server context, for example during the store publish process.


The component tags define the components for which trace is enabled.

How to find version of fix pack of WAS?

1. Go to WAS_installer\runtimes\base_v7\bin>versionInfo.bat

output:

WVER0010I: Copyright (c) IBM Corporation 2002, 2005, 2008; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.1.26, dated 8/9/08

--------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------

Report at date and time November 11, 2011 5:39:01 PM IST

Installation
--------------------------------------------------------------------------------
Product Directory C:\Program Files\IBM\SDP\runtimes\base_v7
Version Directory C:\Program Files\IBM\SDP\runtimes\base_v7\properties\version
DTD Directory C:\Program Files\IBM\SDP\runtimes\base_v7\properties\version\dtd
Log Directory C:\Program Files\IBM\SDP\runtimes\base_v7\logs
Backup Directory C:\Program Files\IBM\SDP\runtimes\base_v7\properties\version\nif\backup
TMP Directory C:\DOCUME~1\SETTU~1.GOP\LOCALS~1\Temp

Product List
--------------------------------------------------------------------------------
BASE installed

Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server
Version 7.0.0.13
ID BASE
Build Level cf131039.07
Build Date 10/2/10
Architecture Intel (32 bit)

--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------

Inventory issues

A. Enable the following trace components on your WebSphere Commerce instance server:

com.ibm.websphere.commerce.WC_ORDER=all:com.ibm.websphere.
commerce.WC_INVENTORY=all

B. The environment is now configured to capture the necessary data when the problem occurs. Reproduce the problem on your environment and proceed to the next step.

3. Collect all necessary data

1. Trace from the WebSphere Commerce Server:
\logs\server1\*
2. What type of inventory system are you using for your store? For example: Are you using WebSphere Commerce to manage your inventory, are you integrating with a backend system, or are you not tracking inventory at all?
To determine the type of inventory, run the following query:

SELECT INVENTORYSYSTEM FROM STORE WHERE STORE_ID=

The possible values are:

-1=ATP
-2=Non-ATP
-3=No inventory
-4=External inventory management system (introduced in WC 6.0.0.1)

3. Configuration Data from the Database

a) SELECT * FROM STORE
b) SELECT * FROM FFMCENTER
c) SELECT * FROM SHPARRANGE
d) If you are using the ATP inventory, collect the following data:

SELECT * FROM BASEITEM WHERE BASEITEM_ID=(SELECT BASEITEM_ID FROM CATENTRY WHERE CATENTRY_ID=)
SELECT * FROM STOREITEM WHERE BASEITEM_ID=
SELECT * FROM ITEMSPC WHERE BASEITEM_ID=
SELECT * FROM INVSTVW WHERE STORE_ID= AND
ITEMSPC_ID=(SELECT ITEMSPC_ID FROM CATENTRY WHERE CATENTRY_ID=)

Otherwise, if you are using non-ATP inventory, collect the following data:
SELECT * FROM INVENTORY WHERE STORE_ID= AND CATENTRY_ID=

Scenario
Describe the failing scenario in detail.

No Products Can Be Added To Shopping Cart

All WebSphere Commerce sites running version 5.6.x, 6.0 and 7.0 might experience this problem.

Shoppers cannot add items to the shopping cart. A message similar to the following is displayed when the shopper adds an item:

CMN2022E: The command is unable to determine an appropriate fulfillment center for an OrderItem.

Content

PROBLEM:

When shoppers try to add items to cart, the following exception is displayed in the trace log with WC_ORDERS:

[6/23/08 4:40:18:116 CDT] 7bd409f2 WC_ORDER d mrCJugify4dA55bTXDzHHQEg6SE%3d%0a com.ibm.commerce.fulfillment.commands.ShippingArrangementWrapper.isValid Shipping arrangement 10001 is not effective for the specified time.
com.ibm.commerce.fulfillment.commands.ResolveFulfillmentCenterCmdImpl.performExecute No fulfillment center has enough inventory: catalogEntryId=333109, quantity=1.0, shipModeId=10001
[6/23/08 4:40:18:117 CDT] 7bd409f2 CommerceSrvr E com.ibm.commerce.fulfillment.commands.ResolveFulfillmentCenterCmdImpl performExecute CMN2022E: The command is unable to determine an appropriate fufillment center for an OrderItem.


NOTE: If you are not experiencing this problem on your site then your store was not published with this condition and no immediate actions are required.



SOLUTION:
Check the SHPARRANGE table and verify that the ENDDATE field has not expired. If it has expired or is set to expire on a date earlier than desired for your site, update this field as per the examples below.

Below are some examples of how to change the ENDDATE.


To change the shipping ENDDATE from '2008-06-22-23.00.00.000000' to a setting which will never expire, update the database with one of the following statements:

For DB2:
"update shparrange set enddate = null where enddate = '2008-06-22-23.00.00.000000'"

For Oracle:
"update shparrange set enddate = null where enddate = timestamp'2008-06-22 23:00:00'"



To change the shipping arrangment ENDDATE from '2008-06-22-23.00.00.000000' to expire in 2018, update the database with one of the following statements:

For DB2:
"update shparrange set enddate = '2018-06-22-23.00.00.000000' where enddate = '2008-06-22-23.00.00.000000'"

For Oracle:
"update shparrange set enddate = timestamp'2018-06-22 23:00:00' where enddate = timestamp'2008-06-22 23:00:00'"

Tunning WCS Developer toolkit

In addition to increasing the JVM heap size, you can perform few more tuning to developer toolkit to improve the performance of development toolkit.

Tuning Apache Derby Database

Derby is a filesystem based database, there are few minor configuration changes that can be
performed on the toolkit Derby properties to improve overall performance of the WCS Developer Toolkit.

The file is located in following location for WCS V7:
IBM\SDP\runtimes\base_v7\derby\derby.properties


With this Derby will be able to access data from cache instead of filesystem, this will reduce overall I/O as data will be read from the cache.

derby.storage.pageCacheSize = 10000
derby.storage.pageSize = 8192

How do enable web service(Webservices over HTTP) in Websphere commerce?

1. Open the Administration Console and select Site or Store.
2. Click Configuration > Transports.
3. The Webservices over HTTP transports should appear in the list and as inactive.

If the transport want to configure is active

1. Select the check box next to the inactive transport.
2. Click Change Status.
3. The transport status should change from Inactive to active.

Enable database SQL statement trace log on Dev

1. Logon WebSphere Administrative console.
2. From left panel select Troubleshooting-->logs and trace->server1->change log details levels
3. Expand com.ibm.ejs.*
4. Expand sub element com.ibm.ejs.persistences.*
5. Enable all Messages and traces for com.ibm.ejs.persistence.EJSDBCFinder and com.ibm.ejs.persistence.EJSJDBCPersister.



6. Click OK and Save.
7. Restart App Server.

Listing enabled WebSphere Commerce features in development environment

we can list the features that have been enabled on WCS 7.

1. Run the check enablement status: WCDE_installdir\bin\checkEnablementStatus.bat
2. The status message appears in the log file. WCDE_installdir\logs\enableFeature.log

Create new Websphere Commerce Database schema using developer machine

Steps to follow

1. Create a user (schema) with DBA privileges in oracle 11g.
2. Go to command prompt where WCS Installed
Ex: D:\WCDE_ENT70\bin>
3. Prepare setdbtype.bat statement.
Ex: setdbtype oracle D:\app\testuser\product\11.2.0\client_1 UATDB wcs7 wcs7 wcs7 wcs7 192.168.140.2 1521 createdb

4. Execute the setdbtype.bat file as mentioned above.


5. setdbtype.bat command will open one more window


6. Verify the createdb.oracle.log file.
7. WCS schema created.

How do you find installed product in Websphere commerce?

if it's windows:

<WCS_INSTALLER>\bin>versionInfo.bat

WVER0010I: Copyright (c) IBM Corporation 2002, 2005; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.1.13, dated 3/29/06

--------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------

Report at date and time June 23, 2011 5:45:22 PM IST

Installation
--------------------------------------------------------------------------------
Product Directory D:\WCDE_E~1
Version Directory D:\WCDE_E~1\properties\version
DTD Directory D:\WCDE_E~1\properties\version\dtd
Log Directory D:\WCDE_E~1\logs
Backup Directory D:\WCDE_E~1\properties\version\update\backup
TMP Directory C:\DOCUME~1\testuser\LOCALS~1\Temp

Product List
--------------------------------------------------------------------------------
Installed Product
--------------------------------------------------------------------------------

Name IBM WebSphere Commerce
Version 7.0.0.2
ID wc.toolkit.be
Build Level 101129asup
Build Date 30/11/10

Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Commerce
Version 2.0.0.0
ID wc.fep2
Build Level 101126dev
Build Date 26/11/10

--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------

Deprecated functionality in Authoring Server in WCS 7

1. Managed Files

• The Manage Files feature in WebSphere Commerce Accelerator is deprecated for WebSphere Commerce Version 7 Feature Pack 2. This feature was used to upload new catalog files, such as images of products for your store, or to reorganize existing files.

Rcommanded Action:

• Use the Assets tool in Management Center to work with attachments, managed files, and managed directories.

2. stagingcheck utility

• The stagingcheck utility has been discontinued.

Rcommanded Action:

• As an alternative, run the stagingprop utility with the transaction parameter set to one (the default value) and the batchsize parameter set to 0. If an error is encountered during the stagingprop transaction, then the entire process is rolled back without any changes to staging or production servers.
  

What is password invalidation? How to Enabling?

Password invalidation, when enabled, requires WebSphere Commerce users to change their password if the user's password has expired. In this case, the user is redirected to a page where they are required to change their password. Users are not able to access any secure pages on the site until they have changed their password.

Enable password invalidation

There are two way can enable password invalidation.

First Step: Directly modify wc-server.xml file.

1. Locate wc-server.xml file
2. Update strPasswordInvalidationSetting = WcsApp.configProperties.getValue("PasswordInvalidation/enabled", "false");
3. Restart your WebSphere Commerce instance.

Second Step: Using Configuration Manager.

1. Open the Configuration Manager.
2. Traverse to the Password Invalidation node for your instance as follows: WebSphere Commerce > node_name > Commerce > Instance List > instance_name > Instance Properties > Password Invalidation
3. To activate the password invalidation feature, click the Enable check box.
4. To apply your changes to Configuration Manager, click Apply. Upon successfully updating the configuration for your instance, you will receive a message indicating a successful update.
5. Restart your WebSphere Commerce instance.

Note: From the above, Websphere best practice is Second Step: (Using Configuration Manager)