Supported Environments

Introduction

The software portfolio of Cubeware is not a standalone platform. Third party software such as operating systems, databases, web servers, and browsers are necessary in order to provide a fully functional BI environment.

As the number, complexity and dependencies of third party software increase, the notion of a supported environment becomes inevitable, in order to guarantee the best level of software quality. A supported environment is a QA tested and supported combination of Cubeware and third party software.

This section contains list of the supported environments. It is fundamental to underline this list of supported environments is going to be updated after every release and only the last version of this list is valid.

Overview

⁽¹⁾ MSSQL/MSAS 2016 are supported as of CSP Connect R8 FP5. MSSQL/MSAS 2017 are supported as of CSP Connect R9.1 FP2. MSSQL/MSAS 2019 are supported as of CSP Connect R9.4.

⁽²⁾ CSP Connect R8 FP5 supports Infor BI Version 11.0 only within the scope of the Infor BI 10.6 functions. The new Infor BI OLAP 11 features are supported as of release CSP Connect R9.

⁽³⁾In order to prevent a possible loss of data when building dimensions using Infor BI Version 10.5.x, we recommend the following: Before changing a dimension by means of Importer/ImportMaster, always unload those cubes first, in which the dimension to be changed is used. This can be done using CSP Connect.

^(4A) Multiple hierarchies and MDX are only supported via the REST API and the TM1 REST driver (cwiotm1r.dll). In contrast to the TM1 11.x C API, the version requires at least the IBM server versions V11.5 or Tm1 Planning Analytics 2.0.7. Older V11 versions have various compatibility problems and are therefore explicitly queried by the TM1 REST connector. The creation of a connection is therefore actively prevented if there is an insufficient version. The creation of attribute-driven hierarchies via the Importer cannot currently be done via the user interface, but via calling the TI processes. As of Release R9.6, the Importer Migration Wizard is supported, which allows migration from a database connection of the TM1U driver to the database connection of the TM1R driver. Further Known Issues see IBM Knowledge Center and IBM Support.

^(4B) Please note that IBM TM1 Planning Analytics 2.0 is going out of service life in October 2025. For deprecation information see https://www.ibm.com/support/pages/deprecation-notices-ibm-planning-analytics-20 and https://community.ibm.com/community/user/blogs/michael-mcgeein/2024/11/20/extending-the-end-of-service-for-planning-analyti.

The descendant version IBM TM1 Planning Analytics 2.1 is a x64 application* and thus connections are only possible via the CSP x64 products suite. https://www.ibm.com/software/reports/compatibility/clarity/index.html?name=IBM%20 Planning%20Analytics%20Local.

Additionally it should be noted that TM1 Planning Analytics 2.1 only supports ReST API clients.

⁽⁵⁾ The OLAP features of the IBM Cognos TM1 database are only supported by the dedicated TM1 driver. The OLE DB for OLAP (ODBO) driver is not designed for use with this database or MDX.

⁽⁶⁾ All versions according to standard ODBC Microsoft are supported, ODBC 3.0.3.5, 3.8 to be named here.

⁽⁷⁾ For IT security reasons, TLS 1.2 should be used in MS SQL Server connections (the old TLS 1.0 and TLS 1.1 protocols have security issues). The 'SQL Server Native Client x.x (SQLNCLI)' provider and the 'Microsoft OLE DB Provider for SQL Server (SQLOLEDB)' were announced as deprecated (see Microsoft Documentation for definition of deprecated database features). Microsoft recommends to use the 'Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL)'. The MSOLEDBSQL driver can be downloaded from the following link: Download OLE DB Driver. See also Announcing the new release of OLE DB Driver for SQL Server und Microsoft OLE DB Driver for SQL Server.

In an existing environment, it is not necessary to change the MS SQL Server OLEDB provider except,

• You get the ERROR MESSAGE described below or,

• Due to security reasons, you must use TLS 1.2 with your MS SQL database.

However, if none of the blocking issues are detected in an environment (see Support policies for OLE DB Driver for SQL Server, Updating an Application from SQL Server 2005 Native Client, Updating an Application to OLE DB Driver for SQL Server from MDAC), there is obviously no reason to continue using the 'Microsoft OLE DB Provider for SQL Server (SQLOLEDB)' provider. ERROR situation fixed by switching to the new 'Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL)': The connections to SQL databases were still configured with OLE DB and the old provider 'Microsoft OLE DB Provider for SQL Server (SQLOLEDB)' - the SQL database used TLS 1.2. The following error was displayed: '[DBNETLIB][ConnectionOpen (SEDoClientHandshake()).]SSL Security error.'. This is because the old OLE DB provider 'Microsoft OLE DB Provider for SQL Server (SQLOLEDB)' and the ODBC provider 'SQL Server' do not support TLS 1.2.

⁽⁸⁾ The CPI-C interface is only supported up to SAP NetWeaver 7.4. From SAP NetWeaver 7.4 on, only the RFC protocol is supported and recommended. CPI-C extractors cannot be used when working with the RFC protocol.

Note: The CPI-C protocol transmission protocol has been marked as deprecated. This option will be removed with the next version. For more Known Issues see Cubeware Release Notes R9.4.

⁽⁹⁾ The CSP Server Manager is a 32-bit application which runs both on 32-bit and on 64-bit systems. The CSP Server, however, is only 64-bit capable.

⁽¹⁰⁾ In case of Office 365 Pro Plus, Cubeware only supports the local Click-to-Run version. Web-based versions are not (yet) supported.

⁽¹¹⁾ Due to rapid development cycles in the browser market, there is a slight chance that – in rare cases – a recently introduced browser feature or enhancement does not properly work with our products. In this case, please contact our product support at https://support.cubeware.com. Thank you for your understanding.

⁽¹²⁾ CSP products have been qualified and now include support for the Windows 11 operating system. However, please note that Kerberos Authentication for Windows 11 has not been tested, hence it is not currently supported.

Support Lifecycle

There are 3 kinds of Cubeware software packages:

• Major Releases represent packages with significant functional and technical innovations. As soon as a major release becomes generally available, the last service release is supported for at least 6 months. This facilitates the migration process.

• Service Releases represent optimizations and bug fixes referring to a major release. As soon as a service release becomes generally available, the previous service release (or major release in case of a first service release) is not supported anymore.

• Fixpacks are in this context similar to service releases.

FAQ

• What happens if my database or browser version is not in any supported environment, e.g., SQL Server 2005 or MIS Alea?

  This implies an unsupported environment. This does not necessarily mean that the environment does not work. It is just not officially supported.

• What happens if my database or browser version is not supported anymore (by the respective vendor), e.g., SQL Server 2005?

  This document does not list unsupported versions. If a third party vendor does no longer support a particular version, it will be excluded from the next version of this document.