Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Workspace Planning Analytics
Created by Guest
Created on Nov 7, 2019

Allow model_upload folder to be outside of data directory

All files uploaded to PAW to be used as datasources are saved in the data directory in a folder labeled model_upload.   We do regular local backups of just our data directories, currently this includes the files in model_upload.  If the upload files are large can causes the backups to grow in size.  There is a bootstrap.properties entry, but it does not allow the directory to be moved out of the base data directory.

  • Guest
    Reply
    |
    Jul 10, 2023

    I opened a case with IBM which is related with this issue

    On PAW on Premise, the model_data folder that PAW creates follows the whole path on the .cfg file

    In this customer's case, there are 4 different locations TM1 uses to hold the objects

    But PAW thought it was only one, so it created a new folder with the full address

    The worst part, is that the folder path creates semicolons, and for some reason TM1 was not being able to recognize the path and would fail the TIs

    Because of that, the drag and drop of .csv files for uploads does not work for them

  • Guest
    Reply
    |
    Oct 13, 2021

    Text data files are often quite large. This means that the Data folder can become bloated with historic text files that were used once, and are no longer required. It may even contain files that were uploaded in error. Unless the model_upload folder is specifically excluded, Data folder backups will include the text files. This means that the backup will take longer to perform, and the backups will take up more disk space.

    There are also the following use cases:

    1. Model migration. The TM1 model is often migrated by copying the Data folder from Production to Development and UAT environments. Text files that are used in one environment, may not be relevant in another environment. Or may even be a security risk (eg confidential data is accidently transferred from Production to Development).
    2. File maintenance. To prevent text files accumulating, regular housekeeping will need to be performed on the contents of the model_upload folder. Users should not have access to the Data folder location, in order to delete obsolete files. There is also the risk that TM1 object files are deleted by mistake.

    There are TM1s.cfg parameters to specify the location of log files (LoggingDirectory), unprocessed audit log files (RawStoreDirectory), bookmark files (IndexStoreDirectory), application units (DistributedPlanningOutputDir), etc. There is even a parameter to separate the Data files from the TM1s.cfg and tm1s-log.properties files (DataBaseDirectory). May we have a tm1s.cfg parameter to specify the location of the model_upload folder please?