Product:

Planning Analytics Workspace 2.1.19

Microsoft Windows 2022 server

Issue:

PAA agent is not connecting to PAW.

The file serversinfo.json in folder D:\Program Files\IBM\tm1_64\paa_agent\paaAgentCache should contain the names of your Tm1 instances. If it is empty, the python script have maybe not been able to read the windows services information.

Error in messages file in folder D:\Program Files\IBM\tm1_64\paa_agent\wlp\usr\servers\kate-agent\logs

[5/5/26, 15:57:40:994 CEST] 00000046 ice.notification.PaKateServerUnresponsiveNotificationService E Error occurred while getting latest servers info from json file
java.lang.NullPointerException: Cannot read field “modules” because the return value of “org.python.core.Py.getSystemState()” is null
at org.python.core.PyModule.module___init__(PyModule.java:64)
at org.python.core.PyModule.<init>(PyModule.java:47)
at org.python.util.PythonInterpreter.<init>(PythonInterpreter.java:104)

Solution:

Restore to the bootstrap.properties file that was installed with the upgrade.

Do not use a backed up file of bootstrap.properties – only add the SMTP parameters you need manually to the new bootstrap.properties.

SMTP_EMAIL_START_TLS_ENABLE=FALSE

SMTP_EMAIL_PASSWORD=

SMTP_EMAIL_PORT=25

SMTP_EMAIL_AUTH=FALSE

SMTP_EMAIL_USERNAME=

PAA_EMAIL_ADDRESS=yourname@domain.com

SMTP_EMAIL_HOST=smtp.yourcompany.domain.com

SEND_GRID_API_KEY=””

Start the PAA agent from the bat file: D:\Program Files\IBM\tm1_64\paa_agent\bin\PAAAgentStart.bat

If above does not work also check this:

• Re-register/Re-register the Agent Service: If upgrading to PAW 2.0.41 or higher, the agent must be updated.
  1. 1. Stop the service.
     2. Run <install_dir>\paa\bin\PAAAgentDelete.bat.
     3. Run <install_dir>\paa_agent\bin\PAAAgentSetJavaHome.bat.
     4. Run <install_dir>\paa_agent\bin\PAAAgentRegister.bat.

• Fix Java Path Issue: If the agent fails to start, run PAAAgentSetJavaHome.bat in <install_dir>\paa_agent\bin to ensure the correct Java home is set.

• Ensure the PAA Agent is updated to match the version of PA Workspace in use. If not, then download the newer PAA Agent .zip file from PA Workspace administration UI.
• Review \paa_agent\wlp\usr\servers\kate-agent\bootstrap.properties for PAA Agent configuration errors
• In \paa_agent\wlp\usr\servers\kate-agent\bootstrap.properties verify SERVERS_DIR points to the parent folder of the TM1 data directories, not directly to one specific data directory.
• Review \paa_agent\wlp\usr\servers\kate-agent\server.xml for WLP-related errors
• Review \paa_agent\wlp\usr\servers\kate-agent\logs\ for errors
• Review \pa_workspace_install\logs\monitor\ for errors
   *The monitor service is what the PA Workspace Administration page uses to communicate with the PAA Agent
• Review \pa_workspace_install\config\paw.env (or paw.ps1) file

• Ensure that the IBM Planning Analytics Administration Agent service is running
• Ensure that the IBM Planning Analytics Administration Agent service account is configured with english locale
• Verify that the PAA Agent URL is accessible in a web browser where PAA Agent is installed (ignore the SSL certificate warning)
  URL: https://localhost:9012
  If available, PAA Agent just responds “NOT FOUND The application or context root for this request has not been found”
  *PAA Agent runs on Port 9012 and uses SSL by default
• Verify that PAA Agent is accessible from inside the docker virtual network of PA Workspace. Open Powershell and run these commands:

  docker exec -it monitor Powershell
  cd curl*
  cd bin
  .\curl -v telnet://paa_agent_servername ipaddress:9012

  Replace “paa_agent_servername” by the exact server name specified in \config\paw.ps1 for “TM1Location” parameter (since PA Workspace finds PAA Agent server from TM1 Admin Server location)

