Business Analytics File-Based Configuration and Extensions

Most file-based configuration or extensions involve information that Business Analytics needs to connect to the Business Analytics Repository or extensions that must be added to the application server’s classpath. In clustered environments, you can share extensions and some of this file-based configuration using an external configuration folder. See Business Analytics Configuration Files That Can Be External and Business Analytics Extensions for details on resources that can be shared across a cluster.

File

Description and Configuration

Default Location

dynamiccache.xml

Default configuration information for dynamic In-Memory Stores created by MashZone NextGen Analytics.

MashZoneNG-install/apache-tomee-jaxrs/presto/WEB-INF/classes

ehcache.xml

Configuration information for Business Analytics caches. This also contains configuration for MashZone NextGen Analytics In-Memory Stores from version 3.6.

presto.config

Miscellaneous Business Analytics properties, including the path to the deployed web app home folder.

rdsJdbc.properties

Connection information for the MetaData and User section of the Business Analytics Repository.

Note:

Although Business Analytics uses JNDI to connect to the Business Analytics Repository, JDBC connection properties are also used in some specific cases.

See Move the Business Analytics repository to a robust database solution for details.

The Terracotta BigMemory license file

The license file for BigMemory, used for Business Analytics caches and MashZone NextGen Analytics In-Memory Stores, is a separate license file from the Business Analytics license. You can keep the BigMemory license in an external folder shared across the cluster.

See Configure BigMemory Servers for Business Analytics Caching and In-Memory Stores for required configuration steps to enable a shared license.

userRespositoryLdap.properties

Connection information for your LDAP Directory. See Integrate Your LDAP Directory with Business Analytics for details.

For clustered environments, you must copy these configuration files to each cluster member. In most cases, you change configuration once, when you first deploy a Business Analytics Server in the cluster. Any subsequent changes to this configuration for one cluster member, however, must be copied to all other cluster members manually, using a scheduled job or using another replication scheme.

File	Description and Configuration
applicationContext-commonServices.xml	You edit configuration in this file if you choose to use distributed response caching for Business Analytics. See Configure BigMemory Servers for Business Analytics Caching and In-Memory Stores for more information. You may need to update this configuration, as needed, to add additional distributed cache nodes to tune performance.
applicationContext-security.xml	You edit this file initially to enable either SSO authentication or X509 certificate authentication for Business Analytics. See Authentication with Single Sign-On Solutions or Authentication with Digital Certificates/SSL for more information.
applicationContext-security-x509.xml	You edit this file initially to enable X509 certificate authentication for Business Analytics. See Authentication with Digital Certificates/SSL for more information.
applicationContext-scheduler.xml	You edit this file when you move the Business Analytics Repository from the default Derby database to a robust solution. See Move the Business Analytics repository to a robust database solution for more information.
log4j.properties	This file is updated automatically when you change logging configuration in the Admin Console. See Configure Logging for the Business Analytics Server for details. When you change logging for Business Analytics Servers in a cluster, only the specific Business Analytics Server that the Admin Console is connected to is affected. To change logging for the entire cluster, you must update this file and copy it to each cluster member.
userRepositoryApplicationContext.xml	You edit these files when you configure Business Analytics to use your LDAP Directory as the user repository. See Integrate Your LDAP Directory with Business Analytics for details.
userRepositoryApplicationContext-ldap.xml

File	Default Location
Scripts or classes called in mashups in EMML using the <script> statement. This includes: JavaScript files Any Java class that is not in java.lang JRuby scripts Groovy scripts	MashZoneNG-install/apache-tomee-jaxrs/presto/WEB-INF/classes or MashZoneNG-install/apache-tomee-jaxrs/presto/WEB-INF/lib (for JARs)
XSLT stylesheets called in mashups in EMML using the <xslt> statement.
Custom XPath function classes used in mashups in EMML.
Local copies of WSDL files used for WSDL web services.
Custom security profile classes used with mashables.
Custom certificate validation classes for certificate authentication. See Configure Additional Certificate Validation for details.
Custom filter classes for single sign-on authentication. See Implementing a Custom SSO Filter for details.
Classes and third-party libraries for a user-defined function library to use with RAQL.