analytics/configuration/ansproperties.xml.sample

<?xml version="1.0" encoding="UTF-8"?>
<!--
	Licensed Materials - Property of IBM
	IBM Cognos Products: ans
	(C) Copyright IBM Corp. 2005, 2010
	US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
-->


<!--  This file allows for configuration of the installed instance of the analysis studio server.  Some properties may also be configured  -->
<!--  using the report server advanced settings dialog.   When configuring such a property, use the name from this file prefixed with "ANS."  -->
<!--  For example, the property DefaultVisibleItemCount would be specified in the advance settings dialog as "ANS.DefaultVisibleItemCount"   -->
<!--  A property value set in the advanced settings dialog will apply to all instances.  If the same configuration file property value is set, then  -->
<!--  the configuration file value will override the advanced settings property for the server instance being configured.  -->

<!--  Not all properties can be configured through the advanced settings dialog at this time. Those that can will have this noted in their -->
<!-- comment section below.  -->

<ans_property xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ansProperty.xsd">
	<structure>
		<!--Setting TraceLogging logs Analysis Studio activities in the ANSTrace.log file which is found in the logs directory. -->
		<!--Note: Trace Logging is not thread-safe. Use IPF for thread-safe logging. -->
		<!--<property>TraceLogging</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!--Setting ErrorLogging logs Analysis Studio errors in the ANSError.log file which is found in the logs directory. -->
		<!--Note: Error Logging is not thread safe. Use IPF for thread-safe logging. -->
		<!--<property>ErrorLogging</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!--Setting DeveloperLogging creates a variety of different files under the logs directory. All these files start with the prefix "ans". -->
		<!--<property>DeveloperLogging</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!--Process ID specific logging creates Process ID specific versions of the Error and Trace logs. -->
		<!--<property>ProcessIDSpecificLogging</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!--Limit the size of pages displayed at one time on the crosstab rows. WARNING - Setting the row PageSize to a value greater than the default
		     of 200 could cause performance degradation. -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>PageSize</property>
		<value type="long">200</value>-->
	</structure>
	<structure>
		<!--Limit the size of pages displayed at one time on the crosstab columns. WARNING - Setting the ColumnPageSize to a value greater than the default
		     of 50 could cause performance degradation. -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>ColumnPageSize</property>
		<value type="long">50</value>-->
	</structure>
	<structure>
		<!--Limit the cache size round tripped between client and server.  Increasing this value may increase network traffic.   The value is specified in kilobytes. -->
		<!--The cache is used to improve performance on the server -->
		<!--The default if not specified is zero. A value of zero means caching is disabled. -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>MaxRoundtripCacheSize</property>
		<value type="long">10</value>-->
	</structure>
	<structure>
		<!-- When a missing or inaccessible member is encounted do you 
			 want to see the UI for correcting the problem or just an error 
             message. 
             <value type="long">0</value> means NO UI, and a simple error message

       		 <value type="long">1</value> Means Missing member UI. This is the 
										  default behaviour
		-->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!-- <property>showMissingMemberUI</property>
		<value type="long">1</value> -->
	</structure>
	<structure>   
		<!-- When EstimatedColumnWidthXtabRendering is true, the client will render crosstab columns based on the width estimates provided by server heuristics.-->
		<!-- When EstimatedColumnWidthXtabRendering is false, the client will determine each crosstab column size.-->
		<!-- -->
		<!-- When the client determines the width, the resize capability is disabled. -->
		<!-- When the server determines the width, the default widths are less accurate, but rendering is faster and the column resize capability is enabled. -->
		<!-- -->
		<!--The default for this property when not specified is true.  i.e. use server estimated column widths -->
		<!--<property>EstimatedColumnWidthXtabRendering</property>
		<value type="long">1</value> -->
	</structure>
	<structure>
		<!-- Setting MaxChartHotAreas sets the maxHotspots attribute in the report spec for maximum number of active areas in a chart. -->
		<!-- The default value (if not specified) is 600 -->
		<!-- Reducing this value will improve performance and increasing will decrease performance on large charts -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>MaxChartHotAreas</property>
		<value type="long">600</value>-->
	</structure>
	<structure>
		<!-- Enable selection based suppression (sparsity removal) -->
		<!-- The default is enabled.  0 == disabled.  1 == enabled (recommended).  -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>EnableSelectionBasedSuppression</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!-- Enable overall suppression (non-selection based suppression) -->
		<!-- The default is enabled.  0 == disabled.  1 == enabled (recommended).  -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>EnableOverallSuppression</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!-- Enabling the Automatic Position Calculations Feature -->
		<!-- The default is enabled.  0 == disabled.  1 == enabled.  -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>EnablePositionedCalcs</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!-- This property restricts drill-through to be allowed for a selected data cell only if both the row member(s) and column member(s) are eligible for drill-through. -->
		<!-- The default is disabled, which allows drill-through without any restriction (by setting the value to 0).  0 == disabled.  1 == enabled.  -->
		<!--<property>restrictedDataCellDrillThrough</property>
		<value type="long">0</value>-->
	</structure>
	<structure>
		<!-- The UI for enabling nodata mode is shown by default.  To remove this capability disable the nodata UI. -->
		<!-- The default is enabled.  0 == disabled.  1 == enabled.  -->
		<!--<property>EnableNoData</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!-- The default is enabled.  0 == disabled.  1 == enabled.  -->
		<!-- This property allows Analysis Studio to attempt to optimize queries based on information gathered during previous gestures in the studio -->
		<!-- When enabled, the order of a users gestures may affect the performance of the queries generated -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>AdaptiveQueryOptimizationEnabled</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!-- Allow the default visible item count per set to be changed.  If not specified, the default is 12  -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>DefaultVisibleItemCount</property>
		<value type="long">12</value>-->
	</structure>
	<structure>
		<!-- Default value for output purpose drill, print, default is drill  -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>DefaultOutputPurpose</property>
		<value type="string">drill</value>-->
	</structure>
	<structure>
		<!-- Column width persistances is enabled by default.  0 == disabled.  1 == enabled.  -->
		<!-- This property allows the user to disable (by setting the value to 0) the ability for the product  -->
		<!-- to save a user changed column width with an analysis.  If disabled, then resized column widths are  -->
		<!-- not saved with the analysis and when opened an analysis will default the column width -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--property>EnableColumnWidthPersist</property>
		<value type="long">1</value-->
	</structure>
	<structure>
		<!-- When column width persistance is enabled, this parameter controls the maxiumum number of  -->
		<!-- resized columns stored in the most recently used list.  A larger value will result in the product  -->
		<!-- storing more column resizes, but will result in a larger analysis written to disk and more information  -->
		<!-- exchanged between client and server during save and load.  The default (if not specified) is 100.  -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--property>PersistColumnWidthMRU</property>
		<value type="long">100</value-->
	</structure>
	<structure>
		<!--temporary switch to enable the new drill through selection model-->
		<!--Default is 1 (ON) == new model; 0 (OFF) == old model -->
		<!--property>AllowNewSelectionContextModel</property>
		<value type="long">1</value-->
	</structure>
	<structure>
		<!-- This flag is used to enable/disable members from the same hierarchy -->
		<!-- to be put in row/column axis, or in context-filter area. -->
		<!-- If QOS flag - MULTIPLE_HIERARCHIES_OF_SAME_DIMENSION is disabled, -->
		<!-- this rule will apply to dimension. -->
		<!-- The default is enabled.  0 == disabled.  1 == enabled (recommended).  -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>EnableSameHierarchyCompatibility</property>
		<value type="long">1</value>-->
	</structure>
	<structure>
		<!-- This flag is used to enable/disable Analytic Operands(Sum & Diff) are used -->
		<!-- as fast-calc items shown in xtab context menu and calc toolbar dropdown button. -->
		<!-- The default is disabled.  0 == disabled(recommended).  1 == enabled. -->
		<!-- This property can configured through the advanced settings.  See note at top of this file -->
		<!--<property>EnableSumDiffFastCalc</property>
		<value type="long">0</value>-->
	</structure>
	

</ans_property>