Reporting engines (servers) comparison

CONFIDENTIAL

19 pages

Date: 16.10.2006

Version: 3.0
REPORTING ENGINES (SERVERS) COMPARISON

Table of Contents

1. 1.1 1.2 1.3 2. 2.1 2.2 2.3 2.4 3. 3.1 3.2 4. 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 5. 5.1 History..... 1 Revision History..... 1 Review History..... 1 Approval History.... 1 Introduction..... 2 Purpose..... 2 Summary..... 2 Scope...... 3 Definitions, Acronyms and Abbreviations.... 3 General information about reporting engines (servers).. 3 Overview of the reports delivery process... 3 Comparison criteria.... 5 Reporting engines (servers) comparison.... 6 Actuate 9 Business Intelligence... 6 Cognos 8 Business Intelligence.... 6 JasperReports 1.2.7 (iReport 1.2.6).... 6 JasperIntelligence 1.1.0.... 7 Eclipse BIRT..... 7 Microsoft SQL Server 2005 Reporting Services (SRSS)... 7 LGX Report..... 7 MicroStrategy..... 8 Crystal Reports (BusinessObjects Enterprise BI)... 8 Oracle Reports.... 8 Synaptris IntelliVIEW..... 9 Applix TM1.... 9
Comparison analysis..... 9 Comparison matrix.... 10

5.2 5.3 5.4

General remarks about report engine comparison... 10 Embeddable Engines.... 10 Business Intelligence solutions.... 10
Appendix A. Comparison table.... 1

1. History

1.1 Revision History
Version 0.1 1.0 Date 19.09.2006 21.09.06 25.09.06 26.09.06 26.09.06 26.09.06 27.09.06 27.09.06 2.0 28.09.06 Description of Changes Created Updated, executive summary added LGX Report added MicroStrategy added BusinessObjects products added Oracle Reports added Synaptris IntelliVIEW added Applix TM1 added Comparison analysis Summary and Scope updated Reformatted Updated upon results of internal review Reason Made by.Moroz, D. Boriskin,.Moroz D. Boriskin D. Boriskin A. Afanasyev.Moroz D. Boriskin D. Boriskin.Moroz

16.10.06

D. Boriskin

1.2 Review History

Version 1.0 2.0 2.0 Date 22.09.06 28.09.06 28.09.06 Reviewer E. Povalyaev A. Ignatov E. Povalyaev Reviewed Reviewed Reviewed Reference

1.3 Approval History

Version Date Approved by Signature or reference

2. Introduction

2.1 Purpose
The main purpose of this document is to present the results of the research established by Luxoft to compare several reporting engines and find out the most appropriate solution, which is eminently suitable to business and technical requirements of Customer.

2.2 Summary

We evaluated and compared several reporting engines and solutions available on the market. The evaluated products fall into two groups (embeddable reporting engines and Business Intelligence tools), both potentially useful depending on project context, and we evaluated them separately. We recommend using JasperReports (Luxoft Choice) as open-source Java-based reporting engine solution because of its stability and feature set; an alternative BIRT engine shows promise but is not ready yet. We recommend using Actuate (Luxoft Choice) in the BI category because of its feature set, and Luxoft experience with this product.

Com parison leaders

Net Value 15
0 Actuate 9 Business Intelligence Cognos 8 Business Intelligence JasperReports 1.2.7 (iReport 1.2.6)

2.3 Scope

The scope of this analysis is limited by the explicit list of engines for evaluation, including

! ! ! ! ! ! ! ! ! ! !

Actuate Business Intelligence; Cognos Enterprise; Jasper; BIRT; MS SQL Server 2005 Analysis & Reporting Services; LGX Report; Microstrategy; Crystal Reports (BusinessObjects Enterprise BI); Oracle Reports; Synaptris IntelliVIEW; Applix TM1.
Solutions are evaluated based on the list of criteria specified by the customer and listed below (section 3.1).
2.4 Definitions, Acronyms and Abbreviations

BI Business Intelligence

3. General information about reporting engines (servers)
3.1 Overview of the reports delivery process
Creating a functional reporting solution requires an understanding of user and business requirements. Existing data sources must be considered and new data stores must be designed to meet reporting needs. From this perspective, the process of creating useful reports consists of three activities:
Authoring: interface for creation of data sources, queries and data sets, and the report definition. Management: interface for managing and deploying report definition files, shared data sources, and configuration settings; it can also be used to view and export report data.
Delivery: Reports may be delivered to a user on demand or a custom application; it can also be scheduled for delivery through subscriptions. Reports can be delivered in the form of a web page, document, file, or even via e-mail.
To help end users support those activities reporting software must be adaptive to the current enterprise infrastructure, especially to the software that is used by information workers, developers and administrators. And this fact is the key to defining several categories of features that are quite common for todays reporting engines and may be used as a basis for their comparison. Here are those categories:
Web Browser support: Web browserbased solutions have become popular for a number of reasons. User accessibility takes on a completely new definition when special software is not required on the client computer. Of course, a web browser makes information available for viewing over the World Wide Web, but browser-based solutions are also a compelling means to deliver information in a controlled business enterprise environment. Whether users access resources within their corporate intranet environment or over the web, the browser paradigm has significantly changed the approach to application delivery. Some of the traditional challenges with browser solutions are the lack of consistent support for clientside script and components. These issues have largely been resolved with server-side rendering mechanisms that output product-independent HTML content. For viewing offline content, HTML documents require links to external files, such as images, sounds, and video. These issues have also been resolved by using a Multipurpose Internet Mail Extensions (MIME)encoded format called MHTML or Web Archive to encapsulate binary content within the page definition. Although not supported in all browsers, this format is a viable means to deliver extensible report content for live and offline viewing. HTML 4.0 works on different types of computers across the Internet and within a LAN on newer web browsers, and HTML 3.2 works with older browsers and on portable or hand-held devices. Office Applications support: Microsoft Office brings together a tremendous assortment of capabilities to assist report users at all levels. Microsoft Excel has been the mainstay tool for data collection and analysis. By rendering a report into Excel, the data may easily be reformatted, modified, or analyzed using formulas and calculations. This capability has been around for several years, but it required writing custom code to use the Excel object model from Access or Visual Basic to produce report data in Excelthis process was tedious at best. Now, pushing complex report data into a useful and well-formatted Excel document is simple. Microsoft Access continues to be the office workers database of choice. Data tracking and management solutions can be created with minimal cost and effort. Access and Excel both provide the Office Web Components that may be used to view pivot tables and charts. Programmability: There may be a possibility for reporting engines features to be duplicated in many cases and be extended through program code. Reports may be viewed in place within an application by using an external web browser window, integrated browser control, or a custom report viewer component. Report content may be rendered to a file for persistent storage to directly into a viewer or browser. Subscriptions: Subscriptions allow users to receive or gain access to reports on a regular schedule. Reports are delivered by e-mail or saved to files where they may be viewed offline at the users convenience. Report subscriptions may be set up for an individual user or large groups of users using data-driven subscriptions. To put this into perspective, effectively, reports may be delivered to any individual or size group of users in practically any readable format at any place and any time.

