For CRS installation details refer below -
http://docs.oracle.com/cd/E22630_01/CRS.1002/pdf/ATGCRSInstall.pdf
Installations you need to have before proceeding further
ATG 10.0.3, JDK 1.6, BEA 10.3, oracle xe. (all are freeware, you dont need any license files)
This steps will also work for ATG9.x, JDK 1.5, BEA 10.0
Below is my Environment details -
DYNAMO_HOME - C:\ATG\ATG10.0.3\home
JAVA_HOME - C:\jdk1.6.0_23
BEA_HOME - BEA_HOME=C:\bea10.3
Installed oracle xe - C:\oraclexe\app\oracle\product\10.2.0\
For oracle jdbc drivers -
CLASSPATH=C:\oraclexe\app\oracle\product\10.2.0\server\jdbc\lib\ojdbc14.jar;
Create a new weblogic domain "CRSV10"
Execute configuration wizard - C:\bea10.3\wlserver_10.3\common\bin\config.exe
When asked for Domain Name give CRSV10
And when asked for JDK give installed jdk 1.6
Thats it CRSV10 domain is created.
Go to C:\bea10.3\user_projects\domains\CRSV10\bin> and run startWebLogic.cmd
http://localhost:7001/console
Keep it running until the setup is completed.
Schema's that needs to be created before going further -
-- For Production site
-- for JNDI - ATGProductionDS - CORE schema
-- core user - crscorev10/password1
create user crscorev10 identified by password1 default tablespace users temporary tablespace temp;
grant connect, resource to crscorev10;
grant select any table to crscorev10;
grant create any table to crscorev10;
grant update any table to crscorev10;
grant delete any table to crscorev10;
grant alter any table to crscorev10;
grant create any view to crscorev10;
-- for JNDI - ATGSwitchingDS_A - for Switching A schema
-- switch A - crscatav10/password1
create user crscatav10 identified by password1 default tablespace users temporary tablespace temp;
grant connect, resource to crscatav10;
grant select any table to crscatav10;
grant create any table to crscatav10;
grant update any table to crscatav10;
grant delete any table to crscatav10;
grant alter any table to crscatav10;
grant create any view to crscatav10;
-- for JNDI - ATGSwitchingDS_B - for switching B schema
-- switch B - crscatbv10/password1
create user crscatbv10 identified by password1 default tablespace users temporary tablespace temp;
grant connect, resource to crscatbv10;
grant select any table to crscatbv10;
grant create any table to crscatbv10;
grant update any table to crscatbv10;
grant delete any table to crscatbv10;
grant alter any table to crscatbv10;
grant create any view to crscatbv10;
-- For Publishing site
-- for JNDI - ATGPublishingDS - Production Core schema
-- pub user - crspubv10/password1
create user crspubv10 identified by password1 default tablespace users temporary tablespace temp;
grant connect, resource to crspubv10;
grant select any table to crspubv10;
grant create any table to crspubv10;
grant update any table to crspubv10;
grant delete any table to crspubv10;
grant alter any table to crspubv10;
grant create any view to crspubv10;
Pre-define ATG servers & Weblogic servers & ports that needs to be created.-- for JNDI - ATGProductionDS - CORE schema
-- core user - crscorev10/password1
create user crscorev10 identified by password1 default tablespace users temporary tablespace temp;
grant connect, resource to crscorev10;
grant select any table to crscorev10;
grant create any table to crscorev10;
grant update any table to crscorev10;
grant delete any table to crscorev10;
grant alter any table to crscorev10;
grant create any view to crscorev10;
-- for JNDI - ATGSwitchingDS_A - for Switching A schema
-- switch A - crscatav10/password1
create user crscatav10 identified by password1 default tablespace users temporary tablespace temp;
grant connect, resource to crscatav10;
grant select any table to crscatav10;
grant create any table to crscatav10;
grant update any table to crscatav10;
grant delete any table to crscatav10;
grant alter any table to crscatav10;
grant create any view to crscatav10;
-- for JNDI - ATGSwitchingDS_B - for switching B schema
-- switch B - crscatbv10/password1
create user crscatbv10 identified by password1 default tablespace users temporary tablespace temp;
grant connect, resource to crscatbv10;
grant select any table to crscatbv10;
grant create any table to crscatbv10;
grant update any table to crscatbv10;
grant delete any table to crscatbv10;
grant alter any table to crscatbv10;
grant create any view to crscatbv10;
-- For Publishing site
-- for JNDI - ATGPublishingDS - Production Core schema
-- pub user - crspubv10/password1
create user crspubv10 identified by password1 default tablespace users temporary tablespace temp;
grant connect, resource to crspubv10;
grant select any table to crspubv10;
grant create any table to crspubv10;
grant update any table to crspubv10;
grant delete any table to crspubv10;
grant alter any table to crspubv10;
grant create any view to crspubv10;
Just keep these values defined, so that at the time of cim installation, you need to provide these values.
For Production -
rmiport - 8860
drpport - 8850
file deployment port - 8810
file synchronization deploy server port - 8815
httpPort=7003
httpsPort=7004
atg server name - crs_production_v10
weblogic server name - crs_production_v10
EAR name - crs_production_v10.ear
For Publishing -
rmiport - 8861
drpport - 8851
file deployment port - 8811
file synchronization deploy server port - 8816
lock server port - 9010
httpPort=7005
httpsPort=7006
atg server name - crs_publishing_v10
weblogic server name - crs_publishing_v10
Ear name - crs_publishing_v10.ear
RUN CIM
Go to <ATG-Home>/home/bin
run cim.bat
At the time of "Product Selection" -
Note: If you already did executed cim.bat & something got messed up previously, you can still select "Production selection" & Continue & select.
Note: When * is selected at option & if you want to go with that option just press enter. Selecting the option again will toggle.
. If cim prompts for example hostname[localhost] > then press enter to select localhost as hostname or enter new value "myhost" to assign to hostname.
Below are the products & Addons I selected
-------PRODUCT MODULE CALCULATION start-----------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Current Product Selection:
ATG Platform and Content Administration
ATG Search
ATG Site Administration
ATG Commerce Reference Store
Selected AddOns:
ATG Search
Merchandising UI
Switching Datasource
Include Search QueryConsole on Production
Index by SKU
Storefront Demo Application
Full
Server Instance Types:
Production Server
DafEar.Admin DPS DSS B2CCommerce DCS.PublishingAgent
DCS.AbandonedOrderServices DAF.Search.Routing DCS.Search Store.Search
DAF.Search.Base.QueryConsole DCS.Search.Index.SKUIndexing
DCS.Search.Query.SKUIndexing Store.Storefront
Publishing Server
DCS-UI.Search DCS-UI.Versioned BIZUI PubPortlet DafEar.Admin
B2CCommerce.Versioned DCS.Versioned DCS-UI Store.EStore.Versioned
Store.Storefront SiteAdmin.Versioned DAF.Search.Versioned DAF.Search.Routing
SearchAdmin.AdminUI DCS.Search.Versioned Store.Search Store.Search.Index
SiteAdmin.Search DCS.Search.Index.SKUIndexing DCS.Search.Query.SKUIndexing
-------PRODUCT MODULE CALCULATION end-----------------------------------------------
1) Database Configuration -
For Database Configuration, you need configure
*[P] Publishing
[S] Switching A
[B] Switching B
[C] Production Core
[D] Done
As CIM prompts, go with default settings, When asked for Connection details, give as below
-------CONNECTION DETAILS START---------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Publishing
Select Database Type
*[1] Oracle Thin
[2] MS SQL
[3] iNet MS SQL
[4] DB2
[5] My SQL
Select one > 1
Enter User Name [[crs10pub]] > crspubv10
Enter Password [[*********]] > *********
Re-enter Password > *********
Enter Host Name [[localhost]] >
Enter Port Number [[1521]] >
Enter Database Name [[xe]] >
Enter Database URL [[jdbc:oracle:thin:@localhost:1521:xe]]
>
Enter Driver Path [[C:/oraclexe/app/oracle/product/10.2.0/server/jdbc/lib/ojdbc14.jar]] >
Enter JNDI Name [[ATGPublishingDS]] >
-------CONNECTION DETAILS END------------------------------------------
Once, above step is done, Test connection, Create Schema, Import Initial Data*[P] Publishing
[S] Switching A
[B] Switching B
[C] Production Core
[D] Done
As CIM prompts, go with default settings, When asked for Connection details, give as below
-------CONNECTION DETAILS START---------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Publishing
Select Database Type
*[1] Oracle Thin
[2] MS SQL
[3] iNet MS SQL
[4] DB2
[5] My SQL
Select one > 1
Enter User Name [[crs10pub]] > crspubv10
Enter Password [[*********]] > *********
Re-enter Password > *********
Enter Host Name [[localhost]] >
Enter Port Number [[1521]] >
Enter Database Name [[xe]] >
Enter Database URL [[jdbc:oracle:thin:@localhost:1521:xe]]
>
Enter Driver Path [[C:/oraclexe/app/oracle/product/10.2.0/server/jdbc/lib/ojdbc14.jar]] >
Enter JNDI Name [[ATGPublishingDS]] >
-------CONNECTION DETAILS END------------------------------------------
And repeat "Database Configuration" for Swithching A(crscatav10), Switching B(crscatbv10) & Core (crscorev10)
Once Database Configuration - Done
2) Server Instance Configuration -
Next step is "Server Instance Configuration"
2 instances one for Publishing and one for Production needs to be configured.
============ PUBLISHING SERVER CONFIGURATION start ================
*[P] Publishing Server - 0 Instances Configured
[S] Production Server - 0 Instances Configured
[D] Done
*[P] Publishing Server General Configuration - REQUIRED
[I] Instance Management - REQUIRED
[C] Modify Calculated Module List - OPTIONAL
[S] Scenario Manager - OPTIONAL
[O] Configure Another Server Instance Type
Enter Production Lock Server Hostname [[crs_production]] > localhost
Enter Production Lock Server Port [[9012]] >
Enter the Remote Production Search Instance Host Name [[crs_production]]> localhost
Enter the Remote Production Search Instance RMI Port Number [[8860]] >
[P] Publishing Server General Configuration - DONE
*[I] Instance Management - REQUIRED
[C] Modify Calculated Module List - OPTIONAL
[S] Scenario Manager - OPTIONAL
[O] Configure Another Server Instance Type
*[A] Add Server Instance
[R] Remove Server Instance
[D] Done
>
Select Type of Server Instance To Create
*[1] Publishing with a Server Lock Manager : Minimum 1 Required
[2] Publishing
Select one >
Enter Server Instance Name : [[atg_publishing_lockserver]] > crs_publishing_v10
Enter HTTP Port [[7003]] > 7005
Enter HTTPS Port [[7004]] > 7006
Enter Site HTTP Port [[7003]] > 7005
Enter RMI Port [[8860]] > 8861
Enter DRP Port [[8850]] > 8851
Enter File Deployment Port [[8810]] > 8811
Enter File Synchronization Deploy Server Port [[8815]] > 8816
============ PUBLISHING SERVER CONFIGURATION end ================
============ PRODUCTION SERVER CONFIGURATION start ================
[P] Publishing Server - 1 Instance Configured - DONE
*[S] Production Server - 0 Instances Configured
[D] Done
>
*[P] Production Server General Configuration - REQUIRED
[I] Instance Management - REQUIRED
[C] Modify Calculated Module List - OPTIONAL
[S] Scenario Manager - OPTIONAL
[O] Configure Another Server Instance Type
>
[P] Production Server General Configuration - DONE
*[I] Instance Management - REQUIRED
[C] Modify Calculated Module List - OPTIONAL
[S] Scenario Manager - OPTIONAL
[O] Configure Another Server Instance Type
>
*[A] Add Server Instance
[R] Remove Server Instance
[D] Done
>
Select Type of Server Instance To Create
*[1] Production with a Server Lock Manager : Minimum 1 Required
[2] Production
Select one > 1
Enter Server Instance Name : [[atg_production]] > crs_production_v10
Enter HTTP Port [[7003]] >
Enter HTTPS Port [[7004]] >
Enter Site HTTP Port [[7003]] >
Enter RMI Port [[8860]] >
Enter DRP Port [[8850]] >
Enter File Deployment Port [[8810]] >
Enter Lock Server Hostname [[crs_production_v10]] > localhost
Enter Lock Server Port [[9012]] >
============ PRODUCTION SERVER CONFIGURATION end ================
2 instances one for Publishing and one for Production needs to be configured.
============ PUBLISHING SERVER CONFIGURATION start ================
*[P] Publishing Server - 0 Instances Configured
[S] Production Server - 0 Instances Configured
[D] Done
*[P] Publishing Server General Configuration - REQUIRED
[I] Instance Management - REQUIRED
[C] Modify Calculated Module List - OPTIONAL
[S] Scenario Manager - OPTIONAL
[O] Configure Another Server Instance Type
Enter Production Lock Server Hostname [[crs_production]] > localhost
Enter Production Lock Server Port [[9012]] >
Enter the Remote Production Search Instance Host Name [[crs_production]]> localhost
Enter the Remote Production Search Instance RMI Port Number [[8860]] >
[P] Publishing Server General Configuration - DONE
*[I] Instance Management - REQUIRED
[C] Modify Calculated Module List - OPTIONAL
[S] Scenario Manager - OPTIONAL
[O] Configure Another Server Instance Type
*[A] Add Server Instance
[R] Remove Server Instance
[D] Done
>
Select Type of Server Instance To Create
*[1] Publishing with a Server Lock Manager : Minimum 1 Required
[2] Publishing
Select one >
Enter Server Instance Name : [[atg_publishing_lockserver]] > crs_publishing_v10
Enter HTTP Port [[7003]] > 7005
Enter HTTPS Port [[7004]] > 7006
Enter Site HTTP Port [[7003]] > 7005
Enter RMI Port [[8860]] > 8861
Enter DRP Port [[8850]] > 8851
Enter File Deployment Port [[8810]] > 8811
Enter File Synchronization Deploy Server Port [[8815]] > 8816
============ PUBLISHING SERVER CONFIGURATION end ================
============ PRODUCTION SERVER CONFIGURATION start ================
[P] Publishing Server - 1 Instance Configured - DONE
*[S] Production Server - 0 Instances Configured
[D] Done
>
*[P] Production Server General Configuration - REQUIRED
[I] Instance Management - REQUIRED
[C] Modify Calculated Module List - OPTIONAL
[S] Scenario Manager - OPTIONAL
[O] Configure Another Server Instance Type
>
[P] Production Server General Configuration - DONE
*[I] Instance Management - REQUIRED
[C] Modify Calculated Module List - OPTIONAL
[S] Scenario Manager - OPTIONAL
[O] Configure Another Server Instance Type
>
*[A] Add Server Instance
[R] Remove Server Instance
[D] Done
>
Select Type of Server Instance To Create
*[1] Production with a Server Lock Manager : Minimum 1 Required
[2] Production
Select one > 1
Enter Server Instance Name : [[atg_production]] > crs_production_v10
Enter HTTP Port [[7003]] >
Enter HTTPS Port [[7004]] >
Enter Site HTTP Port [[7003]] >
Enter RMI Port [[8860]] >
Enter DRP Port [[8850]] >
Enter File Deployment Port [[8810]] >
Enter Lock Server Hostname [[crs_production_v10]] > localhost
Enter Lock Server Port [[9012]] >
============ PRODUCTION SERVER CONFIGURATION end ================
Once "Server Instance Configuration" is done
Next would be "Application Assembly & Deployment"
3) Application Assembly & Deployment
-------DEPLOYMENT SERVER PRODUCTION start------------------------
*[C] crs_production_v10 - Production
[P] crs_publishing_v10 - Publishing with a Server Lock Manager
[D] Done
>
Enter Ear File Name for Production [[atg_production.ear]] > crs_production_v10.ear
Current runAssembler arguments :
-server crs_production_v10
Weblogic Admin Server must be running.
Top Level Module List:
DafEar.Admin DPS DSS B2CCommerce DCS.PublishingAgent
DCS.AbandonedOrderServices DAF.Search.Routing DCS.Search Store.Search
DAF.Search.Base.QueryConsole DCS.Search.Index.SKUIndexing
DCS.Search.Query.SKUIndexing Store.Storefront
*[D] Deploy Production crs_production_v10.ear to Weblogic Online
[R] Register Datasources on Weblogic Online
[A] Add database driver to app server classpath
[P] Post Deployment Actions on Weblogic Online
[E] Edit runAssembler arguments
[O] Configure Another Server Instance
> D
Once deployment of crs_production_v10.ear is done, go with next options like Register Datasource on Weblogic online, Add db driver to app server path,
& Post Deployment Actions on Weblogic online
-------DEPLOYMENT SERVER PRODUCTION start------------------------
-------DEPLOYMENT SERVER PUBLISHING start------------------------
[C] crs_production_v10 - Production - Done
*[P] crs_publishing_v10 - Publishing with a Server Lock Manager
[D] Done
Enter Ear File Name for Publishing with a Server Lock Manager [[atg_publishing_lockserver.ear]] > crs_publishing_v10.ear
Current runAssembler arguments :
-server crs_publishing_v10
Weblogic Admin Server must be running.
Top Level Module List:
DCS-UI.Search DCS-UI.Versioned BIZUI PubPortlet DafEar.Admin
B2CCommerce.Versioned DCS.Versioned DCS-UI Store.EStore.Versioned
Store.Storefront SiteAdmin.Versioned DAF.Search.Versioned DAF.Search.Routing
SearchAdmin.AdminUI DCS.Search.Versioned Store.Search Store.Search.Index
SiteAdmin.Search DCS.Search.Index.SKUIndexing DCS.Search.Query.SKUIndexing
*[D] Deploy Publishing with a Server Lock Manager crs_publishing_v10.ear to
Weblogic Online
[R] Register Datasources on Weblogic Online
[A] Add database driver to app server classpath
[P] Post Deployment Actions on Weblogic Online
[E] Edit runAssembler arguments
[O] Configure Another Server Instance
> d
Once deployment of crs_production_v10.ear is done, go with next options like Register Datasource on Weblogic online, Add db driver to app server path,
& Post Deployment Actions on Weblogic online
-------DEPLOYMENT SERVER PUBLISHING end------------------------
Once Above steps are done, exit CIM.*[C] crs_production_v10 - Production
[P] crs_publishing_v10 - Publishing with a Server Lock Manager
[D] Done
>
Enter Ear File Name for Production [[atg_production.ear]] > crs_production_v10.ear
Current runAssembler arguments :
-server crs_production_v10
Weblogic Admin Server must be running.
Top Level Module List:
DafEar.Admin DPS DSS B2CCommerce DCS.PublishingAgent
DCS.AbandonedOrderServices DAF.Search.Routing DCS.Search Store.Search
DAF.Search.Base.QueryConsole DCS.Search.Index.SKUIndexing
DCS.Search.Query.SKUIndexing Store.Storefront
*[D] Deploy Production crs_production_v10.ear to Weblogic Online
[R] Register Datasources on Weblogic Online
[A] Add database driver to app server classpath
[P] Post Deployment Actions on Weblogic Online
[E] Edit runAssembler arguments
[O] Configure Another Server Instance
> D
Once deployment of crs_production_v10.ear is done, go with next options like Register Datasource on Weblogic online, Add db driver to app server path,
& Post Deployment Actions on Weblogic online
-------DEPLOYMENT SERVER PRODUCTION start------------------------
-------DEPLOYMENT SERVER PUBLISHING start------------------------
[C] crs_production_v10 - Production - Done
*[P] crs_publishing_v10 - Publishing with a Server Lock Manager
[D] Done
Enter Ear File Name for Publishing with a Server Lock Manager [[atg_publishing_lockserver.ear]] > crs_publishing_v10.ear
Current runAssembler arguments :
-server crs_publishing_v10
Weblogic Admin Server must be running.
Top Level Module List:
DCS-UI.Search DCS-UI.Versioned BIZUI PubPortlet DafEar.Admin
B2CCommerce.Versioned DCS.Versioned DCS-UI Store.EStore.Versioned
Store.Storefront SiteAdmin.Versioned DAF.Search.Versioned DAF.Search.Routing
SearchAdmin.AdminUI DCS.Search.Versioned Store.Search Store.Search.Index
SiteAdmin.Search DCS.Search.Index.SKUIndexing DCS.Search.Query.SKUIndexing
*[D] Deploy Publishing with a Server Lock Manager crs_publishing_v10.ear to
Weblogic Online
[R] Register Datasources on Weblogic Online
[A] Add database driver to app server classpath
[P] Post Deployment Actions on Weblogic Online
[E] Edit runAssembler arguments
[O] Configure Another Server Instance
> d
Once deployment of crs_production_v10.ear is done, go with next options like Register Datasource on Weblogic online, Add db driver to app server path,
& Post Deployment Actions on Weblogic online
-------DEPLOYMENT SERVER PUBLISHING end------------------------
Checks & Validations before starting servers -
1) ATG servers that are created by CIM
Production server - C:\ATG\ATG10.0.3\home\servers\crs_production_v10
Publishing server - C:\ATG\ATG10.0.3\home\servers\crs_publishing_v10
2) Ear's that are created by CIM
Production ear - C:\ATG\ATG10.0.3\home\cimEars\crs_production_v10.ear
Publishing ear - C:\ATG\ATG10.0.3\home\cimEars\crs_publishing_v10.ear
Note: All ears are standalone ears
3) The runAssembler command used to create above ears by CIM is
For production ear -
runAssembler -server crs_production_v10 C:/ATG/ATG10.0.3/home/../home/cimEars/crs_production_v10.ear
-m DafEar.Admin DPS DSS B2CCommerce DCS.PublishingAgent DCS.AbandonedOrderServices DAF.Search.Routing DCS.Search Store.Search DAF.Search.Base.QueryConsole DCS.Search.Index.SKUIndexing DCS.Search.Query.SKUIndexing Store.Storefront
For publishing ear --m DafEar.Admin DPS DSS B2CCommerce DCS.PublishingAgent DCS.AbandonedOrderServices DAF.Search.Routing DCS.Search Store.Search DAF.Search.Base.QueryConsole DCS.Search.Index.SKUIndexing DCS.Search.Query.SKUIndexing Store.Storefront
runAssembler -server crs_publishing_v10 C:/ATG/ATG10.0.3/home/../home/cimEars/crs_publishing_v10.ear
-m DCS-UI.Search DCS-UI.Versioned BIZUI PubPortlet DafEar.Admin B2CCommerce.Versioned DCS.Versioned DCS-UI Store.EStore.Versioned Store.Storefront SiteAdmin.Versioned DAF.Search.Versioned DAF.Search.Routing SearchAdmin.AdminUI DCS.Search.Versioned Store.Search Store.Search.Index SiteAdmin.Search DCS.Search.Index.SKUIndexing DCS.Search.Query.SKUIndexing
-m DCS-UI.Search DCS-UI.Versioned BIZUI PubPortlet DafEar.Admin B2CCommerce.Versioned DCS.Versioned DCS-UI Store.EStore.Versioned Store.Storefront SiteAdmin.Versioned DAF.Search.Versioned DAF.Search.Routing SearchAdmin.AdminUI DCS.Search.Versioned Store.Search Store.Search.Index SiteAdmin.Search DCS.Search.Index.SKUIndexing DCS.Search.Query.SKUIndexing
4) Weblogic servers that are created by CIM
In C:\bea10.3\user_projects\domains\CRSV10\config\config.xml
<server>
<name>crs_production_v10</name>
<listen-port>7003</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
</server>
<server>
<name>crs_publishing_v10</name>
<listen-port>7005</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
</server>
<name>crs_production_v10</name>
<listen-port>7003</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
</server>
<server>
<name>crs_publishing_v10</name>
<listen-port>7005</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
</server>
5) App deployments in Weblogic server done by CIM -
Note: By default <staging-mode>nostage</staging-mode> is not added in config.xml
Add <staging-mode>nostage</staging-mode> to each app-deployment, having this option
will not copy the ear to weblogic domain while starting which will consume time at server startup.
<app-deployment>
<name>crs_production_v10.ear</name>
<target>crs_production_v10</target>
<module-type>ear</module-type>
<source-path>C:\ATG\ATG10.0.3\home\..\home\cimEars\crs_production_v10.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>crs_publishing_v10.ear</name>
<target>crs_publishing_v10</target>
<module-type>ear</module-type>
<source-path>C:\ATG\ATG10.0.3\home\..\home\cimEars\crs_publishing_v10.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<
<name>crs_production_v10.ear</name>
<target>crs_production_v10</target>
<module-type>ear</module-type>
<source-path>C:\ATG\ATG10.0.3\home\..\home\cimEars\crs_production_v10.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>crs_publishing_v10.ear</name>
<target>crs_publishing_v10</target>
<module-type>ear</module-type>
<source-path>C:\ATG\ATG10.0.3\home\..\home\cimEars\crs_publishing_v10.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<
6) Before starting servers, make sure your lockmanagers are pointing to right host
In /c/ATG/ATG10.0.3/home/servers/crs_production_v10
./localconfig/atg/dynamo/service/ClientLockManager.properties:lockServerAddress=localhost
./localconfig/atg/dynamo/service/ClientLockManager_production.properties:lockServerAddress=localhost
In /cygdrive/c/ATG/ATG10.0.3/home/servers/crs_publishing_v10
./localconfig/atg/commerce/search/config/RemoteCatalogRankConfigAdapter.properties:remoteHost=localhost
./localconfig/atg/commerce/search/config/RemoteSearchUpdateAdapter.properties:remoteHost=localhost
./localconfig/atg/commerce/search/refinement/RemoteCatalogRefineConfigAdapter.properties:remoteHost=localhost
./localconfig/atg/dynamo/service/ClientLockManager.properties:lockServerAddress=localhost
./localconfig/atg/dynamo/service/ClientLockManager_production.properties:lockServerAddress=localhost
7) Make sure you have protocol.jar added to classpath, if not add it in
C:\bea10.3\user_projects\domains\CRSV10\bin\setDomainEnv.cmd
rem CIM - Prepending protocol.jar CLASSPATH
set CLASSPATH=C:/bea10.3/user_projects/domains/CRSV10/lib/protocol.jar;%CLASSPATH%
8) For faster server startup make sure that you have provided weblogic username/password inset CLASSPATH=C:/bea10.3/user_projects/domains/CRSV10/lib/protocol.jar;%CLASSPATH%
C:\bea10.3\user_projects\domains\CRSV10\bin\startManagedWebLogic.cmd
set WLS_USER=weblogic
set WLS_PW=<weblogic password>
9) Make sure you have database drivers in your classpath.set WLS_PW=<weblogic password>
CLASSPATH=C:\oraclexe\app\oracle\product\10.2.0\server\jdbc\lib\ojdbc14.jar;
Starting weblogic servers
1) Starting production server
In command prompt -
Go to cd C:\bea10.3\user_projects\domains\CRSV10\bin
set JAVA_OPTIONS=-Datg.dynamo.server.name=crs_production_v10
startManagedWebLogic.cmd crs_production_v10
Once server is started.startManagedWebLogic.cmd crs_production_v10
http://localhost:7003/crs/storeus
As you can observe there wont be any images shown yet. They will be shown once you have a full deployment.
2) Starting publishing server
In command prompt -
Go to cd C:\bea10.3\user_projects\domains\CRSV10\bin
set JAVA_OPTIONS=-Datg.dynamo.server.name=crs_publishing_v10
startManagedWebLogic.cmd crs_publishing_v10
Once server is started.startManagedWebLogic.cmd crs_publishing_v10
http://localhost:7005/atg/bcc
=========== If you get errror START ====================
**** Error Wed Jan 25 12:28:48 CST 2012 1327516128324 /atg/portal/framework/PortalObjectResolver No root community folder for portal 'default'
You need to re-import BIZUI
Have below files
C:\ATG\ATG10.0.3\home\localconfig\atg\dynamo\service\jdbc\JTDataSource.properties
$class=atg.service.jdbc.MonitoredDataSource
dataSource=/atg/dynamo/service/jdbc/FakeXADataSource
C:\ATG\ATG10.0.3\home\localconfig\atg\dynamo\service\jdbc\FakeXADataSource.properties
$class=atg.service.jdbc.FakeXADataSource
URL=jdbc:oracle:thin:@localhost:1521:xe
user=crspubv10
password=password1
needsSeparateUserInfo=true
readOnly=false
driver=oracle.jdbc.xa.client.OracleXADataSource
In C:\ATG\ATG10.0.3>
C:\ATG\ATG10.0.3\BIZUI\install\importBizui.bat
before restart delete files - JTDataSource.properties & FakeXADataSource.properties in localconfig.
=========== If you get errror END ====================
3) Full deployment -
Go to http://localhost:7005/atg/bcc
use login - admin/admin
Go to Content Adminstration->Admin Console
Go to Configuration tab -> Click on "Add Site"
Give Site Name as Production & see below options & Repository Mappings are selected.
Click on Agents tab, Click on "Add agent Site"
Give agent Name as "ProdAgent" and rmi port as rmi://localhost:8680/atg/epub/AgentTransport & press ">>". Please refer below screenshot & "Save Changes"
Click on Configuration tab & click on "Make Changes Live"
Go with "Do a full deployment" option & click on "Make Changes Live"
To Monitor deployment status, go to "Overview" tab & selection "production" site to check deployment status
Now check store
http://localhost:7003/crs/storeus
For login id's use "select * from dps_user" on crscorev10 schema
For example -
username - alex@example.com
password for all logins is "password"
Thats it, commerce reference store is ready for development.
Hope this helps!!
Hi,
ReplyDeleteThanks for this wonderful post.
I receievd below error while installation. Can you please help me if you came across the similar issue
**** info Mon Feb 13 13:26:50 EST 2012 1329157610892 atg.cim.task.ant.utility.AntLogger BUILD FAILED
**** info Mon Feb 13 13:26:50 EST 2012 1329157610892 atg.cim.task.ant.utility.AntLogger C:\ATG\ATG10.0.3\CIM\plugins\Base\ant\cim-ant.xml:97: exec returned: 255
**** info Mon Feb 13 13:26:50 EST 2012 1329157610892 atg.cim.task.ant.utility.AntLogger
**** info Mon Feb 13 13:26:50 EST 2012 1329157610892 atg.cim.task.ant.utility.AntLogger Total time: 0 seconds
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask --- C:\ATG\ATG10.0.3\CIM\plugins\Base\ant\cim-ant.xml:97: exec returned: 255
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:636)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:662)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:487)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at java.lang.reflect.Method.invoke(Method.java:597)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.Task.perform(Task.java:348)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.Target.execute(Target.java:357)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.Target.performTasks(Target.java:385)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at atg.cim.task.ant.utility.AntExecutionWrapper.executeAntTarget(AntExecutionWrapper.java:145)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAssemblerExecutorTask at atg.cim.worker.AntTask.executeAntTarget(AntTask.java:93)
**** Error Mon Feb 13 13:26:50 EST 2012 1329157610893 atg.cim.productconfig.appassembly.RunAss
While assembling the EAR it got failed, below or after the above logs did u see anything like "Unable to delete" or "module not found", those are the common reasons runassembler may fail. You can also manually run runassembler to see what might be the issue.
DeleteThanks Rajashekar.
ReplyDeleteI have figured out the issue. It was due to java path and worng usage of weblogic version for my machine. So I have installed all the latest versions which are compatable with 64 bit systems and executed the above steps.
I was able to run the installation as expected but failed in the last step while configuring production server(@BCC. Here is the error message that I have encountered. Could you please help me if you faced similar issue.
Deployment Failed uri:atgvm://VersionManagerService/PublishingFiles/scenario/fa100058 2012-02-14 14:48:18.326
Message Detail:
CONTAINER:atg.deployment.file.DeploymentSourceException: IOException while reading file /atg/registry/data/scenarios/recorders/profileupdate.sdl; SOURCE:deploymentFileCommandIOExcReadFile: level 4: IOException while reading file /atg/registry/data/scenarios/recorders/profileupdate.sdl atg.deployment.file.DeploymentSourceException: IOException while reading file /atg/registry/data/scenarios/recorders/profileupdate.sdl at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1256) at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:740) at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:420) at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:534) at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:307)
Hi Mohammed,
DeleteI am also facing the same issue. Could u please let me know how u resolved this problem?
Hi Rajashekar,
ReplyDeleteThanks for above blog this is really useful, I have existing setup for CRS 10.0.2 which is done in evaluation mode, Now I am planning to setup Development mode/ version of CRS and choosing 10.0.3 as the latest one is available.
Wanted to know which version of CRS has support for CSC, Dose CSC comes as an addon with CRS or I need to setup it separate. Can you point me to additional info.
@Siva - In general 10.0.2 CSC should also work with 10.0.3 if you already have a working version but if you are trying to install new CSC 10.0.3 then yes CSC comes as addon with CRS. At the time of cim installation pick CSC too. Actually I tried having CSC addon everything went fine at the time of installation but I got some issue while starting CSC havent investigated further yet.
Deletehi,
ReplyDeleteIf it s possible to insert my own product on the home featured product slot , if yes how to insert it ? suggest some points
Hi Rajashekar,
ReplyDeleteCan I use CRS 10.0.3 with MySQL
My system env are
JDK 1.6_u27
JBossEAP 5.1
MySQL 5.5.x
I am not able to configure it on MySQL, what sort of things am I missing.
Thanks,
Abdul
This comment has been removed by the author.
DeleteWhat kind of error you are getting?
DeleteThank you very much for your article, it is very educational.
ReplyDeleteHowever I have a problem: when importing production with cim, in 10 of 12, I have an error.
Can you help me?
My system is: RH 5.5 +Weblogic 10.3.5 + oracle xe+ java 1.6.0
The cim.log:
**** info jue ago 23 02:07:10 CEST 2012 1345680430693 atg.cim.task.ant.utility.AntLogger [exec] at atg.adapter.gsa.xml.TemplateParser.runParser(TemplateParser.java:5795)
**** info jue ago 23 02:07:10 CEST 2012 1345680430693 atg.cim.task.ant.utility.AntLogger [exec] at atg.adapter.gsa.xml.TemplateParser.main(TemplateParser.java:5241)
**** info jue ago 23 02:07:10 CEST 2012 1345680430731 atg.cim.task.ant.utility.AntLogger [exec] **** info jue ago 23 02:07:10 CEST 2012 1345680430730 /atg/dynamo/service/Scheduler Scheduler shutting down.
**** info jue ago 23 02:07:10 CEST 2012 1345680430731 atg.cim.task.ant.utility.AntLogger [exec] **** info jue ago 23 02:07:10 CEST 2012 1345680430731 /atg/dynamo/service/Scheduler Scheduler stopped.
**** info jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.task.ant.utility.AntLogger
**** info jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.task.ant.utility.AntLogger BUILD FAILED
**** info jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.task.ant.utility.AntLogger /home/keka/ATG/ATG10.0.3/CIM/plugins/Base/ant/cim-ant.xml:16: exec returned: 1
**** info jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.task.ant.utility.AntLogger
**** info jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.task.ant.utility.AntLogger Total time: 10 seconds
**** Error jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.worker.dynamo.StartSqlRepositoryExecutorTask --- /home/keka/ATG/ATG10.0.3/CIM/plugins/Base/ant/cim-ant.xml:16: exec returned: 1
**** Error jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.worker.dynamo.StartSqlRepositoryExecutorTask at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:636)
**** Error jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.worker.dynamo.StartSqlRepositoryExecutorTask at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:662)
**** Error jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.worker.dynamo.StartSqlRepositoryExecutorTask at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:487)
**** Error jue ago 23 02:07:10 CEST 2012 1345680430777 atg.cim.worker.dynamo.StartSqlRepositoryExecutorTask at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
Hi,I from China and I learning ATG now,but I have a litter question :
ReplyDeleteApplication Server: weblogic
The following installed ATG components are being used to launch:
ATGPlatform version 10.1.1 installed at G:\ATG\ATG10.1.1
"G:\ATG\ATG10.1.1\home\CIM\startDynamo.jar" 已创建,用时 13,743 毫秒。
**** Error 星期日 九月 09 00:17:31 CST 2012 1347121051576 /
atg.nucleus.NucleusResources->beanConfiguratorCannotParseProperty : 无法将 "/atg
/dynamo/service/logging/CimLog.schedule" 的属性值 "in 0 seconds" 分析为 atg.serv
ice.scheduler.Schedule java.lang.IllegalArgumentException: atg.nucleus.PropertyV
alueParseException: atg.service.scheduler.SchedulerPropertyEditorResources->sche
duleParserInvalidScheduleFormat : 计划格式无效
Nucleus 正在运行
Oracle ATG Web Commerce Configuration Installation Manager
=======CIM MAIN MENU============================================================
*Could you give me a answer,please,thank you very much.
It happen on I want to run cim.bat,thx
DeleteHi,
ReplyDeleteWhen I go with "Do a full deployment" option & click on "Make Changes Live".
In Monitor deployment status, go to "Overview" tab & selection "production" site to check deployment status, it encountered error as below:
Message Detail:
CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:CONTAINER:atg.repository.RepositoryException; SOURCE:com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Cannot add or update a child row: a foreign key constraint fails (`switchingb`.`dcs_price`, CONSTRAINT `dcs_pricpric_lst_f` FOREIGN KEY (`price_list`) REFERENCES `dcs_price_list` (`price_list_id`)) at atg.deployment.repository.RepositoryWorkerThread.processMarkerForAddUpdatePhase(RepositoryWorkerThread.java:273) at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562) at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
Any ideas?
Thanks.
Could you check first by running startSQLRepository?
DeleteJust to add up:
ReplyDeleteSometimes we might face the full deployment exception due to more concurrent threads. I faced the same in ATG10.1.1 installation with jboss.
Here are the settings:
Set the values in Deployment Manager(http://:/dyn/admin/nucleus/atg/deployment/DeploymentManager/)of Publishing Server as below:
maxThreads=1
transactionBatchSize=5000
threadBatchSize=5000
Now Continue with the Full deployment. Hope this helps
not able to see the promotions and images rest works fine. please help
ReplyDelete**** Error Fri Nov 21 14:56:11 IST 2014 1416561971588 / Invalid attempt to resolve component /atg/registry/Slots/HomeTheme in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971594 / Invalid attempt to resolve component /atg/registry/Slots/PromotedProduct1 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971598 / Invalid attempt to resolve component /atg/registry/Slots/PromotedProduct2 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971603 / Invalid attempt to resolve component /atg/registry/Slots/PromotedProduct3 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971609 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct2 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971615 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct3 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971620 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct4 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971626 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct5 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971632 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct1 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971638 / Invalid attempt to resolve component /atg/registry/Slots/CategoryPromotionContent2 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:11 IST 2014 1416561971642 / Invalid attempt to resolve component /atg/registry/Slots/CategoryPromotionContent1 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972038 / Invalid attempt to resolve component /atg/registry/Slots/HomeTheme in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972043 / Invalid attempt to resolve component /atg/registry/Slots/PromotedProduct1 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972048 / Invalid attempt to resolve component /atg/registry/Slots/PromotedProduct2 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972053 / Invalid attempt to resolve component /atg/registry/Slots/PromotedProduct3 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972058 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct2 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972063 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct3 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972069 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct4 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972074 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct5 in scope global. It is defined in scope request
**** Error Fri Nov 21 14:56:12 IST 2014 1416561972079 / Invalid attempt to resolve component /atg/registry/Slots/FeaturedProduct1 in scope global. It is defined in scope request
Hi i am new to ATG.
ReplyDeleteWhile product selection i havn't get the option for the ATG search although i am using ATG 10.0.3