Language Selection

English French German Italian Portuguese Spanish

Jaspersoft Launches JasperIntelligence 1.0

Filed under
OS

Open source business intelligence architecture strengthened with new analysis product and enhanced server capabilities

SAN FRANCISCO —June 28, 2006—JasperSoft Corporation, the leader in open source business intelligence, today announced the general availability of JasperIntelligence 1.0. New in JasperIntelligence, JasperAnalysis brings people in small and mid-size organizations open source Online Analytical Processing (OLAP) capability, enabling easy to use analysis of data. With this release of JasperIntelligence, JasperSoft is announcing major new versions of the full line of JasperSoft open source products, including JasperReports, iReport, JasperServer, and JasperAnalysis.

JasperAnalysis, new in JasperIntelligence 1.0, gives users the ability to analyze large datasets in real-time. With an easy-to-use graphical interface, business users can easily organize information along different axes to identify trends, anomalies, and correlations within the data. For example, sales information for a multi-location component manufacturer can be organized by year, product, and region to find out what components to order for different sites. Advanced reports can be easily created in JasperIntelligence and viewed as HTML, PDF, Microsoft Excel, Microsoft Word documents, or other output formats.

“When we announced the JasperIntelligence architecture in April, we promised to bring BI to everyone. Thanks to the speed and efficiencies of open source development, we have reached a major milestone toward that goal with the launch of JasperIntelligence 1.0,” said Paul Doscher, CEO of JasperSoft.
JasperAnalysis is designed to make BI accessible to all employees in an organization. Accountants, executives, and operational managers can now easily access BI analysis tools that were previously available only to upper management. Unlike traditional BI analysis products, JasperAnalysis can be seamlessly integrated into new and existing applications.

Additional JasperAnalysis features include:

· Dynamic drill, pivot, filter, and charting;
· Easy-to-use web interface for end-users;
· High-performance relational OLAP engine;
· Maps onto existing relational data sources without requiring data movement; and
· MDX and XML/A compliant.

JasperServer has also been updated in the new version of JasperIntelligence. New JasperServer features include:

· New object-level security in JasperServer that provides fine-grained access control on a per- report and object basis;
· More complete web services API;
· Scheduling;
· Report distribution.

A new release of JasperReports and iReport is also now available. The latest release includes a plug-in for JasperServer and usability improvements.

“JasperSoft is fully committed to the open source community behind iReport, JasperAnalysis, JasperReports, and JasperServer,” said Doscher. “We’re continuously working with the open source community on feature enhancements and quality improvements to make the best open source BI products available to everyone.”

Led by the popularity of JasperReports, JasperIntelligence popularity has grown to more than 1 million downloads, 10,000 deployments, and 3,000 paying customers. Earlier this month, JasperReports for SugarCRM was named Editor’s Pick and SugarForge Project of the Month for June, having been downloaded more than 15,000 times from the SugarForge site since it was first released in March.

Availability
JasperSoft products are freely available as open source and can be downloaded at http://www.jaspersoft.com. Commercial licenses for JasperSoft products are available. The company also provides a complete set of support and services options for any size organization.

About JasperSoft
JasperSoft is the leader in open source business intelligence (BI). With more than one million downloads and 10,000 corporate deployments in 200 countries, JasperSoft offers the most widely used open source BI software in the world. The company’s JasperIntelligence architecture is comprised of open source server, report design, analytics, and commercial software for scalable enterprise applications. JasperSoft is based in San Francisco and is backed by leading venture capital firms Morgenthaler Ventures, Doll Capital Management, Discovery Ventures, and Partech International. More information is available at http://www.jaspersoft.com.
# # #

For media inquiries, please contact:
Craig Oda
Page One PR (for JasperSoft)
coda@pageonepr.com
650-565-9800 x102

More in Tux Machines

