TIBCO Spotfire can connect to many different data sources in order to acquire data, from many vendors such as SAP, Oracle, IBM, or even just local files.
It can work with data using in memory mode, this makes the loading process faster.
It is easy to customize, and extendable with custom functions.
A very useful API is provided in order to integrate it easily with any web application.
The developing and runtime environment are very stable. The TIBCO Spotfire architecture environment is not complex. However, not all the runtime components are multiplatform. To be exact, the component whose purpose is to render the data in a web browser can be installed only on Microsoft machines. This is a very big limitation from this point of view.
The first approach was in 2010. I have used TIBCO Spotfire in four or five different projects as of 2016.
The TIBCO Spotfire product is really stable. No relevant issues have been encountered.
Most of the time the TIBCO Spotfire dashboard is used by business users. It was very common for them to notify us regarding weird behavior in business data patterns that was always ending with a discovery of bugs on the backend applications.
Technical support was always very good and fast. Always leading to a resolution of the problem immediately.
Together with TIBCO, my previous company was a partner of SAS. Recently, SAS provided a BAM and BI solution, but personally I have found it not comparable to Spotfire: huge memory consumption, no API available, not customizable.
The initial setup is quite easy, a few steps to perform before the application is ready.
A little bit more complex is the configuration of SSO, but the documentation is covering all the scenarios in a very clear way.
Implementation with TIBCO Spotfire consists basically of understanding the business requirements, and transforming them into readable dashboards and diagrams. Most of the time, in my case, implementation was made by a one-man team.
TIBCO Spotfire is a new challenge, very different from any typical implementation a developer used to do. Most of the time, it consists of understanding the data. Very often, that requires direct contact with the business department of the customer.
Hola,
Gasping at your brilliance! Thanks a tonne for sharing all that content. Can’t stop reading. Honestly!
i am testing ADB adapter 7.2 for 40 Million data processing.
As adb 7.2 supports Multithreading in Publication Service we want to use this feature.
but during testing we found that there is "JVM thread count" as well configurable during deployment of ADB adapter.
we are configuring "Number of Publication Service Thread" as 100 but keeping "JVM thread count" default as 8. In this case which will take precedence, will the Number of Publication Service Thread override the value of "JVM thread count" or we have to keep both these threadcount value same. we want 100 threads used by adapter(Heap is 4 GB).
It would be great if we get some clarification quickly.
Great effort, I wish I saw it earlier. Would have saved my day :)
MuchasGracias,
Mark Hetch