Immuraliraj-TechTalks

com.endeca.itl.component.manager.ComponentManagerException - Could not create component instance

2018-11-16T23:57:00.002-08:00

ERROR [ComponentInstanceManager] [main] com.endeca.itl.component.manager.impl.ComponentInstanceManagerImpl: Error auto starting instance 'Extensions of type RecordStore
com.endeca.itl.component.manager.ComponentManagerException: Could not create component instance
at com.endeca.itl.component.manager.impl.ComponentInstanceManagerImpl.startInstance(ComponentInstanceManagerImpl.java:142)
at com.endeca.itl.component.manager.impl.ComponentInstanceManagerImpl.<init>(ComponentInstanceManagerImpl.java:60)
at com.endeca.itl.component.manager.impl.ComponentInstanceManagerImpl.<init>(ComponentInstanceManagerImpl.java:47)
at com.endeca.itl.service.ServiceHubServlet.loadBus(ServiceHubServlet.java:50)
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.endeca.itl.plugin.ThreadContextRunner$1$1.doWork(ThreadContextRunner.java:19)
at com.endeca.itl.plugin.ThreadContextRunner.run(ThreadContextRunner.java:110)
at com.endeca.itl.plugin.ThreadContextRunner$1.invoke(ThreadContextRunner.java:25)
at com.sun.proxy.$Proxy1.init(Unknown Source)
at com.endeca.itl.bootstrap.CasBootStrapServlet.init(CasBootStrapServlet.java:42)
at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440)
at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:736)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at com.endeca.itl.jetty.Main.main(Main.java:74)
Caused by: com.endeca.itl.recordstore.RecordStoreException: Error starting embedded database: Database lock acquisition failure: lockFile: org.hsqldb.persist.LockFile@f1d244ec[file =/u01/endeca/CAS/workspace/state/WCSExtensions/data/dictionary/db.lck, exists=true, locked=false, valid=false, ] method: checkHeartbeat length: 2289
at com.endeca.itl.recordstore.impl.RecordStoreImpl.startup(RecordStoreImpl.java:108)
at com.endeca.itl.recordstore.impl.RecordStoreImpl.<init>(RecordStoreImpl.java:91)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.endeca.itl.component.manager.impl.ComponentInstanceManagerImpl.startInstance(ComponentInstanceManagerImpl.java:130)
... 31 more
Caused by: java.sql.SQLException: Database lock acquisition failure: lockFile: org.hsqldb.persist.LockFile@f1d244ec[file =/u01/endeca/CAS/workspace/state/WCSExtensions/data/dictionary/db.lck, exists=true, locked=false, valid=false, ] method: checkHeartbeat length: 2289
at org.hsqldb.jdbc.Util.sqlException(Util.java:418)
at org.hsqldb.jdbc.Util.sqlException(Util.java:113)
at org.hsqldb.jdbc.JDBCConnection.<init>(JDBCConnection.java:3596)
at org.hsqldb.jdbc.JDBCDriver.getConnection(JDBCDriver.java:322)
at org.hsqldb.jdbc.JDBCDataSource.getConnection(JDBCDataSource.java:190)
at org.hsqldb.jdbc.JDBCDataSource.getConnection(JDBCDataSource.java:149)
at com.endeca.itl.db.Database.createConnection(Database.java:116)
at com.endeca.itl.db.Database.createConnection(Database.java:112)
at com.endeca.itl.db.Database.startup(Database.java:88)
at com.endeca.itl.recordstore.impl.RecordStoreImpl.startup(RecordStoreImpl.java:105)
... 37 more
Caused by: org.hsqldb.HsqlException: Database lock acquisition failure: lockFile: org.hsqldb.persist.LockFile@f1d244ec[file =/u01/endeca/CAS/workspace/state/WCSExtensions/data/dictionary/db.lck, exists=true, locked=false, valid=false, ] method: checkHeartbeat length: 2289
at org.hsqldb.error.Error.error(Error.java:81)
at org.hsqldb.error.Error.error(Error.java:70)
at org.hsqldb.persist.LockFile.newLockFileLock(LockFile.java:642)
at org.hsqldb.persist.Logger.acquireLock(Logger.java:1211)
at org.hsqldb.persist.Logger.openPersistence(Logger.java:349)
at org.hsqldb.Database.reopen(Database.java:227)
at org.hsqldb.Database.open(Database.java:193)
at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:250)
at org.hsqldb.DatabaseManager.newSession(DatabaseManager.java:157)
at org.hsqldb.jdbc.JDBCConnection.<init>(JDBCConnection.java:3576)
... 44 more
2018-10-18 11:40:51,114 INFO [ComponentInstanceManager] [main] com.endeca.itl.component.manager.impl.ComponentInstanceManagerImpl: Starting component instance 'CRS_en_data' of component type 'RecordStore'.
2018-10-18 11:40:51,192 INFO [CRS_en_data] [main] com.endeca.itl.recordstore.impl.RecordStoreImpl: Starting up RecordStore
2018-10-18 11:40:51,299 INFO [CRS_en_data] [main] com.endeca.itl.recordstore.impl.GenerationManager: Last committed generation: 13

Solution:

1. Stop CAS services

2. Run initialize_rs_feeds.sh script for linux or initialize_rs_feeds.bat for windows

3. Start CAS services

4. Run Baseline indexing in Dyn/Admin

RMI Over SSL in ATG Platform Configuration

2015-10-07T06:13:00.001-07:00

RMI Over SSL

Component:

Use this component for RMI over SSL configuration /atg/dynamo/service/socket/SSLRMISocketFactory

Enable RMI Over SSL:

set the RMISocketFactory property of the /atg/dynamo/server/RmiInitialization component to point to the SSLRMISocketFactory component

eg: RMISocketFactory=/atg/dynamo/service/socket/SSLRMISocketFactory

Configuring Keys and Certificates:

1. Go to your ATGDir\home directory.

2. Use the keytool utility to export the Oracle ATG Web Commerce certificate:

keytool -export -alias atgkey –keystore ..\DAS\keystore\atg-ssl.jks
-rfc –file ..\DAS\keystore\atg-ssl.cer

3. Enter atgkey when prompted for the key store password:

Enter password name: atgkey
Certificate stored in file <..\das\keystore\atg-ssl.cer>

4. Now import the Oracle ATG Web Commerce certificate:

keytool -import -alias atgcert -file ..\DAS\keystore\atg-ssl.cer -keystore
..\DAS\keystore\cacerts.jks

The key tool utility displays information about the certificate:

5. Owner: CN=Snorthog, OU=Dynamo, O=Art Techonology Group, L=Cambridge,
ST=MA, C=US
Issuer: CN=Snorthog, OU=Dynamo, O=Art Techonology Group, L=Cambridge,
ST=MA, C=US
Serial number: 3eef2fc2
Valid from: Tue Jun 17 11:12:02 EDT 2003 until: Thu May 04 14:50:08
EDT 2006
Certificate fingerprints:
MD5: 95:0E:9A:3A:D7:C9:A6:CA:73:B5:CA:C0:44:DB:E0:1E
SHA1: 32:38:3C:AD:57:BB:59:B7:9C:91:A3:79:03:56:9E:96:44:37:20:4C

6. Answer yes when prompted whether to trust the certificate:

Trust this certificate? [no]: yes
Certificate was added to keystore

Generating a New Certificate on Production Environment:

We can use the keytool utility to generate a new private key and public key, and wrap the public key into a new self-signed certificate.

1. Configure the /atg/dynamo/security/BasicSSLConfiguration component on each server.

2. You must set the keyStore and trustStore properties to point to your new key store and trust store file locations. You must also set the keyStorePassword and trustStorePassword properties to the values that you used when creating the key store and trust store.

Note: Use the JDK keytool utility with the –genkey flag to generate a new self-signed certificate that wraps the public key.

LDAPConnection - CommunicationException: someUrl.domain:389 : ATG

2015-07-01T10:54:00.000-07:00

LDAPConnection - CommunicationException: someUrl.domain:389

Solution:

GoTo ==> <ATGDir>\DAS\LDAP\MicrosoftActiveDirectory\config\atg\dynamo\security

InitialContextEnvironment.properties

Edit providerURL=ldap://someUrl.domain:389 to ldap://localhost:389

Example:

# @version $Id: //product/DAS/version/11.1/release/DAS/LDAP/MicrosoftActiveDirectory/config/atg/dynamo/security/InitialContextEnvironment.properties#1 $$Change: 875535 $

$class=atg.adapter.ldap.LDAPJNDIEnvironment

# URL of the LDAP server

providerURL=ldap://localhost:389

# Authentication mechanism for the provider to use. Possible

# values are:

# CRAM-MD5 - use the CRAM-MD5 (RFC-2195) SASL mechanism

# none - use no authentication (anonymous)

