TIBCO Spotfire Server Release Notes. Software Release February 2013

Transcription

1 TIBCO Spotfire Server Release Notes Software Release February 2013

2 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 N OT 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 this 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, IN CLUDING 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 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

3 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 Changes in Functionality... 4 Release Deprecated and Removed Features... 5 Release Migration and Compatibility... 6 Release Closed Issues... 7 Known Issues... 9

4 ii Preface Topics Typographical Conventions, page iii Connecting with TIBCO Resources, page iv

5 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.

6 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 / How to Access All TIBCO Documentation After you join TIBCOmmunity, you can access the documentation for all supported product versions here: / docs.tibco.com/ TibcoDoc 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: / services/ support If you already have a valid maintenance or support contract, visit this site: / 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.

7 Release Notes 2 Release Notes Check the TIBCO Prod uct Support web site at / 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 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 9

8 Release Notes 3 New Features This section lists features added since the last release of this product. Release The following are new features in this release. Configuration Tool To complement the Configuration Command Line Tool, a graphical user interface Configuration Tool has been developed. This tool has support for most common configuration tasks. There is also a discovery and test functionality to facilitate LDAP configuration. The tool may be started as the last stage of installation, but can also be launched later from the Windows Start Menu (Start > TIBCO Spotfire Server 5.0 > Configure TIBCO Spotfire Server) or from the <installation dir>\tomcat\bin directory using the command uiconfig.bat or uiconfig.sh. Configuration Command Line Tool Commands There are several new commands available in the Configuration Command Line Tool which can be used when scripting an installation. The new commands are: update-deployment and show -deployment which allows client deployments to be added, updated and shown. export-users, export-groups, import-users and import-groups which allows users and groups (including group hierarchies) to be exported and imported (like they could previously be, using the Administration Manager). export-library-content and export-library-content which allows Library content to be exported and imported (like they could previously be, using the Library Manager). show-basic-ld ap-auth which shows the LDAP configurations used for authentication. show-import-export-directory which shows the current library export directory. show-join-d atabase which shows the current default join database. show-restart-policy which shows the current restart policy. Local Caching of Library Files When a library file is retrieved from the database its content is cached in a temporary folder. If a new request comes to this file and the file s modification date has not changed, the cached content is returned (otherwise it will be discarded, ensuring that no stale d ata will ever be returned). There is a maximum cache size which will prevent the disk from filling up. The temporary files are encrypted to prevent information disclosure. Support for Kerberos through GSSAPI TIBCO Spotfire server now supports Kerberos through GSSAPI for LDAP.

9 Release Notes 4 Changes in Functionality This section lists changes in functionality since the last release of this prod uct. Release The following are changes in functionality in this release. Optimized User Directory The user directory has been rewritten to reduce the communication with external LDAP directories and Windows NT d omain controllers. The Spotfire user directory is periodically synchronized with those external directories. Previously, the user directory had synchronization schedu les for group synchronization. Those schedules will now be used for synchronizing both users and groups. The user directory can now also handle multiple domains, which allows users with the same username from different domains to be hand led properly. As a consequence of this new functionality, end users must now log in using both user and domain name. The configuration of LDAP group synchronization has been simplified. The administrator can now choose between explicitly listing all groups to be synchronized and explicitly listing the LDAP containers which contains the groups to be synchronized. The ad ministrator can also have an empty list of group names, causing all groups belonging to the LDAP configuration to be synchronized.

10 Release Notes 5 Deprecated and Removed Features Release Deprecated Features None. Removed Features The old way of using and configuring NTLMv1 by copying jcifs.jar and jcifs-ext.jar from the old installation is no longer supported. To configure NTLM v1 & v2 in the supported way see chapter NTLM in the TIBCO Spotfire Server - Installation and Configuration manual. The old User Directory SPI that was deprecated in TSS 3.0 has now been removed without replacement. Two deprecated methods in the com.spotfire.server.security.securitycontext API class have also been removed without replacement. TIBCO Spotfire User's Manuals in pdf format have been removed.

11 Release Notes 6 Migration and Compatibility This section explains how to migrate from a previous release to this release. Release Upgrade from TIBCO Spotfire Server 3.0 or Later Refer to the chapter Upgrade from 3.0 or later to 5.0 in the TIBCO Spotfire Server Installation and Configuration Manual. Migration from TIBCO Spotfire Analytics Server 10.1 Refer to the TIBCO Spotfire Server Migration Manual.

