TIBCO Spotfire Server Release Notes Software Release 6.5.0 April 2014
Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of t his document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, The Power of Now, TIBCO Spotfire are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/ or other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/ OR CHANGES IN THE PRODUCT(S) AND/ OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/ OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. This Product is covered by U.S. Patent No. 6,014,661 and 7,216,116. Copyright 2006-2014 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information
i Contents Preface... ii Typographical Conventions... iii Connecting with TIBCO Resources... iv How to Join TIBCOmmunity... iv How to Access All TIBCO Documentation... iv How to Contact TIBCO Spotfire Support... iv Release Notes... 2 New Features... 3 Release 6.5.0... 3 Changed Features... 4 Release 6.5.0... 4 Deprecated and Removed Features... 5 Release 6.5.0... 5 Migration and Compatibility... 6 Release 6.5.0... 6 Closed Issues... 7 Known Issues... 8
ii Preface Topics Typographical Conventions, page iii Connecting with TIBCO Resources, page iv
iii Typographical Conventions General Typographical Conventions Convention code font bold code font italic font Key combinations Use The following typographical conventions are used in this manual. Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the foo process. Bold code font is used in the following ways: In procedures, to indicate what a user types. For example: Type admin. In large code samples, to indicate the parts of the sample that is of particular interest. In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [ enable disable] Italic font is used in the following ways: To indicate a document title. For example: See Concepts. To introduce new terms For example: A portal page may contain several p ortlets. Portlets are mini-applications that run in a portal. To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName Key name separated by a plus sign ind icate keys pressed simultaneously. For example: Ctrl+C. Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q. The note icon indicates information that is of sp ecial interest or importance, for example, an additional action required only in certain circumstances. The tip icon indicates an id ea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result. The warning icon indicates the potential for a d amaging situation, for example, data loss or corruption if certain steps are taken or not taken.
iv Connecting with TIBCO Resources How to Join TIBCOmmunity TIBCOmmunity is an online destination for TIBCO customers, partners, and resid ent experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http:/ / www.tibcommunity.com. How to Access All TIBCO Documentation After you join TIBCOmmunity, you can access the documentation for all supported product versions here: http:/ / docs.tibco.com/ How to Contact TIBCO Spotfire Support For comments or problems with this manual or the software it addresses, please contact TIBCO Spotfire Support as follows. For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: http:/ / www.tibco.com/ services/ support If you already have a valid maintenance or support contract, visit this site: https:/ / support.tibco.com Entry to this site requires a user name and password. If you do not have a user name, you can request one.
Release Notes 2 Release Notes Check the TIBCO Prod uct Support web site at https:/ / support.tibco.com for prod uct information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site. See the TIBCO Spotfire System Requirements web page for a detailed description of the system requirements for TIBCO Spotfire 6.5.0. Topics New Features, see page 3 Changes in Functionality, see page 4 Deprecated and Removed Features, see page 5 Migration and Compatibility, see page 6 Closed Issues, see page 7 Known Issues, see page 8
Release Notes 3 New Features This section lists features added since the last release of this product. Release 6.5.0 The following are new features in the 6.5 release. Responsive Web The Web Player library is now designed for both desktop and mobile devices. It is also possible to switch between different views. Expect a slightly different experience on IE8 (due to browser limitations). Licenses A SOAP API has been added for licenses, like the ones for UserDirectoryService, LibraryService, SecurityService. Command Line tools have been added for ad ministrating licenses and to generate a license report. External Library Storage It is possible configure the system to store library content files on Amazon S3. The library content BLOBs are stored outside of the Spotfire database. The meta -data about the library items are still stored in the Spotfire d atabase. Other Enhancements During library import the conflict resolution Replace existing, also hand les bookmarks. The about dialog is upd ated to display build date and hotfix version. The library import has been improved to be faster for import of information services content.
Release Notes 4 Changed Features Release 6.5.0 None
Release Notes 5 Deprecated and Removed Features Release 6.5.0 Deprecated Features None Removed Features None
Release Notes 6 Migration and Compatibility This section explains how to migrate from a previous release to this release. Release 6.5.0 Upgrade from TIBCO Spotfire Server 3.0 or Later Refer to the chapter Upgrading in the TIBCO Spotfire Server Installation and Configuration Manual. Upgrades between service pack versions, for example from 6.5.0 to 6.5.1, shall be performed by applying the latest hotfix and not by running the service pack installer. Go to http:/ / support.spotfire.com/ patches_spotfireserver.asp to d ownload the latest hotfix. Migration from TIBCO Spotfire Analytics Server 10.1 Refer to the TIBCO Spotfire Server Installation and Configuration Manual.
Release Notes 7 Closed Issues Various Bug Fixes Issue Fix version Comment Action Logs: When using the "Automatic 6.5 The database logger now starts Force" as restart policy the database again when using Automatic Force as restart policy logger does not start again unless the service itself is restarted.
Release Notes 8 Known Issues Key The table in this section lists known issues in this release. Summary/Workaround Summary: Action logging: When action logging to the database is enabled a decision should be made if you want to create the indices. The indices are not used when the bundled analysis file is used, but might serve a purpose if you are doing on demand lookups, use the views, searches etc. The indices are enabled per default in the database creation script; if you don't plan to use them, remove the index creation statements before the script is run. When the indices are created they will consume extra space in the database storage and need to be rebuilt periodically, also see chapter 7 in the manual. Summary: General: On the Windows operating system, if the msvcr71.dll is not found in the path when starting the Windows service for the TIBCO Spotfire Server, it will fail to start. Workaround: Copy the msvcr71.dll from the <installation dir>\jdk\bin folder to either the <installation dir>\tomcat\bin folder or to the Windows system32 folder. Summary: HTTPS: The instructions in the manual for setting up HTTPS refer to the directory <installation directory>/tomcat/certs. This directory is not created by the server installer for Solaris. Workaround: Create the directory <installation directory>/tomcat/certs manually. Summary: HTTPS: If you use OpenSSL on a Windows operating system to generate X.509 certificates, beware that international characters in certificates will not work. Workaround: Avoid international characters or use Microsoft Certification Authority Services instead. Summary: Information Services: Filtering on a column that is defined as DOUBLE can produce incorrect behavior under certain circumstances. Workaround: This is due to a bug in Oracle (According to Oracle, the following bug numbers apply: 1375960, 1569966, and 895268). To solve the problem apply the appropriate patches from Oracle. Summary: Information Services: Substructure search may fail for structures larger than 4000 bytes if the columns in the query are in a certain order. This is a limitation in Symyx Direct. Workaround: None known. Summary: Information Services: There is a problem with running an Information Link from the Information Library, when using structure search prompting. The Edit structure function is broken; returning this structure to the prompt dialog will not work.
Release Notes 9 Key Summary/Workaround Workaround: None known. Summary: Information Services: Accessing stored procedures via Oracle database links does not work. Workaround: None known. Summary: Information Services: Procedures cannot handle parameters of Oracle type Date. Workaround: None known. Summary: Information Services: The server side data pivoting capabilities in Information Services require sub-queries support in the underlying database. Sub-queries are not supported in older databases such as MySQL 4.0. Workaround: None known. Summary: Information Services: Information Services does not support stored procedures using the Teradata database. Workaround: None known. Summary: Information Services: The DataDirect JDBC driver for Oracle reports procedure types as Pre instead of Query. Workaround: This will not prevent a user from setting the procedure to a query procedure in Information Services. Summary: Information Services: Properties are not always converted to data table or column properties correctly when reading an Information Link. Workaround: None known. Summary: Information Services: For pre-version 5.0 Composite JDBC drivers, values of type DATE or TIME created or manipulated in Composite Studio will not show the correct date or time, respectively, in TIBCO Spotfire. Workaround: Upgrade the JDBC driver. Summary: Information Services: If you use the bundled DataDirect v4.1 Microsoft SQL Server JDBC driver to connect to a database, listing that database might fail if the schema contains overloaded procedure definitions. Workaround: Use the Microsoft JDBC driver. Summary: Information Services: There is an issue with the bundled DataDirect v4.1 Microsoft SQL Server JDBC driver and TIME columns in Microsoft SQL Server 2008. If you try to read this data type through Information Services without supplying a database name on the connection URL the call will fail. Workaround: Use the Microsoft JDBC driver.
Release Notes 10 Key Summary/Workaround Summary: Information Services: The Netezza JDBC driver, versions 5.0.8 and earlier, must have fetch size set to 255 or less, or the complete dataset may not be read. Workaround: Set the fetch size to 255 or less, or upgrade the JDBC driver. Summary: Configuration Tool: When running the Configuration Tool remotely from a Linux or Solaris server, maximizing its window causes its dropboxes not to listen to mouse clicks. Workaround: Do not maximize the Configuration UI. Summary: Command Line Tool: Non-flag arguments cannot contains spaces. Workaround: Copy the files to a location where the path does not contain spaces before providing it as an argument to the command. Summary: Upgrade: When upgrading the server to 6.0 on Linux or Solaris you might get unnecessary error messages in upgrade-issues.html. The error messages regarding JAAS login module, SQL Server (DataDirect) database drivers and Oracle (DataDirect) database driver can be ignored. Workaround: No workaround needed, the server will work. Summary: JMX: Cannot restart the server through JMX when authorization is enabled. Workaround: Either restart Tomcat or enable automatic restarts (on configuration changes).