TM1 Server updates

Updates to the TM1Crypt utility

The TM1Crypt utility has been updated. For more information, see Running the TM1Crypt utility.

Enhanced cube rule area definition support for model using multiple hierarchies

Cube rules have changed as of IBM TM1 Server version 11.1.0.0. You can use a single rule statement to cover a set of same-named consolidated elements across hierarchies of the same dimension. This approach gives you greater flexibility with hierarchies.

For more information, see Use the Or operator to specify cube rules across hierarchies.

Changes to default behavior for FileRetry.FileSpec parameter

As of IBM TM1 Server version 11.1.0.0, if the FileRetry.FileSpec parameter is not specified in the tms1.cfg file (default), the retry logic is applied to all files in the logs directory only.

For more information, see FileRetry.FileSpec.

New tm1s.cfg parameter ODBCTimeoutInSeconds

The ODBCTimeoutInSeconds parameter specifies the timeout value that is sent to the ODBC driver using the SQL_ATTR_QUERY_TIMEOUT and SQL_ATTR_CONNECTION_TIMEOUT connection attributes.

For more information, see ODBCTimeoutInSeconds.

New tm1s.cfg parameter SQLRowsetSize

The SQLRowsetSize parameter specifies the maximum number of rows to retrieve per ODBC request.

For more information, see SQLRowsetSize.

New logger introduced

The TM1 server uses monitoring code to generate log messages that are pushed out to the ops.logger. Critical events that are pushed out to this logger include the following:

• Threads and their state
• Thread state of interest
• High contention
• Pool memory size
• Chore failure

To learn more, see Logging essential server information and Set database configuration parameters.

Updates to TM1 REST APIs

Types, actions, and functions have been added or changed in the TM1 REST API schema for IBM Planning Analytics Local version 2.0.3. These include the following features for TM1 server version 11.1.0.0:

• Locking and unlocking cubes or dimensions.
• Rule tracing, which includes tracing the calculation of a single cell. The result contains any components of the calculation.
• Ability to set the Context on a Session to better identify sessions and their associated threads. The client or consumers sets a context, which in turn allows consumers of this information to know who the client or consumer is.
• New properties in the Document, ExternalDatabaseSettings, and Session entities.

For more information, see the Release notes in TM1 REST API documentation.