• In the web browser, verify that the SSL Certificate is valid
  See: https://www.ibm.com/support/pages/node/6562425
• Verify that the PAA Agent URL is also accessible through the Planning Analytics Workspace host by using browser or curl command
  URL: https://paa_agent_servername:9012
• Verify that PAA Agent is listening on port 9012: from Windows start menu, run “resmon.exe”, select “Listening Ports”, and verify “javaw.exe” is listening on port 9012
• In Planning Analytics Administration Tool page, verify the IP addresses returned for the Admin Host and TM1 Server
  URL: http://workspace_servername:8888
• Does your PAA Agent bootstrap.properties file contain a AGENT_API_KEY setting?
  • Does Workspace paw.env / paw.ps1 file have AdminAgentAPIKey set?
    See: https://www.ibm.com/support/pages/whats-coming-next-ibm-planning-analytics-workspace-2060
• Does your PAA Agent use custom SSL?
  • Were the certificates imported into Workspace?
    See: https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=ctas-configure-tls-between-planning-analytics-workspace-local-other-servers
• Does your TM1 Admin Server and TM1 Server use custom SSL?
  • Were the certificates imported into the PAA Agent keystore?

• Stop the IBM Planning Analytics Administration Agent service
• Update the \paa_agent\wlp\usr\servers\kate-agent\bootstrap.properties file to include
  • com.ibm.ws.logging.trace.specification=”*\=audit\:com.ibm.pa.kate.agent.*\=all”
  • com.ibm.ws.logging.console.log.level=ERROR
• Start the IBM Planning Analytics Administration Agent service
• Replicate the problem as required
• Review the files in \paa_agent\wlp\usr\servers\kate-agent\logs\

More information:

https://www.ibm.com/support/pages/planning-analytics-administration-agent-not-reachable

https://www.ibm.com/support/pages/how-troubleshoot-planning-analytics-administration-agent

https://www.ibm.com/support/pages/how-obtain-planning-analytics-tm1-server-certificate 

https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=only-configure-agent-windows 

https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=cloud-configuring-premises-agent

If you find this error in the message.log for PAA agent instead;

Then you have more than one DATA folder, and the model_upload folder is created in wrong data folder. PAW PA Agent does not support more than one DATA folder listed in TM1S.CFG file.

Product:
Planning Analytics 2.1.14
Microsoft Windows 2022 server

Issue:
How many RUNPROCESS can you run in parallel on a server?

RunProcess lets you run TurboIntegrator processes in parallel, each on its own thread that is managed by TM1® Server. This approach speeds up data load and other operations where TurboIntegrator processes are used to divide the work.

Suggested Solution:

You can only run, same number of virtual CPU cores you have on the server, with the RUNPROCESS command, to ensure proper data handling.

If you run more RUNPROCESS command than CPU cores, you may get that CELLPUTN command will not be executed, and you will not get a error. The process continue as all is fine.  On the other hand ASCIIOUTPUT maybe will work fine, so to run more RUNPROCESS in parallel to only create csv files works better.

If you have the ASCIIOUTPUT in the Data tab, and then the CELLPUTN in the Epilog tab of your TI process that you call from a RUNPROCESS command,

add a SLEEP (1001) before the CELLPUTN line, will in some cases solve the issue.

The solution is to add a delay somewhere in the processes, to make the server catch up with what you try to do.

More Information:

https://code.cubewise.com/blog/4-ways-to-speed-up-your-processes-in-ibm-tm1-and-planning-analytics/

https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=tf-process-control-turbointegrator-functions

https://aggregated.blogspot.com/2015/02/running-tm1-processes-from-outside-tm1.html

https://www.ibm.com/docs/fi/planning-analytics/2.0.0?topic=mtf-logoutput-1

Product:
Planning Analytic 2.1.19  tm1server = 11.8.03500.6

Microsoft Windows 2019 server

Issue:

