Any scenario where you need to reach back into TIBCO support is something I would highly avoid. Most responses at the second round get you pointed to engaging their professional services. The general mentality seems to be "since our product acquisition cost is low, why don't you engage PS to get the value you need" If you are looking at enterprise scenarios, I would highly recommend looking at other more established products.
As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.
Very intuitive tool - An Advanced reporting user can figure out in a day on the end to end operations.
Easy customization - Simple changes in UI makes it less headache for the end user who maintains the tool. Being an open source product (offers Jasper web services) makes a lot developer friendly compared to SSRS, Cognos etc.
Easy Connectivity - Can connect to any data source (can connect to multiple data sources) for a single report - can be customized.
Community - A very strong community available online, videos - on basic how to questions, also provides assistance to use case specific scenarios.
Ease of Reporting - Can create a reports with in few clicks with out struggle.
Domain Designer - A very powerful tool you can create a dataset using clicks with out writing SQL code.
OnDemand Scheduling - A very good scheduling feature and a has got lot more simplistic compared to other popular tools like Cognos.
Jasper Studio - Very good programmatic tool (desktop tool) lets you customize the reports more company specific, can embed complex coding with 3rd party languages like Java, Groovy (scripting language).
Easier to customize the Jasper Server GUI. More flexibility with the input controls look and feel and maybe more input control types to select from.
Have browser event functionality in the reporting itself.
An easier way to iterate through an object. Maybe an option that tells the report Java run-time to stop following the report sequential flow and first integrate through this stated object many times.
An easier way to create a list and add values to this list.
Maybe one could stipulate the process flow of what needs to be computed first in a given field.
The crosstab is a bit buggy on the Jasper studio side, so if that could be improved.
Better and more examples of custom components
The jive functionality on the tables needs an update. It looks so old and outdated.
Connection managers for online data sources can be tricky to configure.
Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
Mapping destination using OLE DB command is difficult as destination columns are unnamed.
Excel or flat file connections are limited by version and type.
Even though there are challenges with Architecture, sizing and other areas with Jaspersoft provided that Jaspersoft comes up with the right set of innovation, performance, scalability, and documentation in future it will be great expansion (win-win) situation for the clients and as well as Jaspersoft.
Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure
The overall performance of this platform has been excellent. It is easy to work with the user interface. Creation of digital content and publishing on our social media platforms during marketing has been easy. Running our applications and upgrading our system to meet international standards has been successful. The user dashboard displays reports and performance of all departments effectively.
SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.
SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.
We have only had a couple of tickets to be open while using Jaspersoft. Each time we have a very prompte responses that would meet our expectations. We always felt that our issues were being address in a timely manner
The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.
While the training was somewhat beneficial, a lot of what was taught to us was what we managed to figure out in the weeks prior. It did provide some useful tips and reference material, but overall something more tailored to our requirements would've been better.
New releases can be very buggy, also lacking when it comes to standard time zones and formats that are outside the US. As a company we never feel comfortable implementing a new release for at least 3-6 months due to errors that are found
The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools
Crystal reports is very expensive and does not integrate well with java based servers. Jasper also provides community edition, if we every want to downgrade the use, we always have the option of eliminating the server and using the reports as they are. Jasper also give you the opportunity to build BI on case by base basis including Dashboards.
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
Jaspersoft Community Edition has not had any significant impact on our ROI as we have purchased the commercial edition of the product.
The only impact on ROI is that when we bring on new developers, he or she can begin work using the community edition while awaiting the installation of the commercial edition.
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.