Report Formats: In addition to the three HTML rendering formats, document types can be used to control formatting elements, printing layout, and adding other capabilities. The PDF document format remains the most popular means for ensuring that documents are formatted exactly as they were intended. Rendering a report to a Microsoft Excel workbook gives users the ability to continue to massage data and perform calculations. Importing Data/Exchanging Data: Not all reports may be intended to be read or printed. Reporting engines usually provide several report rendering formats that can be used for export/import and data exchange. For example, using either the CommaSeparated Values (CSV) or XML formats, reporting engines provide a very convenient mechanism for intersystem data exchange or pushing data out to a trading partner. Ad Hoc Reporting: Another important component of a reporting platform is the ability for users to easily create their own reports. This means a feature that helps users to create a semantic layer on top of the database data. The semantic layer provides an easy-to-understand model for the user to navigate. Users will not have to understand how to query the underlying database to create reports. Such a possibility gives users an easy-to-use interface for building reports.

3.2 Comparison criteria

The following list of criteria is in no particular order.
1) 2) 3) 4) 5) 6) 7) 8) 9)
Application server support (including WebLogic and JBoss); DBMS support (including Oracle and Sybase); Supported report output formats (DOC/RTF, XLS, HTML, PDF, ODS); Supported report template formats (DOC/RTF, XLS); Support for formulas and macros in XLS and DOC reports; Support for password-protected fields in reports; Support for images and charts in report; Visual tools for report creation; Ad-hoc query capability;
10) OLAP support; 11) Batch report generation (performance, scheduling support, parallel query execution); 12) J2EE/web application integration support; 13) Is it open source; 14) Product and support pricing.
4. Reporting engines (servers) comparison
4.1 Actuate 9 Business Intelligence
Actuate 9 Business Intelligence provides a complete line of Excellent Data Sources products to meet the business analysis and reporting needs Good Output formats within the context of a business-specific application Excellent Application integration experience. The Actuate 9 Collaborative Reporting Excellent Performance Architecture blends the open technologies from the Eclipse Foundation BIRT (Business Intelligence and Reporting Excellent Manageability Tools) project with the scalability, performance and Sufficient Cost (invert) reliability of the Actuate iServer and the interactivity of AJAX (Asynchronous JavaScript and XML) into a unified Business Intelligence environment. The result is dynamic, interactive enterprise reports for any type of deployment and an ad-hoc web reporting environment that allows end-users and IT to collaborate and iterate on report definitions, effortlessly evolve report designs and dynamically craft interactive web reports.

4.2 Cognos 8 Business Intelligence
Cognos 8 Business Intelligence is a BI product with Good Data Sources capabilities of reporting, analysis, scorecarding, Good Output formats dashboards, business event management and data integration, on a single, proven architecture. Cognos 8 BI Excellent Application integration delivers a simplified BI environment that improves user Good Performance adoption, enables better decision-making, and serves as an Excellent Manageability enterprise-scale foundation for performance management. Sufficient Cost (invert) Cognos 8 BI architecture is built with Web services to deliver BI from a single extensible and flexible BI platform. Everything is zero-footprint and Web-based.
4.3 JasperReports 1.2.7 (iReport 1.2.6)
JasperReports is an open source Java reporting tool Data Sources that has the ability to deliver rich content onto the Output formats screen, to the printer or into PDF, HTML, XLS, CSV, Application integration and XML files. JasperReports is written in Java and can be used in a variety of Java-enabled Performance applications, including J2EE or Web applications to Manageability generate dynamic content. The main purpose of Cost (invert) JasperReports is to help create page-oriented ready-to-print documents in a simple and flexible manner. Satisfactory Good Satisfactory Satisfactory Sufficient Satisfactory
iReport is a visual report builder/designer for JasperReports written in java. iReport allows users to visually edit complex reports with charts, images, subreports, and more. iReport is integrated with JFreeChart, one of the most diffused open source chart libraries for java. The data to print can be retrieved through several ways including multiple JDBC connections, TableModels, JavaBeans, XML, etc.
4.4 JasperIntelligence 1.1.0
JasperIntelligence is the web platform project for JasperReports, iReport, JasperServer (business intelligence server designed for operational and departmental reporting and analytics), and JasperAnalysis. JasperIntelligence is an open source business intelligence platform from JasperSoft, providing common services like security and metadata management, and the capability to easily add additional functionality. Data Sources Output formats Application integration Performance Manageability Cost (invert) Good Good Good Satisfactory Satisfactory Sufficient

4.5 Eclipse BIRT

BIRT is an Eclipse-based open source reporting system for web applications, especially those based on Java and J2EE. BIRT has two main components: a report designer based on Eclipse, and a runtime component that you can add to your app server. BIRT also offers a charting engine that lets you add charts to your own application. Data Sources Output formats Application integration Performance Manageability Cost (invert) Sufficient Sufficient Satisfactory Sufficient Sufficient Good

4.6 Microsoft SQL Server 2005 Reporting Services (SRSS)
SSRS is a comprehensive and extensible reporting platform, which includes an integrated set of processing components, programmatic interfaces, and tools. Processing components are the basis for the multilayered architecture of SSRS and interact with each other to retrieve data, process layout, render, and deliver a report to a target destination. SSRS supports two categories of components: Data Sources Output formats Application integration Performance Manageability Cost (invert) Poor Satisfactory Satisfactory Good Satisfactory Excellent
1) Processors Ensure integrity of SSRS and supply an infrastructure that enables developers to add a new functionality (extensions). Processors itself are not extendable in this release of SSRS. 2) Extensions Assemblies that are invoked by processors and perform specific processing functionality, such as data retrieval. Developers can write custom extensions.

4.7 LGX Report

LGX Report is one of a family of web-based business intelligence applications created by LogiXML, Inc. LGX Report is used to design and generate web-based reports based on a wide range of data sources, such as Microsoft SQL Server, Microsoft Access, MySql, Cache and Oracle, as well other data sources accessible Data Sources Output formats Application integration Performance Manageability Cost (invert) Excellent Excellent Satisfactory Good Good Sufficient
through ODBC. The platform LGX Report hosted on is ASP.NET. The process of rendering the XML file to the report cannot be customized in the sense that you have no programmatic control over what is happening, but there is a lot of control over how the XML page is created to get some control over how a report looks.

4.8 MicroStrategy

