TIBCO Spotfire® Server - Release Notes

TIBCO Spotfire® Server

Release Notes

Software Release 6.0.0 November 2013

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 © 2006-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

| i

TIBCO Spotfire Server Release Notes

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.0.0 ................................................................................................................................. 3

Changed Features .............................................................................................................................. 5

Release 6.0.0 ................................................................................................................................. 5

Deprecated and Removed Features ................................................................................................... 6

Release 6.0.0 ................................................................................................................................. 6

Migration and Compatibility............................................................................................................. 7

Release 6.0.0 ................................................................................................................................. 7

Closed Issues ..................................................................................................................................... 8

Known Issues .................................................................................................................................... 9

| ii


Preface

Topics

Typographical Conventions, page iii

Connecting with TIBCO Resources, page iv

| iii


Typographical Conventions

The following typographical conventions are used in this manual.

General Typographical Conventions

Convention Use

code font Code font identifies commands, code examples, filenames, pathnames, and output d isplayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font

Bold code font is used in the following ways:

In procedures, to ind icate what a user types. For example: Type admin.

In large code samples, to ind icate the parts of the sample that is of particu lar interest.

In command syntax, to ind icate the default parameter for a command. For example, if no parameter is specified , MyCommand is enabled : MyCommand [ enable | disable]

italic font Italic font is used in the following ways:

To ind icate a document title. For example: See Concepts.

To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-app lications that run in a portal.

To ind icate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations Key name separated by a p lus sign ind icate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space ind icate keys pressed one after the other. For example: Esc , Ctrl+Q.

The note icon ind icates information that is of special interest or importance, for example, an add itional action required only in certain circumstances.

The tip icon ind icates an id ea that could be useful, for example, a way to app ly the information provided in the current section to achieve a specific result.

The warning icon ind icates 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, p lease 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.

http://www.tibcommunity.com/

http://docs.tibco.com/

http://www.tibco.com/services/support

https://support.tibco.com/

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

Topics

New Features, see page 3

Changes in Functionality, see page 5

Deprecated and Removed Features, see page 6

Migration and Compatibility, see page 7

Closed Issues, see page 8

Known Issues, see page 9

https://support.tibco.com/

http://support.spotfire.com/sr.asp

Release Notes| 3


New Features

This section lists features added since the last release of this product.

Release 6.0.0

The following are new features in this release.

Correlate System Performance

The Web Player Server and the Spotfire Server collects a number of metrics regard ing the system performance. In the 6.0 release these metrics have been added to the Action Logs and System Performance framework to enable customers to correlate usage with system performance.

Audit Administrator Actions

The audit functionality guarantees log events to be stored in the database without impacting the performance.

Improved Linux Installer

When installing the Spotfire Server on Linux as of version 4.5 the customer uses an RPM package. This requires root access which the Spotfire admins might not have. To solve this problem the Spotfire Server will be available as a tarball which can be extracted . Both the 32 bit and a 64 bit versions of the server is available.

Remote Configuration

The Server Configuration Tool can as of Spotfire 6.0 be installed on other machines than the Spotfire Server.

Authentication Filter

The authentication filter can either be used to filter incoming requests to the Spotfire Server or it can be used for authentication in combination with External authentication. The customer can in their implementation for example block all requests from a certain IP address or country.

External Authentication

This was previously called Delegated au thentication but has now been renamed to External authentication. Previously it could only retrieve the username from an HTTP request attribute. In the 6.0 release the possibility to get the username from a head er, a cookie or the Authentication filter has also been added .

All kind s of au thentication methods that can be implemented using an ISAPI filter or an implementation of Spotfire.Dxp.Web.CustomAuthenticator in the web player can also be implemented using a stand ard servlet filter (implementation of the javax.servlet.Filter interface).

In this release the possibility to specify a regular expression for allowed hosts and IP addresses has also been ad ded , previously it was only possib le to specify unique values. The possibility to require SSL has also been ad ded .

Release Notes| 4


Match Certificate Id

When using client certificates in combination with basic authentication the username from the certificate w ill be compared with the prompted username. If the usernames do not match the user is not granted permission. This new functionality will be configurable which will give existing customers the ability to use the old behavior.

Other Enhancements

Added the possibility to delete users and groups in bu lks from the Spotfire database.

New command, delete-d isabled -users, that deletes d isabled users while possibly (configurable) keeping users that have at some point logged in, users that are members of any groups, users that have Library access permissions assigned explicitly to them or that have created or modified Library items.

It is now possible to select the LDAP groups to synchronize by specifying group Distinguished names (DNs) containing wildcards. This makes it possible to for example synchronize all groups beginning with a particular string.

Release Notes| 5


Changed Features

Release 6.0.0

None

Release Notes| 6


Deprecated and Removed Features

Release 6.0.0

Deprecated Features

The 6.0 release is the last release with support for 32-bit servers.

Removed Features

None

Release Notes| 7


Migration and Compatibility

This section explains how to migrate from a previous release to this release.

Release 6.0.0

Upgrade from TIBCO Spotfire® Server 3.0 or Later

Refer to the chapter “Upgrade from 3.0 or later to 6.0” in the TIBCO Spotfire Server – Installation and Configuration Manual.

Migration from TIBCO Spotfire® Analytics Server 10.1

Refer to the TIBCO Spotfire Server – Installation and Configuration Manual.

Release Notes| 8


Closed Issues

The table in this section list issues that were closed in the named releases.

Various Bug Fixes

Issue Fix version Comment

Release Notes| 9


Known Issues

The table in this section lists known issues in this release.

Key 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: 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: 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.


Summary: Information Services: Accessing stored procedures via Oracle

database links does not work.

Release Notes| 10




Summary: Information Services: Procedures cannot handle parameters of

Oracle type Date.


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.


Summary: Information Services: Information Services does not support stored

procedures using the Teradata database.


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.


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.

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.

Release Notes| 11



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: Configuration Tool: When changing authentication/user directory

mode in the 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: General: The server may fail to start when using a 32-bit JVM due

to failure to allocate a sufficient amount of memory. The log file tss550-

stdout<date>.log will contain the following message: Could not reserve enough

space for object heap.

Workaround: Reduce the configured amount of virtual memory according to

the instructions in section 11.3 in the TIBCO Spotfire® Server Installation

and Configuration Manual (start by reducing the maximum allocated

memory from 1536 MB to 1024 MB).

Summary: Configuration Tool: The configuration Tool might get

unresponsive if the configured LDAP server is not reachable.

Workaround: Use Command Line Tool.

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: Action Logs: When using the "Automatic Force" as restart policy

the database logger does not start again unless the service itself is restarted.

Workaround: Stop and start the Spotfire Server Windows service instead.

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 (Data Direct)

database drivers and Oracle (DataDirect) database driver can be ignored.

Workaround: No workaround needed, the server will work.

Date post:	14-Feb-2017
Category:	Documents
Upload:	vokien
View:	248 times
Download:	5 times

TIBCO Spotfire® Server - Release Notes

Documents