# simple - use weak authentication (cleartext password)

securityAuthentication=simple

# The identity of the principal to be authenticated, in form

# of a distinguished name.

securityPrincipal=RootDN

# The credentials of the principal to be authenticated.

securityCredentials=password

Creating Endeca Discover Application For Beginners : Endeca

2015-05-31T12:28:00.001-07:00

Create Discover App:

1. Go To => C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin

2. Open Command Prompt from the above location,

3. Note: deploy.bat file will call deploy.pl file from ToolAndFrameworks lib folder

4. Note: deploy.pl file will allow the system to call respective variable for creating new app

5. Follow the below steps:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin>deploy.bat --app C:\Endeca\ToolsAndFrameworks\3.1.1\reference\discover-data\deploy.xml

------------------------------------------------------------------------------

Found version 6.1 of the Endeca IAP installed in directory

C:\Endeca\PlatformServices\6.1.3. If either the version or location are
incorrect, type 'Q' to quit and adjust your ENDECA_ROOT environment variable.
Press enter to continue with these settings.

Continue?

------------------------------------------------------------------------------

Deployment Template installation script.

This script creates the directory structure for your
deployment and installs configuration files and scripts
into the directory structure.

05/05/2015 12:11:57 [deploy.pl] INFO: Starting deployment template
installation.

------------------------------------------------------------------------------

The following app modules were specified on the command line argument:

C:\Endeca\ToolsAndFrameworks\3.1.1\reference\discover-data\deploy.xml

Modules may be deployed standalone or on top of a base deployment type. Do
you want to install a base deployment with the specified module(s)?

Install base deployment? [Y/N]: Y

05/05/2015 12:12:05 [AppDescriptorReader] INFO: Parsing application descriptor
file C:\Endeca\ToolsAndFrameworks\3.1.1\reference\discover-data\deploy.xml.
05/05/2015 12:12:05 [AppDescriptorReader] INFO: Parsing application descriptor
file

C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\app-templates\base_descriptor.xml.

------------------------------------------------------------------------------

Enter a short name for your application.

Note: The name must conform to this regular expression: ^[a-zA-Z0-9]+$
[default: Discover]

Choosing a different application name may require additional configuration on
your web application.

Application name: lifestyle

------------------------------------------------------------------------------

Specify the path into which the application will be deployed. The specified
directory must exist and cannot contain spaces.

For example, to deploy into c:\apps\lifestyle, specify the path as c:\apps.

Deployment directory: C:\Endeca\Apps

------------------------------------------------------------------------------

Specify the port on which the Endeca Application Controller is running. This
is configured in the server.xml file in the workspace of the Endeca software
install and should be the same for all applications deployed in this
environment. Ports must be in the range 1024-65535 [default: 8888].

EAC port: 8888

05/05/2015 12:12:46 [deploy.pl] INFO: Deploying application into
C:\Endeca\Apps\lifestyle

------------------------------------------------------------------------------

What port is the Workbench running? [Default: 8006]

8006

------------------------------------------------------------------------------

Note: I have another app running on 15000 Port. In this app i am using 18000 port

-------------------------------------------------------------------------------

What port should be used for the Live Dgraph? [Default: 15000]

18000

------------------------------------------------------------------------------

What port should be used for the Authoring Dgraph? [Default: 15002]

18002

------------------------------------------------------------------------------

What port should be used for LogServer? [Default: 15010]

18010

05/05/2015 12:13:25 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\app-templates\base_descriptor.xml.
05/05/2015 12:13:25 [deploy.pl] INFO: Processing install with id 'Dgraph'
05/05/2015 12:13:27 [AppDescriptorReader] INFO: Parsing application descriptor
file C:\Endeca\ToolsAndFrameworks\3.1.1\reference\discover-data\deploy.xml.
05/05/2015 12:13:27 [deploy.pl] INFO: Processing install with id
'DefaultTemplateManagerApp'
05/05/2015 12:13:30 [deploy.pl] INFO: Application successfully deployed.

C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin>

Note: Verify our new app will be created under C:/Endeca/Apps folder. if it is created. then we are successfully created the new app.

Run Initial_Services.bat

C:\Endeca\Apps\lifestyle\control>initialize_services.bat
Setting EAC provisioning and performing initial setup...
[05.05.15 12:17:51] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.05.15 12:17:51] INFO: Setting definition for application 'lifestyle'.
[05.05.15 12:17:52] INFO: Setting definition for host 'AuthoringMDEXHost'.
[05.05.15 12:17:52] INFO: Setting definition for host 'LiveMDEXHostA'.
[05.05.15 12:17:53] INFO: Setting definition for host 'ReportGenerationHost'.
[05.05.15 12:17:53] INFO: Setting definition for host 'WorkbenchHost'.
[05.05.15 12:17:53] INFO: Setting definition for host 'ITLHost'.
[05.05.15 12:17:53] INFO: Setting definition for component 'AuthoringDgraph'.
[05.05.15 12:17:53] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgidx-output'.
[05.05.15 12:17:57] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-forge-output'.
[05.05.15 12:17:58] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-cumulative-partials'.
[05.05.15 12:17:59] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-workbench-dgraph-config'.
[05.05.15 12:18:01] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgraph-input'.
[05.05.15 12:18:02] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-cumulative-partials'.
[05.05.15 12:18:03] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgraph-config'.
[05.05.15 12:18:04] INFO: Setting definition for component 'DgraphA1'.
[05.05.15 12:18:05] INFO: Setting definition for script 'PromoteAuthoringToLive'.
[05.05.15 12:18:05] INFO: Setting definition for custom component 'WorkbenchManager'.
[05.05.15 12:18:05] INFO: Updating provisioning for host 'ITLHost'.
[05.05.15 12:18:05] INFO: Updating definition for host 'ITLHost'.
[05.05.15 12:18:05] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.05.15 12:18:07] INFO: [ITLHost] Starting shell utility 'mkpath_-data-workbench-temp'.
[05.05.15 12:18:08] INFO: Setting definition for custom component 'IFCR'.
[05.05.15 12:18:08] INFO: Updating provisioning for host 'ITLHost'.
[05.05.15 12:18:08] INFO: Updating definition for host 'ITLHost'.
[05.05.15 12:18:08] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.05.15 12:18:10] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.05.15 12:18:11] INFO: Setting definition for component 'LogServer'.
[05.05.15 12:18:11] INFO: [ReportGenerationHost] Starting shell utility 'mkpath_-reports-input'.
[05.05.15 12:18:13] INFO: Setting definition for script 'DaySoFarReports'.
[05.05.15 12:18:13] INFO: Setting definition for script 'DailyReports'.
[05.05.15 12:18:13] INFO: Setting definition for script 'WeeklyReports'.
[05.05.15 12:18:13] INFO: Setting definition for script 'DaySoFarHtmlReports'.
[05.05.15 12:18:14] INFO: Setting definition for script 'DailyHtmlReports'.
[05.05.15 12:18:14] INFO: Setting definition for script 'WeeklyHtmlReports'.
[05.05.15 12:18:14] INFO: Setting definition for component 'WeeklyReportGenerator'.
[05.05.15 12:18:14] INFO: Setting definition for component 'DailyReportGenerator'.
[05.05.15 12:18:20] INFO: Setting definition for component 'DaySoFarReportGenerator'.
[05.05.15 12:18:20] INFO: Setting definition for component 'WeeklyHtmlReportGenerator'.
[05.05.15 12:18:21] INFO: Setting definition for component 'DailyHtmlReportGenerator'.
[05.05.15 12:18:21] INFO: Setting definition for component 'DaySoFarHtmlReportGenerator'.
[05.05.15 12:18:21] INFO: Setting definition for script 'BaselineUpdate'.
[05.05.15 12:18:21] INFO: Setting definition for script 'PartialUpdate'.
[05.05.15 12:18:21] INFO: Setting definition for component 'Forge'.
[05.05.15 12:18:22] INFO: [ITLHost] Starting shell utility 'mkpath_-data-incoming'.
[05.05.15 12:18:23] INFO: Setting definition for component 'PartialForge'.
[05.05.15 12:18:23] INFO: [ITLHost] Starting shell utility 'mkpath_-data-partials-incoming'.
[05.05.15 12:18:25] INFO: Setting definition for component 'Dgidx'.
[05.05.15 12:18:25] INFO: Definition updated.
[05.05.15 12:18:25] INFO: Provisioning site from prototype...
[05.05.15 12:18:26] INFO: Finished provisioning site from prototype.
[05.05.15 12:18:26] INFO: Uploading config files to Workbench.
[05.05.15 12:18:26] INFO: [ITLHost] Starting shell utility 'emgr_update_update_mgr_settings'.
[05.05.15 12:18:36] INFO: Finished uploading config files to Workbench.
Finished updating EAC.
Importing sample content...
[05.05.15 12:18:37] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.05.15 12:18:37] INFO: Definition has not changed.
[05.05.15 12:18:38] INFO: Packaging contents for upload...
[05.05.15 12:18:38] INFO: Finished packaging contents.
[05.05.15 12:18:38] INFO: Uploading contents to: http://ADMINIB-EAOPVNR:8006/ifcr/sites/lifestyle/
[05.05.15 12:18:39] INFO: Finished uploading contents.
[05.05.15 12:18:40] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.05.15 12:18:41] INFO: Definition has not changed.
[05.05.15 12:18:41] INFO: Packaging contents for upload...
[05.05.15 12:18:41] INFO: Finished packaging contents.
[05.05.15 12:18:41] INFO: Uploading contents to: http://ADMINIB-EAOPVNR:8006/ifcr/sites/lifestyle/content
[05.05.15 12:18:42] INFO: Finished uploading contents.
[05.05.15 12:18:43] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.05.15 12:18:44] INFO: Definition has not changed.
[05.05.15 12:18:44] INFO: Packaging contents for upload...
[05.05.15 12:18:44] INFO: Finished packaging contents.
[05.05.15 12:18:44] INFO: Uploading contents to: http://ADMINIB-EAOPVNR:8006/ifcr/sites/lifestyle/pages
[05.05.15 12:18:44] INFO: Finished uploading contents.
Finished importing sample content
Importing editors configuration...
[05.05.15 12:18:45] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.05.15 12:18:46] INFO: Definition has not changed.
[05.05.15 12:18:46] INFO: Packaging contents for upload...
[05.05.15 12:18:46] INFO: Finished packaging contents.
[05.05.15 12:18:46] INFO: Uploading contents to: http://ADMINIB-EAOPVNR:8006/ifcr/sites/lifestyle/configuration/tools/xmgr
[05.05.15 12:18:46] INFO: Finished uploading contents.
Finished importing editors configuration
Importing media...
[05.05.15 12:18:47] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.05.15 12:18:47] INFO: Definition has not changed.
[05.05.15 12:18:47] INFO: Packaging contents for upload...
[05.05.15 12:18:48] INFO: Finished packaging contents.
[05.05.15 12:18:48] INFO: Uploading contents to: http://ADMINIB-EAOPVNR:8006/ifcr/sites/lifestyle/media
[05.05.15 12:18:49] INFO: Finished uploading contents.
Finished importing media
Importing templates...
Removing existing cartridge templates for lifestyle
Setting new cartridge templates for lifestyle
Finished setting templates
Finished importing templates

