Spotfire Ideas Portal
ADD A NEW IDEA

System Administration

Showing 290

Ability to restart Information Service sub-process independently

Starting from Ver12.1, java.exe for Information Services runs as sub-process of Spotfire Server. But so far it's not possible to manage / restart java.exe for Information Services independently. Please consider to add ability to manage/restart Inf...
about 1 year ago in Spotfire / System Administration 0 Future Consideration

Create Health Endpoints for Nodes

Currently we have no idea if the nodes are available and working. Using AWS infrastructure, we would like health endpoints for the nodes similar to the server so we can automate the infrastructure instead of waiting for failing reports.
about 1 year ago in Spotfire / System Administration 0 Future Consideration

command line to start/stop/restart services under Node Manager

Customer would like to have a command line tool to start/stop/restart services under Node Manager. Currently service start/stop/restart can only be done from Web UI. They need to schedule service start/stop/restart together with other applications...
about 1 year ago in Spotfire / System Administration 0 Future Consideration

capability to schedule to start/stop/restart services under Node Manager

Customer would like to have a capability to schedule to start/stop/restart services(WP/AS/TERR/Python) under Node Manager. Currently they are restarting these services using Windows Task Scheduler and OS command like "sc stop xxx & sc start xx...
about 1 year ago in Spotfire / System Administration 0 Future Consideration

add option to set limit on paging file size generated by each Analyst process

Customer has many end users (around 100) and all of them are connecting to a shared server(1.5TB memory available) via RDP and using Analyst to analyze huge amount of data (up to hundreds of GB). Analyst often pages data out to disk under "C:\User...
over 1 year ago in Spotfire / System Administration 0 Future Consideration

allow to set memory limit on each Analyst process

Customer has many end users (around 100) and all of them are connecting to a shared server(1.5TB memory available) via RDP and using Analyst to analyze huge amount of data (up to hundreds of GB). They want to set memory limit (by size of percentag...
over 1 year ago in Spotfire / System Administration 1 Future Consideration

append user agent information to access.log

Customer wants to use access.log to monitore user login. We understand user action log can do this as well but the customer wants to use access.log because it's easy to use. They need to distinguish access from Analyst application or Consumer brow...
over 1 year ago in Spotfire / System Administration 0 Future Consideration

Create a new licence to hidden (or blocked acces) about the URL connection

In this case, all analyst need to URL acces to information_designer to create "join" or column element but generally they don't in charge of manage connection (always manage by IT)... We need more option to manage information_designer rules. It's ...
over 1 year ago in Spotfire / System Administration 3 Future Consideration

show different RSS feed content on different clients (Analyst or Consumer)

Customer wants to show different RSS feed content on different clients (Analyst or Consumer), e.g. show "sentence A" on Analyst but show "sentence B" on Consumer. https://docs.tibco.com/pub/spotfire_server/12.0.3/doc/html/TIB_sfire_server_tsas_adm...
over 1 year ago in Spotfire / System Administration 0 Future Consideration

Admin view and export all users and their licenses types from the portal

Provide easy way to view and export list of all Spotfire Users, last time access and their licenses types from the portal so management can have better view and analysis over the users.
over 1 year 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