Your customer engagement transformation starts here · · 2014-09-25OpenDeploy (Receiver) ... run...
31
© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Your customer engagement transformation starts here
-
Upload
hoangduong -
Category
Documents
-
view
220 -
download
2
Transcript of Your customer engagement transformation starts here · · 2014-09-25OpenDeploy (Receiver) ... run...
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
Your customer engagement transformation starts here
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
Performance Tuning with HP LiveSite
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice3
Engage 2014
Agenda
bull HP LiveSite Overview
bull HP LiveSite Best Practices
bull Case Study BuyAToyotacom
bull QampA Session
This session provides general best practices for configuring a LiveSite environment
Please note that every implementation is unique and all of these best practices may
not apply to your specific environment
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite OverviewShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice5
Engage 2014
What is LiveSite
bull HP LiveSite enables the delivery of dynamic targeted and interactive content to site visitors to provide a personalized and engaging experience Together with HP TeamSite and HP OpenDeploy it provides an end to end Web Content Management (WCM) Solution
bull LiveSite includes LiveSite Display Services (LSDS) and LiveSite Content Services (LSCS) LSCS uses IDOL as itrsquos content repository
bull The typical configuration set-up of a WCM solution will include a Development server and a Runtime Server
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice6
Engage 2014
Web Experience Management Architecture
Production1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Content Editors amp Developers
Open Deploy
DB
LiveSite
DevelopmentUsers
LoadBalancer
Production Users
DB
LiveSite
1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
Development1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Each LS Instance has1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
LS 1
LS N
LSDev
TS
TSDev
LS 2
TSSearch
TSSearch
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice7
Engage 2014
Content Development Server
What is LiveSite
The development server includes the followings components
TeamSiteSitePublisher
TeamSite runs on JBOSS SitePublisher is installed as part of TeamSite In TeamSite users create Sites Each site is composed of templates and pages which are created with SitePublisher Pages and templates include components There are many OOTB components Most customers create their own custom components
OpenDeploy (Base Server)
OpenDeploy Base Server is used to copy files from the development server to the runtime environment server PLC work-flow deployments leverage OpenDeploy to submit content to Runtime
LiveSite Content Services (Authoring)
LSCS is a front end to IDOL which indexes content for optimized search LSCS gives the ability to fetch this content using Rest API queries Most customers use components with external code to fetch content and then display it on the page LSCS Authoring gives content developers the ability to test these components before they publish the pages to runtime
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice8
Engage 2014
Runtime Server
What is LiveSite
The runtime server includes the followings components
OpenDeploy (Receiver)
OpenDeploy Receiver is used to receive files on Runtime from OpenDeploy base that is installed on the Development Server
LiveSite Display Services
LiveSite Display Services provides a runtime environment to implement sites created on the development server It can run on several web application servers such as Tomcat WebSphere WebLogic and IIS (LSDS NET) The Default installation is on TomCat and is installed by the installer if it doesnrsquot exist
LiveSite Content Services (Runtime)
LiveSite Content Services (Runtime) connects the Website presentation layer (ASP JSP AJAX portal and so on) to a runtime view of the content and metadata developed in TeamSite This connection is done through REST API based calls By default LSCS also runs on TomCat but can be made to run on WebSphere or Weblogic
Java 2 Standard Edition Java Development Kit (J2SE JDK)
LiveSite requires the J2SE JDK to support rendering of page components at run time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
Performance Tuning with HP LiveSite
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice3
Engage 2014
Agenda
bull HP LiveSite Overview
bull HP LiveSite Best Practices
bull Case Study BuyAToyotacom
bull QampA Session
This session provides general best practices for configuring a LiveSite environment
Please note that every implementation is unique and all of these best practices may
not apply to your specific environment
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite OverviewShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice5
Engage 2014
What is LiveSite
bull HP LiveSite enables the delivery of dynamic targeted and interactive content to site visitors to provide a personalized and engaging experience Together with HP TeamSite and HP OpenDeploy it provides an end to end Web Content Management (WCM) Solution
bull LiveSite includes LiveSite Display Services (LSDS) and LiveSite Content Services (LSCS) LSCS uses IDOL as itrsquos content repository
bull The typical configuration set-up of a WCM solution will include a Development server and a Runtime Server
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice6
Engage 2014
Web Experience Management Architecture
Production1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Content Editors amp Developers
Open Deploy
DB
LiveSite
DevelopmentUsers
LoadBalancer
Production Users
DB
LiveSite
1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
Development1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Each LS Instance has1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
LS 1
LS N
LSDev
TS
TSDev
LS 2
TSSearch
TSSearch
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice7
Engage 2014
Content Development Server
What is LiveSite
The development server includes the followings components
TeamSiteSitePublisher
TeamSite runs on JBOSS SitePublisher is installed as part of TeamSite In TeamSite users create Sites Each site is composed of templates and pages which are created with SitePublisher Pages and templates include components There are many OOTB components Most customers create their own custom components
OpenDeploy (Base Server)
OpenDeploy Base Server is used to copy files from the development server to the runtime environment server PLC work-flow deployments leverage OpenDeploy to submit content to Runtime
LiveSite Content Services (Authoring)
LSCS is a front end to IDOL which indexes content for optimized search LSCS gives the ability to fetch this content using Rest API queries Most customers use components with external code to fetch content and then display it on the page LSCS Authoring gives content developers the ability to test these components before they publish the pages to runtime
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice8
Engage 2014
Runtime Server
What is LiveSite
The runtime server includes the followings components
OpenDeploy (Receiver)
OpenDeploy Receiver is used to receive files on Runtime from OpenDeploy base that is installed on the Development Server
LiveSite Display Services
LiveSite Display Services provides a runtime environment to implement sites created on the development server It can run on several web application servers such as Tomcat WebSphere WebLogic and IIS (LSDS NET) The Default installation is on TomCat and is installed by the installer if it doesnrsquot exist
LiveSite Content Services (Runtime)
LiveSite Content Services (Runtime) connects the Website presentation layer (ASP JSP AJAX portal and so on) to a runtime view of the content and metadata developed in TeamSite This connection is done through REST API based calls By default LSCS also runs on TomCat but can be made to run on WebSphere or Weblogic
Java 2 Standard Edition Java Development Kit (J2SE JDK)
LiveSite requires the J2SE JDK to support rendering of page components at run time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice3
Engage 2014
Agenda
bull HP LiveSite Overview
bull HP LiveSite Best Practices
bull Case Study BuyAToyotacom
bull QampA Session
This session provides general best practices for configuring a LiveSite environment
Please note that every implementation is unique and all of these best practices may
not apply to your specific environment
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite OverviewShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice5
Engage 2014
What is LiveSite
bull HP LiveSite enables the delivery of dynamic targeted and interactive content to site visitors to provide a personalized and engaging experience Together with HP TeamSite and HP OpenDeploy it provides an end to end Web Content Management (WCM) Solution
bull LiveSite includes LiveSite Display Services (LSDS) and LiveSite Content Services (LSCS) LSCS uses IDOL as itrsquos content repository
bull The typical configuration set-up of a WCM solution will include a Development server and a Runtime Server
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice6
Engage 2014
Web Experience Management Architecture
Production1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Content Editors amp Developers
Open Deploy
DB
LiveSite
DevelopmentUsers
LoadBalancer
Production Users
DB
LiveSite
1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
Development1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Each LS Instance has1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
LS 1
LS N
LSDev
TS
TSDev
LS 2
TSSearch
TSSearch
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice7
Engage 2014
Content Development Server
What is LiveSite
The development server includes the followings components
TeamSiteSitePublisher
TeamSite runs on JBOSS SitePublisher is installed as part of TeamSite In TeamSite users create Sites Each site is composed of templates and pages which are created with SitePublisher Pages and templates include components There are many OOTB components Most customers create their own custom components
OpenDeploy (Base Server)
OpenDeploy Base Server is used to copy files from the development server to the runtime environment server PLC work-flow deployments leverage OpenDeploy to submit content to Runtime
LiveSite Content Services (Authoring)
LSCS is a front end to IDOL which indexes content for optimized search LSCS gives the ability to fetch this content using Rest API queries Most customers use components with external code to fetch content and then display it on the page LSCS Authoring gives content developers the ability to test these components before they publish the pages to runtime
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice8
Engage 2014
Runtime Server
What is LiveSite
The runtime server includes the followings components
OpenDeploy (Receiver)
OpenDeploy Receiver is used to receive files on Runtime from OpenDeploy base that is installed on the Development Server
LiveSite Display Services
LiveSite Display Services provides a runtime environment to implement sites created on the development server It can run on several web application servers such as Tomcat WebSphere WebLogic and IIS (LSDS NET) The Default installation is on TomCat and is installed by the installer if it doesnrsquot exist
LiveSite Content Services (Runtime)
LiveSite Content Services (Runtime) connects the Website presentation layer (ASP JSP AJAX portal and so on) to a runtime view of the content and metadata developed in TeamSite This connection is done through REST API based calls By default LSCS also runs on TomCat but can be made to run on WebSphere or Weblogic
Java 2 Standard Edition Java Development Kit (J2SE JDK)
LiveSite requires the J2SE JDK to support rendering of page components at run time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite OverviewShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice5
Engage 2014
What is LiveSite
bull HP LiveSite enables the delivery of dynamic targeted and interactive content to site visitors to provide a personalized and engaging experience Together with HP TeamSite and HP OpenDeploy it provides an end to end Web Content Management (WCM) Solution
bull LiveSite includes LiveSite Display Services (LSDS) and LiveSite Content Services (LSCS) LSCS uses IDOL as itrsquos content repository
bull The typical configuration set-up of a WCM solution will include a Development server and a Runtime Server
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice6
Engage 2014
Web Experience Management Architecture
Production1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Content Editors amp Developers
Open Deploy
DB
LiveSite
DevelopmentUsers
LoadBalancer
Production Users
DB
LiveSite
1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
Development1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Each LS Instance has1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
LS 1
LS N
LSDev
TS
TSDev
LS 2
TSSearch
TSSearch
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice7
Engage 2014
Content Development Server
What is LiveSite
The development server includes the followings components
TeamSiteSitePublisher
TeamSite runs on JBOSS SitePublisher is installed as part of TeamSite In TeamSite users create Sites Each site is composed of templates and pages which are created with SitePublisher Pages and templates include components There are many OOTB components Most customers create their own custom components
OpenDeploy (Base Server)
OpenDeploy Base Server is used to copy files from the development server to the runtime environment server PLC work-flow deployments leverage OpenDeploy to submit content to Runtime
LiveSite Content Services (Authoring)
LSCS is a front end to IDOL which indexes content for optimized search LSCS gives the ability to fetch this content using Rest API queries Most customers use components with external code to fetch content and then display it on the page LSCS Authoring gives content developers the ability to test these components before they publish the pages to runtime
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice8
Engage 2014
Runtime Server
What is LiveSite
The runtime server includes the followings components
OpenDeploy (Receiver)
OpenDeploy Receiver is used to receive files on Runtime from OpenDeploy base that is installed on the Development Server
LiveSite Display Services
LiveSite Display Services provides a runtime environment to implement sites created on the development server It can run on several web application servers such as Tomcat WebSphere WebLogic and IIS (LSDS NET) The Default installation is on TomCat and is installed by the installer if it doesnrsquot exist
LiveSite Content Services (Runtime)
LiveSite Content Services (Runtime) connects the Website presentation layer (ASP JSP AJAX portal and so on) to a runtime view of the content and metadata developed in TeamSite This connection is done through REST API based calls By default LSCS also runs on TomCat but can be made to run on WebSphere or Weblogic
Java 2 Standard Edition Java Development Kit (J2SE JDK)
LiveSite requires the J2SE JDK to support rendering of page components at run time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice5
Engage 2014
What is LiveSite
bull HP LiveSite enables the delivery of dynamic targeted and interactive content to site visitors to provide a personalized and engaging experience Together with HP TeamSite and HP OpenDeploy it provides an end to end Web Content Management (WCM) Solution
bull LiveSite includes LiveSite Display Services (LSDS) and LiveSite Content Services (LSCS) LSCS uses IDOL as itrsquos content repository
bull The typical configuration set-up of a WCM solution will include a Development server and a Runtime Server
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice6
Engage 2014
Web Experience Management Architecture
Production1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Content Editors amp Developers
Open Deploy
DB
LiveSite
DevelopmentUsers
LoadBalancer
Production Users
DB
LiveSite
1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
Development1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Each LS Instance has1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
LS 1
LS N
LSDev
TS
TSDev
LS 2
TSSearch
TSSearch
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice7
Engage 2014
Content Development Server
What is LiveSite
The development server includes the followings components
TeamSiteSitePublisher
TeamSite runs on JBOSS SitePublisher is installed as part of TeamSite In TeamSite users create Sites Each site is composed of templates and pages which are created with SitePublisher Pages and templates include components There are many OOTB components Most customers create their own custom components
OpenDeploy (Base Server)
OpenDeploy Base Server is used to copy files from the development server to the runtime environment server PLC work-flow deployments leverage OpenDeploy to submit content to Runtime
LiveSite Content Services (Authoring)
LSCS is a front end to IDOL which indexes content for optimized search LSCS gives the ability to fetch this content using Rest API queries Most customers use components with external code to fetch content and then display it on the page LSCS Authoring gives content developers the ability to test these components before they publish the pages to runtime
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice8
Engage 2014
Runtime Server
What is LiveSite
The runtime server includes the followings components
OpenDeploy (Receiver)
OpenDeploy Receiver is used to receive files on Runtime from OpenDeploy base that is installed on the Development Server
LiveSite Display Services
LiveSite Display Services provides a runtime environment to implement sites created on the development server It can run on several web application servers such as Tomcat WebSphere WebLogic and IIS (LSDS NET) The Default installation is on TomCat and is installed by the installer if it doesnrsquot exist
LiveSite Content Services (Runtime)
LiveSite Content Services (Runtime) connects the Website presentation layer (ASP JSP AJAX portal and so on) to a runtime view of the content and metadata developed in TeamSite This connection is done through REST API based calls By default LSCS also runs on TomCat but can be made to run on WebSphere or Weblogic
Java 2 Standard Edition Java Development Kit (J2SE JDK)
LiveSite requires the J2SE JDK to support rendering of page components at run time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice6
Engage 2014
Web Experience Management Architecture
Production1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Content Editors amp Developers
Open Deploy
DB
LiveSite
DevelopmentUsers
LoadBalancer
Production Users
DB
LiveSite
1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
Development1 TeamSite2 Open Deploy Base3 TeamSite Search4 Database
Each LS Instance has1 LSDS
2 LSCS 3 Open Deploy Receiver4 Database
LS 1
LS N
LSDev
TS
TSDev
LS 2
TSSearch
TSSearch
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice7
Engage 2014
Content Development Server
What is LiveSite
The development server includes the followings components
TeamSiteSitePublisher
TeamSite runs on JBOSS SitePublisher is installed as part of TeamSite In TeamSite users create Sites Each site is composed of templates and pages which are created with SitePublisher Pages and templates include components There are many OOTB components Most customers create their own custom components
OpenDeploy (Base Server)
OpenDeploy Base Server is used to copy files from the development server to the runtime environment server PLC work-flow deployments leverage OpenDeploy to submit content to Runtime
LiveSite Content Services (Authoring)
LSCS is a front end to IDOL which indexes content for optimized search LSCS gives the ability to fetch this content using Rest API queries Most customers use components with external code to fetch content and then display it on the page LSCS Authoring gives content developers the ability to test these components before they publish the pages to runtime
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice8
Engage 2014
Runtime Server
What is LiveSite
The runtime server includes the followings components
OpenDeploy (Receiver)
OpenDeploy Receiver is used to receive files on Runtime from OpenDeploy base that is installed on the Development Server
LiveSite Display Services
LiveSite Display Services provides a runtime environment to implement sites created on the development server It can run on several web application servers such as Tomcat WebSphere WebLogic and IIS (LSDS NET) The Default installation is on TomCat and is installed by the installer if it doesnrsquot exist
LiveSite Content Services (Runtime)
LiveSite Content Services (Runtime) connects the Website presentation layer (ASP JSP AJAX portal and so on) to a runtime view of the content and metadata developed in TeamSite This connection is done through REST API based calls By default LSCS also runs on TomCat but can be made to run on WebSphere or Weblogic
Java 2 Standard Edition Java Development Kit (J2SE JDK)
LiveSite requires the J2SE JDK to support rendering of page components at run time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice7
Engage 2014
Content Development Server
What is LiveSite
The development server includes the followings components
TeamSiteSitePublisher
TeamSite runs on JBOSS SitePublisher is installed as part of TeamSite In TeamSite users create Sites Each site is composed of templates and pages which are created with SitePublisher Pages and templates include components There are many OOTB components Most customers create their own custom components
OpenDeploy (Base Server)
OpenDeploy Base Server is used to copy files from the development server to the runtime environment server PLC work-flow deployments leverage OpenDeploy to submit content to Runtime
LiveSite Content Services (Authoring)
LSCS is a front end to IDOL which indexes content for optimized search LSCS gives the ability to fetch this content using Rest API queries Most customers use components with external code to fetch content and then display it on the page LSCS Authoring gives content developers the ability to test these components before they publish the pages to runtime
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice8
Engage 2014
Runtime Server
What is LiveSite
The runtime server includes the followings components
OpenDeploy (Receiver)
OpenDeploy Receiver is used to receive files on Runtime from OpenDeploy base that is installed on the Development Server
LiveSite Display Services
LiveSite Display Services provides a runtime environment to implement sites created on the development server It can run on several web application servers such as Tomcat WebSphere WebLogic and IIS (LSDS NET) The Default installation is on TomCat and is installed by the installer if it doesnrsquot exist
LiveSite Content Services (Runtime)
LiveSite Content Services (Runtime) connects the Website presentation layer (ASP JSP AJAX portal and so on) to a runtime view of the content and metadata developed in TeamSite This connection is done through REST API based calls By default LSCS also runs on TomCat but can be made to run on WebSphere or Weblogic
Java 2 Standard Edition Java Development Kit (J2SE JDK)
LiveSite requires the J2SE JDK to support rendering of page components at run time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice8
Engage 2014
Runtime Server
What is LiveSite
The runtime server includes the followings components
OpenDeploy (Receiver)
OpenDeploy Receiver is used to receive files on Runtime from OpenDeploy base that is installed on the Development Server
LiveSite Display Services
LiveSite Display Services provides a runtime environment to implement sites created on the development server It can run on several web application servers such as Tomcat WebSphere WebLogic and IIS (LSDS NET) The Default installation is on TomCat and is installed by the installer if it doesnrsquot exist
LiveSite Content Services (Runtime)
LiveSite Content Services (Runtime) connects the Website presentation layer (ASP JSP AJAX portal and so on) to a runtime view of the content and metadata developed in TeamSite This connection is done through REST API based calls By default LSCS also runs on TomCat but can be made to run on WebSphere or Weblogic
Java 2 Standard Edition Java Development Kit (J2SE JDK)
LiveSite requires the J2SE JDK to support rendering of page components at run time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
HP LiveSite Best PracticesShabih Syed
Product Manager HP TeamSite
Hewlett-Packard
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice10
Engage 2014
Performance Inflection Points
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice11
Engage 2014
LSDS performance component and page caching
Component Cache Time setting control how often a component refreshes its content and communicates with the server to refresh its data
Choose appropriate settings
bull Until published
bull Never
bull Time interval
Frequently looked up pages are cached automatically
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice12
Engage 2014
LSDS performance LSDS uses JCS cache
bull JCS is a distributed caching system written in java
bull The cache should not require tuning but if for some unforeseen reason it does the WEB-INFclassescacheccf file is used to tune the cache
bull Following definitions is used by all component caches jcsregioncomponentcacheattributesMaxObjects=40
bull Following definitions is used by all page cachesjcsregionpagecacheattributesMaxObjects=128
bull cache-resource-configxml is used for configuring the pool size By Default 13 component pools and 3 page pool
bull Components and pages that are not in memory will be spooled off to the disk cache MaxKeySizeof the disk region specifies how many components per cache are written to disk
bull Accessing JCShttpltlsds-server-hostnamegtltlsds-portgtiwadminJCSjsp
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice13
Engage 2014
LSDS Performance MinMax Heap
bull Max Heap setting directly relates to how much page and component cache will be stored in the heap and how much overflows to disk
bull [Tomcat] Increase the heap size in InterwovenLiveSiteDisplayServicesruntimerunsh
The default values are set to
SET CATALINA_OPTS=CATALINA_OPTS -Xms128m
SET CATALINA_OPTS=CATALINA_OPTS -Xmx768m
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice14
Engage 2014
LSDS Troubleshooting
Log4jxml located underInterwovenLiveSiteDisplayServicesruntimewebWEB-INFclasses
For database issues see sectionlt-- spring and hibernate extension loaders ndashgt
For component externals addltcategory name=cominterwovenlivesiteexternalruntimegtltpriority value=DEBUG gtltcategorygt
Output goes to livesiteruntimelog or console log
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice15
Engage 2014
Types of LSCS Queries
Following query to return all documentshttpxxxx1876lscsv1document$q=ampproject=kli-72 spinterwovencomdefaultmaineSupportContent
You will see that for each document there are METADATA values returned Notice that for each document these are the same as what were in the lscsidxfile only that the format is different
ltfield name=TeamSiteMetadataOSgtP013-18ltfieldgt
ltfield name=TeamSiteMetadatadisplayHiddenfgtyltfieldgt
ltfield name=TeamSiteMetadataPublicationgtNAltfieldgt
ltfield name=G11NLocalegtenltfieldgt
ltfield name=TeamSiteMetadataPartsCategorygtP013-12-ltfieldgt
ltfield name=TeamSiteMetadataTitlegtFlash BIOS update (Flash from operating system version)ltfieldgt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice16
Engage 2014
Types of LSCS Queries
What if you want all documents that had TeamSiteMetadataOS value set to P013-18
This can be done as follows
httpxxxx1876lscsv1document$q=TeamSiteMetadataOSP013-18ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
What if you want all documents that had G11NLocale value set to enhttpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice17
Engage 2014
What impacts query response time
Number of factors related to
bull Configuration
bull Query structure
bull Routine maintenance
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice18
Engage 2014
bull In IDOL configuration file (IWLSCSContentcfg) the Number of threads should be set to of cpu cores +2
bull To configure LSDS to LSCS connections reference contentproperties file located under InterwovenLiveSiteDisplayServicesruntimewebWEB-INFconflivesite_customer
bull To configure LSCS to IDOL connections reference searchproperties file located underInterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
httpmaxconnectionshost= ltTotal number of connections for the same query at a timegt
httpmaxconnectionstotal=ltTotal number of connections at a timegt
Configuration Tuning
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice19
Engage 2014
Configuration IDOL configuration
Sometimes there are some attribute names that occurs commonly in queries
For example if you repeatedly do queries that look up documents with en locale
httpxxxx1876lscsv1document$q=G11NLocaleenampproject=kli-72-spinterwovencomdefaultmaineSupport Content
httpxxxx1876lscsv1document$q=G11NLocaleen AND TeamSiteMetadataPartsCategoryP013-12-ampproject=kli-72-spinterwovencomdefaultmaineSupport Content
Then you have an option to tell IDOL to pre-index this content so that look-ups are faster
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice20
Engage 2014
Configuration Config [SetMatchFields]
Specify fields whose entire value is frequently used as a restriction in a search and are thus stored for optimized matching Such fields cannot be numeric or parametric
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetMatchFields] section
bull For example if you are frequently running queries on TeamSiteMetadataProducts attribute then you can add the ltLSCS_HOMEgtidolIWLSCSContentcfg as follows
bull [SetMatchFields]Property=MatchFieldsPropertyFieldCSVs=LSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS_Products
Notice the format difference You can find the corresponding format to put into IDOL by opening the lscsidx file
A real customer exampleProperty=MatchFieldsPropertyFieldCSVs=parentDiridpathprojectNameARCHIVEDisDeletedLSCS_STR_TeamSite__HSALS__Templating__HSALS__DCR__HSALS__TypeLSCS_ST
R_TeamSite__HSALS__Metadata__HSALS__AliasIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__LegacyDocIDLSCS_STR_TeamSite__HSALS__Metadata__HSALS__AudienceLSCS_STR_TeamSite__HSALS__Metadata__HSALS__WebableLSCS_STR_TeamSite__HSALS__Metadata__HSALS__isFAQLSCS_STR_G11N__HSALS__LocaleLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__IDLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProductsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__ProjectsLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__OSLSCS_STR_MVF_TeamSite__HSALS__Metadata__HSALS__PageInfoLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__ReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsReleaseDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__NewsExpireDateLSCS_DT_TeamSite_HSALS__Metadata__HSALS__PartsCategorydocStatus
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice21
Engage 2014
Configuration IDOL Config [SetNumericFields]
Specify which fields are entirely numeric (or a csv of numbers) to be stored for optimized numeric matching
bull In the IDOL configuration file located in ltLSCS_HOMEgtidolIWLSCSContentcfg add ltindexed attribute namegt to the PropertyFieldCSVs property under [SetNumericFields] section
Customer example
bull Property=NumericFieldsPropertyFieldCSVs=contextDeployedDatefileSizeLSCS_NUM_
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice22
Engage 2014
Configuration regeneratematchindex=true
For SetNumericFields and SetMatchFields to take effect add
bull regeneratematchindex=true to the [server] section in IWLSCSContentcfg and then restart IDOL
bull Once you restart IDOL you need to remove this setting or set it to false You do not want to regenerate every time
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice23
Engage 2014
Configuration [SetMatchFields] structure
bull The indexed attribute name is of the form LSCS_lttypegt_[FCT_][MVF_]ltparsed_original_attribute_namegt
bull To generate the parsed original attribute name the characters [ ] ltspacegt amp the original attribute name are respectively replaced by __HSALS__ __TKRBSB__ __TKRBSE__ __ECAPS__ __TNCREP__
bull __HSAH__ __DNASA__
bull The presence of the FCT_ indicates faceted attribute and MVF_ indicates a multi-valued attribute
bull The lttypegt could be TXT STR DT NUM or BIN
bull The type facet and MVF status are configured in the lscs-authoringxml file
bull For example an attribute named foo that is of type string and multi-valued has an indexed attribute
bull name of LSCS_STR_MVF_foo
bull Similarly an attribute named TeamSiteMetadataCountry that is of the type text and faceted has an indexed attribute name of LSCS_TXT_FCT_TeamSite__HSALS__Metadata__HSALS__Country
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice24
Engage 2014
Improve IDOL PerformanceQuery StructureWhere possible use ldquo=rdquo instead of ldquordquo
bull For example If you have a query that searches on tag Products
document$q=TeamSiteMetadataProductsP014
then changing that to
bull document$q=TeamSiteMetadataProducts=P014z
will decrease the response time significantly because = will do an exact match instead of a substring match
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice25
Engage 2014
Improve IDOL Performance reduce memory foot print
bull By default there is no limit on how many indices are stored It will use the maximum heap and then overflow to disk
bull Numeric indices are stored in heap memory To reduce heap size you can cap memory usage for numeric indices This can improve performance if customers complain that their heap is being 100 used or they experience high IDOL CPU because it has to do a lot of disk swap after heap is all consumed
bull Example Add NumericNormalMaxMem=102400
bull [NumericFields]NumericType=TRUENumericNormalMaxMem=102400
bull [NumericDateFields]NumericDateType=TRUENumericNormalMaxMem=102400
bull If concerned about index size on disk one possibility is to remove remove fullTextContentunder [SetIndexFields]
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice26
Engage 2014
Routine Maintenance for IDOL
How to run DRECOMPACTDRECOMPACT is a memorycpu consuming process so it is strongly recommended to run this during off business hours so that it doesnt impact your production environment DRECOMPACT can be issued in the browser using the following URL httplocalhostltindex-portgtltDRECOMPACT
You can check the value of the Index Port in IWLSCSContentcfg When you run this command you will get a INDEXID in the browser You can check the status of this by doing the following
Create an output directory in the IDOL folder then executehttplocalhostltlscs-portgtlscsv1util-commandidolptaction=indexergetstatusampoutput=fileampfilename=outputmyfilexmlFind the job for your indexid and check its status periodically to make sure it finished
What to expectAfter DRECOMPACT finishes run the getStatus command againhttplocalhostltlscs-portgtlscsv1util-commandidolptaction=GetStatus
You will notice the committed documents and document sections are now the same Also you may notice that the size of the IDOLnodetable directory has now shrunk from before
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice27
Engage 2014
Troubleshooting
bull Add profilingOn=true in webappslscsWEB-INFclasseslscs-confproperties file
bull Configure the methods you want to profile in webappslscsWEB-INFcontextdiagnostic-contextxml
bull Uncomment the following lines in the xmlltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoSearchDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoAssetDao()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrrequesthandlerRequestHandlerhandle()) gt
ltaoparound method=timingAdvice pointcut=execution( cominterwovenwcmiwrrdaoidolIdolACIexecute()) gt
bull Restart lscs once these changes are made
bull Append query parameter profile=yes to HTTP the request and observe the profiling result from the browserhttpltlscs-servergt1876lscsv1document$q=ampprofile=yes
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice28
Engage 2014
Troubleshooting LSCS profiling result
- ltprofilegt
ltmethod name=AssetDaogetDocumentByAssetIdAndContext() value=092ms gt
ltmethod name=AssetDaogetAllEaInfoAsMap() value=1161ms gt
ltmethod name=AssetDaogetLatestContext() value=173ms gt
ltmethod name=ControllerhandleRequest() value=6037ms gt
ltmethod name=RequestHandlerhandleGet() value=5788ms gt
ltmethod name=SearchDaodocumentSearch() value=3158ms gt
ltmethod name=AssetDaogetDefaultProject() value=018ms gt
lturigtdocument$q=ampprofile=yeslturigt
ltprofilegt
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice29
Engage 2014
Troubleshooting verifying LSCS is running
Try to access URL
httpltlscs-servergt1876lscsadmindebugpanelindexhtml
Go under Admin -gt Status
In 721 and above the following three should report UP status and not SUSPENDED
If schemaLocation is suspended check your LSCS license If Search Server Repository is suspended check to make sure IDOL is up If Database Repository is suspended then make sure Database is accessible
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2014 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice30
Engage 2014
Troubleshooting LSCS and IDOL debugging
LSCS Debug log4jproperties located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses
log4jcategorycominterwoven=DEBUG
log4jcategorycomautonomyaci=DEBUG
log4jcategorycomautonomynonaci=DEBUG
IDOL Debug In IWLSCSContentcf g located under InterwovenLiveSiteCSRTruntimewebappslscsWEB-INFclasses change LogLevel=full from LogLevel=normal under the [Logging] section
What to collect
a Zipped copy of InterwovenLiveSiteCSRTlog folder
b Zipped copy of InterwovenLiveSiteCSRTidollogs
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
THANK YOU
copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice
![Design and Evaluation of [vSoC]: Virtualised Security ... · AWS Cloudtrail . Amazon S3. Azure. Application Serv Weblogic. WebSphere. Tomcat. Data Integration • Increasing move](https://static.fdocuments.us/doc/165x107/5f6f13203ac09c368e06eec4/design-and-evaluation-of-vsoc-virtualised-security-aws-cloudtrail-amazon.jpg)