Run load_baseline_test_data.bat

C:\Endeca\Apps\lifestyle\control>load_baseline_test_data.bat

C:\Endeca\Apps\lifestyle\config\script\..\..\test_data\baseline\camerastore.xml.gz
1 file(s) copied.
Setting flag 'baseline_data_ready' in the EAC.

Run baseline_update.bat

C:\Endeca\Apps\lifestyle\control>baseline_update.bat
[05.06.15 01:11:14] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.06.15 01:11:15] INFO: Updating provisioning for component 'DailyReportGenerator'.
[05.06.15 01:11:15] INFO: Updating definition for component 'DailyReportGenerator'.
[05.06.15 01:11:15] INFO: Definition updated.
[05.06.15 01:11:15] INFO: Starting baseline update script.
[05.06.15 01:11:15] INFO: Acquired lock 'update_lock'.
[05.06.15 01:11:15] WARNING: Baseline data not ready for processing.
[05.06.15 01:11:15] INFO: Released lock 'update_lock'.
[05.06.15 01:11:15] INFO: Baseline update script finished.

Run promote_content.bat

C:\Endeca\Apps\lifestyle\control>promote_content.bat
[05.06.15 01:11:55] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.06.15 01:11:56] INFO: Definition has not changed.
[05.06.15 01:11:56] INFO: Promoting IFCR content...
[05.06.15 01:11:58] INFO: Finished promoting IFCR content.

Final Step:

Verify lifeStyle in Endeca Workbench by accessing below URL

http://localhost:8006

Also check access your lifestyle application by accessing below URL

http://localhost:8006/lifestyle

Thats It.

Endeca Issues When creating Any App:

Some times when you are trying to execute baseline_update.bat, you may face below issues.

C:\Endeca\Apps\lifestyle\control>baseline_update.bat

[05.05.15 12:19:45] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.05.15 12:19:45] INFO: Definition has not changed.
[05.05.15 12:19:45] INFO: Starting baseline update script.
[05.05.15 12:19:45] INFO: Acquired lock 'update_lock'.
[05.05.15 12:19:46] INFO: [ITLHost] Starting shell utility 'move_-_to_processing'.
[05.05.15 12:19:47] INFO: [ITLHost] Starting copy utility 'fetch_config_to_input_for_forge_Forge'.
[05.05.15 12:19:48] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Forge'.
[05.05.15 12:19:49] INFO: [ITLHost] Starting component 'Forge'.
[05.05.15 12:19:54] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Dgidx'.
[05.05.15 12:19:55] INFO: [ITLHost] Starting component 'Dgidx'.
[05.05.15 12:20:01] SEVERE: Batch component 'Dgidx' failed. Refer to component logs in C:\Endeca\Apps\lifestyle\config\script\..\..\.\logs\dgidxs\Dgi
dx on host ITLHost.
Occurred while executing line 25 of valid BeanShell script:
[[

22| Forge.archiveLogDir();
23| Forge.run();
24| Dgidx.archiveLogDir();
25| Dgidx.run();
26|
27| // distributed index, update Dgraphs
28| DistributeIndexAndApply.run();

]]

[05.05.15 12:20:01] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.

Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 - null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
com.endeca.soleng.eac.toolkit.component.BatchComponent run - Batch component 'Dgidx' failed. Refer to component logs in C:\Endeca\Apps\lifestyle\conf
ig\script\..\..\.\logs\dgidxs\Dgidx on host ITLHost.

[05.05.15 12:20:01] INFO: Released lock 'update_lock'.

Solution:

1. This issue will occur only when your Mdex Engine is not started properly.

Go to Windows ==> Run ==> Type "Services.msc"

And Start/Restart Endeca Mdex will resolve this issue.

Creating Endeca App Using CRS For Beginners : Endeca

2015-04-30T13:14:00.001-07:00

Create Endeca App:

1. Go To => C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin

2. Open Command Prompt from the above location,

3. Note: deploy.bat file will call deploy.pl file from ToolAndFrameworks lib folder

4. Note: deploy.pl file will allow the system to call respective variable for creating new app

5. Follow the below steps:

C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin>deploy.bat --app C:\ATG\ATG10.1.2\CommerceReferenceStore\Store\Storefront\deploy\deploy.xml

------------------------------------------------------------------------------

Found version 6.1 of the Endeca IAP installed in directory

C:\Endeca\PlatformServices\6.1.3. If either the version or location are

incorrect, type 'Q' to quit and adjust your ENDECA_ROOT environment variable.

Press enter to continue with these settings.

Continue?

------------------------------------------------------------------------------

Deployment Template installation script.

This script creates the directory structure for your

deployment and installs configuration files and scripts

into the directory structure.

05/01/2015 00:50:05 [deploy.pl] INFO: Starting deployment template

installation.

------------------------------------------------------------------------------

The following app modules were specified on the command line argument:

C:\ATG\ATG10.1.2\CommerceReferenceStore\Store\Storefront\deploy\deploy.xml

Modules may be deployed standalone or on top of a base deployment type. Do

you want to install a base deployment with the specified module(s)?

Install base deployment? [Y/N]: Y

05/01/2015 00:50:09 [AppDescriptorReader] INFO: Parsing application descriptor

file

C:\ATG\ATG10.1.2\CommerceReferenceStore\Store\Storefront\deploy\deploy.xml.

05/01/2015 00:50:09 [AppDescriptorReader] INFO: Parsing application descriptor

file

C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\app-templates\base_descriptor.xml.

------------------------------------------------------------------------------

Enter a short name for your application.

Note: The name must conform to this regular expression: ^[a-zA-Z0-9]+$

[default: CRS]

Choosing a different application name may require additional configuration on

your web application.

Application name: MyNewApp

------------------------------------------------------------------------------

Specify the path into which the application will be deployed. The specified

directory must exist and cannot contain spaces.

For example, to deploy into c:\apps\MyNewApp, specify the path as c:\apps.

Deployment directory: C:\Endeca\Apps

------------------------------------------------------------------------------

Specify the port on which the Endeca Application Controller is running. This

is configured in the server.xml file in the workspace of the Endeca software

install and should be the same for all applications deployed in this

environment. Ports must be in the range 1024-65535 [default: 8888].

EAC port: 8888

05/01/2015 00:50:38 [deploy.pl] INFO: Deploying application into