How use SUBST instead of STR function in a process?

In PAL 2.1.18 STR function does not truncate a string when a length parameter is passed. The original value is returned as a string.

Solution:

This should give the same result

sTestA = STR(1000000, 4, 0) ;
sTestB = SUBST (numbertostring (1000000) , 1, 4) ;

Syntax for SUBST is:

SubSt(String, Beginning, Length)​

• ​String = A text string​
• Beginning = Substring starting position​
• Length = Length of the string that we want to keep

More Information:

• AsciiDelete: Deletes an ASCII file
• AsciiOutputOpen: Appends or overwrites content in a specified existing file that you would use in conjunction with functions that write to a file like AsciiOutput and TextOutput.
• AsciiOutput: writes data to a file to a directory the TM1 Server can access, using data sources from a cube, an ODBC source or no data sources.
• CapIt = capitalises the first letter of every word in a string
• Char = Converts the ASCII numeric code into the character
• Code = Converts the character to the ASCII numeric code
• CodeW = Returns the UTF-8 numeric code for a specified character within a string
• DatasourceAsciiDecimalSeperator: Sets the decimal separator
• DatasourceAsciiDelimiter: Sets the delimiter
• DatasourceASCIIHeaderRecords: sets the header records for a text file.
• DatasourceAsciiQuoteCharacter: Sets the quote character
• DatasourceASCIIThousandSeparator: sets the thousand separator for a text file.
• DatasourceCubeview: sets the cube view in the data source.
• DatasourceDimensionSubset: sets the dimension subset in the data source.
• DatasourceNameForClient: sets the name of the data source from the client’s perspective when creating or editing the process.
• DatasourceNameForServer: sets the name of the data source.
• DatasourcePassword: sets the password used for the data source
• DatasourceQuery: sets query for the data source
• DatasourceType: sets the type used for the data source
• DatasourceUsername: sets the name used to connect to the data source
• DatasourceODBOCatalog: sets the name of the ODBO database collection that you want to connect.
• DatasourceODBOConnectionString: sets the connection parameters required to connect to the OLAP server.
• DatasourceODBOCubeName: sets the cube name you want to connect to from the OLAP Server.
• DatasourceODBOHierarchyName: This function is used for OLAP products like SAP BW and sets the name of the hierarchy from a dimension.
• DatasourceODBOLocation: sets the name of the OLAP server’s location.
• DatasourceODBOProvider: sets the name of the ODBO provider installed on your server.
• DatasourceODBOSAPClientID: sets the client ID that connects to the SAP Server.
• DatasourceODBOSAPClientLanguage: sets the language specification from the SAP Server.
• Delet = Deletes a specified number of characters from a specified position within a string
• Fill = Repeats a string to the specified number of lengths
• Insrt = Inserts one string into another string at the given position number
• Long = Returns the length of the string
• Lower = converts text characters to lowercase
• NumberToString: convert a number to a string
• NumberToStringEx: Convert a numeric value into a string based on a specific numeric format string
• Numbr = Converts string character to a number
• Scan = Searches the specified substring within a string and returns the starting position of the substring
• SetInputCharacterSet: Specify the encoding used in the data source.
• SetOutputCharacterSet: specifies the character set when writing to a text file using TextOutput.
• SetOutputEscapeDoubleQuote: Retains or removes double quotes when outputting element names or data values to a text file
• Str = Converts number to a string character
• SubSt = Returns the substring of a specified string
• TextOutput: Writes and generates a text file in the specified path
• Trim = Removes any leading and trailing spaces from a string
• Upper = Converts text characters to upper case
• ViewExtractFilterByTitlesSet: Skip or include elements in the title axis when exporting a view using ASCIIOutput.
• ViewExtractSkipCalcsSet: Skip or include consolidated values when exporting a view using ASCIIOutput.
• ViewExtractSkipConsolidatedStringsSet: Skip or include strings on consolidated values when exporting a view using ASCIIOutput.
• ViewExtractSkipRuleValuesSet: Skip or include ruled values when exporting a view using ASCIIOutput.
• ViewExtractSkipZeroesSet: Skip or include zeros when exporting a view using ASCIIOutput.

