Wednesday, September 9, 2015

Business/IT features ATG/Endeca 11

1) Personalization enhancements:
  • Endeca experience manager can now refer user segments created in BCC.
  • Business users working with experience manager can now create page experiences that are specific to user segments             created with in BCC to give personalized experience to different customers. As new segments are created within the BCC, these segments are updated and available to business users in experience manager to use as trigger condition for specific experience (landing page, targeted content etc).
    Benefits:
  • Customers can take advantage of integrated segments management capabilities to simplify creation of targeted experiences.
  • Business users can work efficiently because segments are managed at one place but can be utilized in experience manager also.
2)  Experience Manager Preview enhancements:
  • Experience manager allows business users to make edits and preview changes without needing to mark their changes as live for production.
Benefits:
Business users can work more effectively by previewing inactive content items. This is major feature which is not available in previous version of experience manager.
3) Experience Manager content organization:
  • Endeca experience manager provides more flexible content organization.
  • Content can be managed in hierarchical folder structures that may be organized by brand or category. Permission can be assigned to any folder and folders can be restricted to specific content types.
Benefits:
  • Easy to understand Experience manager UI.
  • Business user teams have flexibility and control over how to organize and manage content to reflect their needs.
  • Folder structures and permissions allow teams to work on project together in a way that supports more decentralized work.
4)  Single signon:
  • Single signon functionality is added between ATG BCC and Endeca experience manager.
  • Endeca workbench is accessible from BCC homepage and BCC is accessible from Endeca workbench so business users can navigate between these 2 business applications.
Benefits:
Business users gets access of both tools by logging into one tool. Similarly logout from one tools logs out user from other tool also.
5) Environment management enhancements:
  • Improved import and export capabilities added in experience manager
Benefits.
  • This enables easier environment migration of experience manager data from one environment to other.
6) Automatic phrasing tool in Experience manager:
  • Endeca workbench includes automatic phrasing tool. Business users can manage multi word search terms that will then be treated as phrase in customer search queries. When site visitor enters search terms in query, the phrasing feature groups these individual terms as single search phrase and results are returned for phrase. Ex: “Red Dress”, “Summer Collection” can be entered in via tool and will be considered as phrase during customer search.
Benefits:
This feature generates specific targeted results for site visitor by eliminating unnecessary results also phrase search results in better conversions.
7) Relevance ranking evaluator:
  • Relevance ranking evaluator tool is included by default in workbench. Business users can run multiple search simultaneously, using different relevance ranking modules and other search parameters.
Benefits:
  • Business users can test different relevancy strategies without requiring extra steps for IT to install the tool.

Triggering Auto Indexing with BCC Project Deployment in Stage Site

Environment Type(ATG 11): This solution is applicable only if Staging/Production both sites are configured in BCC for project deployment. This is not applicable if your BCC workflow does not include Stage Site Target. This is applicable if ATG Stage and ATG production application connects to different Endeca applications.

Problem Statement: OOTB ATG integration with Endeca provides components to trigger Partial Index on Production site target with BCC project deployment but it does not provide components to start Index for project deployment to Stage site.
Solution: Below components can be configured in BCC/ATG Stage servers for triggering index with project deployment to Stage Site. This configuration assumes that indexing will not run on BCC server rather remote index will be triggered on ATG Stage Server.

