TM1 Server updates

IBM® Planning Analytics Local version 2.0.4 and the cloud release of IBM Planning Analytics version 2.0.4 includes the following features for IBM TM1® Server version 11.2.0.

Encryption at rest

TM1 Server uses a two-tier key management system to encrypt and decrypt server data. TM1 APIs enable and disable data encryption. With the TM1 Server command line utility, you can perform primary key rotations for added security. And, if you need to, you can restore files by using the TM1Crypt utility. For more information, see the TM1 Server data encryption in the Planning Analytics Installation and Configuration documentation.

Note: Encryption is not supported for IBM Planning Analytics on cloud. Encryption is available for Planning Analytics Local customers only. Encryption is not supported on a TM1 Server that is using replication and sync. Blobs are excluded from server artifacts that are encrypted by encryption at rest.

Server stability and improved server shutdown

The TM1 Server performs the following tasks to safely shut down the server:

  1. Terminates all spawned external processes.
  2. Cancels all running threads (which is the same as an administrator logging in and canceling all running threads).
  3. Collects and produces information and metrics for the shutdown process.
  4. Sends data to the event log and the server log.

You can use IBM Planning Analytics Administration to start and stop databases.

Change to reporting of memory consumed by feeders in TM1 Server

TM1 Server now reports the memory that is consumed by feeders only once. If there are no changes to rules or cube data, the memory consumption represents a static value that is recorded after the server successfully starts. If there are changes to rules, feeders, or cube data during the running of the server, the Memory Used for Feeders value in the }StatsByCube control cube is updated the next time that the server starts.

Note: The memory accounting is accurate at start-up time. You cannot change your feeders and see what kind of memory profile is generated without restarting the server.

For more information, see Performance Monitoring Control Cubes.

Selectively enable multi-threaded query processing

The MTQQuery parameter in the tm1s.cfg file is now set to True by default. You can use a new TI function, EnableMTQQuery(), to selectively enable or disable multi-threaded query processing when calculating a view to be used in a TI process.

TM1 support for localizable attributes for View, Subset, and TI Processes

TM1 Server supports localizable attributes. You can provide a localized value for the attributes of Dimension, Element, and Cube. TM1 Server automatically returns the correct value for an attribute based on the user-supplied language locale or preferred language locale setting. You don't need to create an alias attribute or text attribute for each language.

In this version of TM1 Server, the View, TI Process, and Subset objects can also have attributes that are localizable. For more information, see Attributes and localization.

Sandbox comparisons

To enable sandbox comparisons, you can set EnableSandboxDimension parameter in your tm1s.cfg file.

For more information, see EnableSandboxDimension.

REST API updates

The following changes were made to the TM1 REST APIs:

  • You can use the REST API actions ExecuteCubeDrillthrough and ExecuteRelationalDrillthrough to preview a datasource. For more information, see Preview a datasource.
  • You can rename or copy a folder in the TM1 Server by using the Copy and Move actions that are bound to the Entry entity. Copy creates an Entry with a different name in the target destination and leaves the source Entry the same. Move creates an Entry with a different name in the target destination and removes the source Entry. You can specify whether the Entry that is created should be public or private. If the target folder is unspecified, the parent folder of the source is used. If the target Name is unspecified, the name of the source is used.
  • You can retrieve elements by supplying either alias or invariant name: The OData-compliant REST API requires an application to know the type of the key when asked for dimension element. The supplied key can either be invariant name or alias. However, when the type is not known, that is, can be either invariant name or alias, the application cannot determine which one to use. For more information, see Retrieve elements by supplying either alias or invariant name.
  • You can now execute a PUT on the reference of the subset element collection to update the collection. You can execute a DELETE on the reference of the collection to empty the collection. The $filter query option can be used to specify which element to be removed. For more information, see Update all elements in a static set.

To learn more, see What's new in 11.2.0.