LWN on Linux: LTS, API, Pointer Leaks and Linux Plumbers Conference (LPC)

  • Cramming features into LTS kernel releases
    While the 4.14 development cycle has not been the busiest ever (12,500 changesets merged as of this writing, slightly more than 4.13 at this stage of the cycle), it has been seen as a rougher experience than its predecessors. There are all kinds of reasons why one cycle might be smoother than another, but it is not unreasonable to wonder whether the fact that 4.14 is a long-term support (LTS) release has affected how this cycle has gone. Indeed, when he released 4.14-rc3, Linus Torvalds complained that this cycle was more painful than most, and suggested that the long-term support status may be a part of the problem. A couple of recent pulls into the mainline highlight the pressures that, increasingly, apply to LTS releases. As was discussed in this article, the 4.14 kernel will include some changes to the kernel timer API aimed at making it more efficient, more like contemporary in-kernel APIs, and easier to harden. While API changes are normally confined to the merge window, this change was pulled into the mainline for the 4.14-rc3 release. The late merge has led to a small amount of grumbling in the community.
  • Improving the kernel timers API
    The kernel's timer interface has been around for a long time, and its API shows it. Beyond a lack of conformance with current in-kernel interface patterns, the timer API is not as efficient as it could be and stands in the way of ongoing kernel-hardening efforts. A late addition to the 4.14 kernel paves the way toward a wholesale change of this API to address these problems.
  • What's the best way to prevent kernel pointer leaks?
    An attacker who seeks to compromise a running kernel by overwriting kernel data structures or forcing a jump to specific kernel code must, in either case, have some idea of where the target objects are in memory. Techniques like kernel address-space layout randomization have been created in the hope of denying that knowledge, but that effort is wasted if the kernel leaks information about where it has been placed in memory. Developers have been plugging pointer leaks for years but, as a recent discussion shows, there is still some disagreement over the best way to prevent attackers from learning about the kernel's address-space layout. There are a number of ways for a kernel pointer value to find its way out to user space, but the most common path by far is the printk() function. There are on the order of 50,000 printk() calls in the kernel, any of which might include the value of a kernel pointer. Other places in the kernel use the underlying vsprintf() mechanism to format data for virtual files; they, too, often leak pointer values. A blanket ban on printing pointer values could solve this problem — if it could be properly enforced — but it would also prevent printing such values when they are really needed. Debugging kernel problems is one obvious use case for printing pointers, but there are others.
  • Continuous-integration testing for Intel graphics
    Two separate talks, at two different venues, give us a look into the kinds of testing that the Intel graphics team is doing. Daniel Vetter had a short presentation as part of the Testing and Fuzzing microconference at the Linux Plumbers Conference (LPC). His colleague, Martin Peres, gave a somewhat longer talk, complete with demos, at the X.Org Developers Conference (XDC). The picture they paint is a pleasing one: there is lots of testing going on there. But there are problems as well; that amount of testing runs afoul of bugs elsewhere in the kernel, which makes the job harder. Developing for upstream requires good testing, Peres said. If the development team is not doing that, features that land in the upstream kernel will be broken, which is not desirable. Using continuous-integration (CI) along with pre-merge testing allows the person making a change to make sure they did not break anything else in the process of landing their feature. That scales better as the number of developers grows and it allows developers to concentrate on feature development, rather than bug fixing when someone else finds the problem. It also promotes a better understanding of the code base; developers learn more "by breaking stuff", which lets them see the connections and dependencies between different parts of the code.

An update on GnuPG

The GNU Privacy Guard (GnuPG) is one of the fundamental tools that allows a distributed group to have trust in its communications. Werner Koch, lead developer of GnuPG, spoke about it at Kernel Recipes: what's in the new 2.2 version, when older versions will reach their end of life, and how development will proceed going forward. He also spoke at some length on the issue of best-practice key management and how GnuPG is evolving to assist. It is less than three years since attention was focused on the perilous position of GnuPG; because of systematic failure of the community to fund its development, Koch was considering packing it all in. The Snowden revelations persuaded him to keep going a little longer, then in the wake of Heartbleed there was a resurgent interest in funding the things we all rely on. Heartbleed led to the founding of the Core Infrastructure Initiative (CII). A grant from CII joined commitments from several companies and other organizations and an upsurge in community funding has put GnuPG on a more secure footing going forward. Read more

Ubuntu: GNOME, New Video, Ubuntu Podcast, Refreshing the Xubuntu Logo

  • Ubuntu 17.10: We're coming GNOME! Plenty that's Artful in Aardvark, with a few Wayland wails
    Ubuntu has done a good job of integrating a few plugins that improve GNOME's user experience compared to stock GNOME – most notably a modified version of the Dash-to-Dock and the App Indicator extensions, which go a long way toward making GNOME a bit more like Unity. It's worth noting that Ubuntu's fork of Dash-to-Dock lacks some features of the original, but you can uninstall the Ubuntu version in favour of the original if you prefer. In fact you can really revert to a pretty stock GNOME desktop with just a few tweaks. Canonical said it wasn't going to heavily modify GNOME and indeed it hasn't.
  • What’s New in Ubuntu 17.10 Artful Aardvark
  • Ubuntu Podcast: S10E33 – Aggressive Judicious Frame
    This week we’ve been protecting our privacy with LineageOS and playing Rust. Telegram get fined, your cloud is being used to mine BitCoin, Google announces a new privacy focused product tier, North Korea hacks a UK TV studio, a new fully branded attack vector is unveiled and Purism reach their funding goal for the Librem 5.
  • Refreshing the Xubuntu logo
    Earlier this year I worked a bit with our logo to propose a small change to it – first change to the logo in 5 years. The team approved, but for various reasons the new logo did not make it to 17.10. Now we’re ready to push it out to the world.

Intel Linux and GCC Work

  • Intel Begins Landing GFNI Support In GCC 8
    Intel compiler engineers have begun landing "GFNI" support within the GNU Compiler Collection as one of the new ISA extensions not expected until the Icelake processor debut.
  • Control-Flow Enforcement Technology Begins To Land In GCC 8
    Intel Control-flow Enforcement Technology (CET) support has begun landing within the GNU Compiler Collection (GCC) for this code safety feature. Patches have been in the works for several months while now the start of the patches are being merged to mainline. Coincidentally, at the same time Intel is also landing their GFNI instruction patches in GCC as well.
  • Intel Continues Landing New i915 DRM Features For Linux 4.15
    Jani Nikula has sent in another drm-intel-next update for David Airlie's DRM-Next tree. They continue prepping more updates to their Direct Rendering Manager (DRM) for targeting the upcoming Linux 4.15 cycle. There have already been several Intel "i915" DRM driver updates queued in DRM-Next for this new kernel version. Past pulls have included marking Coffeelake graphics as stable, continued Cannonlake "Gen 10" graphics enablement, various display improvements, and quite a lot of other low-level code improvements.