The MicroStrategy 8 platform provides a solid Excellent Data Sources business intelligence (BI) product for analytic and Good Output formats enterprise reporting. The offering provides strong Good Application integration OLAP capabilities with extended access to SAP Satisfactory Performance BW cubes, along with strong administration and security capabilities and solid Microsoft Office Satisfactory Manageability integration capabilities. MicroStrategy includes an Satisfactory Cost (invert) enterprise reporting component (Report Services) within the core product; however; limitations in data access lower the overall appeal of the production reporting mechanism. Overall, MicroStrategy is a strong performer in both enterprise and analytic reporting with a greater emphasis on analytic reporting.
4.9 Crystal Reports (BusinessObjects Enterprise BI)
BusinessObjects company has a very complex Data Sources product: BusinessObjects BI (Business Output formats Intelligence). This product is integrated platform for Application integration data integration and visualization for enterprise. BusinessObjects Enterprise XI - powers the Performance management and secure deployment of Manageability specialized tools for reporting, query and analysis, Cost (invert) performance management, and analytic applications on a proven, scalable, and open-services oriented architecture. Excellent Good Good Excellent Satisfactory Satisfactory

4.10 Oracle Reports

Oracle Reports is the enterprise reporting Good Data Sources component of Oracles Business Intelligence (BI) Good Output formats offering. It enables an organization to convert data Good Application integration into information, and publish the information securely and reliably. Oracle Reports provides the Good Performance tools to create reports in pixel-perfect printable Satisfactory Manageability format and to publish reports on the corporate Web Poor Cost (invert) site as true Web pages. Oracle Reports is an award-winning solution that has successfully fulfilled the enterprise reporting needs of thousands of organizations for a decade and a half. Its extremely scalable and high-performance capabilities allow to publish reports to several thousand end users. It leverages Oracle Application Server Platform Security and Identity Management to make sure that the information is only available to authorized users. Furthermore, Application Programming Interfaces (APIs) documented in Reports Software Development Kit (RSDK), can be used to easily extend existing functionality or create completely new functionality to fit the business requirements.
4.11 Synaptris IntelliVIEW
IntelliVIEW is a reporting solution that allows users Good Data Sources to create interactive and pre-formatted reports Good Output formats (simple, parameterized and scheduled reports) Good Application integration from all popular database (Oracle, DB2, MSSQL Satisfactory Performance etc) and abstract data sources. Using IntelliVIEW Designer, report-creators can connect to Satisfactory Manageability databases and create rich, interactive reports Satisfactory Cost (invert) without the need for complex programming. IntelliVIEW Report Analyzer is used to view, analyze data, create charts, print and export reports to multiple formats, and distribute them through email.

4.12 Applix TM1

The Applix company line of products called TM1. Excellent Data Sources Basically, this is a MOLAP (multidimensional Good Output formats OLAP) solution as it uses linked hypercubes of data to analyze and to summarize large arrays of Satisfactory Application integration data in real time. TM1 applications are promoted Good Performance by the company as a helper to financial Satisfactory Manageability professionals for consolidating of financial data and Satisfactory Cost (invert) analyze this data. TM1 is based on OLAP (On-Line Analytical Processing) technology which enables users to quickly view and understand large sets of complex business data. Analysts, managers and executives can view data across multiple dimensions and drill down into the specific data underlying those summaries. TM1 does all the calculating in RAM, providing much faster response times - up to a million times faster compared to OLAP engines that store their data on a disk drive.

5. Comparison analysis

In this paragraph are shown most perspective report engines. The main candidates for further research will be chosen next. In the conclusion the basic actions on risks minimization at a choice of report engines are considered.

5.1 Comparison matrix

The report engines comparison matrix is presented in the Appendix A.
5.2 General remarks about report engine comparison
First, we should note that all the reporting tools under consideration break up into two main categories:
embeddable reporting engines, usually also including report design tools; and enterprise-class Business Intelligence solutions, usually including report engines and design tools per se, as well as analytic capabilities, server components for collaborative work, report scheduling, and integration with various business-specific applications.
The first category is represented here by JasperReports and BIRT, and the second includes all other products. Both categories of products can be useful depending on specific project requirements, e.g. embeddable reporting engine might be the easiest solution when there is a need for the specific report-generation functionality with predefined set of templates, and the BI solution may serve as the basis for the enterprise-wide information portal that integrates with business-specific application data or serves them as portlets. Therefore we will evaluate the two groups more or less separately.

5.3 Embeddable Engines

Of the two engines examined, JasperReports looks more mature and stable. It supports more output formats than BIRT, and the report generation component is more efficient and scalable. Both engines are open source, but their further development might take differing courses: JasperReports is developed under the aegis of JasperSoft with the ultimate goal of inclusion to JasperIntelligence product, and BIRT is a part of Eclipse Foundation, thus emphasizing the development tools/platform side. At this time we recommend using JasperReports as an embeddable Java reporting engine.
5.4 Business Intelligence solutions
To choose the winning solutions we did two sequential steps. First, we chose two aggregated criteria (described below), rated the solutions on these criteria, and plotted the results on the grid. Second, we filtered the products that are unsuitable for the customer environment. The first aggregated criterion is Readiness, meaning roughly the inverse of the effort needed to put it into production use, including (inverted) cost, manageability and

performance parameters. The second criterion is Facilities, including all other parameters (such as data source support, application integration, output formats and templates support) plus manageability. Manageability is aggregated twice because it affects both solution readiness for production and the potential diversity of supported features. Some of the products in this category, while being good and solid BI solutions, seem unsuitable to the customers requirements. For example, MS Reporting Services only works with the data in MS SQL Server database and can be deployed in the context of SQL Server installation. While it can be accessed via web services interface, its clearly unable to reach live data in Oracle and/or Sybase DB as well as be deployed in application servers of choice. Oracle Reports, on the other hand, works with Oracle data (as well as with other JDBC data sources, such as Sybase) and can be invoked from any Java application, but needs Oracle Application Server for deployment, which might add significant maintenance and support costs.
Magic square for report tools
Cognos Enterprise Actuate 8 Microstrategy 8 Platform LGX Report Crystall Report

Facilities

Synaptris IntelliVIEW
Oracle Reports Applix TM1

Jasper BIRT

MS SQL A&R - SRSS 2005
Actuate 8 MS SQL A&R - SRSS 2005 Microstrategy 8 Platform Cognos Enterprise Crystall Report Synaptris IntelliVIEW Jasper Oracle Reports Applix TM1 BIRT LGX Report
Looking at the plot we see that there are two clear leaders in this category Actuate and Cognos, with Crystal Reports the close third. Both top solutions are mature and functionally rich, integrate easily with J2EE-based applications and Oracle database, and can be deployed in JBoss as well as WebLogic. The main Crystal Reports drawback is its limited scalability in the standalone server mode that requires more programming effort for embedding the engine in the business application. Other products meriting consideration are Microstrategy (limited scalability, unclear pricing) and IntelliVIEW (relatively poor ready-to-use capabilities, no OLAP support). JasperIntelligence and LGX have even less functionality and we consider them too poor for further examination. Applix TM1 seems pretty good in terms of performance and functionality, including strong OLAP support, but it seems that much of the functionality is implemented on the Windows-based client (unfortunately the public documentation lacks much technical detail) and the pricing is not available at the moment.

