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,
Post an idea
Upvote ideas that matter most to you
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
I support this feature to allow scheduled restart of PA instance on Cloud.
I support this feature to allow scheduled restart of PA instance on Cloud. Not only for those who migrate or plan to migrate from premise to the Cloud which they already have this feature in the existing premise instance, also allow the restart at a controlled low usage system period.
We have specific timelines where our business users need to have access to the PA/TM1 instances - therefore having the ability to schedule a stop and restart on a particular day/time is crucial. Currently this is best done on a Sunday AEST - however we don't currently have a support team that is available on weekends.
Given this is possible for an on premises environment - it should be available on the Cloud
While we are able to schedule a chore/TI to executecommand to restart TM1 service on periodic basis as mentioned by Guest below in an on-prem PA environment, unfortunately, this method does not work for PAoC.
Would appreciate IBM come up with a solution for this, especially for PAoC. For one of the environments we support, CCRoC (FAP) is integrated with PAoC. Each time Full Initial Publish runs, the space/memory consumed by the push into FAP_ staging cubes will continue to grow and does not release server memory. Overtime, the server hosting PAoC will run out of memory.
It would be good that an automated/scheduled way can be impleemented for PAoC to mitigate the need for administrator to manually restart the service from time to time.
Not sure if this would be an option for the OP environment, but an approach does exist using a TI (and chore for scheduling). While perhaps not ideal - a TI can accomplish this via the ExecuteCommand function and a batch file to stop the service and then start it. This approach can be fine-tuned of course for timing aspects and include other housekeeping actions as well.
Yes, there is no way to schedule TM1 Server restart. We are doing it every month manually. It would be really helpful & reduce the overheads if this feature added to PAoC.
Agreed. We have no easy way to maintain our cloud environment to keep it in sync with the current on-prem we are moving from while running them in parallel.
This will also be needed to keep our cloud DEV in sync with PRD once fully migrated.
I believe CCC is the best solution as there are other processes that will be dependent upon when the server comes down so that data copies can take place, and then started back up.