Spotfire Ideas Portal
ADD A NEW IDEA

System Administration

Showing 254

Specific role or licence for "Nodes & Services" option

To have a specific role or a specific licence to control access for "Nodes & Services" option. This idea is similar https://ideas.tibco.com/ideas/TS-I-5549 but it talks about read only access. In my case I need to allow access an user to this ...
over 7 years ago in Spotfire / System Administration 0 Future Consideration

Please revive the error stack in the web player

Somewhere along the recent 7.x versions, the stack trace disappeared along with the error icon in the web player. In practice, this has been a useful and helpful feature - the user can just send the stack trace along to support and troubleshooting...
over 7 years ago in Spotfire / System Administration 0 Future Consideration

Geographically dispersed Spotfire Nodes and Servers in a single collective

The idea here is that by supporting geographically dispersed collectives we can gain several improvements: Ability to process data near the data source (e.g. if we have a large database in Europe and others in US it would be advantageous to proce...
over 7 years ago in Spotfire / System Administration 1 Future Consideration

Add a command line to start and stop the node manager services/instances from the Spotfire Server

Many of our customers are more and more keen to use command line to control or monitor the services instead of the web interface. Some need to restart the services remotely as part of a global scheduler workflow.
over 7 years ago in Spotfire / System Administration 0 Future Consideration

Re-enable Web Player Windows performance counters

Up until 7.0 there were a set of Windows performance counters exposed by the web player. We used to monitor these counters using third party monitoring tools - e.g. we were able to chart the "web player MB available before swapping to disk" metric...
over 7 years ago in Spotfire / System Administration 1 Future Consideration

Configure Tomcat to use log4j logging

Modify the default Spotfire installation so that Tomcat logging uses log4j. Set up a default configuration where significant Tomcat messages are stored in the server log. The current default installation creates a mishmash of files using different...
over 7 years ago in Spotfire / System Administration 0 Future Consideration

Add description field to Groups and Licenses in Administration Manager

Description field would allow notation for things such as the purpose of a group and documentation on which manager are allowed to request changes to a group.
over 7 years ago in Spotfire / System Administration 1 Future Consideration

Feature to Suspend Web Player Instance without removing cached Analysis

It would be great feature if you can add Suspend feature along with shutdown which will take Instance offline but schedule updates should still run and update analysis on that instance. Suspend option should only block the end user request route ...
over 7 years ago in Spotfire / System Administration 0 Future Consideration

Web Player details missing in 7.5+ Action Log

It has been observed that since the change of architecture to 7.5 the action log no longer captures some Web Player information. In the 7.0 and before it would log the the web player version and the fact that a user was logging in via the Web Play...
over 7 years ago in Spotfire / System Administration 0 Future Consideration

Create a spotfire server rule to force certain user to certain pool?

support case number 01259320 we want to force certain user account to stay using web player instance of certain pool, not using other user's pool. Current logic, according to support staff, is when user A's pool is full, he can consume the web p...
about 8 years ago in Spotfire / System Administration 0 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