This chapter describes the configuration files that are updated by the silent installer when it installs Analytics. This chapter also provides guidelines for setting properties in the configuration files. The files are:
When installing Analytics, the silent installer sets the values of various properties to match the values that you specified in analytics-build.properties
. The properties are stored in the following files:
Once Analytics is installed, you can tune various properties directly in their respective files, as necessary. Guidelines are available in the rest of this chapter.
Caution:
Installation directories (and related configurations) created by the silent installer must not be moved, renamed, or otherwise modified in any way.The Analytics silent installer modifies the global.xml
file on each server where the file is stored and where the installer is executed. Once Analytics is installed, you can customize global.xml
directly on its respective hosts.The customizable sections are:
LFS Logwriter Implementation Parameters
Note:
Properties that must not be reset are shaded in the tables below. Each application has its ownglobal.xml
file, located in the application's classpath.This section contains properties that define Analytics installation directories, system administrators' contact information, the handling of raw data, and data processing conditions.
Caution:
In Table 28-1, some parameters have an asterisk (*) suffixed to indicate that these parameters MUST NOT be reset.Table 28-1 Analytics parameters in global.x
ml
Typically, users require only one database connection. Custom reporting may require multiple connections. If you need to define your own JDBC resources or reference the existing JDBC connections via JNDI, use the following tag:
<connection name="<connection_name>" default="true" type="<jdbc_or_resource>" classname="<database_driver_classname>" url="<database_url>" user="<database user name>" password="<database password>" />
Table 28-2 describes database connection parameters.
Table 28-2 Database Connection Parameters
Parameter | Description |
---|---|
|
Name of the connection. Example: |
|
There must be exactly one connection marked with |
|
Type of connection: |
|
JNDI attribute; JNDI name Note: Used only if |
|
JDBC driver class. Example: |
|
JDBC URL |
|
JDBC attribute; database user name |
|
JDBC attribute; database password |
<connection name="jdbcsample" default="true" type="jdbc" classname="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@dbserver:1521:sid" user="analytics" password="analytics" />
The LFS logwriter implementation writes incoming raw data to the local file system. If you wish to change the root path (the location to which raw data will be written), use the following tag:
<logwriters> <logwriter type="LFS" name="LFS" rootpath="C:/analytics/ sensorlocal" /> </logwriters>
Caution:
In Table 28-3, some parameters have asterisk (*) suffixed to indicate that these parameters MUST NOT be reset.Table 28-3 Logwriter Parameters
Parameter | Description |
---|---|
type* |
Type of logwriter. Legal value: LFS |
name* |
Alias name of the logwriter. Legal value: LFS |
rootpath |
Location, on the local file system, to which raw data will be written. Examples: UNIX: rootpath="/analytics/sensor" Windows: rootpath="c:/analytics/sensor" |
The silent installer modifies the log4j.properties
file on each server where the file is stored and the installer is executed. Once the Analytics installation is complete, you can customize properties directly in all or selected log4j.properties files, as shown in Table 28-4. (The log4j.properties
file is located in <HADOOP_HOME>/conf
.)
Table 28-4 Parameters in log4j.properties
Property | Description | Example / Format |
---|---|---|
log4j.rootLogger |
Specify the log level and the appender of the root logger. Multiple appenders can be specified, separated by commas. |
log4j.rootLogger=INFO, DaRoFiAppender - or - log4j.rootLogger=INFO, DaRoFiAppender, ConsoleAppender |
log4j.category. com.fatwire. analytics |
Specify the log level. The following explains the log levels in decreasing order of severity:
Note: In production mode, this property should be set to |
INFO |
log4j.appender. DaRoFiAppender |
Specify the appenders to be used for logging. |
org.apache.log4j. DailyRollingFileAppender |
log4j.appender. DaRoFiAppender. datePattern |
Specify the date pattern in the following format: |
'.'yyyy-MM-dd |
log4j.appender. DaRoFiAppender.file |
Specify the location of the log file, along with the name of the log file. |
../logs/xxx.log |
log4j.appender. DaRoFiAppender.layout |
Specify the layout. |
org.apache.log4j.PatternLayout |
log4j.appender. DaRoFiAppender.layout. ConversionPattern |
Specify the layout pattern. |
%d{ISO8601}%- 5p[%t]%c:%m%n |
Edit log4j.properties
file by adding the following parameters:
hadoop.root.logger=WARN,console, DRFA hadoop.log.file=hadoop.log log4j.rootLogger=${hadoop.root.logger}, DRFA, EventCounter # # Daily Rolling File Appender # log4j.appender.DRFA=org.apache.log4j.DailyRollingFileAppender log4j.appender.DRFA.File=${hadoop.log.dir}/${hadoop.log.file} # Rollver at midnight log4j.appender.DRFA.DatePattern=.yyyy-MM-dd # 30-day backup log4j.appender.DRFA.MaxBackupIndex=30 log4j.appender.DRFA.layout=org.apache.log4j.PatternLayout # Pattern format: Date LogLevel LoggerName LogMessage log4j.appender.DRFA.layout.ConversionPattern=%d{ISO8601} %p %c: %m%n
The silent installer modifies the futuretense_xcel.ini
file of the WebCenter Sites application that resides on the machine where the silent installer is running. The purpose of modifying the file is to specify the location of the Analytics application and the authorized user.
Caution:
In Table 28-5, some parameters have asterisk (*) suffixed to indicate that these parameters MUST NOT be reset.Table 28-5 Analytics Properties in futuretense_xcel.ini
Property | Description | Example |
---|---|---|
analytics.datacaptureurl* |
URL where the Analytics data capture servlet ( |
http://<ipaddress>:<port> /sensor/statistic |
analytics.enabled |
Indicates whether Analytics is available. Note: If set to |
true |
analytics.piurl* |
URL where the Analytics performance indicator servlet is running. For information about the performance indicator, see the "Integrating Oracle WebCenter Sites: Analytics with Oracle Web Center Sites" chapter in the Oracle Fusion Middleware WebCenter Sites: Analytics Administrator's Guide. |
http://<ipaddress>:<port> /analytics/PI |
analytics.reporturl* |
URL where the generated report is displayed. |
http://<ipaddress>:<port> /analytics/Report.do |
analytics.user* |
Pre-configured Analytics user who logs in to Analytics from WebCenter Sites. |
csuser Default in Analytics. Changing the name is not recommended. |