C:\Endeca\Apps\MyNewApp

------------------------------------------------------------------------------

Please enter the CAS install directory using Unix-style forward slashes,

including the version number (e.g. C:/Endeca/CAS/3.1.1).

C:\Endeca\CAS\3.1.1

------------------------------------------------------------------------------

Please enter the version for CAS jar files (or hit 'enter' to use the

default). [Default: 3.1.1]

3.1.1

------------------------------------------------------------------------------

Please enter the hostname where CAS is running (or hit 'enter' to use the

default). [Default: localhost]

localhost

------------------------------------------------------------------------------

Please enter the port where CAS is running (or hit 'enter' to use the

default). [Default: 8500]

8500

------------------------------------------------------------------------------

Please enter the language code to use (or hit 'enter' to use the default).

[Default: en]

------------------------------------------------------------------------------

Please enter the hostname of the Workbench.

localhost

------------------------------------------------------------------------------

Please enter the preview host name. [Default: localhost]

localhost

------------------------------------------------------------------------------

Please enter the preview port number. Typical values are 7003 for WebLogic,

8080 for JBoss and Tomcat, and 9080 for WebSphere.

7003

------------------------------------------------------------------------------

Please enter the context root of the preview application. [Default: crs]

MyNewApp

------------------------------------------------------------------------------

What port is the Workbench running? [Default: 8006]

8006

------------------------------------------------------------------------------

What port should be used for the Live Dgraph? [Default: 15000]

15000

------------------------------------------------------------------------------

What port should be used for the Authoring Dgraph? [Default: 15002]

15002

------------------------------------------------------------------------------

What port should be used for LogServer? [Default: 15010]

15010

05/01/2015 00:51:35 [AppDescriptorReader] INFO: Parsing application descriptor

file

C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\app-templates\base_descriptor.xml.

05/01/2015 00:51:36 [deploy.pl] INFO: Processing install with id 'Dgraph'

05/01/2015 00:51:37 [AppDescriptorReader] INFO: Parsing application descriptor

file

C:\ATG\ATG10.1.2\CommerceReferenceStore\Store\Storefront\deploy\deploy.xml.

05/01/2015 00:51:37 [deploy.pl] INFO: Processing install with id 'CRSApp'

05/01/2015 00:51:38 [deploy.pl] INFO: Application successfully deployed.

C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin>

Note: Verify our new app will be created under C:/Endeca/Apps folder. if it is created. then we are successfully created the new app.

Run Initial_Services.bat

After Completion of new app creation. We must run initial_services,bat file to initialize all the services for the newly created app. Follow the below steps,

1. Go To => C:\Endeca\Apps\MyNewApp\control folder

2. Open the Command Prompt

3. Enter C:\Endeca\Apps\MyNewApp\control\initialize_services.bat

4. Check the Command Prompt log whether agraph, dgraph are created or not.

5. Find below the log details

C:\Endeca\Apps\MyNewApp\control> initialize_services.bat

Setting EAC provisioning and performing initial setup...

[05.01.15 01:30:28] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[05.01.15 01:30:28] INFO: Setting definition for application 'MyNewApp'.

[05.01.15 01:30:30] INFO: Setting definition for host 'AuthoringMDEXHost'.

[05.01.15 01:30:30] INFO: Setting definition for host 'LiveMDEXHostA'.

[05.01.15 01:30:30] INFO: Setting definition for host 'ReportGenerationHost'.

[05.01.15 01:30:30] INFO: Setting definition for host 'WorkbenchHost'.

[05.01.15 01:30:31] INFO: Setting definition for host 'ITLHost'.

[05.01.15 01:30:31] INFO: Setting definition for component 'AuthoringDgraph'.

[05.01.15 01:30:33] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgidx-output'.

[05.01.15 01:30:35] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-forge-output'.

[05.01.15 01:30:36] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-cumulative-partials'.

[05.01.15 01:30:37] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-workbench-dgraph-config'.

[05.01.15 01:30:38] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgraph-input'.

[05.01.15 01:30:39] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-cumulative-partials'.

[05.01.15 01:30:41] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgraph-config'.

[05.01.15 01:30:42] INFO: Setting definition for component 'DgraphA1'.

[05.01.15 01:30:42] INFO: Setting definition for script 'PromoteAuthoringToLive'.

[05.01.15 01:30:42] INFO: Setting definition for custom component 'WorkbenchManager'.

[05.01.15 01:30:43] INFO: Updating provisioning for host 'ITLHost'.

[05.01.15 01:30:43] INFO: Updating definition for host 'ITLHost'.

[05.01.15 01:30:43] INFO: [ITLHost] Starting shell utility 'mkpath_-'.

[05.01.15 01:30:44] INFO: [ITLHost] Starting shell utility 'mkpath_-data-workbench-temp'.

[05.01.15 01:30:45] INFO: [ITLHost] Starting shell utility 'mkpath_-data-processing'.

[05.01.15 01:30:47] INFO: Setting definition for custom component 'IFCR'.

[05.01.15 01:30:47] INFO: Updating provisioning for host 'ITLHost'.

[05.01.15 01:30:47] INFO: Updating definition for host 'ITLHost'.

[05.01.15 01:30:47] INFO: [ITLHost] Starting shell utility 'mkpath_-'.

[05.01.15 01:30:49] INFO: [ITLHost] Starting shell utility 'mkpath_-'.

[05.01.15 01:30:50] INFO: Setting definition for component 'LogServer'.

[05.01.15 01:30:50] INFO: [ReportGenerationHost] Starting shell utility 'mkpath_-reports-input'.

[05.01.15 01:30:51] INFO: Setting definition for script 'DaySoFarReports'.

[05.01.15 01:30:51] INFO: Setting definition for script 'DailyReports'.

[05.01.15 01:30:52] INFO: Setting definition for script 'WeeklyReports'.

[05.01.15 01:30:52] INFO: Setting definition for script 'DaySoFarHtmlReports'.

[05.01.15 01:30:52] INFO: Setting definition for script 'DailyHtmlReports'.

[05.01.15 01:30:52] INFO: Setting definition for script 'WeeklyHtmlReports'.

[05.01.15 01:30:52] INFO: Setting definition for component 'WeeklyReportGenerator'.

[05.01.15 01:30:52] INFO: Setting definition for component 'DailyReportGenerator'.

[05.01.15 01:30:53] INFO: Setting definition for component 'DaySoFarReportGenerator'.

[05.01.15 01:30:53] INFO: Setting definition for component 'WeeklyHtmlReportGenerator'.

[05.01.15 01:30:53] INFO: Setting definition for component 'DailyHtmlReportGenerator'.

[05.01.15 01:30:54] INFO: Setting definition for component 'DaySoFarHtmlReportGenerator'.

[05.01.15 01:30:54] INFO: Setting definition for script 'BaselineUpdate'.

[05.01.15 01:30:54] INFO: Setting definition for script 'PartialUpdate'.

[05.01.15 01:30:54] INFO: Setting definition for component 'ConfigurationGeneratorForge'.

[05.01.15 01:30:54] INFO: Setting definition for component 'Forge'.

[05.01.15 01:30:55] INFO: [ITLHost] Starting shell utility 'mkpath_-data-incoming'.

[05.01.15 01:30:56] INFO: Setting definition for component 'PartialForge'.

[05.01.15 01:30:57] INFO: [ITLHost] Starting shell utility 'mkpath_-data-partials-incoming'.

[05.01.15 01:30:59] INFO: Setting definition for component 'Dgidx'.

[05.01.15 01:30:59] INFO: Definition updated.

[05.01.15 01:30:59] INFO: Provisioning site from prototype...

[05.01.15 01:31:02] INFO: Finished provisioning site from prototype.

Finished updating EAC.

Initializing record stores...

These record stores exist:

NAME TYPE STATUS

CRS_en_schema RecordStore RUNNING

CRS_en_dimvals RecordStore RUNNING

CRS_en_prules RecordStore RUNNING

CRS_en_data RecordStore RUNNING

==================================================

Dropping old record stores (errors will occur on non-existent rs):

Error during execution (check log for more info): Component instance not found: MyNewApp_en_schema

Error during execution (check log for more info): Component instance not found: MyNewApp_en_dimvals

Error during execution (check log for more info): Component instance not found: MyNewApp_en_prules

Error during execution (check log for more info): Component instance not found: MyNewApp_en_data

==================================================

Creating fresh record stores:

Successfully created component: MyNewApp_en_schema

Successfully created component: MyNewApp_en_dimvals

Successfully created component: MyNewApp_en_prules

Successfully created component: MyNewApp_en_data

==================================================

Deploying rs configs:

Successfully set recordstore configuration.

==================================================

Finished initializing record stores

Importing sample content...

[05.01.15 01:31:52] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[05.01.15 01:31:53] INFO: Definition has not changed.

