Spotfire Ideas Portal
ADD A NEW IDEA

Installation

Showing 54

Support Podman as Docker alternative for node manager on Linux to run TERR and Python Services

Hey Tibco Team. To setup a node manager running TERR or Python Service on a Linux platform, Docker is at the moment the only supported option. Since we would like to use e.g. Podman as docker alternative, please consider also support this containe...
over 1 year ago in Spotfire / Installation 0 Future Consideration

Spotfire Server - Migrate certificate information and more from previous server.xml file

During an upgrade of Spotfire Server from 7.11 to 10.3, the upgrade tool reset several settings within the server.xml file, and among them, the certificate name (file extension) and type. The upgrade tool was able to copy over the certificate file...
about 5 years ago in Spotfire / Installation 5 Future Consideration

New server hotfix installation process

We have noticed the change you made of patching the server from Hotfixes to now applying Service Packs. These Service Packs installation basically equates to an upgrade. So, the patching of our infrastructure went from being a simple process with ...
almost 5 years ago in Spotfire / Installation 2 Future Consideration

how to remove 'update dialog'

After new modules are deployed at Spotfire Server, we can see 'update' dialog when log-in to Spotfire Analyst. Unfortunately, we cannot hide the pop-up completely. we can either make it "offline" or "Later". When users log in, I hope the update di...
over 7 years ago in Spotfire / Installation 3 Future Consideration

Improve the upgrade process (reuse existing configuration)

It would be great if the Web Player upgrade process could be more of an upgrade (e.g. the existing WP installation is updated using the UpgradeTool), and not like today, where you basically install a new Web Player and then manually transfer setti...
almost 9 years ago in Spotfire / Installation 0 Future Consideration

Automate deployment of custom packages when updating Spotfire

In our Spotfire environment we use some custom packages (cobranding and some others related to the download section) and every time we update our Spotfire environment we have to manually update those packages and manually apply refresh the nodes t...
about 6 years ago in Spotfire / Installation 1 Future Consideration

Clearer recommended, tested and documented robust upgrade and migration paths

The problem is that there is a lack of solid boundaries around the upgrade process. The product allows you to "upgrade" a few different ways. You can either directly upgrade using the documented procedure, or you can do a clean install of a newer ...
almost 9 years ago in Spotfire / Installation 1 Future Consideration

Deploying a new deployment area to Spotfire client removes the older packages and modules

Hi Developers, Switching to a new deployment area through Spotfire client startup removes the older packages (modules) and replaces them with the new packages into the Modules folder. This makes switching between versions not possible since every ...
about 5 years ago in Spotfire / Installation 2 Future Consideration

Include script for Spotfire Analyst installation to re-direct installing components

We are having problems installing Spotfire Analyst in Citrix for remote deployment across a company. The issue is that when Spotfire Analyst launches for a user for the first time, there is always an "update" that occurs to install components for ...
over 4 years ago in Spotfire / Installation 2 Future Consideration

Webservices revisions

I would like to have more control on how Services are presented after upgrade and migrating from one service to another. The best solution in my mind is to have an in place upgrade and display history for the Webservice in a separate panel. I beli...
almost 8 years ago in Spotfire / Installation 1 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