WebSphere Commerce 7 | Dataload Jobs | Dataload Summary in the Logs | Feature Pack 6 Vs Feature Pack 8

With Feature Pack 6:

===============================================================================

WebSphere Commerce Data Load

===============================================================================

Load started at: Thu Sep 05 09:05:59 EDT 2013

Initialization completed in 2.229 seconds.

Processing CatalogEntry...

----------------------------------------------------------------------------------

Load summary for load item: CatalogEntry.

----------------------------------------------------------------------------------

Business Object Configuration: wc-loader-catalog-entry.xml

Data loader mode: Replace.

Batch size: 1.

Commit count: 100.

Error Tolerance Level: 1.

Error Count: 0.

Amount of business objects processed: 13.

Amount of business objects committed: 13.

Data loader initialization time: 0 seconds.

Data loader execution began: Thu Sep 05 09:06:07 EDT 2013

Data loader execution ended: Thu Sep 05 09:06:13 EDT 2013

Data loader completed in 5.765 seconds.

Total flush time: 0 seconds.

Total commit time: 0.003 seconds.

CSV file location: C:\IBM\WCDE_ENT70\bin\..\samples\DataLoad\Catalog\CatalogEntries.csv.

Affected tables (13):

Table name: BASEITEM, Affected number of rows: 5.

Table name: BASEITMDSC, Affected number of rows: 5.

Table name: STOREITEM, Affected number of rows: 5.

Table name: ITEMVERSN, Affected number of rows: 5.

Table name: DISTARRANG, Affected number of rows: 5.

Table name: CATENTRY, Affected number of rows: 13.

Table name: STORECENT, Affected number of rows: 13.

Table name: CATENTDESC, Affected number of rows: 13.

Table name: CATGPENREL, Affected number of rows: 13.

Table name: LISTPRICE, Affected number of rows: 13.

Table name: ITEMSPC, Affected number of rows: 8.

Table name: VERSIONSPC, Affected number of rows: 8

Table name: CATENTREL, Affected number of rows: 8

----------------------------------------------------------------------------------

Program exiting with exit code: 0.

Load completed successfully with no errors.

Load ended at: Thu Sep 05 09:06:13 EDT 2013

Load completed in 13.901 seconds.

With Feature Pack 8:

===============================================================================

WebSphere Commerce Data Load

===============================================================================

Load started at: Thu Sep 05 09:05:59 EDT 2013

Initialization completed in 2.229 seconds.

Processing CatalogEntry...

----------------------------------------------------------------------------------

Load summary for load item: CatalogEntry.

----------------------------------------------------------------------------------

Business Object Configuration: wc-loader-catalog-entry.xml

Data loader mode: Replace.

Batch size: 1.

Commit count: 100.

Error Tolerance Level: 1.

Error Count: 0.

Amount of business objects processed: 13.

Amount of business objects committed: 13.

Data loader initialization time: 0 seconds.

Data loader execution began: Thu Sep 05 09:06:07 EDT 2013

Data loader execution ended: Thu Sep 05 09:06:13 EDT 2013

Data loader completed in 5.765 seconds.

Total flush time: 0 seconds.

Total commit time: 0.003 seconds.

Total ID resolver time: 1.138 seconds.

CSV file location: C:\IBM\WCDE_ENT70\bin\..\samples\DataLoad\Catalog\CatalogEntries.csv.

Affected tables (13):

Table                |     Total |    Insert |    Update |    Delete

---------------------|-----------|-----------|-----------|-----------

BASEITEM             |         5 |         0 |         5 |         0

BASEITMDSC           |         5 |         0 |         5 |         0

STOREITEM            |         5 |         0 |         5 |         0

ITEMVERSN            |         5 |         0 |         5 |         0

DISTARRANG           |         5 |         0 |         5 |         0

CATENTRY             |        13 |         0 |        13 |         0

STORECENT            |        13 |         0 |        13 |         0

CATENTDESC           |        13 |         0 |        13 |         0

CATGPENREL           |        13 |         0 |        13 |         0

LISTPRICE            |        13 |         0 |        13 |         0

ITEMSPC              |         8 |         0 |         8 |         0

