Shipping Calculation Code

Shipping jurisdictions, rules and charges can be configured using calculation code data model within websphere commerce.

SHIPMODE table consists of the shipping mode / method.
SHIPMODEDESC table consists of the description of the shipping method defined above

JURST consists of a Jurisdiction definition and JURSTGROUP is the grouping of the Jurisdictions. The JURST table also consists of the zip code range for which the shipping rule may apply.

JURSTGPREL table defines the relationship between JURST and JURSTGROUP. The SUBCLASS field of JURSTGPREL defines whether it is a ShippingJurisdiction (1) or TaxJurisdiction (2)

SHPJCRULE contains the relationship between the Jurisdiction and the Shipping mode. If multiple rows from the SHPJCRULE table qualify for the rule, then the row that has the highest precedence set will be applied.  If two rules have the same precedence then both the rules are applied.

Migrating OpenLaszlo module from WCS FEP1 to WCS FEPx

When applying a new feature pack / fix pack, the out of the box files that are customized may be overwritten by the fix/feature pack. To migrate all the customizations to the new fix / feature pack, follow the instructions

1. Start websphere commerce developer environment
2. In the enterprise explorer view, right click on “LOBTools” module and select “OpenLaszlo Migration à Compare Customizations”
3. The compare editor will open displaying details about the changes that needs to be migrated. Also displays the line number.
4. Manually migrate the changes to the new version

More details at

http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/index.jsp?topic=%2Fcom.ibm.commerce.management-center_customization.doc%2Ftasks%2Fttfmigcmc.htm

IBM Websphere Commerce v7.0 Installation Primer

• Install IBM Websphere RAD v7.5.4 and IBM App Server Test Environment v7.0 (Assuming that RAD disks 1 through 6 have been extracted in to disk1,disk2,disk3,disk4,disk5 and disk6 respectively and the RAD setup itself has been extracted to RAD_SETUP folder )

a.    Click on “launchpad” under RAD Setup directory

b.    Choose the language in the following window (“English”)

c.    In the following window, select IBM Rational Application Developer for Websphere Software.

d.    This will first prompt for installation of “IBM Installation Manager”. Select the version of the installation manager on the screen (1.3.2) and click “Install”

e.    Enter a short path in the installation directory. For e.g., “C:\IBM\Installation Manager\eclipse”

f.     Upon completion of the installation, you’ll be prompted to restart the Installation Manager.

g.    Once the installation manager restarts, update the installation repositories by selecting “File à Preferences à Add Repository”. Browse and select diskTag.inf from RAD_SETUP and add. Also add diskTag.inf from disk1 folder of Websphere Application Server Test Environment. Ensure that you have placed your disk folders in the appropriate order as shown

RAD >

          RAD_SETUP

          Disk1

          Disk2

          Disk3  etc..

h.    Click on “Install” from the main screen of the installation manager and select RAD 7.5.4 and WAS 7.0.0 components. Sometimes, you may get a warning that the disk1 of RAD cannot be found. Ignore this at the moment as the installation manager will prompt you for disk1 path later on. Same with WAS disk 1. Please note that the providing RAD disk1 repository path at the time of installing RAD sometimes will not install RAD correctly. I faced this issue where the licenses were installed as Trial mode instead of Permanent mode (I had a permanent license, a partnerworld account)

i.      Once the RAD and WAS are installed, Select “Update” from the “Installation Manager” main screen. (Ensure that you have configured the proxy if you are behind a proxy server by selecting File > Preferences > Internet > HTTPProxy. This will first prompt for update of installation manager itself. Please update the installation manager to latest version (1.5) and installation manager will restart to proceed with RAD And WAS updates.

j.     Installation manager will automatically find the updates from the default repository and repositories configured by you. Select the suggested updates and update. (for e.g., update RAD to 7.5.5.5 and WAS to 7.0.0.19). The updates might be downloaded from Internet based on whether you have them locally or not and the repository is configured appropriately.

•   Installing the IBM Websphere Commerce v7.0

a.    From the installation manager start screen, click on File à Preferences à Add Repository. 

b.    Add the websphere commerce local repository WCDEVENT\repository.config in the extracted zip

c.    Once repository is configured, click “Install” from the installation manager main screen.

d.    Select the Websphere Commerce Version displayed (7.0.0) and install.

e.    Please check setup.log under WCDE_ENT70\logs to check if WCS was installed correctly.

•    Applying Fix pack and Feature Packs on top of Websphere Commerce

a.    Install the Fix pack 1 for commerce by downloading the fix pack 1 and then configuring the repository in Installation manager to point to the fix pack 1 location. Fix pack 1 installed. No problem

b.    Installing Feature Pack 1 for websphere commerce had some issues. The IBM installation manager just wouldn’t let me install FEP 1 and always gives the following error

installing IBM WebSphere Commerce Developer Feature Pack 1.0.0.0 is not allowed; it is not compatible with IBM WebSphere Commerce Developer Enterprise Edition 7.0.0.1.
In root installation context:
Undefined selector "ee" in component "com.ibm.commerce.toolkit.native.cmc.enterprise" version 7.0.0.20091017_2008

IBM says update your installation manager to greater than 1.4.1 but my installation manager was already 1.5. After much R&D found that it was an installation manager issue and we need a fix to rectify it. Download the fix provided in the following link

https://www-304.ibm.com/support/docview.wss?uid=swg24027424

Unzip the fix to a temp folder. Configure the installation manager repository to point to the above fix and also configure FEP1 repository. This will resolve the issue and you can continue installing the FEP 1.

Error While Building OpenLaszlo module

Error While Building OpenLaszlo module

Sometimes while building and deploying using WCBD can throw errors while compiling open Laszlo as below

Call to a possibly undefined method LzLoader, in line: this.loader = new LzLoader(view_$0.sprite, {attachname: "debugloader"});

This is because there are .ser files checked in to the repository and the build contains all the .ser files. These are usually hidden in RAD and shouldn't be a part of build.

To rectify this, remove all the .ser files in the LOBTools module and then rebuild. This should resolve the issue.

More information at

https://www-304.ibm.com/support/docview.wss?uid=swg21498905