BCC server components configuration:
1) /atg/commerce/search/ProductCatalogOutputConfig_staging.properties
repositoryItemGroup=/atg/commerce/search/IndexedItemsGroup_staging
repository^=/atg/commerce/search/IndexedItemsGroup_staging.repository
incrementalLoader=/atg/search/repository/IncrementalLoader_staging
targetName=Staging
2) /atg/search/SynchronizationInvoker_staging.properties
localSynchronizationInvoker=null
host=<remote server host>
port=<remote server port>
3) /atg/search/repository/ConfigAndRepositoryPersister_staging.properties
$class=atg.repository.search.indexing.ConfigAndRepositoryPersister
repository=/atg/search/repository/IncrementalItemQueueRepository_staging
transactionManager=/atg/dynamo/transaction/TransactionManager
configAndRepositorySearchStatement=configPath = ?0 AND contentId = ?1 AND repositoryPath = ?2
configAndContentIdSearchStatement=configPath = ?0 AND contentId = ?1
4) /atg/search/repository/ConfigStatePersister_staging.properties
$class=atg.repository.search.indexing.ConfigStatePersister
repository=/atg/search/repository/IncrementalItemQueueRepository_staging
clientLockManager=/atg/dynamo/service/ClientLockManager_staging
itemDescriptorName=searchConfig
sessionIdAddress^=/atg/dynamo/Configuration.drpHostAddr
sessionIdPort^=/atg/dynamo/Configuration.drpPort
alwaysAcquireWriteLock=false
transactionManager=/atg/dynamo/transaction/TransactionManager
5) /atg/search/repository/IncrementalItemQueueRepository_staging.properties
$class=atg.adapter.gsa.GSARepository
dataSource=/atg/dynamo/service/jdbc/DirectJTDataSource_staging
XMLToolsFactory=/atg/dynamo/service/xml/XMLToolsFactory
definitionFiles=/atg/search/repository/IncrementalItemQueue.xml,/atg/endeca/index/endecaIndexing.xml
transactionManager=/atg/dynamo/transaction/TransactionManager
idGenerator=/atg/dynamo/service/IdGenerator_staging
lockManager=/atg/search/service/SearchClientLockManager
eventServer=/atg/search/service/SearchSQLRepositoryEventServer
6) /atg/search/repository/IncrementalItemQueue_staging.properties
$class=atg.repository.search.indexing.IncrementalItemQueue
configAndRepositoryPersister=/atg/search/repository/ConfigAndRepositoryPersister_staging
configStatePersister=/atg/search/repository/ConfigStatePersister_staging
repository=/atg/search/repository/IncrementalItemQueueRepository_staging
transactionManager=/atg/dynamo/transaction/TransactionManager
invalidatorService=/atg/dynamo/service/GSAInvalidatorService
itemDescriptorName=item
7) /atg/search/repository/IncrementalLoader_staging.properties
$class=atg.endeca.index.RecordStoreIncrementalLoaderImpl
configStatePersister=/atg/search/repository/ConfigStatePersister_staging
incrementalItemQueue=/atg/search/repository/IncrementalItemQueue_staging
indexingPeriodicService=/atg/search/repository/IndexingPeriodicService_staging
8) /atg/search/repository/IndexingDeploymentListener.properties
indexingOutputConfigs+=/atg/commerce/search/ProductCatalogOutputConfig_staging
9) /atg/search/repository/IndexingPeriodicService_staging.properties
$class=atg.repository.search.indexing.IndexingPeriodicService
configStatePersister=/atg/search/repository/ConfigStatePersister_staging
incrementalLoader=/atg/search/repository/IncrementalLoader_staging
ATG Stage server components configurations:
1) /atg/commerce/endeca/index/CategoryTreeService.properties
indexingOutputConfig=/atg/commerce/search/ProductCatalogOutputConfig_staging
2) /atg/commerce/endeca/ProductCatalogSimpleIndexingAdmin.properties
$class=atg.endeca.index.admin.SimpleIndexingAdmin
phaseToPrioritiesAndTasks=\
PreIndexing=5:CategoryTreeService,\
RepositoryExport=10:\
SchemaExporter;\
CategoryToDimensionOutputConfig_staging;\
RepositoryTypeDimensionExporter;\
/atg/commerce/search/ProductCatalogOutputConfig_staging,\
EndecaIndexing=15:EndecaScriptService
3) /atg/commerce/endeca/RepositoryTypeDimensionExporter.properties
indexingOutputConfig=/atg/commerce/search/ProductCatalogOutputConfig_staging
4) /atg/commerce/endeca/SchemaExporter.properties
indexingOutputConfig=/atg/commerce/search/ProductCatalogOutputConfig_staging
5) /atg/endeca/ApplicationConfiguration.properties
workbenchPort=<Workbench Port>
workbenchHostName=<Workbench Host>
baseApplicationName=<STAGE APP Name>
keyToApplicationName= default=<STAGE APP Name>
6) /atg/endeca/assembler/AssemblerApplicationConfiguration.properties
defaultMdexPort=<STAGE APP MDEX PORT>
defaultMdexHostName=<STAGE APP MDEX HOST>