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

No comments:

Post a Comment

My Writings........

HCL Commerce v9.1 | Local Store Vs Remote Store

  Local Store Remote Store Project Type Migrated (Lift & Shift) - Newly Imp...