Prerequisites:
1. A supported application server, such as JBoss .
Oracle Database.
Ensure that ATG-Service2007_1(CSC) has been installed.
–This can be done by running ATGService.jar file.
4. Ensure that you have the correct license for ATG Commerce Service Center and place it in the <ATG-DIR>/home/localconfig .
STEPS:
Create an agent schema with dba previlage.
2.Similarly create a production schema.(It is possible to use the schema which is already exist as a production schema).
3.Configure the FakeXADataSource :
(i) Create FakeXADataSource_agent.properties file .
(ii) Create JTDataSource_agent.properties file .
<ATG2007.1-dir>/home/localconfig/atg/dynamo/service/jdbc/ in the file type
$class=atg.service.jdbc.FakeXADataSource_agent
user=<username>
needsSeparateUserInfo=false
URL=jdbc:oracle:thin:@<hostname>:1521:<SID>
password= <password>
driver=oracle.jdbc.OracleDriver .
(iii) Create JTDataSource.properties file .
<ATG2007.1-dir>/home/localconfig/atg/dynamo/service/jdbc/ in the file type
$class=atg.service.jdbc.FakeXADataSource_agent
user=<username>
needsSeparateUserInfo=false
URL=jdbc:oracle:thin:@<hostname>:1521:<SID>
password= <password>
driver=oracle.jdbc.OracleDriver .
(Note:JTDataSource.properties should also point to the agent).
(iv) Create FakeXADataSource_production.properties file .
(v) Create JTDataSource_production.properties file .
<ATG2007.1-dir>/home/localconfig/atg/dynamo/service/jdbc/ in the file type
$class=atg.service.jdbc.FakeXADataSource_production
user=<username>
needsSeparateUserInfo=false
URL=jdbc:oracle:thin:@<hostname>:1521:<SID>
password= <password>
driver=oracle.jdbc.OracleDriver .
3. Run the create-service-all.bat script in the <ATG2007.1dir>/Service2007.1/Service/install directory for your database type.
This script runs a number of SQL files for your specific environment.
(Note: Other way of running all sql files mentioned for agent and production schema is ,asusual logon to the specified schema and run the corresponding sql files mentioned in Create-service-all.sh in the same directory).
4. Scripts to run in the production database
(i)<ATG2007.1dir>/CSC2007.1/DCS-CSR/sql/db_components/DCS-CSR_ddl.sql .
(ii)<ATG2007.1dir>/CSC2007.1/DCS-CSR/sql/db_components/DCS-CSR_ticketing_ddl.sql
5. Scripts to run in the Agent database
<ATG2007.1dir>/CSC2007.1/DCS-CSR/sql/db_components/DCS-CSR_logging_ddl.sql
6. Import the data by going to the <ATG2007.1dir>/bin directory and entering the following commands:
i)startSQLRepository -m DSS -repository /atg/userprofiling/ProfileAdapterRepository -import
<ATG2007.1dir>/Publishing/base/install/epub-role-data.xml .
ii)Run the <DYNAMO_HOME>/../Service2007.1/install/import- scripts/ import-service- -all.sh file.
(Note: For Windows, run (.bat) files instead of (.sh) files ).
7.Execute the following files to import login and access rights data:
(i)<ATG2007.1dir>/CSC2007.1/DCS-CSR/install/importDCSCSR.sh.
(ii)<ATG2007.1dir>/CSC2007.1/DCS-CSR/install/importDCSCSREvalSuperUser.sh .
8. Configure Jndi datasource in the /atg/dynamo/service/jdbc in JTDataSource_production.properties delete everything inside it and type the following
$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGOracleDS <it should point to Production schema>
(Eg:JNDIName=java:/ATGProductDS)
9. Configure Jndi datasource in the /atg/dynamo/service/jdbc in JTDataSource.properties and JTDataSource_agent.properties delete everything inside it and type the following ,
$class=atg.nucleus.JNDIReference
JNDIName=java:/ATGAgentDS <it should point to CSC_Agent schema>
10. Adjusting the JBoss Heap Size
(i)Edit the <jboss-dir>/bin/run.sh|bat file by searching for “Sun JVM memory allocation pool parameters” and changing the JAVA_OPTS line:
set JAVA_OPTS=%JAVA_OPTS% -server -Xms1152m -Xmx1152m -XX:MaxPermSize=128m
-XX:MaxNewSize=128m
11. Start the server by startDynamoOnJBoss -m <eshop-Modules> DCS-CSR.
12. To access CSC application http://hostname:portno/agent
Username and Password is csr / csr .
Realted Errors while installing CSC:
1. While importing scripts using ./import-service-all.sh
ORA-12516 & ORA-12519 Population to repository failed (SQLException),
TNS:listener could not find available handler with matching protocol stack
Soln:
Run the following command in agent schema with admin previleges, else login as system admin of oracle.
ALTER SYSTEM SET PROCESSES=150 SCOPE=DPFILE;
(NOTE: kill all the unwanted oracle server instance running(i-e)unwanted local oracle instance).
2. JDBC driver specification error
We have to create two xml files such as
(i) atg-apps-solid-ds.xml (With JNDI name information,username,pwd of production schema)
(ii) atg-solid-ds.xml (With JNDI name information,username,pwd of agent schema)
and should put it in the following destination/opt/jboss-4.0.5.GA/server/atg/deploy.
3. Illegal access: this web application instance has been stopped already. Could not load org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl.
The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
Soln: Delete all the ear files already existing within the ‘atg’ server in the Jboss
4. While cleared all the errors,and after running the command startDynamoOnJboss.sh,
then if u get any errors in the browser ,DELETE ALL COOKIES AND HISTORY of the browser.
5.Create a separate JTDataSource for both agent and production in case there is an exception in addition to the JTDataSource where both JTDataSource_agenat and JTDataSource points to the same Agent Schema.
6.Avoid creation of Individual Servers for both the agent and the production during the installation phase
No comments:
Post a Comment