When you do database migration from WCS6 to WCS7, migration scripts executes successfully with “check” parameter. When you execute the migration script with “migrate” parameter, some of the steps get executed successfully but when it reaches the IdResolver, it appears to be hung. Execution may appear to be hung at the line,
[idResolve] IDResolving /opt/IBM/WebSphere/CommerceServer70/xml/policies/xml/MergedACUserGroups_en_US_xmltrans.xml
Infact it is not hung, the script will keep on executing but takes long time to complete and if you let it run, it gets executed after long time (Approx. 10-15 hours). This issue is caused due to auto generated SQL by JDBC, which accesses ALL_CONSTRAINTS and ALL_CONS_COLUMNS and hence making it slow.
There is a work around to fix this issue is set the OPTIMIZER_FEATURES_ENABLE value to one of the prior versions of Oracle. Following is the query:
ALTER SESSION SET OPTIMIZER_FEATURES_ENABLE=’10.1.0′;
I felt, this is same as version of the oracle installed on your machine, you can reset once migration scripts are executed successfully
You can also refer to the following links for detailed information:
1. “idresgen (ID Resolver) hangs with Oracle database”
2. “Installing and configuring Oracle 11g database”
-Raghavendra Shanthappa
When you are working on WebSphere Commerce v7 migration, sometimes you may face this issue, the webactivity created for cross sells doesn’t appear at all on the store front. This is due to entry present in config file. You will have to edit this file to make it working.
After migration of both Application and the Database you have to make following changes to the configuration file.
In wc-server.xml, find an entry for
<Marketing version=”Dialog“/>
And change it to
<Marketing version=”Classic“/>
On v6, wc-server.xml doesn’t have an entry for the element .
Note: This is when you are not using Management center marketing tool. If you are using management center, you may need to revert the changes, refer to the following link also. (https://www-304.ibm.com/support/docview.wss?uid=swg21445625)
-Raghavendra Shanthappa
This post is brought to you by Robert Brown, Senior WebSphere Commerce Consultant, www.redbaritone.com
WebSphere Commerce v6 uses the Java Server Tag Library (JSTL) language for most all starter store JSP code. The starter store JSPs typically include the four core tag libraries as indicated below at the top of each file
Read the rest of this entry »
When changes are made to files in your commerce application such as commerce config files or your application config files, you would simply copy these files to WC_InstName.ear folder and get away with it. This was true up until version 5.6.x of WebSphere Commerce, whose backbone is WebSphere App Server 5.0. But things changed with WCS 6.0 and WAS 6.0.
Read the rest of this entry »
Typical configuration changes implemented on a commerce instance is done via the famous instance xml file. This file is located at
{WCS_HOME}/instances/{INST_NAME}\xml\{INST_NAME}.xml
Going back to 5.6.x version of commerce, any changes to this xml file are immediately picked up by commerce when the server is restarted.This changed with Commerce 6.0 and up.
Read the rest of this entry »
This week I had a unique opportunity to test drive the installation of the newly released WebSphere Commerce 6.0 Developer. Here are my experiences from a Windows XP installation.
I will handle the quirks with the database setup after dealing with the basics.
Read the rest of this entry »
Now that WebSphere Commerce 6.0 is out, let us take a quick look at what it has to offer to the business process, developers and adminstrators.
At the high level it is a complete revamp over its prior version. There are changes almost at every conceivable level. There are new “separately orderable features” such as IBM Sales Center and IBM Gift Center. Order processing capabilities now include several features that left many wondering how we lived without these features in the past! Most retailers added these features by customizing the heck out of the commerce versions they were using. Multi-tender, multiple ship dates and support for non-taxable items - some of the desparately sought after features - are finally available out of box. If you ever wondered whether Payments Cassettes is easy to use - you will find the answer in this: WebSphere Commerce now provides support for Payment Cassettes for backward compatibility! The new rule for payments is lightweight plug-in architecture. The big deals for stage propagation are the concepts of workspaces and quick and global publishing options.
Now that the core feature list is dumbed down to one paragraph, let us shift gears and focus on what matters the most for the developers.
Read the rest of this entry »