This chapter contains the following sections:
md5 (a cryptographic hash function that produces a 128-bit (16-byte) hash value) is used as the resource ID automatically. In this case, when visitors visit a page repeatedly, the same content is shown to them by Community-Gadgets. Therefore, it is recommended that the resource ID be equal to the page ID (if it is managed by a content management system), so the association is straightforward and intuitive.When the same comment feed needs to be shown on two separate pages, it is sufficient to specify the same resource ID. For example,
xyz can be used as the resource ID on both pages, so that the same content is rendered on these pages.
This section contains the following topics:
Configuration and monitoring of log files is an important aspect of product maintenance. This section describes log4j loggers that are available for troubleshooting/monitoring.
log4j-cos.properties file is the main configuration file for the logging in Community-Gadgets web application. The
log4j-shindig.properties file is the main configuration file for the logging in Shindig web application. These files are located in the
standalone_node folders (default locations are:
To enable all logging specific to Community-Gadgets, set the following loggers to debug level:
To monitor all the requests that Community-Gadgets sends to the WebCenter Sites data repository, enable the following logger:
log4j.logger.com.fatwire.cos.core.jpa.cmd.wem.WemCommandManager = TRACE
To monitor all the requests that Community-Gadgets sends to network and which network proxy is used, enable the following logger:
To monitor lifecycle management of CAS tickets that are used to connect to WebCenter Sites over REST, enable the following loggers:
log4j.logger.com.fatwire.cos.core.jpa.session.wem.WemSessionManager = TRACE
log4j.logger.com.fatwire.cos.core.sites.wem.WemManager = TRACE
To monitor inCache operations performed by Community-Gadgets, enable the following logger:
log4j.logger.com.fatwire.cos.core.cache.appcache.wem.WemAppCacheFacility = TRACE
To monitor inCache invalidations coming from WebCenter Sites, enable the following logger:
log4j.logger.com.fatwire.cos.core.cache.appcache.wem.IncacheServlet = TRACE
When troubleshooting data consistency issues and the synchronization functionality (locking) in the system, enable the following loggers:
log4j.logger.com.fatwire.cos.cluster.CacheLockClientFacility = TRACE
log4j.logger.com.fatwire.cos.cluster.ClusterLockImpl = TRACE
When deploying widgets that support search engine optimization (SEO), you need to download the
cos-widget-tag.jar file containing the widget deployment and rendering logic, and place it into the classpath of your web applications. Navigate to Comments, then Deploy, then Comments, and then select Custom settings and scroll down to the Widget Tag field. To download the JAR file, click the link in the Note section.
This is a lightweight JAR file, and it is created to function independently of any external logging libraries. However, to enable log messages provided by this library (
cos-widget-tag.jar), it is necessary to add the
-Dcos.widget.tag.debug=true Java parameter to JVM that runs the web application. This ensures that the log messages display in the standard output stream (console).
To optimize this library for performance, it is recommended that you add the following JVM parameters:
<Number> value must be aligned with the concurrency rates on the application server on which the pages with the SEO deployment tag were deployed, as well as with the number of processing threads available on the application server.
Before contacting the support team, compile the information required for investigation. This will help you avoid unnecessary communication round-trips and speed up the troubleshooting process.
The following is the recommended list of items to be provided to support for quick and efficient troubleshooting:
Operating system name and version
System language, locale, and time zone
JVM name and version
Application server name and version
Archive the contents of the product configuration directory and attach the archive to the support ticket. For example,
Management_Node1, configurations are saved in the
<install folder>/deploy/production and
<install folder>/deploy/management directories. Other required files are: the
setup_*.properties files from the
Log files of Community-Gadgets, its CAS and Shindig
Log files of the WebCenter Sites application and its CAS
Log files of Community-Gadgets and WebCenter Sites application servers (including the standard output and standard error consoles)