Skip to main content

Update ATG references after installing a new version of JDK

If you already have a JDK version installed on your machine, but then you change it to another version (for example, after installing latest java patch for jdk 1.6 which includes a fix for TLSv1.2), you will probably get something like this when starting up your instance:

 11:15:09,925 WARNING [config] Unable to process deployment descriptor for context '/DCS-CSR-UI'
11:15:09,925 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/DCS-CSR-UI'
11:15:09,959 INFO  [TomcatDeployment] deploy, ctxPath=/DCS-CSR
11:15:09,976 WARNING [config] Unable to process deployment descriptor for context '/DCS-CSR'
11:15:09,977 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/DCS-CSR'
11:15:10,001 INFO  [TomcatDeployment] deploy, ctxPath=/ServiceFramework
11:15:10,014 WARNING [config] Unable to process deployment descriptor for context '/ServiceFramework'
11:15:10,014 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/ServiceFramework'
11:15:10,041 INFO  [TomcatDeployment] deploy, ctxPath=/tru
11:15:10,055 WARNING [config] Unable to process deployment descriptor for context '/tru'
11:15:10,055 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/tru'
11:15:10,098 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
11:15:10,117 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
11:15:10,125 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8443

11:15:10,134 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 23s:685ms

 If you don't want to reinstall your ATG version, all you need to do is update these files with the correct JDK within your ATG installation:
- $ATG_HOME\installconfig\config.xml
- $ATG_HOME\installconfig\configXMLproperties.txt
- $ATG_HOME\localconfig\dasEnv.bat

Comments

Post a Comment

Popular posts from this blog

Configure LDAP SSO for BCC and Endeca Workbench

If you want to setup your BCC with a SSO server along with LDAP validation you can follow the next steps, this is all for OOTB configs: LDAP In Memory Server Feel free to clone and build:  https://github.com/kwart/ldap-server Then you can start it with:  java -jar ldap-server.jar -b 127.0.0.1 -p 10389 ldap_test.ldif Lastly, you can validate connectivity with this command:  ldapsearch -h localhost -p 10389 -x -D "uid=admin,ou=system" -w secret Just make sure that you defined user and organization appropriately. CIM Setup SSO Run <ATG_ROOT>/home/bin/cim.sh Select options as follows: Platform-Guided Search Integration [8] Content Administration Choose Commerce AddOns: [4] Single Sign On (SSO) [D] Done [1] Commerce Only SSO Authentication [1] LDAP Server Authentication [1] Non-Switching Datasource Don't include demo application [2] Index by Product [A] Select Application Server [2] Weblogic Enter Weblogic home path: /your/weblogic/wlserver/path Enter domain path: /your/...
Post a Comment
Read more

Fix broken sequence on parent-child relationship tables for PUB schema

Whenever you find an error like this (for category-product relationship for example) ERROR [nucleusNamespace.atg.commerce.catalog.ProductCatalog-ver]  Error reading list or array index from the database. Expected: "0", got "1". The following property was not read: " {fixedChildProducts,pType=List,IDesc=[ItemDesc: category],table=dcs_cat_chldprd,cols=child_prd_id   ,pBI=atg.beans.MergedDynamicBeanInfo@5409e0ad,pIDesc=null   ,cType=interface atg.repository.RepositoryItem,cBI=[ItemDesc: product],cIDesc=[ItemDesc: product],colHandle=null}", for item id: "2350:36". This means the data base table holding this property does not have sequential integers starting with 0 in its multi-column. This should only happen if the database table was modifie d directly (outside of Dynamo).: java.lang.Exception It means sequence_num column doesn't contain a consecutive sequence number for the category on all of its products, this is, if category has ...
2 comments
Read more

ATG - Clean up CORE and PUB schemas

In case you want to clean up your environments a little bit you can make use of the following scripts: DEFINE CORE_SCHEMA = '<atg_core_name>'; DEFINE PUB_SCHEMA = '<atg_pub_name>'; -- Delete server host names DELETE FROM &CORE_SCHEMA..rout_instance; DELETE FROM &CORE_SCHEMA..das_sds; DELETE FROM &PUB_SCHEMA..das_sds; DELETE FROM &CORE_SCHEMA..rout_host_inf; commit;  -- Delete projects not checked in DELETE FROM &pub_schema..epub_pr_history WHERE project_id IN (SELECT project_id FROM &pub_schema..epub_project WHERE checked_in = 0); DELETE FROM &pub_schema..epub_proc_history WHERE process_id IN (SELECT process_id FROM &pub_schema..epub_process WHERE PROJECT IN (SELECT project_id FROM &pub_schema..epub_project WHERE checked_in = 0)); DELETE FROM &pub_schema..epub_proc_taskinfo WHERE ID IN (SELECT process_id FROM &pub_schema..epub_process WHERE PROJECT IN (SELECT project_id FROM &pub_schema..epub_pro...
Post a Comment
Read more