[05.01.15 01:31:53] INFO: Packaging contents for upload...

[05.01.15 01:31:53] INFO: Finished packaging contents.

[05.01.15 01:31:53] INFO: Uploading contents to: http://localhost:8006/ifcr/sites/MyNewApp/

[05.01.15 01:31:54] INFO: Finished uploading contents.

Finished importing sample content

Importing media...

Finished importing media

Importing editors configuration...

[05.01.15 01:31:56] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[05.01.15 01:31:57] INFO: Definition has not changed.

[05.01.15 01:31:57] INFO: Packaging contents for upload...

[05.01.15 01:31:57] INFO: Finished packaging contents.

[05.01.15 01:31:57] INFO: Uploading contents to: http://localhost:8006/ifcr/sites/MyNewApp/configuration/tools/xmgr

[05.01.15 01:31:57] INFO: Finished uploading contents.

Finished importing editors configuration

Importing templates...

Removing existing cartridge templates for MyNewApp

Setting new cartridge templates for MyNewApp

Finished setting templates

Finished importing templates

Final Step:

Verify MyNewApp in Endeca Workbench by accessing below URL

http://localhost:8006

Endeca Workbench

Thats it: Endeca App Created successfully, Follow these methods for any new app

How To Make Product Catalog To Use PriceLists : ATG

2015-03-31T20:33:00.001-07:00

Product Catalog To Use PriceLists

Oracle ATG Web Commerce includes a tool that can be used to convert your existing product catalog without price lists so that it can use price lists.

The PriceListMigration component first creates two price lists:

1. list price,
2. sales price.

For each SKU in the product catalog, the PriceListMigration component creates a price that points to the list price list and sets its list price as the SKU’s list price. If the onSale property for the SKU is true, it creates another price that points to the sales price list and set its list price as the SKU’s salePrice.

How to use the PriceListMigration component:

1. Run the price list SQL script against your catalog database. This script can be found at:

C:/ATG/ATG10.1.2/DCS/sql/db_components/dbvendor/priceLists_ddl.sql

2. Start the /atg/commerce/pricing/priceLists/PriceListMigration component.

3. Open the component editor for the PriceListMigration component. Invoke the runMigration method from the methods tab in the component editor.

Note:

The ATG Control Center allows users to create, edit, and delete price lists. When a user attempts to view or edit a price list, the security system checks the security information associated with the object and grants or denies access based on the information.

For example, if a user does not have write access to a particular item, then the ACC will display the item in gray characters. Additionally, certain objects might not be visible to certain users.

Based on these criteria's we need to follow on when doing PriceListMigration, so that security policies cannot be overridden.

How to Configure/Integrate Spring Framework with ATG

2015-02-28T12:48:00.004-08:00

Introduction:

Spring is a framework (open source). More important thing here is ATG accepts spring based application which can be integrate along with ATG modules. Spring framework providing the way to establish its mechanism to ATG with the help of nucleus based approach. Spring is based on JavaBeans as like as Nucleus.

Steps to start with:

1. Create a spring framework entry in web.xml which is available in our ATG projects,