12 Release Notes 7 Closed Issues The table in this section list issues that were closed in the named releases. Various Bug Fixes JDK has been upgraded to version 7. Tomcat has been upgraded to version 7. Issue Fix version Comment TSS Fixed problem when downloading an analysis containing bookmarks and encryption of temporary files was enabled. TSS Fixed: After LDAP synchronization, previously existing users that were not returned during synchronization where not able to login. TSS Sometimes when opening a file through library URL it did not work when the file contained bookmarks. This has now been fixed. TSS Fixed problem when upgrade failed on machine with French locale. TSS Fixed problem when the SQL join's WHERE clause was not used when multiple rows where marked. TSS Updated terminology in the Configuration UI to signal that the bootstrap file must be namned bootstrap.xml. TSS Fixed database update problem when upgrading from TIBCO Spotfire server 3.3. TSS Removed JDBC-ODBC bridge since it doesn't work on 64bit server. TSS Added logging when there is a guid conflict or path conflict and conflict resolution mode is set to KEEP_NEW. TSS Fixed problem with exception thrown when importing users and groups. TSS Removed datasource template setting display-name from the documentation. TSS Added configuration UI to the TIBCO Spotfire server. TSS Fixed problem that upgrade didn t proceed when 'Integrated Login' option was selected in the upgrade tool. TSS Added a descriptive explanation when third party download failure causes installation rollback. TSS It is now not possible to update the server with an incompatible patch, earlier the installer silently allowed installing an older release's patch to a newer release. TSS The server previously had a live connection to the LDAP server and therefore had to fetch all users both from LDAP and the database and filter those. This has been changed so that the server only synchronizes periodically with the LDAP directory.

13 Release Notes 8 TSS Added note in chapter 7.2 in Server manual about manually editing the server.xml file with possible changes. TSS Improved the performance when searching for a user in a large user directory. TSS Implemented commands for library import and export. TSS Added note in chapter 7.2 regarding that the upgrade tool doesn't copy over tomcat server.xml settings. TSS The server no longer performs a live search against the LDAP directory and the user directory cache has been improved (with longer cache times etc). TSS Upgrade tool failing for invalid LDAP configuration TSS Upgrade tool does not validate LDAP configurations before proceeding with the upgrade TSS Upgrade tools fails to collect passwords from server installation when choosing "Do not copy configuration" during upgrade TSS LDAP synchronization fails with an out of memory error TSS Upgrade fails when a custom LDAP configuration has no member attribute set, even though group synchronization isn t enabled for this LDAP configuration TSS Configuration tool creates LDAP configurations with incorrect properties related to group synchronization TSS Group import in Administration Manager not working TSS Confusing error message for certain combinations of authentication method, User Directory mode and domain name style TSS LDAP domain name extraction only supports the DC top level attribute TSS Synchronizing LDAP users or groups without proper account names causes an error that terminates the entire LDAP synchronization TSS LDAP authentication and synchronization fails when the configured context definitions contains mixed case letters

14 Release Notes 9 Known Issues Key The table in this section lists known issues in this release. Summary/Workaround 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 directory to either the <installation dir>\tomcat\bin folder or to the Windows system32 folder. Summary: SSL: 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: Migration: The Oracle 10g JDBC driver (ojdbc14.jar) cannot be used by the Migration Tool (when migrating from TIBCO Spotfire Analytics Server 10.1). Workaround: Temporarily replace the driver with the Oracle 11g JDBC driver (ojdbc6.jar). For more information refer to the Database Drivers chapter in the TIBCO Spotfire Server Migration Manual. Summary: User Directory: Some LDAP group synchronization configurations may be ignored when synchronization using multiple configurations occurs concurrently. Workaround: Configure the synchronization using cron schedules and separate them as much as possible in time. Summary: User Directory: When using multiple LDAP group synchronization schedules some synchronized groups may be erroneously editable in the Administration Console. Workaround: Do not edit these groups. 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: , , and ). 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

15 Release Notes 10 Key Summary/Workaround search prompting. The Edit structure function is broken; returning this structure to the prompt dialog will not work. 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 If you try to read this data type through Information Services without supplying a database name on the connection URL the call will fail.

16 Release Notes 11 Key Summary/Workaround Workaround: Use the Microsoft JDBC driver. Summary: Information Services: The Netezza JDBC driver, versions 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 UI: When running the Configuration UI 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: Administration console: Users listing does not follow alphabetical ordering. Workaround: None known. Summary: Configuration UI: When changing authentication/user directory mode in the graphical configuration tool the changes are not saved until selecting authentication/user directory panels. Workaround: Select the Authentication: <Authentication mode> panel and/or User Directory: <User Directory Mode> panel and then the authentication/user directory modes will be saved. Summary: Admin command: Error message displayed while running 'configdelegate-auth' CLI without providing 'allowed-hosts' as an argument. Workaround: Always add allowed-hosts as an argument.