The choice between the leaders is more complicated. They are mostly functionally equivalent, but nevertheless might differ significantly in specific areas; e.g. Cognos pricing is more convoluted than Actuates, and for some licensing arrangements (user/server count, conficuration) Cognos might be as much as twice more expensive than Actuate; ad-hoc query building capabilities of Cognos are more flexible and user-friendly than Actuates, though Actuate provides powerful e.Spreadsheet component that allows the user to play with dynamic data right in the Excel sheet. All in all, we suggest to use Actuate as business intelligence solutions based on Customer defined criteria with taking into account their priorities.
Appendix A. Comparison table
Table 1 Comparison table (#1)
Actuate 9 Business Intelligence Cognos 8 Business Intelligence JasperReports 1.2.7 (iReport 1.2.6) JasperIntelligence 1.1.0 Eclipse BIRT 2.1.1 MS SQL A&R SRSS 2005
1 1.1 1.2.1 2.3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11

COMPARISON CRITERIA

App server support

JBoss WebLogic

Y (no support) Y Y Y Y (RTF) Y Y Y N N Y Y N N Y Y
Y Y Y Y Y (RTF) Y Y Y N N Y N N N Y Y
Y (embeddable Java) Y (embeddable Java) Y (JDBC, Hibernate) Y (JDBC, Hibernate) Y (RTF) Y Y Y N N N N N N Y Y
Y N Y (JDBC, Hibernate) Y (JDBC, Hibernate) Y (RTF) Y Y Y N N N N N N Y Y
Y Y Y (JDBC) Y (JDBC) N N Y Y N (planned) N N N N N Y Y
not applicable not applicable SQL Server not applicable not applicable N Y Y Y Y N N N N N Y Y

DB support

Oracle Sybase

Report formats

output DOC/RTF output XLS output HTML output PDF output ODS templates DOC/RTF templates XLS formulas support in XLS macros support for DOC, XLS p/w protecetd fields in DOC images in report charts in report
Visual tool for report creation Ad-hoc reporting support OLAP support Report generation
performance scheduling capabilities
Actuate 9 Business Intelligence
Cognos 8 Business Intelligence
JasperReports 1.2.7 (iReport 1.2.6)

JasperIntelligence 1.1.0

Eclipse BIRT 2.1.1
MS SQL A&R SRSS 2005 Y (Workgroup, Standard, Enterprise) Y (Enterprise) Y

7.1 7.2

3rd-party (iReport etc.) N N
3rd-party (iReport etc.) Y Y
Y N N Medium, report in mem N

Very high, scalable Y

High, scalable Y
High, scalable Programmatic N (can be programmed explicitly) Y

7.8.1 8.2 9

parallel query execution

N Y Y Y N

N via JasperReports N N Y

N Y Y Y Y

J2EE/web application integration support
set report parameters start report generation
not applicable not applicable N

Open source

Product pricing

$500/named user

Avg 300$ per user
$3,899 - $24,999 per processor or $739 with 5 CALs $13,969 with 25 CALs per server

Support pricing

10000$ for SDK
Table 2 Comparison table (#2) COMPARISON CRITERIA
1 1.1 1.2.1 2.3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.7 Crystal Reports XI OracleReports 10g Release 2 LGX Report v7.4.0 MicroStrategy Platform 8 Synaptris IntelliVIEW v3.5 Applix TM1 v9.0
Y (own server) Y (own server)

Y Y Y Y Y Y

N (runs on OracleAS) N (runs on OracleAS)

Y Y (JDBC) Y Y Y Y

N N Y Y Y Y Y Y Y N N N N N Y Y Y Y (LGX Ad-hoc) Y (LGX OLAP)

N Y (portal integration)

Y (J2EE compatible) Y (J2EE compatible)

N N N N Y Y Y Y Y Y

N N Y N N Y Y Y Y Y

N N N N N Y Y Y N N

N Y Y N N Y Y Y Y Y

Crystal Reports XI

OracleReports 10g Release 2

LGX Report v7.4.0

MicroStrategy Platform 8
Synaptris IntelliVIEW v3.5

Applix TM1 v9.0

Very High, Scalable

High, Scalable

High, scalable
Y Y N 670 USD developer edition (3211 - 5 users); 7500 USD - Crystal Report Server 5 concurrent acesses; + 3129 USD Advanced developer
Y (Java client, Web Services)
Y Y N Y Y N Free (LGX Report and LGX OLAP Express), $995 $9,995 per processor (LGX AdHoc) Y Y N

20,000USD per processor

Have not information
195 USD for one product (online and phone calls); base offline support cost free
4,400 USD for software update license and support (5 years)

$749 - $4,999

Release Notes
Applix TM1 TM1 9.0 Release February 24, 2006

In This Release

This document contains information important to TM1 9.0 customers. The following information is provided: TM1 9.0 Platform Support Language Support Statement Important Installation Notes and Tips TM1 Licensing New Features of TM1 9.0 Known Issues in TM1 9.0 Fixed Issues in TM1 9.0

TM1 9.0 Release Notes

TM1 9.0 Platform Support
The following table outlines platform support for the TM1 9.0 release. A complete platform support matrix is available on the Applix Web site and on your installation CD.

Platform Support Notes

In addition to the platform support matrix, administrators installing TM1 products should note the following: TM1 Perspectives requires Microsoft Excel 2000 or higher. Applix recommends running TM1 Web on Microsoft Internet Explorer 6.0 or higher. Microsoft no longer supports IE 5.5. If you are running TM1 Web on IE 5.5 and experience issues that are browser-version related, Applix will make a reasonable effort to address these issues. Please note, however, that these efforts may be limited by the support available through Microsoft. Applix strongly recommends that you run TM1 Web with IE 6. Known issues with IE 5.5 are documented in the Known Issues section of these release notes. Microsoft Excel 2002 0r 2003 must be installed on the web server used to deliver TM1 Web. If one of these versions of Excel is not present on the web server, you cannot access Websheets in TM1 Web. TurboIntegrator connectivity with SAP BW requires version 6.4 of the SAP GUI, and version 3.5.1.563 of the SAP BW OLE DB Provider, and version 3.1 Patch Level 15 of SAP BW. TurboIntegrator processes support OLE DB 2.6 and later.
Excel Feature Support in TM1 Web
Applix publishes a document detailing the support for various Excel features in TM1 Web. This document, TM1Web.Net Feature List.pdf, is available on the Applix Website under Service & Support >> Download Docs.
The purpose of this document is to provide Applix customers a way to identify differences between TM1 Web and Excel when importing Excel spreadsheets to TM1 Web and when exporting TM1 Websheets and Cube Viewer charts to Excel. These differences primarily appear in charts, although other exceptions are noted in the document.
Language Support Statement
TM1 9.0 is available in English only. TM1 9.0 is supported only on English versions of the Windows OS, in conjunction with English versions of Excel and Internet Explorer.

End-of-Life Statements

The in-process local server will not be supported beyond the 8.4.x releases.
Important Installation Notes and Tips
It is very important that you read the installation help prior to running the installation program. The installation help is available on the Applix web site under the Documentation link. It is also available on the Applix CD. On the CD, open the Help folder, and then click on the file Installation.htm to run the Installation help. Prior to installing the new software on a machine where TM1 has been previously installed, you must un-install the older version first, using Microsofts Add/Remove Programs utility. If you uninstall a previous version of TM1 Web in preparation for a TM1 9.0 installation, you must manually delete the TM1 Web virtual
directory from IIS, as well as the physical directory from the IIS root directory. In most cases this directory is C:\Inetpub\wwwroot. The <Applix_Home>\Custom directory is not deleted when you uninstall. This directory contains files and applications which you may have created or modified. If you are upgrading from an earlier version of TM1, copy the contents of this directory to a safe place on your hard disk, then delete this directory. It is especially important to delete the <Applix_Home>\Custom\config directory. This directory contains configuration files, such as entsvr.conf. These files are rebuilt by the installation. The location of the Tm1p.ini file was changed between TM1 versions 8.2.x and TM1 version 8.4. In TM1 8.2.x, Tm1p.ini is installed in c:\windows. When a TM1 Client runs, Tm1p.ini file is copied to c:\Documents and Settings\<user>\TM1 where <user> is the name of the user running the client. In TM1 8.4 and subsequent releases, Tm1p.ini is installed in C:\Documents and Settings\All Users\Application Data\Applix\TM1. When a TM1 Client runs, the Tm1p.ini file is copied to C:\Documents and Settings\<user>\Application Data\Applix\TM1 where <user> is the name of the user running the client. The Tm1p.ini file in C:\Documents and Settings\<user>\TM1 is not removed when you un-install TM1 8.2.x. This ensures that client options are retained when upgrading from TM1 8.2.x to TM1 8.4 or later versions. If you un-install and re-install TM1 while changing some installation options, the changed options may not be written to the Tm1p.ini file. If you want to uninstall and re-install the same version of TM1, you should first delete Tm1p.ini. When you install the web components for TM1 Web, be sure that the permissions on the directory into which your web components are installed are set to Everyone. If the permissions on this directory are limited, you may not be able to run your Applix web client.

TM1 Licensing

You must license all the TM1 products you install before you can use them. Please note the following: If you are upgrading to TM1 9.0 from a previous TM1 release, your old license file will work. If you are upgrading from a previous release and upgrading server components adding Planning Manager or SAP support, for example you will need a new Tm1s.lic file. New customers installing TM1 9.0 for the first time should receive an email from Applix containing TM1 license codes. Follow the instructions under Licensing TM1 Products on Microsoft Windows to generate new license files for your product. TM1 9.0 Release Notes 10

TM1 License Files

There are two files that contain TM1 license information. These files are generated by the TM1 License manager, as follows:
Tm1s.lic The TM1 server license file. This file should be located in
the data directory of your TM1 server. Many TM1 components and products are licensed as options in Tm1s.lic. Those options are listed in the following table:
License TM1 server Prerequisites None Description Licenses the TM1 server Licenses the TM1 server to access the advanced features of TM1 Turbo Integrator. Licenses the TM1 server to support the Planning Manager application. Licenses the TM1 server to support TurboIntegrator SAP BW integration. Licenses the TM1 server to support the TM1 Financial Reporting application.

TurboIntegrator

TM1 server

Planning Manager

SAP BW Integration

Financial Reporting

Tm1p8.lic The TM1 Perspectives license file. This file should be located on each machine from which you want to run TM1 Perspectives or TM1 Architect. The file should be in the <Documents and Settings>/All Users/Application Data/Applix/TM1 directory on the workstation.
There is no license file required for TM1 Web in version 9.0.
License Distribution in a Distributed System
TM1 systems can be distributed across several physical machines. In large company environments, you might have Perspectives clients, Architect clients, a TM1 server, a TM1 Web server, and TM1 Web clients all running on separate physical machines. The following figure shows how licenses files are distributed in this environment.

Licensing TM1 Products on Microsoft Windows
To license a new TM1 product on Microsoft Windows, follow these steps: 1. After you install TM1, click Launch License Manager. The following dialog box appears:
2. Choose a component from the Select Component to License field. The default path for the license file for the component you chose appears in the Path to License File field. Open the email sent to you by Applix. (If you have not received licensing information from Applix, call us at one of the locations listed below.) The email includes license information. TM1 9.0 Release Notes 14
Applix Office UK Germany Asia Pacific
Number to Call +44 (0) 4353 +24447780-12 +61414339980 +61422111109

1-866-403-2991

3. Copy and paste this information into panel marked Paste New License Here: 4. Click Validate and Save. 5. Repeat steps 2 through 4 for each TM1 product you installed.

New in TM1 9.0

This section describes new functionality introduced in the TM1 9.0 release.
New TM1 Web Server and Client
TM1 9.0 includes a new optimized TM1 Web server and a new TM1 Web client. The server delivers better performance and significantly increased functionality, while the client provides an updated look and feel in comparison to previous TM1 Web releases. For complete information on the new TM1 Web product, see the TM1 Web Guide.

Cube Viewer in TM1 Web

TM1 Web cube viewers provide the ability to use any TM1 view that resides on your TM1 server. You do not have to publish an Excel spreadsheet to see your TM1 data. The following figure shows a TM1 Web cube viewer.
The cube viewer allows you to pivot your view by dragging and dropping dimensions. The cube viewer allows you to enter data into N-level element cells, review your changes before submission to the server, and submit the complete set of data changes to TM1. The cube viewer includes many of the most powerful features of TM1, including a full-featured subset editor, automatic recalculation, and zero suppression.

Charting in TM1 Web

TM1 Web 9.0 includes the ability to view cube viewer data in grid format, chart format, or a combined grid/chart presentation. To view data in grid format, click To view data in chart format, click on the cube viewer toolbar. on the cube viewer toolbar.

To view data in a combined grid/chart presentation, click
When you install TM1 Web, Applix installs Dundas Charts technology. Dundas Charts provides the charting functionality of TM1 Web. Dundas Charts technology is delivered through two DLLs that are installed on your IIS web server:
C:\Inetpub\wwwroot\TM1Web\bin\DundasWebChart.dll C:\Inetpub\wwwroot\TM1Web\DundasWinChart\DundasWinChart.dll
Zoom In/Zoom Out in TM1 Websheets
Three Zoom options on the TM1 Websheet toolbar let you change the magnification of Websheets.
Managing the Display of Objects in the TM1 Web Navigation Pane
The navigation pane of the TM1 Web client displays three object nodes: the Application node, the View node, and the Administration node.
The Application node is always visible in this pane, but you can selectively enable or disable the display of the View and Administration nodes. The display of these nodes is determined by key values in the Web.config file, which is located in the TM1Web directory on your web server. If you accepted the default installation directory during your TM1 Web installation, the full path to this file is C:\Inetpub\wwwroot\TM1Web\Web.config.
To globally enable or disable the display of object nodes in TM1 Web: 1. Open Web.config in a text editor. The keys that determine the display of object nodes appear at the top of the file in the TM1Web Configuration section. 2. Set a key value to determine the display of the View node. To enable the display of the View node, set the NavTreeDisplayServerView key value to Y. To disable the display of the View node, set the
NavTreeDisplayServerView key value to N.
3. Set a key value to determine the display of the Administration node. To enable the display of the Administration node, set the NavTreeDisplayAdministration key value to Y. To disable the display of the Administration node, set the
NavTreeDisplayAdministration key value to N.
4. Save and close Web.config. You must log out of TM1 Web and log back in to see the effect of your edits to Web.config.
Object Administration through TM1 Web
TM1 Web includes the ability to perform basic administration tasks through your web browser. For example, you can run TurboIntegrator processes from TM1 Web. You can also view and modify object properties for TM1 clients, cubes and dimensions.

Planning Manager in TM1 Web
Planning Manager 1.2.1 is supported in TM1 Web 9.0. If Planning Manager is licensed on your TM1 server, users can access the Planning Manager toolbar to open and complete Planning Manager tasks in TM1 Web.
NOTE: The Planning Manager administration console is not supported in TM1 Web. Administration functions, such as setting up mapping and security for Planning Manager tasks, must be done through Excel. The display of the Planning Manager toolbar in TM1 Web is determined by key values in the Web.config file, which is located in the TM1Web directory on your web server. If you accepted the default installation directory during your TM1 Web installation, the full path to this file is C:\Inetpub\wwwroot\TM1Web\ Web.config. To enable the display of the Planning Manager toolbar in TM1 Web: 1. Open Web.config in a text editor. 2. Locate the DisplayCustomToolbar key. This key appears near the top of the file in the TM1Web Configuration section. 3. Set the key value to Y. 4. Locate the CustomToolbarURL key. 5. Ensure that this key value is set to TM1WebPlanManToolbar.aspx. TM1 9.0 Release Notes 21
6. Save and close Web.config. You must log out of TM1 Web and log back in to see the effect of your edit to Web.config.
New Look and Feel for TM1 Server Explorer
The TM1 Server Explorer has been enhanced to include a new look and feel. The icons in the user interface are updated for a more modern look. The new look is available from any TM1 Server Explorer running on Windows XP or later. The following figure shows the enhanced Server Explorer.
Changes to TM1 Products in TM1 9.0
Some important changes to TM1 products are included in TM1 9.0. This section lists those changes.
Functionality Differences between TM1 Web 8.4 and TM1 9.0
Certain features of TM1 Web 8.4 are not included in the new TM1 Web product. The following table lists these features. Feature VBA add-in support Description TM1 Web 8.4 allowed administrators to execute an Excel VBA add-in from the web client at login time. This functionality is not included in TM1 Web 9.0. Dynamic slices are supported in TM1 9.0, but when a dynamic slice is opened as a Websheet in TM1 Web, dynamic slice functionality is disabled. For example, you cannot edit row or column subsets in slices accessed through Websheets, nor can you drill down/roll up consolidations. When you publish a dynamic slice to an application, the state of the sheet at time of publication will be reproduced when you open the slice in a Websheet. Any formatting present at publication will show up in the Websheet, but any dynamic (element-based) formatting applied to the slice will not update in the Websheet.

New Icons in TM1 Web and Server Explorer
The following icons have been updated in TM1 Web and the Server Explorer. The TM1 9.0 documentation set references the old icons exclusively. Icon Name Websheet View Current Icon Old Icon

Known Issues in TM1 9.0

This section describes known issues in the TM1 9.0 release.
Dundas Chart Problem: Text Display in Charts (297205)
Text display for legends and other text elements in Websheet and Cube Viewer charts can be problematic when you shrink the size of the browser window, then recalculate the view. For example, consider the following chart:
to recalculate If you reduce the size of the browser window, and click the chart, the text in the chart can appear crowded and illegible, as shown in the following figure.
This is a problem with the Dundas chart package. Applix is working with Dundas to address this.
Problem Running the TM1 Web client with Older Versions of Internet Explorer (299857)
Applix testing revealed a problem on a German version of Windows XP. Using German Windows XP Internet Explorer version 6.0.2800.1106.xpsp2.032422-1633, the TM1 Web client crashes when you drag and drop dimensions in a cube viewer. Upgrading the Internet Explorer software to a more recent version (6.0.2800.1106.xpsp2.050301-1526) solved the problem. This problem also appeared on German version of Windows 2003. Upgrading Internet Explorer to version 6.0.3790.1830 with service pack 1 solved the problem. If you are running a version of Internet Explorer older than these two recommended versions, Applix recommends updating your browser software.
TM1 Web Navigation Pane Does Not Display Properly in IE 5.5 (304126)
When you first open the TM1 Web client in Internet Explorer 5.5, the TM1 Web navigation pane does not display properly. The contents of the pane are largely obscured, as in the following image.
To restore the display of the navigation pane, simply move the mouse pointer over the pane. TM1 9.0 Release Notes 31
Excel Crashes When Copying/Pasting Slice Cells That Reference Hidden Cells (298323)
When Excel is in Automatic calculation mode, copying and then pasting a slice cell that references any hidden cell may crash Excel. If you encounter this problem, you can set the worksheet containing the TM1 slice to Manual recalculation mode to safely copy/paste slice cells.
Functions with Grouped Arguments Cause Unhandled Exceptions in TM1 Web (298860)
TM1 Web cannot parse multiple function arguments grouped as a single argument enclosed in parenthesis. For example, a function in the form DBRW('SData:SalesCube', (A1, A2, A3, A4, A5, A6, B1, B2), C1, D3) will cause an unhandled exception in TM1 Web. To work around this problem, remove any parenthesis from grouped arguments.
Generating PDF Reports from TM1 Web (298954)
To generate PDF reports from TM1 Web, the following items must be installed on the computer where the TM1 Web components are installed: GNU Ghostcript Provides an interpreter for the PostScript language and the PDF file format The Tm1p.ini file Includes a parameter, TM1PostScriptPrinter, which determines the printer driver used to generate PDF

These components are automatically installed and configured when you perform a standard TM1 Web installation. However, these components are not installed if you perform a custom TM1 Web installation and choose to install only the TM1 Web components.
To ensure that users can generate PDF reports from TM1 Web you must install one of the TM1 clients (Architect, Perspectives, or Client) along with the TM1 Web components when you perform a custom TM1 Web installation.
TM1 Application Filenames Containing Characters from the Extended ASCII Character Set Cannot Be Viewed in TM1 Web (301521, 305552)
You can successfully add an external file to a TM1 application, either by reference or by uploading the file directly to the TM1 server, when the filename includes characters from the extended ASCII character set. However, only such files that have been uploaded to the TM1 server can be opened in TM1 Web as a Websheet. If a TM1 Web user attempts to open a filename containing characters from the extended ASCII character set, and that file has been inserted into an application by reference, the user receives an error stating that the file does not exist:
To ensure that all external file with names containing characters from the extended ASCII character set are available to TM1 Web users, always upload such files directly to the TM1 server. For complete details on adding external files to TM1 applications, please refer to the TM1 Clients Guide.
Need to Log Out and Back In to TM1 Web after Network Disconnect (304165)
If a TM1 Web user is logged in to the TM1 Web system, and either the TM1 server or the Web server used to deliver TM1 experience a momentary interruption of network connectivity, the TM1 Web user will not be able open any Websheets or Views. In this case, even though the TM1 server or Web server has reestablished a network connection, the TM1 Web user must log out and back in to the TM1 Web client to restore access to Websheets or Views on the TM1 server.
Hyperlinks in Websheets Must Be Fully Qualified (304129)
Only fully qualified HTTP hyperlinks work in TM1 Websheets. Hyperlinks using relative paths or UNC paths return an error in Websheets.

Rollup Consolidations Not Supported on Title Dimensions in Websheets(304124)
When you open the TM1 Web Subset Editor from a title dimension in a Websheet, the Advanced mode of the Subset Editor allows you to create a rollup consolidation from selected elements.
However, Websheets do not support rollup consolidations on title dimensions. Any Websheet with a rollup consolidation on a title dimension displays an empty data set.
Cannot Attach an Excel File to an Application When File Extension Uses Capital Letters (303002)
If you attempt to attach or upload an Excel file to a TM1 Application from the Server Explorer, and the Excel file extension appears in capital letters (.XLS), TM1 does not recognize the file as a valid Excel file. In this circumstance, TM1 issues the following error:
To work around this problem, save all Excel files with lower case characters in the file extension (.xls).
Switching from Advanced Mode to Simple Mode in TM1 Web Subset Editor (305333)
The TM1 Web Subset Editor may freeze or report an error in the following scenario: 1. Open the Subset Editor. 2. Click the Advanced button. 3. Select one or more elements in the Available Elements pane.
4. Click any button or select any option on the Subset Editor toolbar. For example, click the Keep button or select an alias from the Alias list. 5. Click the Simple button. The Subset Editor reverts to Simple mode, but the displayed elements are frozen; you can make no further modifications to the subset while in Simple mode. Double-clicking an element may, in some cases, cause a runtime error. When this occurs, you can safely close and then reopen the Subset Editor.
Cell Font Set To Automatic Does Not Appear In TM1 Websheets (303242)
In the following scenario, cell values do not display correctly in TM1 Web when the cell font is set to Automatic. 1. Select one or more entire rows in an Excel worksheet. 2. Set the Fill Color and Font Color for the rows to the same color value. TM1 9.0 Release Notes 36
Any cell values are now hidden, because there is no discernible difference between the font color and fill color. 3. Select a range of cells within the rows you selected in Step 1. 4. Set the Font Color for the selected cells to Automatic. Values in the selected cells are now visible in the worksheet. 5. Save the worksheet as an external file in a TM1 Application. 6. Open the file as a Websheet in TM1 Web. The contents of the cells you formatted as Automatic are not visible in the Websheet. The Websheet ignores the Automatic formatting and uses the Font Color you selected in Step 2.

Multiple Element Names Overlaid in TM1 Windows Subset Editor (300314, 304200)
In some circumstances that are very difficult to reproduce, several element names are overlaid in the first position in the TM1 Subset Editor, as in the following image:
In the course of testing, Applix has reproduced this situation only on laptop computers. Further, this situation occurs only when the Properties pane is enabled in the Subset Editor. at the corner of If you encounter this issue, click and drag the handle the Subset Editor to resize the window. You must resize the window prior to performing any actions in the Subset Editor.
Formatting Order of Precedence Varies between TM1 Windows Cube Viewer and TM1 Web Cube Viewer (305317)
When multiple format attributes apply to a given cell in the Windows Cube Viewer, the following order of precedence determines which format is displayed: 1. Columns In the event of stacked dimensions, the dimension closest to the data grid takes precedence. 2. Rows - In the event of stacked dimensions, the dimension closest to the data grid takes precedence. TM1 9.0 Release Notes 38
3. Titles In the event of multiple title dimensions, precedence begins at the left-most title dimension. When multiple format attributes apply to a given cell in the TM1 Web Cube Viewer, the following order of precedence determines which format is displayed: 1. Columns In the event of stacked dimensions, the dimension farthest from the data grid takes precedence. 2. Rows - In the event of stacked dimensions, the dimension farthest from the data grid takes precedence. 3. Titles In the event of multiple title dimensions, precedence begins at the right-most title dimension.
Table of Other Known Issues
The following table provides an inquiry number and brief summary of other known issues in the TM1 9.0 release.

Inquiry #

280570

Summary

The user interface for the ETLDAP utility is not localized; only an English version is available. The UI will be localized in a future TM1 release. Launching the Set Element Order dialog creates a duplicate copy of the dimension, resulting in a memory leak. In some instances, the progress bar on the Internet Explorer status bar continues to display after you successfully close a Websheet. Websheets containing a large number of ELCOMP functions (or any other non-DBRW functions) do not display in the TM1 Web client. The Filter option is not available on the Version Status tree when you use Planning Manager on TM1 Web. The shortcut menu is not available when you right-click a task in Planning Manager on TM1 Web. The default action button is not available in the Task window when you use Planning Manager on TM1 Web. Opening TM1 Web cube viewers containing very large row or column subsets (1000s of elements) can cause aspnet_wp.exe to recycle due to lack of memory. In such an event, the cube viewer does not display but your TM1 Web session remains active. In some rare instances, the row and column headings of 40

303024

304197
2. Select the title dimension containing the accented element in the Websheet Export dialog box. 3. Click OK.

304237

When you attempt to open a Websheet that contains a chart which references a single cell, TM1 Web issues a Specified cast is not valid error. In some rare circumstances, text attribute values can appear garbled when viewed in an }ElementAttributes control cube. If you encounter this problem, you can click on the Cube Viewer to restore the correct appearance of the text attribute values. In some instances where a Websheet contain a large number of empty or sparsely populated rows, along with large and/or multiple images, the images are not rendered correctly in the Websheet.

305310

305390

Fixed Issues in TM1 9.0

The following table lists significant customer-reported issues that are resolved in TM1 9.0. This list may not be complete. If you have a question regarding the status of an inquiry, please contact Applix customer support.

275639

Zoom functionality is now available in TM1 Websheets. There are three options: Zoom In, Zoom Out, Restore

Original Zoom.

276455
Help for the VUSLICE macro function formerly indicated that the slice is inserted starting at the current cursor position in the active worksheet." The help has been corrected to indicate that the slice is inserted starting at the top left cell (A1 or R1C1) in the active worksheet.

277050

Help for the SUBNM function incorrectly documented Attribute as the final function argument. The help has been changed to use Alias as the final argument, with clear description of the argument and details of what happens when you use this optional argument.

281161

The TM1 Security Guide incorrectly described how reset default security for a dimension. The correct procedure is described in the 9.0 TM1 Security Guide.

281896

In versions of TM1 prior to 9.0, the Help window was configured to always remain on top of other 45

applications. In 9.0, you can move other application windows on top of the Help window.

284219

The W_DBSENABLE function was not publicly documented in previous version of TM1. This function is documented in the online help for TM1 9.0.

284566

Beginning in TM1 8.4.2, the ProcessBreak TurboIntegrator function was not working correctly. This problem is resolved in TM1 9.0, as well as in 8.4.3. The online help for the DBRW worksheet function did not contain specific information on recalculating worksheets with VBA. The help for the function now note the following: If you use VBA to calculate a worksheet containing DBRW functions, you must call the W_CALC TM1 macro function to calculate the worksheet. Do not use the VB Calculate method to calculate a worksheet containing DBRW functions; doing so causes each DBRW function to be executed individually, defeating the purpose of the function.

285514

285753
Previous versions of TM1 Web did not support the Freeze Panes Excel feature in Websheets.
Freeze Panes is supported in TM1 9.0 Websheets.

286118

In previous versions of TM1, the online help for the DimensionDeleteAllElements TurboIntegrator function did not explicitly state that deleting an element deletes all cube data associated with the element. 46

287033

This oversight has been addressed in TM1 9.0. In some previous versions of TM1, any attempt to use a processing worksheet when the worksheet name contained a period character (. ) would cause a File Not Found error. For example, the file name sheet 8.7.xls would cause such an error. This problem is resolved in TM1 9.0. The syntax described for assigning TurboIntegrator variables was incorrect in the 8.4.2 online help. This has been corrected in TM1 9.0. In previous versions of TM1, Help examples for TurboIntegrator functions used the ASCII 145 quote character, making it impossible to copy examples directly into TurboIntegrator scripts. This TM1 9.0.help uses the ASCII 39 quote character in all examples.

287459

297410

297902

In some previous versions of TM1, if user attempted to start Perspectives or Architect with an expired tm1p8.lic file, Excel or Architect (respectively) would crash. This problem is address in TM1 9.0. An attempt to start Perspectives or Architect without a valid license file now returns an error.

298032

In early beta versions of TM1 9.0, an attempt to open a dimension with a name containing the # character caused an error in the TM1 Web Subset Editor. This problem is resolved in final 9.0 release. The help for the DBRW and DBSW functions did not explicitly state that these functions cannot be used in 47

300114

processing worksheets. The 9.0 help has been updated to reflect the fact that only DBR/DBS functions can be used in processing worksheets.

300293, 297279

In some previous versions of TM1, shutting down an inprocess local server could cause the TM1 client to hang. This problem is resolved in TM1 9.0. Please note, however, that Applix does not formally support the inprocess local server in the 9.0 release. In TM1 8.4.x, a drill-through from a dynamic slice produced KEY_ERRs if performed after a drill-through from a classic slice. This issue is resolved in TM1 9.0. In some previous versions of TM1, undoing zero suppression across multiple slices on a shared axis could cause KEY_ERRs in the slices. This problem is resolved in TM1 9.0. In TM1 8.4.2, when two dynamic slices were linked along the row as axis, and the right-most slice contained all zeros in the final column, that final column was not suppressed when zero suppression was applied to the slices. This problem is resolved in TM1 9.0. In some previous versions of TM1, if the TM1 server was configured to use integrated login, read-only users could incorrectly occupy read/write ports on the server. This could lead to Maximum Number of Connections Exceeded on the Server errors when legitimate 48

300294, 297321

300297, 297326

300295, 298052

300336, 287566
read/write users attempted to log in to the server. This problem is fixed in TM1 9.0. Previous versions of the Applix installation program did not install the 64-bit ODBO provider. This is resolved in the 9.0 installation program. In previous versions of TM1, DBRA functions, rather than returned function values, appeared in TM1 Reports when using the Snapshot option. This problem is resolved in TM1 9.0; TM1 Reports now display the correct function values.
300337, 286239 300338, 287614

300339, 286418

In previous versions of TM1, a drill-through from an Excel worksheet to a relational datasource placed the drill-through results in a new sheet of the current workbook. In TM1 9.0, a drill-through from an Excel worksheet to a relational datasource inserts the drill-through results in an entirely new workbook.

302370, 300225

In TM1 8.4.2, NON EMPTY statements in an MDX query caused the TM1 server to hang. This problem is resolved in TM1 9.0. In TM1 8.3 and 8.4, processing worksheet recalculated one extra time after processing was complete. This problem is resolved in TM1 9.0. When loading some very large dimensions, TM1 8.4.3 used four times more memory for a given dimension compared to TM1 8.4.2.

302402, 297082

302553, 302391, 298569

302569, 299676

This problem is resolved in TM1 9.0. In TM1 8.3, executing a TurboIntegrator process using a non-existent data file sometimes caused a TM1 server crash. This problem is resolved in TM1 9.0. In previous versions of TM1, blank lines/rows in a rules worksheet were ignored when the rule was compiled and saved as a.rux file. Consequently, line error reporting, which is based on the.rux file, would be inaccurate. This problem is resolved in TM1 9.0; blank lines/rows in a rules worksheet are retained in the associated.rux file.

302574, 299677, 284507

303220, 301236
In some rare circumstances, there was a data disparity between a TM1 Websheets viewed as the ADMIN user and the same Websheet viewed as any other user. This problem is resolved in TM1 9.0.