Spotfire Ideas Portal
ADD A NEW IDEA

Installation

Showing 80

Reliable distro files naming convention

We had invested a lot of effort into building automations that would allow upgrade Spotfire quickly. Every such upgrade process starts with new distro files as inputs. But for some reason, distro filename convention keeps changing and it breaks o...
12 days ago in Spotfire / Installation 0 To be Reviewed

Improve performance of query retrieving user authorization for more than 300% by removing order by statement

We discovered a Spotfire query that retrieves user authorization, which has the highest cost and is used more than 400 times an hour on our system. It contains an "order by" statement. If this statement is removed it performs 300% faster. Although...
almost 2 years ago in Spotfire / Installation 7 Future Consideration

MacOS Spotfire Analyst Client

Will there ever be a Spotfire Analyst client for the MacOS? Installing a VM isn't always ideal, and I'd rather have a true native client. Most of my team members are running Macs as well, and it would ease in our deployment if a MacOS version was ...
about 8 years ago in Spotfire / Installation 8 Future Consideration

CLI or API to automate Update/Migrate Services & Update Node Managers

We have pretty much automated all the steps to apply hotfixes to our Spotfire servers except automating updating node managers and update/migrate services. I have asked this question before when we were using Spotfire version 7.0.0 and the answer ...
almost 7 years ago in Spotfire / Installation 4 Future Consideration

Change backend version of packages to match the dxp version imported

The current behavior is when you import and save a dxp package; say the spotfire client dxp. it adds/updates all the sub components to some random updating verison number. For example; spotfire client 14.3.0 hf-001 says the automation service vers...
7 months ago in Spotfire / Installation 0 Future Consideration

Enable install and cli install option for TERR package path

By default Spotfire 11.x and 12.x sets the default TERR package path to C:\Users\(username)\AppData\Local\TIBCO\Spotfire Spotfire 14.x sets the default TERR package path to C:\Users\(username)\AppData\Local\Spotfire I am requesting the spotfire cl...
7 months ago in Spotfire / Installation 0 To be Reviewed

replace the Spotfire container middleware Tomcat with TongWeb Pas or other china middleware container

Hi tibco team as the Chinese market is now heavily pushing forward with the "XinChuang" policy (a general understanding is that all operating systems, databases, and middleware layers use domestically produced software in China) due to the coun...
2 months ago in Spotfire / Installation 0 Future Consideration

Analyst/Web Player/Automation Services to support .NET Core on Windows

Customer is asking for Analyst/Web Player/Automation Services to support .NET Core on Windows. Preferably supporting .NET Core 8 on Windows.
3 months ago in Spotfire / Installation 0 Future Consideration

Spotfire Server - Make the upgradetool.bat keep previous service parameters

I would expect from an upgrade tool where an input on the previous installation folder is required, to copy over to the new Spotfire Server the settings from the previous installation. This is especially relevant for the JvmMs and JvmMx settings, ...
over 4 years ago in Spotfire / Installation 0 Future Consideration

Spotfire Server - Official procedure for refreshing databases

Could TIBCO provide some official guidance on how to refresh a Spotfire database in the Test environment with data from Production environment? As per the issues seen and the information received, there is no such guidance in place. IDs are carrie...
almost 5 years ago in Spotfire / Installation 2 Future Consideration
This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out. Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved. Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement. Terms of Use | Privacy Policy | Trademarks | Patents | Contact Us