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
Hi Christian,
We have both running in the Microsoft Azure cloud, and by both I mean the Spotfire server, and an Azure cloud service accessing the Spotfire server via the Tibco provided Web Services API.
Understood, no way to do it, whether via a web service, or un-supported database sql statements. This means the enhancement request is the only way to go, hopefully it will be implemented in a future version.
Thank you!
Yanet Alba
Senior Software Engineer
T 305.328.9927
E Yanet.Alba@RelayHealth.com
RelayHealth
A division of McKesson
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Well you never said you were running Spotfire in the Tibco cloud. I guess that's one of the drawbacks of using the cloud, less customization is possible.You are stuck then, I know no other way of doing what you want.
Hi Christina,
And how would I access the Tibco database from a cloud service running in Microsoft azure?
Yanet Alba
Senior Software Engineer
T 305.328.9927
E Yanet.Alba@RelayHealth.com
RelayHealth
A division of McKesson
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
I understand what you are trying to do. What I am saying is that you can programatically update the data source name with an update SQL statement directly on the Spotfire Admin schema. This can easily integrate as part of your customer onboarding code. As I said before this is not supported but we have been doing this for years without any issues at all. And we have tested this on version 4.5 till version 7.8 without issues again. That's not to say this might break in the future, that's always the risk with using undocumented or unsupported features, but between doing a manual setup or having a totally automated solution I think that's a risk worth taking. Plus you can always test your integration before upgrading.
Hi Christian, we have the choice to rename the data source in the Information Designer as well, however, this is not what we want to do because we on-board our customers programatically using the web services api. What my enhancement request is calling for is a new web service method, part of the InformationModel service, or make the renaming part of the updateDatasource service.
Thank you.
I find it weird that you could pre-define data sources since presumable each customer will have some unique data sources. Perhaps there are some shared ones if by customers you mean different departments within a company. Anyway have a look at this query, the column name you want to update is TITLE:
SELECT *
FROM LIB_ITEMS
WHERE ITEM_TYPE IN (SELECT TYPE_ID
FROM LIB_ITEM_TYPES
WHERE DISPLAY_NAME IN ('datasource'))
Of course your Idea is still valid but it's not that couldn't do this via an update SQL statement.
Hello Christian,
Our Spotfire server is multi-tenant, we have several customers sharing the environment, having access only to their own folders. When we on-board a customer, we create a pre-defined folder structure, and copy a pre-defined templates folder to their folders. This pre-defined templates folders contains a set of analysis, a data source, and info links. We use the Spotfire LibraryService web service, method CopyFolders for this. This method copies data sources with the same original name. Then we use the InformationModelService method UpdateDataSource to re-point the data source to the customer own db, and to redirect the dependent elements. When we open Information Designer, and select the Data sources tab, all the data sources have the same name, so the only way to find a specific sutomer data source is in the Elements tab, and expanding the customer's folder structure.
I hope this makes sense, let me know if I need to provide mroe info.
Thank you!
Can be done easily on the database. It's not supported but I doubt you will face any issues. The real question is why do you need to copy data sources? We have multiple environments but we purposely leave data sources in a different folder so we can import reports, info links, elements, etc without touching data sources.
We copy data sources programatically (via web services api). It would be nice to have a service to rename them programatically also, as they all get created with the same name as the source, and can only be renamed manually via Information Modeler.