<servlet>
   <servlet-name>spring</servlet-name>
   <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
   <load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
   <servlet-name>spring</servlet-name>
   <url-pattern>/spring/*</url-pattern>
</servlet-mapping>

a) DispatcherServlet act as controller and it is a bridge between ATG and Spring components

2. Make sure our pageFilter has a entry for spring under <filter-mapping>

<filter-mapping>
    <filter-name>PageFilter</filter-name>
    <url-pattern>/spring/*</url-pattern>
</filter-mapping>

a) DAF pipeline will take care of rest of the process.

3. We should use Two OOTB ATG Classes for this spring integration

a) NucleusResolverUtil:

It contains a single static resolveName method. which attempts to resolve the specified Nucleus path. Since Spring is unaware of Nucleus component scope.

It will check resolve name on current request, if it is fails then in next attempt it will resolve the name in the global Nucleus scope.

eg:
To make a Nucleus component available in Spring, you declare it in your Spring configuration XML file. For example, to resolve the current user profile as a Spring component:
<bean name="/Profile" class="atg.nucleus.spring.NucleusResolverUtil"
    factory-method="resolveName" singleton="false">
  <constructor-arg value="/atg/userprofiling/Profile"/>
</bean>
a) singleton="false" : Profile is a session based component. only global scope component will be specified as singleton="true", request and session component should be specified as  singleton="false"

b) NucleusPublisher:

The NucleusPublisher class publishing a Spring configuration to nucleus path.

<bean name="/NucleusPublisher" class="atg.nucleus.spring.NucleusPublisher"
    singleton="true">
  <property name="nucleusPath">
    <value>/atg/spring/MyspringBeanClass</value>
  </property>
</bean>

4. We have to add springtonucleus.jar

Path: <ATGDir>/DAF/spring/lib/springtonucleus.jar. 

a) NucleusPublisher requires access to the Spring classes, so the springtonucleus.jar must be added to the WEB-INF/lib

5. Now you can check your application

System Level Deployment Error : ATG BCC

2015-01-30T10:27:00.001-08:00

System Level Deployment Error:

Note: These error will occur because of data issues, try to deploy your project with valid assets, If not these kind of exception will occur,

1. Temporarily how to skip this issue on deployment: Goto DeploymentManager Component in ACC and make "ErrorLevel" to some number, Above screen shot I had issues with many asserts which causes 11 errors. To skip these errors i set "ErrorLevel" as 11,

2. Once you sets the "ErrorLevel" on DeploymentManager It will skip 11 errors in the deployment, and then it will resume the deployment as soon as possible,

3. This is not a good practice to follow up, but still you can use it if there is some critical scenario where your application requires that particular deployment to be happen

4. Always start your deployment with valid assets,

5. On the other side these issues will arise because of your publishing server not started properly also, Check the log before trying above steps.

BCC Snapshot ID is not Valid: ATG

2014-12-31T21:46:00.001-08:00

BCC Snapshot ID is not Valid

Solution:

1. This issue will arise when you try to force the invalid snapshot id, or deleted snapshot id, Try to delete all the deployment tables and start the server.

Note: Dont create snapshot id's manually on deployment tables, it wont work,

Bcc Transport UnInstantiated Issue : ATG

2014-12-31T21:39:00.004-08:00

BCC Transport UnInstantiated Issue:


Transport UnInstantiated Issue

Solution:

1. This issue will occurs when your agent server is down, also check the port configuration of the agent whether it is rightly configured or not.

2. Restart your Agent server will fix this issue,

BCC issues : ATG BCC

2014-11-30T23:02:00.003-08:00

1. fileMarker cause NullPointerException

**** Error    Thu Nov 27 19:53:23 IST 2014    1417098203972    /atg/deployment/DeploymentManager    item = fileMarker:mark600001 cause = java.lang.NullPointerException
**** Error    Thu Nov 27 19:53:23 IST 2014    1417098203972    /atg/deployment/DeploymentManager        at atg.epub.file.VersionFilePropertyDescriptor.verifyLatestFileVersion(VersionFilePropertyDescriptor.java:353)
**** Error    Thu Nov 27 19:53:23 IST 2014    1417098203972    /atg/deployment/DeploymentManager        at atg.epub.file.VersionFilePropertyDescriptor.getPropertyValue(VersionFilePropertyDescriptor.java:205)

Solution:

Delete all your epub datas and import it again, This issue will arise missing of some required data's, Check your epub tables and if you know the exact value you can directly put that into required tables if not then enable logDebug=true for your repository and DeploymentManager component and find out the table which causing this exception.

2. GSAInvalidatorService java.rmi.server.ExportException

**** Error    Thu Nov 27 20:28:06 IST 2014    1417100286825    /    Unable to create class atg.adapter.gsa.invalidator.GSAInvalidatorService for configuration /atg/dynamo/service/GSAInvalidatorService java.rmi.server.ExportException: Port already in use: 0; nested exception is:
**** Error    Thu Nov 27 20:28:06 IST 2014    1417100286825    /        java.net.BindException: Address already in use: JVM_Bind    java.rmi.server.ExportException: Port already in use: 0; nested exception is:
**** Error    Thu Nov 27 20:28:06 IST 2014    1417100286825    /        java.net.BindException: Address already in use: JVM_Bind
**** Error    Thu Nov 27 20:28:06 IST 2014    1417100286825    /        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)

Solution:

This issues will arise when your agent server is down. or it is not started properly, Check your agent server, Whether it is in disabled mode or not. if it is enable mode and also this issue arise, it is because of port issue. you should check the lockserver ports and then pointing to these into valid port which is not used before,

Difference between Dynamic vs Static Pricing : ATG

2014-10-31T15:06:00.002-07:00

Difference between Dynamic vs Static Product Pricing

Static pricing :

1. There is a property called listPrice in each item in catalog repository, Commerce Pricing services

are using this price as a base price for calculating the order prices, (Shipping, total, tax etc),

2. It is sku based pricing, it uses the pricelist components

3. We can use static pricing on where static prices are required. Not so many places where we can use

this. only few areas static prices are used nowa days

Dynamic Pricing :

1. These prices are normally coming from external services which reach the repository through

Programming API's, It will dynamically changing the prices on different conditions with the help

of programmatic approach,

2. It is also a sku based pricing, it uses the pricelist components and site configuration components,

3. Dynamic pricing can cause a significant decreases in performance compared to using static

pricing. Many sites do not need to show dynamic pricing on product pages; it may be sufficient to

show dynamic prices only when a customer places items in the shopping cart,

4. Example: suppose you send a specific group of customers a coupon for 20oRs off all blue items.

On the product pages of the site, blue items appear with their static list or sale price, which is the

same for all customers. However, when a customer with the “200Rs off” coupon adds a blue item

to his or her shopping cart, dynamic pricing takes effect, and the item price appears on the

Shopping Cart or Checkout page (for example) with a discount of 200Rs.

5. We can use dynamic pricing on certain product templates

6. Dynamic pricing will provides the high level of performance by using the pricing features

selectively.

Create Promotion Template and Add ClosenessQualifier : ATG

2014-09-30T12:19:00.002-07:00

Steps:

1. Create Screen-Segments with ,

<screen-segment display-name-resource="closenessQualifierTitle" ></screen-segment>,

2. Add display-once=true to screen-segments, because it should be mandatory for all the templates.

<screen-segment display-name-resource="closenessQualifierTitle"
display-once="true"></screen-segment>,

3. Have one or more line elements for Closeness Qualifier information.

<line>
      <label id="amountToSpend"
             display-name="Amount to spend:"/>
      <textInput id="textId${inc}" placeholder-name="myAmount"/>
   </line>

Finally it looks like:

<screen-segment display-name-resource="closenessQualifierTitle"
display-once="true">
   <line>
      <label id="amountToSpend"
             display-name="Amount to spend:"/>
      <textInput id="textId${inc}" placeholder-name="myAmount"/>
   </line>
</screen-segment>

3. Create a Promotion (Upsell) in ACC/BCC (eg: When spending limit crosses $2000, Then that customer is eligible for free shipping ).

4. Create item-properties section which will including PMDL Rule,

Note: There should be only one <item-properties> for each and every screen segment.

<item-properties>
<property name="closenessQualifiers">

<item-properties>
    <property name="pmdlRule">
      <![CDATA[
<pricing-model>
    <qualifier>
      <comparator name="greater-than-or-equals">
        <value>order.priceInfo.amount</value>
        <constant>
          <data-type>java.lang.Double</data-type>
          <string-value> ${myAmount} </string-value>
        </constant>
      </comparator>
    </qualifier>
</pricing-model>
]]>
</property>
</item-properties>
</property>
</item-properties

5. Comparator name "greater-than-or-equals" will give you a exact result when spending limit crosses $2000 it allowing the new promotions to be display in the application.

6. Note : When we are creating PMDL rule then we should have
<property name="closenessQualifiers"> under item-property tag.

7. Spend around $2000 and see the application, Now you could see the free shipping available on your application (Note: you must create shipping flags for displaying free shipping messages)

8. That's it.

Disabling the Gift List In ATG

2014-08-30T23:17:00.000-07:00

Steps:

Go to --> /atg/registry/ContentRepositories component and remove the value in the initialRepositories property that references the /atg/commerce/gifts/Giftlist component.

Go to --> /atg/commerce/gifts/GiftlistTools component and set the giftlistRepository property to null.

Go to --> userProfile.xml file and remove properties that reference items in the Giftlists repository. The userProfile.xml file is located in the Commerce configuration layer. Remove the following tables.
    1. dcs_user_wishlist
    2. dcs_user_giftlist
    3. dcs_user_otherlist

eg:

Remove below repository entries


<table name="dcs_user_wishlist" type="auxiliary"
id-column-name="user_id">
<property category="Commerce - Lists" name="wishlist"
            item-type="gift-list"
            repository="/atg/commerce/gifts/Giftlists"
            column-name="giftlist_id"cascade="insert,update,delete"
            display-name="Wish list"/>
</table>


<table name="dcs_user_giftlist" type="multi"
id-column-name="user_id" multi-column-name="sequence_num">
<property category="Commerce - Lists" name="giftlists"
            data-type="list" component-item-type="gift-list"
            repository="/atg/commerce/gifts/Giftlists"
            column-name="giftlist_id" display-name="Gift list"/>
</table>


<table name="dcs_user_otherlist" type="multi"
id-column-name="user_id" multi-column-name="sequence_num">
<property category="Commerce - Lists" name="otherGiftlists"
            data-type="list" component-item-type="gift-list"
            repository="/atg/commerce/gifts/Giftlists"
            column-name="giftlist_id"
            display-name="Other gift lists"/>
</table>

Go to --> updateGiftRepository and sendGiftPurchased processors from the commerce pipeline and Remove these processors . These processors are found in the processOrder pipeline chain. After these entries have been removed from the chain definition, create a link from the authorizePayment processor to the addOrderToRepository processor.

Thats it, Gift list has been disabled permanently in your application.

ATG - Endeca Integration Architecture Diagram

2014-08-30T22:47:00.001-07:00

Product Comparison Simple Analysis : ATG

2014-07-31T13:03:00.001-07:00

Product Comparison:

Product Comparison provides the ability to compare the products in the catalog.

A simple site may offer the user a single product comparison list and enable the user to add and remove products from the list, as well as compare the properties of the products in the list. A more complex site may offer the user multiple comparison lists to compare different types of items (for example, one list to compare funitures, a different list to compare mobiles, and so on).

Components Involved:

1. /atg/commerce/catalog/comparison/ProductList
2. /atg/commerce/catalog/comparison/ProductListContains.
3. /atg/commerce/catalog/comparison/ProductListHandler
4. /atg/commerce/catalog/comparison/ProductComparisonList

ProductList:

1. The items property of the ProductList component stores the list of Entry objects that represent each product in the product comparison list
2. Each Entry object in the ProductList combines category, product, SKU, and inventory information in a single object,
3. A unique ID that names the list entry. You can use this property to retrieve individual entries by calling

<dsp:valueof bean="ProductList.entries[id]"/>

ProductComparisonList:

1. It is a session scoped component located in nucleus,
2. To manage multiple comparison lists (for eg: list to compare mobiles, list to compare TV's) we can use ProductComparisonList,
3. ProductComparisonList provides some convenience methods like sortProperties and tableColumns that call through to the referenced TableInfo object,
4. ProductList.tableColumns is equivalent to the expression ProductList.tableInfo.tableColumns, you can use either of it.

Example:

   <dsp:param bean="ProductList.tableColumns" name="array"/>
   <dsp:param value="" name="sortProperties"/>

JSP Code Snippet for ProductComparisonList

<dsp:droplet name="ForEach">
<dsp:param bean="ProductComparisonList.items" name="array"/>
<dsp:oparam name="output">
    <p>Product Name:
      <dsp:valueof param="element.product.displayName"/><br>
       Category:
      <dsp:valueof param="element.category.displayName"/><br>
       Inventory: <dsp:valueof param="element.inventoryInfo.inventoryAvailabilityMsg"/><br>
</dsp:oparam>
</dsp:droplet>

ProductListContains:

1. It is a global scope component located in nucleus,
2. The very good advantage of using ProductListContains if you dont specify a categoryId for a given product, then ProductListContains checks the list of entry
whose category matches either the given products default category or if there is no category for the given product (null), we can blindly go with this component,

ProductListHandler:

1. It is a request scope component located in nucleus,
2. This component is used for setting the forms and submitting the forms,
3. This component will provide you the very flexible way of adding and removing the products to the comparison list.

Example:

<dsp:input bean="ProductListHandler.addProductList" value="Add to list" type="submit"/>

<dsp:input bean="ProductListHandler.removeEntries" value="Remove selected items" type="submit"/>

<dsp:input bean="ProductListHandler.clearList" value="Remove all" type="submit"/>

Note: Previously /atg/commerce/catalog/SearchFormHandler has been used for providing the search result for product comparison list.

Example : <dsp:param bean="SearchFormHandler.searchResults" name="array"/>,

Nowa days Oracle Endeca is providing some search component for more flexible way of providing the search results.

OOTB Promotions : ATG

2014-06-30T12:04:00.004-07:00

OOTB Promotions :

Specific amount off a particular product
Percentage amount off a whole order
Specific amount or percentage off a product based on an attribute
Free shipping for a specific product
Buy one, get one free
Free gift with purchase

Adding a new discount type involves the following tasks:

Extend or create a calculator that supports the discount type.
Modify the CalculatorInfo object to include the new discount type and calculator information.

The PMDL uses the CalculatorInfo to identify which calculator to use.

You can determine the promotion type by checking if its item descriptor is a subtype of the base item, shipping, and order discount item descriptors:

if (((GSAItemDescriptor) pricingModel.getItemDescriptor()).isSubTypeOf("Item Discount"))

List qualifyingItems = qualifierService.findQualifyingItems(...params..);

Creating a New Pricing Engine : ATG

2014-05-22T12:42:00.001-07:00

Creating a New Pricing Engine

If you want to create a new pricing engine that prices Sample costs separately from shipping. You create a SamplePricingEngine that acts independently of the ShippingPricingEngine.

Create an interface called SamplePricingEngine that extends PricingEngine.

Create an implementation called SamplePricingEngineImpl that extends PricingEngineService.

Create a SamplePricingInfo that extends the atg.commerce.pricing.AmountInfo price holding class.

Create a calculator called SamplePricingCalculator and implementations of it that calculate and discount Sample as your business requires.

Modify the Promotions repository definition file (by default, pricingModels.xml). Add an item-descriptor for the Sample discount type and sub-descriptors for the various implementations of the SamplePricingCalculator that you created.

Create properties files for the SamplePricingEngine and each of the calculators.

Your engine is ready for use. You may also want to add preCalculators that calculate the base cost of Sample.

Item Caches and Query Caches : ATG Repository

2014-04-20T11:41:00.003-07:00

Each item descriptor in a SQL repository has its own separate item cache and query cache. This lets you size and flush caches separately for separate item types. The item cache holds property values for repository items. It is indexed by the repository item IDs. The query cache holds the repository IDs of items that match particular queries in the cache.

For example, suppose you have a query like this:

color = red AND size = XXL

If query caching is enabled, the first time this query is issued, the result set is retrieved from the database and stored in the query cache. Then, the next time this same query is issued, the SQL repository can retrieve the result set from the cache, rather than needing to access the database.

The item caches hold the values of repository items. Repository queries are performed in two passes, using two separate SELECT statements. The first statement gathers the IDs of the repository items that match that query. The SQL repository then examines the result set from the first SELECT statement and finds any items that already exist in the item cache. A second SELECT statement retrieves from the database any items that are not in the item cache.

Query caching is turned off by default. If items in your repository are updated frequently, or if repeated queries are not common, you may not receive enough benefit from a query cache to justify the minor amount of overhead in maintaining the cache.

Invalidate the item caches for every item descriptor in a repository:

RepositoryImpl rep = getRepository();
String[] descriptorNames = getItemDescriptorNames();

// iterate over all the descriptors

for (int i=0; i<descriptorNames.length; i++) {
String name = descriptorNames[i];
ItemDescriptorImpl d = (ItemDescriptorImpl)rep.getItemDescriptor(name);
d.invalidateItemCache();
}

Cache Timeout:

if you set item-expire-timeout to 1000 milliseconds, the SQL repository will reload those properties after they have been in the cache for 1 second. If you set query-expire-timeout to 1000 milliseconds, the SQL repository re-executes the query after that entry has been in the query cache for 1 second.

To use the item-expire-timeout and query-expire-timeout attributes, set the value (in milliseconds) in the item-descriptor tag.

For example:

<item-descriptor name="order" cache-mode="simple"
item-expire-timeout="180000"
query-expire-timeout="180000">
...
</item-descriptor>

What is New in ATG10.2

2014-03-05T02:29:00.000-08:00

NEW FEATURES IN ATG 10.2

Site Administration

1. Profile realms provide multisite profile management support

REST Web Services

1. A new extensible REST architecture (the REST MVC Web Services API) is available in addition to the legacy REST API.

ATG Content Administration

1. An extensible asset purge function removes unneeded repository items.

2. Emergency workflows are now available for situations where an emergency project must be updated within minutes, bypassing standard deployment.

Oracle ATG Web Commerce

1. Cross-channel inventory visibility adds in-store pickup functionality, and enhances the current ATG Inventory system to accommodate multiple locations for any given SKU.

Oracle ATG Web Commerce Merchandising

• New roles and access rights help control the content that business users can access in the Business Control Center.

• Configurable filters can now restrict how promotions are applied to qualifiers and target items.

• In Oracle ATG Web Merchandising layout view, Promotions Visibility features analyze how promotions behave when preview users shop for items. You can also edit promotions directly from layout view.

• Promotions now support non-discountable items.

• The workbench pane that appears at the top of the Merchandising window bookmarks assets for organization and editing. (Previously, the workbench could be used only for Multi Edit operations.)

• New UI for working with internal, preview, and external users.

• New Store Location assets contain information about physical “brick and mortar” stores, such as addresses and hours.

• The existing rich text editor has been replaced with FCKeditor HTML editor. FCKeditor is installed automatically with the Oracle ATG Web Commerce applications that require it.

• In multisite environments, administrators can limit Merchandising users’ access to catalog assets and promotions based on their site affiliation.

• All personalization items can be configured to use site groups.

Oracle ATG Web Commerce Reference Store

• Updated code to improve checkout performance.

• Example of Oracle ATG Web Commerce returns functionality.

• Optional integration with Oracle RightNow Knowledge Cloud Service, which displays context-sensitive knowledgebase and support information.

• Integration with Oracle Endeca Commerce. All search facilities use Oracle Endeca Commerce and the Commerce Reference Store category pages and search results pages are Endeca-driven.

• A build environment allows you to quickly and easily rebuild the Commerce Reference Store modules using the Apache Ant build tool.

Commerce Reference Store iOS Universal Application

ATG Web Commerce 10.2 includes the first release of the Commerce Reference Store iOS Universal Application (CRS-IUA) that serves both iPhone and iPad.

Oracle ATG Web Commerce Business Intelligence

The following features are new to Oracle ATG Web Commerce Business Intelligence.

• Data aggregation to improve reporting performance in the Business Intelligence data warehouse.

• Usability improvements in Business Intelligence reports.

Oracle ATG Web Commerce Service Center

The following features are new to Oracle ATG Web Commerce Service Center.

• Optional integration with Oracle Endeca Commerce for catalog search.

• Commerce Service Center can be configured to use in-store pickup, which allows the customer to go to a store near them and pickup the merchandise. Returns with in-store pickup are also supported.

• Support for profile realms, which provide multisite profile management support.

• Optional integration with Oracle Live Help On Demand Click to Call.

Simple Way To Create Payment Group : ATG

2014-02-28T11:25:00.001-08:00

Creating a Payment Group

A PaymentGroup contain information about the payment method that will be used to purchase a group of commerce items.

1. By default, a new Order has one default PaymentGroup.

2. As items are added to the Order, these items automatically become part of the default PaymentGroup.

3. Once a second PaymentGroup is added to the Order, all the items in the Order are removed from the default PaymentGroup and must be explicitly added to one of the two payment groups.

4. Relationships must now be created to associate the items with payment groups.

5. Payment groups also contain a requisitionNumber property for orders that require approval before a means of payment can be specified.

6. Orders with requisition numbers are automatically assumed to require approval.

Follow these steps to create a new PaymentGroup and add it to an Order:

1. Call PaymentGroupManager.createPaymentGroup().

2. Make any changes to the PaymentGroup. For example, you could set the credit card number and expiration date.

3. Call PaymentGroupManager.addPaymentGroupToOrder(pOrder, pPaymentGroup) to add the payment group to the order.

Refer to the following example:

// Get a reference to the OrderManager
OrderManager orderManager = (OrderManager)
request.resolveName("/atg/commerce/order/OrderManager");

// Create the PaymentGroup
PaymentGroup paymentGroup = paymentGroupManager.createPaymentGroup();

// Add the PaymentGroup to the Order
paymentGroupManager.addPaymentGroupToOrder(pOrder, paymentGroup);

Tips For Creating Multiple Payment Groups

1. Multiple payment groups (which implement Multipayment) on a commerce site permit a customer to split the cost of an order by amount and/or items. For example, suppose a customer begins the checkout process on a site that supports multiple payment methods for a single order. The customer chooses to partition payment by putting the first $1000 of a $1250 order on a Visa credit card. The customer then chooses to pay for the remaining $250 using points earned on the site during previous visits.

The following assumptions were made regarding Multipayment:

1. Customers can divide payment for an order or individual items by item quantity, percentage, or amount.

2. Customers can pay for part of a purchase using one payment method and use another payment method for the rest of the purchases.

3. Gift certificates are implemented as payment methods.

Note: The base commerce classes have built-in support for multiple payment methods. Multipayment allows customers to pay for purchases using multiple payment methods. For example, a customer can choose to pay for an order using two or more credit cards and a gift certificate. While customers can select payment methods by item level, amount level, or any combination of the two, you can limit the ways in which an order’s costs can be split, if necessary. The product UI for this component is entirely JSP-based.

Simple Way To Create Shipping Group : ATG

2014-02-11T10:05:00.002-08:00

Creating Shipping Groups:

A ShippingGroup contains information on the shipping address and delivery method for a group of commerce items.

1. By default, a new Order has one default ShippingGroup.

2. As items are added to the Order, these items automatically become part of the default ShippingGroup.

3. Once a second ShippingGroup is added to the Order, all the items in the Order are removed from the default ShippingGroup and must be explicitly added to one of two shipping groups.

4. Relationships must now be created to associate the items with shipping groups.

Follow these steps to create a new ShippingGroup and add it to an Order:

1. Call ShippingGroupManager.createShippingGroup().

2. Make any changes to the ShippingGroup, such as setting the address.

3. Call ShippingGroupManager.addShippingGroupToOrder(pOrder, pShippingGroup) to add the ShippingGroup to the Order.

Refer to the following example:

// Get a reference to the OrderManager
OrderManager orderManager = (OrderManager)
request.resolveName("/atg/commerce/order/OrderManager");

// Create the ShippingGroup
ShippingGroup shippingGroup = shippingGroupManager.createShippingGroup();

// Add the ShippingGroup to the Order
shippingGroup.addShippingGroupToOrder(pOrder, shippingGroup);

When setting the shipping and billing addresses, normally you pass a RepositoryContactInfo object to setShippingAddress() or setBillingAddress(). If you want to use a ContactInfo object instead, but do not want to subclass RepositoryContactInfo (see defaultShippingGroupAddressType in the OrderTools section), you must modify some Nucleus components. List the properties of your address object in the savedProperties property of /atg/commerce/order/processor/SaveShippingGroupObjects and the loadProperties property of atg/commerce/order/processor/LoadShippingGroupObjects.

Tip For Multiple Shipping Groups

1. Multiple shipping groups (which implement Multishipment) on a commerce site permit a customer to ship parts of an order to different addresses using different methods of delivery.

2. For example, suppose a customer enters the checkout process on a site that supports multiple shipping methods for a single order. The customer chooses to have the items shipped to different locations. The site must provide a UI that allows the customer to enter an address, and then associate it with a shipper, such as UPS or US Postal.

3. After the customer selects a shipper, a ShippingGroup is created. The site must then provide a UI that allows the customer to associate items with that shipping group. If there is only one shipping group, then all the items to be shipped will go into that shipping group. If more than one shipping group is associated with the order, then the customer must decide which items go into each group.

----------------------------------------------------------------------------------------------------------------------------

Creating a Configurable Commerce Item : ATG

2014-01-16T09:37:00.000-08:00

Configurable commerce items are items with other items as optional components, and are described in the Using and Extending the Standard Catalog chapter of this manual.

Follow these steps to create a new ConfigurableCommerceItem and associate it with an Order:

Call CommerceItemManager.createCommerceItem() to create the base commerce item.

Call CommerceItemManager.addSubItemToConfigurableItem() or addAsSeparateSubItemToConfigurableItem() to add options to the base item.

The example below illustrates how to programmatically create a ConfigurableCommerceItem with subSKU items and then add it to an Order.

Example:

// Creating Configurable CommerceItem
ConfigurableCommerceItem configurableItem = (ConfigurableCommerceItem)
getCommerceItemManager().createCommerceItem("configurableCommerceItem",
"sku10001", null, "prod10001", null, 1, null, null, new ItemPriceInfo());

SubSkuCommerceItem subskuItem = (SubSkuCommerceItem)
getCommerceItemManager().createCommerceItem("subSkuCommerceItem",
"sku20001", null, "prod20001", null, 1, null, null, new ItemPriceInfo());
getCommerceItemManager().addSubItemToConfigurableItem(configurableItem,
subskuItem);

subskuItem = (SubSkuCommerceItem)
getCommerceItemManager().createCommerceItem("subSkuCommerceItem",
"sku20002", null, "prod20002", null, 1, null, null, new ItemPriceInfo());
getCommerceItemManager().addSubItemToConfigurableItem(configurableItem,
subskuItem);

//Adding Configurable CommerceItem to Order
getCommerceItemManager().addItemToOrder(order, configurableItem);

Creating a Standard Commerce Item : ATG

2014-01-16T09:25:00.004-08:00

Follow these steps to create a new CommerceItem and associate it with an Order:

1. Call CommerceItemManager.createCommerceItem().

2. Make any changes to the CommerceItem, such as setting the quantity.

3. Call CommerceItemManager.addItemToOrder(pOrder, pCommerceItem) to add the CommerceItem to the Order.

Refer to the below example:

// Get a reference to the OrderManager
OrderManager orderManager = (OrderManager)
request.resolveName("/atg/commerce/order/OrderManager");

// Create the CommerceItem
CommerceItem commerceItem =
commerceItemManager.createCommerceItem(pCatalogRefId);
commerceItem.setQuantity(3);

// Add the CommerceItem to the Order
commereceItemManager.addItemToOrder(pOrder, commerceItem);

Note: createCommerceItem() will work even if you pass it a nonexistent catalog reference ID. This allows you to use ATG Commerce as an ordering system with multiple catalogs, some of which may not have repositories. If you want to prevent this behavior, you must institute a check.

Auxiliary data is a construct that exists in a CommerceItem object. This structure allows arbitrary data to be stored with a CommerceItem.

This data could be the options for a CommerceItem such as size and color. It could also refer to the product reference in the catalog. An important concept is that any data that is inserted into the auxiliary data can be serialized at any time in a system that contains remote components.

When defining AuxiliaryData objects, the classes must be defined as serializable. As initially defined, the class includes ProductID, ProductRef, PropertyValue, and CatalogRef properties.

Session Management in ATG Applications : ATG

2013-12-23T10:59:00.002-08:00

Note: This is about session management in ATG applications running on third-party application servers

The J2EE specification defines that each web application has its own session object and any attributes added to the session are only accessible from within that web application. The application server is entirely responsible for managing session life cycles; it generates a unique session ID, creates the session, invalidates it, fails it over, etc. An “ATG session” refers to session-scoped components Also, keep in mind that Nucleus components have a tree structure, and can include multiple scopes, with each scope being rooted at a particular component. The root for session-scoped components is /atg/dynamo/servlet/sessiontracking/GenericSessionManager/sessionid/ where sessionid is generated by the application server.

Sharing Session Information Among ATG Applications

You can run multiple ATG applications in the form of WAR files within a single EAR. In this case, you should share session-scoped Nucleus components so that your application will always have access to the same instance of session scoped components. By default, J2EE servers hand out different session objects in each web application visited, even if all requests came from the same browser. Sharing sessions across ATG applications ensures that you can build a J2EE application consisting of multiple WAR files in a single EAR, and each WAR has access to the same session-scoped components. Note that you should never run more than a single ATG EAR per application server instance.

When multiple web applications exist in the ATG EAR file, one of them must be designated as the parent application. Being the parent means that that application’s session ID is used as the basis for creating the ATG session scope root.

By default, ATG makes the <ATG10.2dir>\DafEar\base\j2ee-components\atg_bootstrap.war file the parent web application. The parent context path is /dyn. No additional configuration is required to use this, but your web applications should define the atg.session.parentContextName and atg.dafear.bootstrapContextName parameters in their web.xml to point to the parent web-application as shown:

<context-param>
<param-name>atg.session.parentContextName</param-name>
<param-value>/dyn</param-value>
</context-param>
<context-param>
<param-name>atg.dafear.bootstrapContextName</param-name>
<param-value>/dyn</param-value>
<description>The name of the DAF bootstrap WAR context.</description>
</context-param>

The context path the context-param points to must be for a WAR file with the SessionNameContextServlet defined in its web.xml:

<servlet>
<servlet-name>SessionNameContextServlet</servlet-name>
<servlet-class>atg.nucleus.servlet.SessionNameContextServlet
</servlet-class>
</servlet>

Note that there can be only one parent web application specified per EAR file. Therefore, if you change the parent application, be sure to set the context-param to the same values in all web.xml files within your EAR file:

<context-param>
<param-name>atg.session.parentContextName</param-name>
<param-value>/portal</param-value>
</context-param>

Note: This information applies only to session-scoped Nucleus components, and does not affect HTTP sessions obtained using atg.servlet.ServletUtil.getDynamoRequest(request).getSession(), which retain a context particular to the current web application.

Managing User Sessions

You can manage user sessions from the Dynamo Component Browser for debugging or administrative purposes. To access the Session Manager, click through the hierarchy:

/atg/dynamo/servlet/sessiontracking/

Click GenericSessionManager to view sessions. Choose the selection criteria, then click the View button. Click an individual session to see its properties.