Built-in “Who am I?” identity function for TurboIntegrator (TI)

Problem statement

IBM Planning Analytics SaaS already knows its own identity, but there is currently no supported way for a TurboIntegrator (TI) process to retrieve that information.

In practice, TI processes often need to know which Planning Analytics environment they are executing in. Typical examples include deployment automation, integration frameworks, logging, auditing and reusable application frameworks.

Today, customers must manually maintain information such as Tenant ID, Database Name, PAW URL and REST endpoint in configuration cubes, process parameters or external configuration files.

This creates unnecessary maintenance, introduces configuration errors and makes reusable solutions more difficult to build.

Real-life scenario

A company operates multiple Planning Analytics SaaS environments (Development, Test and Production), each containing several TM1 databases.

The same TI processes and frameworks are deployed across all environments. During execution, a process needs to know which tenant and database it belongs to in order to:

• write audit logs

• call external services

• generate links back to PAW

• identify the current environment

• avoid maintaining duplicate configuration

Since this information cannot be retrieved from the platform itself, every deployment requires manual configuration that must be kept synchronized.

Current workaround

Customers typically store server identity information manually in:

• Control cubes

• Configuration parameters

• Text files

• Environment variables

• External configuration databases

These values must be maintained manually whenever environments are created, cloned or changed.

Proposed solution

Introduce a new TurboIntegrator function:

GetServerIdentity(<Property>)

Examples:

sTenantId = GetServerIdentity("TenantId");
sDatabase = GetServerIdentity("DatabaseName");
sDatabaseId = GetServerIdentity("DatabaseId");
sPawUrl = GetServerIdentity("PawUrl");
sRestUrl = GetServerIdentity("RestBaseUrl");

Suggested initial properties:

• TenantId

• DatabaseName

• DatabaseId

• PawUrl

• RestBaseUrl

• Region

• EnvironmentId

IBM could extend the list over time without affecting existing applications.

As a future extension, the same server identity information should also be exposed through a supported REST API endpoint, allowing external automation tools and services to retrieve identical information.

Benefits

• Eliminates duplicate configuration

• Simplifies deployment automation

• Enables self-configuring TI applications

• Makes reusable frameworks easier to build

• Improves audit logging and observability

• Reduces configuration errors

• Better supports multi