Learnings :
* The schema/User
created must be given dba privileges.
* The version of
jboss should not be higher than 6.1
* All the
installations/configurations related to the ATG should be done inside
a particular folder.
* If using CRS ,
the endeca application creation should be performed from
<ATG-HOME>/CommerceReferenceStore/Store/Storefront/deploy , not
from endeca Tools and framework reference app. This helps evade
sample camera store data
ISSUES :
Issue 1
: Not able to install Oracle in local.
Why :
a) linux packages
not present .
b) Init run level is
set to 1 . As per message while Oracle installation , it should be
set 3,5
Solution :
a) downloaded and
added the packages. BUT STILL ORACLE did not work
b) Set Init run
level to 3 BUT THIS CRASHES THE MACHINE. NEEDED TO REINSTALL UBUNTU
Workaround : Pointed
to Oracle VM on 192.168.10.19
Issue 2 :
Publishing Schema Data import not working
Why: ClassPath was
not setr properly
Triage : Check the
cim logs. Some classNotfound error was there for a class file
Solution:
add the j2ee jars
(which have those classes in them – Download if needed) to the
classpath as followign :
if DEFINED
JBOSS_HOME set
CLASSPATH=%CLASSPATH%;%JBOSS_HOME%\lib\jboss-javaee.jar;%JBOSS_HOME%\common\lib\jsp-api.jar;%JBOSS_HOME%\common\lib\servlet-api.jar
Workaround:
NA
Isssue 3 :
Search box and endeca dependent pages not displaying
Why : Data indexing did not happen properly
Solution : Perform a full deployment through BCC and run baseline
index to get the pages dependent on endeca
Workaround : NA
Issue 4 :
Images on home page not displaying .
Why : The images depend on Slot and Targeters which are dependent on
BCC deployment.
Triage : Check the logs of production server which states HomeTheme
component not fould
Solution : Perform a full publishing deployment.
Workaround : you can continue working without targetters.
Issue 5 :
BCC full delployment failed with general error
Why : Due to java out of memory
Triage : Check in publishing server log which shows that gc ran into
memory out of Heap exception
Solution
: Increase the java heap in /common/jboss-5.1.0.GA/bin/run.conf
as shown below :
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms512m
-Xmx1024m
-XX:MaxPermSize=512m
-Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000"
# CIM - Modifying JBoss JVM Memory Settings
JAVA_OPTS="$JAVA_OPTS -server -XX:MaxNewSize=256m"; export
JAVA_OPTS
fi
Issue 6 :
Issue while running publishing server for ATG-CRS application. Unable
to query table "das_id_generator"
Why : publishing Datasource was not pointing to right schema.
Triage
: asked query on OTN : https://community.oracle.com/thread/3638300
Solution : Update atg-ds file @
<jboss-home>/server/<pub-server-name>/atg-ds.xml and
point pub schema to ATGPublishing
