This is a guest post from Revelwood’s Jay Apwah.
Did you know that since IBM Planning Analytics was released on the cloud, there have been changes to IBM Planning Analytics server configuration parameters? New parameters have been introduced, existing ones have had their default values changed, and the behavior upon changing has changed for some others. This blog post briefly describes the eight changes.
New Parameters:
There are a handful of new parameters that have been introduced. Here is one:
UseExcelSerialDate
Setting this parameter to T causes Planning Analytics functions to use Jan 1, 1900 as the initial serial date instead of Jan 1, 1960. Jan 1, 1900 is also the initial serial date that Microsoft Excel uses. The default value for this parameter is F. Set UseExcelSerialDate = T for Planning Analytics functions to use the Excel serial date scheme.
Changes to default value:
MTQ
In previous releases, the default value was F. The default value is now ALL. This parameter allows Planning Analytics to take advantage of multiple processor cores in order to split calculations into multiple parallel threads.
MDXSelectCalculatedMemberInputs
In previous releases, the default value was F. The default value is now T. This parameter protects against unintended suppression of calculated members when the calculation components are not requested in the query results.
Changed from static to dynamic:
Some parameters are now dynamic, which means parameter values can be edited while the Planning Analytics server is running. It takes 60 seconds for the changed parameter value to take effect.
AuditLogOn
This is an optional parameter that enables and disables audit logging. To enable, set AuditLogOn = T
IntegratedSecurityMode
Although this parameter is dynamic, each user must be logged out of all Planning Analytics components it to take effect.
UseLocalCopiesforPublicDynamicSubsets
This parameter improves performance of public dynamic subsets by using local copies of the public subset instead of the public subset itself.
No longer used:
AuditLogMaxTempFileSize
A similar parameter still exists: AuditLogMaxFileSize. Use it to indicate the maximum audit log file size before a new one is created.
ParallelInteraction
This parameter was used for allowing read/write concurrency on the same cube object.
IBM Planning Analytics is full of new features and functionality. Not sure where to start? Our team here at Revelwood can help. Contact us for more information at info@revelwood.com. And stay tuned for more Planning Analytics Tips & Tricks weekly in our Knowledge Center and in upcoming newsletters!
Read additional blog posts on IBM Planning Analytics Tips & Tricks:
Top 5 IBM Planning Analytics Tips & Tricks
IBM Planning Analytics Tips & Tricks: Using Attributes
IBM Planning Analytics Tips & Tricks: Upgrading from TM1