VERSIONSPC           |         8 |         0 |         8 |         0

CATENTREL            |         8 |         0 |         8 |         0

----------------------------------------------------------------------------------

Program exiting with exit code: 0.

Load completed successfully with no errors.

Load ended at: Thu Sep 05 09:06:13 EDT 2013

Load completed in 13.901 seconds.

WebSphere Commerce 7 | Dataload Jobs | Running & Debugging from RAD

Here is the way, you can run your run/debug your WebSphere Commerce Dataload Utilities from your RAD,

• Click on “Run Configurations”

 

• In “Main” tab, Provide Main class as “com.ibm.commerce.foundation.dataload.DataLoaderMain”

•  In the “Arguments” tab,
• In “Program arguments”, provide Dataload command with all the required parameters '
• In “VM arguments”, provide the value as “-Dj2se=true”
• In “Working directory”  --> other, provide bin folder path

 

• In the “Classpath” tab, add ojdb5.jar as External Jar (If you using Oracle as backend DB)

• While running the job, run it as the configuration, you have created

 

WebSphere Commerce 7 | SetDBType is failing | Issues Faced & Resolution | No data found in OOB Tables

After WebSphere Commerce Installation, we have migrated from Cloudscape to Oracle Database. After running "setdbtype" command with "createdb" option for the Oracle Database Schema, we have noticed SITE Table is not updated with the feature pack details and it was totally empty. And also, we have noticed most of the OOB tables hasn't populated (Tables are there, but data is not available in that). After running "updatedb" command also, we have the same result.

SETDBTYPE Command with CREATEDB Option,
setdbtype oracle C:\oracle\product\11.2.0\dbhome_1 orcl system Passw0rd wcsb2bdev Passw0rd localhost 1521 createdb

Later, we could able to notice the following error in messages log,
Exception in thread "main" java.lang.UnsatisfiedLinkError: ocijdbc11 (.\ocijdbc11.dll is not a valid Win32 application. )
 at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1011)
 at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:975)
 at java.lang.System.loadLibrary(System.java:469)
 at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:3506)
 at java.security.AccessController.doPrivileged(AccessController.java:202)
 at oracle.jdbc.driver.T2CConnection.loadNativeLibrary(T2CConnection.java:3502)
 at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:252)
 at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:531)
 at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:148)
 at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:53)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:503)
 at java.sql.DriverManager.getConnection(DriverManager.java:322)
 at java.sql.DriverManager.getConnection(DriverManager.java:358)
 at com.ibm.wca.dbconnect.DbConnectionImpl.connect(DbConnectionImpl.java:243)
 at com.ibm.wca.MassLoader.MassLoad.loadDbConnection(MassLoad.java:1176)
 at com.ibm.wca.MassLoader.MassLoad.execute(MassLoad.java:181)
 at com.ibm.wca.MassLoader.MassLoad.<init>(MassLoad.java:114)
 at com.ibm.wca.MassLoader.MassLoad.main(MassLoad.java:101)
Infocenter does provide some options to change it to a thin driver, but then I hit one error after another, and finally decided to give up and go with 32 bit version of Oracle software.\
.............
.............

As part of the resolution, we have download "ocijdbc11.dll" of Windows 32 and replaced it with one in the oracle folder "C:\oracle\product\11.2.0\dbhome_1\BIN". After we ran the process again and it started working fine as expected.

WebSphere Commerce 7 | Feature Pack 8 Installation | Issues Faced & Resolutions | Enable "content-version" Feature

When we were trying to enable "content-version" feature after installing WebSphere Commerce Feature Pack 8 with the following command,
enableFeature.bat -DfeatureName=content-version

Feature enablement has been failed with the following exception,
CV_enable:
com.ibm.commerce.context.version.ant.tasks.CreateVersionSchemaTask performTask() autoCommit: false
com.ibm.commerce.content.exception.ContentApplicationException: An error has occurred.  If this problem persists, contact product support.
    at com.ibm.commerce.context.version.objects.VersionSchemaUtility.createSchema(VersionSchemaUtility.java:487)
    at com.ibm.commerce.context.version.ant.tasks.CreateVersionSchemaTask.performTask(CreateVersionSchemaTask.java:298)
    at com.ibm.commerce.context.version.ant.tasks.CreateVersionSchemaTask.execute(CreateVersionSchemaTask.java:168)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
    at org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:30)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
    at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at 