Product:

Planning Analytics 2.1.14
Microsoft Windows 2022 server

Issue:

How replace \ with / in a string in a TM1 TI process?

Solution:

Enter below code in you prolog:

vTemp = '';
vChar = '';
k=1;
WHILE( k <= LONG(pFilePath) );
  vChar = SUBST(pFilePath, k, 1);
  IF(vChar @= '\');
    vChar = '/';
  ENDIF;
  vTemp = vTemp | vChar;
  k = k + 1;

END;
NewFilePath = vTemp;

Content in pFilePath will be updated to NewFilePath variable.

More information:

WHILE Function: How to Use, Syntax, and Examples

https://cubewise.com/functions-library/tm1-function-for-ti-while/ 

Product:
Planning Analytics 2.1.14
Microsoft Windows 2022 Server

Issue:

How call RUSHTI.EXE from TI process when using SSO with IntegratedSecurityMode=5  (CAM)?

https://github.com/cubewise-code/rushti

Solution:

Run the TM1 service  (IBM TM1 Admin Server x64) and TM1 application service (IBM TM1 Server x64 – budget) with a windows account in your domain, that have rights inside your TM1 application (maybe ADMIN).  The ExecuteCommand is run with the user who runs the TM1 service.
Go to Windows service, and for your TM1 service, change the log on from Local System to account (a service account that does not change password) in the domain.

To call RUSHTI from a TI process enter something like this:

sCMD = 'd:\rushti\rushti run --tm1-instance "Budget" --workflow "load data fast" --max-workers 8 --mode opt' ;
ExecuteCommand(sCMD, 1);

https://github.com/cubewise-code/rushti/releases

To install RUSHTI.EXE you need to download the zip file, and unpack it to a folder on your server (d:\rushti)

Installation

1. Download rushti-windows.zip  (to start with, take this file https://github.com/cubewise-code/rushti/releases/download/v2.0.0/rushti-windows.zip )
2. Extract to your desired location (keeps directory structure intact)
3. Copy config/config.ini.template to config.ini and configure your TM1 connections
4. (Optional) Copy config/settings.ini.template to settings.ini for custom defaults
5. Run rushti.exe from command line

Note: This build uses PyInstaller’s onedir mode for fast cold starts.
Keep all files in the extracted directory together – the exe requires the bundled libraries.

You must have the files in the _internal folder, the files can not be replaced.

The config.ini contains the information to connect to your TM1 instance. Change for your environment, ports etc:

# The section name (e.g., [Budget]) is used as the instance identifier
# in task files and command-line arguments.
# For SSO set username to blank etc
# Copy this file to config.ini and update with your actual TM1 server details.
# the name of the tm1 application you should work with
[Budget]
# TM1 server hostname or IP address
address=tm1servername.domain.com
# REST API port (check your tm1s.cfg HTTPPortNumber setting)
port=12387
namespace=AD
gateway=http://caservername.domain.com:80/ibmcognos/bi/v1/disp
user=""
password=""
# Set to True if password is base64 encoded
decode_b64=False
# Set to True if TM1 server uses HTTPS (check UseSSL in tm1s.cfg)
ssl=True

Settings.ini is the file for defaults of the system to activate collection of data to database etc. It can look like this:

# RushTI Settings Configuration
# ==============================
#
# This file configures RushTI behavior settings, separate from TM1 connection
# settings in config.ini.
#
# Settings Precedence (highest to lowest):
# 1. CLI arguments (e.g., --max-workers 8)
# 2. JSON task file settings section
# 3. This settings.ini file
# 4. Built-in defaults
#
# To use this file:
# 1. Copy to settings.ini in the directory called config
# 2. Uncomment and modify the settings you need
# 3. Delete or leave commented any settings you want to use defaults for
# ------------------------------------------------------------------------------
# [defaults] - Common execution settings
# ------------------------------------------------------------------------------
[defaults]
# Maximum number of parallel workers
# Valid range: 1-100 (start with the same amount of CPU cores you have on the server)
# Default: 4
max_workers = 8

# Number of retries for failed process executions
# Valid range: 0-10
# Default: 0
# retries = 0

# Output file path for execution results summary CSV
# Set to a file path to create a summary CSV (e.g. rushti.csv)
# Leave empty or omit to skip creating the summary CSV
# Default: (empty - no CSV created)
result_file = rushti.csv

# Execution mode: 'norm' (normal) or 'opt' (optimized with dependencies)
# Default: norm
mode = opt

# ------------------------------------------------------------------------------
# [optimization] - Automatic task ordering optimization
# ------------------------------------------------------------------------------
[optimization]

# Enable automatic task optimization during execution.
# When enabled, ready tasks are sorted by estimated runtime (longest first)
# to maximize parallel efficiency. Dependencies are always preserved.
#
# Requires: [stats] enabled = true (needs historical data for estimates)
# Override: Use --no-optimize flag to disable for a specific run
#
# Default: false
# enabled = false

# ------------------------------------------------------------------------------
# [logging] - Enhanced logging settings / you must adjust this file to make it work
# ------------------------------------------------------------------------------
[logging]
# level = INFO
# file = /log/rushti.log

# ------------------------------------------------------------------------------
# [tm1_integration] - TM1 integration for reading taskfiles and logging results
# ------------------------------------------------------------------------------
[tm1_integration]

# Push execution results to TM1
# When enabled, the results CSV is uploaded to TM1 files after each run
# as: rushti_{workflow}_{run_id}.csv
#
# To set up TM1 integration:
# 1. Run: python rushti.py build --tm1-instance tm1srv01
# This creates the required dimensions and cube automatically.
# 2. Set push_results = true and configure default_tm1_instance below
#
# Default: false
push_results = true

# Automatically load results into TM1 cube after push
# When enabled (and push_results = true), calls }rushti.load.results TI process
# on the target TM1 instance after uploading the results CSV.
# The TI process must exist on the target instance.
#
# Default: false
# auto_load_results = false

# Default TM1 instance for reading taskfiles and writing results
# Used when --tm1-instance is specified without an instance, and for auto-upload
# Must be defined in config.ini, set the name for the section in config file.
default_tm1_instance = Budget

# Default cube name for task definitions and results
# The build command creates this cube with dimensions:
# - rushti_workflow: Workflow identifiers
# - rushti_task_id: Task sequence (1-5000 default elements)
# - rushti_run_id: "Input" for definitions, timestamps for results
# - rushti_measure: Task field measures
#
# Default: rushti
default_rushti_cube = rushti

# ------------------------------------------------------------------------------
# [stats] - SQLite stats database for execution history
# ------------------------------------------------------------------------------
[stats]

# Enable the stats database for storing execution history
# The stats database stores execution statistics for:
# - Optimization features (EWMA runtime estimation)
# - TM1 cube logging data source
# - Historical analysis via 'rushti db' commands
# Default: false
enabled = true

# Path to the SQLite database file
# Relative paths are resolved from the application directory
# Default: data/rushti_stats.db
db_path = data/rushti_stats.db

# Number of days to retain execution history
# Valid range: 1-365
# Default: 90
retention_days = 90

To create the RUSHTI cube, you run the command:

rushti build --tm1-instance "Budget"

If not using a CUBE for the tasks, you can use a TXT file. See link.
https://code.cubewise.com/open-source/tm1py/rushti/

To create an HTML file of the run information, enter command like below in the DOS prompt:

rushti tasks visualize  --tm1-instance "Budget"  --workflow "load data fast"  --output dag.html

Open the dag.htlm file in your web browser (with javascript enabled).

In the RUSHTI cube, you can use the predecessors column to tell what process should be finish before this process start. In below example the process number 3 starts first when process 2 is finished.

in process filed, enter the name of the TI process to run.

In parameters field, when you have more parameters than one , they can be formatted like this:

{ "pVersion": "Prognos 1", "pYear": "2025" , "pMonth": "03" }

There is a colon (:) between the prompt and the value, and a comma (,) between the parameters, or the simpler format shown below will work (you need the space before ,):

pVersion=Budget , pYear=2026 , pMonth=01

If you have a path in your parameter, then you need to enter / (forward slash) instead of \. So it should look like this:

{ "pNewCube": "thecubename", "pFilePath": "D:/Tm1 Data/budget/Export/to_other/read/Budget_2026_01.csv" }

You need to create a element in dim Rushti_workflow for your tasks settings, this i called from the rush command. For it to know what task list it should execute on, in the cube. e.g. –workflow “load data fast”

More Information:

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=pctf-executecommand

https://code.cubewise.com/blog/introducing-the-tm1py-universe/

Full documentation is available at cubewise-code.github.io/rushti/docs

• Installation
• Quick Start
• Task Files
• CLI Reference
• Settings Reference

https://code.cubewise.com/downloads/

https://code.cubewise.com/blog/run-processes-in-parallel-using-only-connection/

Product:
Mirantis Docker
Microsoft Windows 2022 server

Issue:

How update the lic file on the docker installation on a Windows server?

Solution:

Buy a new license (Mirantis Container Runtime with LabCare Support) from Mirantis, one per PAW server. You will get a mail with a link, that will download the MCR file direct to your computer.

Then rename the file from like MCR 3xNode LabCare.lic  to docker.lic.

Copy the docker.lic file to your docker folder – normally that is D:\docker on your Planning Analytics Workspace (PAW) server.

To check that you have a license, enter below in CMD:

docker info --format '{{.ProductLicense}}'

You should get a text like this ‘Valid until 2026-04-09 for sf0643587264358638568230756MAC’ if all is fine.

More Information:

https://docs.mirantis.com/mcr/25.0/single/index.html#install-the-license

You can update the license in your cluster at any time during the week before your license expire.

As per our terms of service – “Users are not authorized to run MCR without a valid license.”, but even if you do not replace the license after the 10th, the docker service will not be forcefully stopped and there won’t be any interruptions to your applications and workloads.

You download Mirantis license (.lic) files from the Mirantis CloudCare Portal (or from a purchase confirmation email, depending on the product):

For MKE / MSR / MKE 4k:

1. Find the email from Mirantis Support with subject similar to “Welcome to Mirantis’ CloudCare Portal” and log in as instructed. [MKE 3.7 license; MSR 2.9 license]
2. In the top navigation bar, click Environments.
3. Click the Cloud Name associated with the license you need.
4. Scroll down to License Information and click the License File URL.
5. In the new tab, click View file to download the .lic file. [MKE 3.8 license; MSR 2.9 single]

For MCR (Mirantis Container Runtime):

• If you bought via the Mirantis Store, the license file is available from the link in your purchase confirmation email. Otherwise, you must contact Mirantis Sales/Support to get the file. [MCR 25.0 license]  

For Mirantis Container Runtime (MCR) / Mirantis Docker Engine, the license file must be placed in the daemon data directory and named docker.lic.

On Windows (default path):

• Copy the file to: %PROGRAMDATA%\docker\docker.lic [MCR install license]

Install MKE offline – Mirantis Kubernetes Engine

Index of win/static/stable/x86_64

By default, MCR automatically records and transmits data to Mirantis for monitoring and analysis purposes. The data collected provides the Mirantis Customer Success Organization with information that helps us to better understand the operational use of MCR by our customers. It also provides key feedback in the form of product usage statistics, which enable our product teams to enhance Mirantis products and services.

When antivirus and antimalware software products scan files in use by MCR, these files can lock in a way that causes Docker commands to hang or causes orphaned snapshots to leak disk space. To circumvent these problems, you can add the Docker data directory to the software’s exclusion list, which is by default /var/lib/docker on Linux systems and %ProgramData%\docker on Windows Server systems. As a result of this action, though, viruses or malware in local Docker images, writable layers of containers, or volumes will go undetected.