.................
.................
.................
.................
.................
  
BUILD FAILED

C:\IBM\WCDE_E~1\components\common\xml\enableFeatureForToolkit.xml:59: The following error occurred while executing this line:
C:\IBM\WCDE_E~1\components\common\xml\enableFeatureForToolkit.xml:126: The following error occurred while executing this line:
C:\IBM\WCDE_E~1\components\common\xml\databaseTasks.xml:50: The following error occurred while executing this line:
C:\IBM\WCDE_E~1\components\common\xml\databaseTasks.xml:344: The following error occurred while executing this line:
C:\IBM\WCDE_E~1\components\common\xml\databaseTasks.xml:357: The following error occurred while executing this line:
C:\IBM\WCDE_E~1\components\content-version\schema\xml\custom\fep2\customAction.xml:23: The following error occurred while executing this line:
C:\IBM\WCDE_E~1\components\content-version\schema\xml\custom\fep2\configureContentVersionComponent.xml:140: The following error occurred while executing this line:
C:\IBM\WCDE_E~1\components\content-version\schema\xml\custom\fep2\configureContentVersionComponent.xml:195: com.ibm.commerce.content.exception.ContentApplicationException: An error has occurred.  If this problem persists, contact product support.
    at com.ibm.commerce.context.version.objects.VersionSchemaUtility.createSchema(VersionSchemaUtility.java:487)
    at com.ibm.commerce.context.version.ant.tasks.CreateVersionSchemaTask.performTask(CreateVersionSchemaTask.java:298)
    at com.ibm.commerce.context.version.ant.tasks.CreateVersionSchemaTask.execute(CreateVersionSchemaTask.java:168)

We have fixed this issue with the following steps,

• Logged into DB with SYSTEM user credentials and noticed one schema has been created with the name VCW_XXX,

           SELECT * FROM dba_users WHERE USERNAME LIKE 'VCW_%'; 

 Deleted this schema with the following SQL Query,
           DROP USER VCW_DEMO CASCADE;

• Ran the enable "content-version" feature command and it worked as expected.

WebSphere Commerce 7 | Installation Procedure | Pointing from Cloudscape/Derby to Oracle

While doing the installation of WebSphere Commerce, it comes with Cloudscape/Derby DB. If you wanted to point to your Oracle Database, here is the procedure,

• Install Oracle Database
• Login with System/Sys User and create new User (Here I have created "wcsdev" User)

    a. create tablespace WCSADMIN datafile 'C:\oracle\oradata\ORCL\WCSADMIN.dbf' size 500M autoextend on;
    b. ALTER DATABASE DATAFILE 'C:\oracle\oradata\ORCL\WCSADMIN.dbf' RESIZE 1000M;
    c. create user wcsb2bdev identified by Passw0rd default tablespace WCSADMIN;
    d. grant connect, resource to wcsdev;
    f. grant create procedure, create sequence, create session, create synonym, create table, create trigger, create view, create materialized view to wcsdev;
    g. ALTER USER wcsdev QUOTA UNLIMITED ON WCSADMIN;

• Run SetDBType Command with "createdb" option, so that it creates WCS Schema for the newly created user,

    setdbtype oracle C:\oracle\product\11.2.0\dbhome_1 orcl system Passw0rd wcsdev Passw0rd localhost 1521 createdb

•  Enable all the features in the following sequence,

    enableFeature.bat -DfeatureName=foundation (Takes almost 1 Hr)
    enableFeature.bat -DfeatureName=management-center (Takes around 25 Min)
    enableFeature.bat -DfeatureName=store-enhancements (Takes around 10 Min) 
    enableFeature.bat -DfeatureName=social-commerce (Takes around 15 Min)
    enableFeature.bat -DfeatureName=content-version (Takes around 5 Min)
    enableFeature.bat -DfeatureName=location-services (Takes around 5 Min) 

•  Publish the required store