Supported environments

Minimum supported version is 44

Compatibility mode is not supported.

Compatibility mode is not supported.

Performance limitations: page loading with IE10 and IE11 is two times slower. This issue is observed when forms have many input components, and particularly many multi-occurrence groups.

Graphical layout: graphical rendering in IE10 and IE11 can slightly differ from other browsers (for example, the alignment of some labels, icons and other components can be off by a few pixels).

As Mozilla Firefox is updated frequently, TIBCO Software Inc. only fully supports version ESR 68. See Mozilla Firefox ESR for more details.

As Google Chrome is updated frequently and it is not possible to deactivate automatic updates, TIBCO Software Inc. only tests and makes the best effort to support the latest version available.

The distinction of null values bears certain limitations. On simple xs:string elements, Oracle does not support the distinction between empty strings and null values. See Empty string management for more information.

The user with which EBX® connects to the database requires the following privileges:

• CREATE SESSION,

• CREATE TABLE,

• ALTER SESSION,

• CREATE SEQUENCE,

• A non-null quota on its default tablespace.

When using PostgreSQL as the underlying database, a request fetch size must be set, otherwise the JDBC driver will fetch the whole result set at once. This could lead to an OutOfMemoryError when retrieving large amounts of data.

Also, see this limitation regarding the evolution of datamodels in mapped modes.

See Request.setFetchSize.

The user with which EBX® connects to the database needs the CONNECT privilege on the database hosting the EBX® repository. Other than this, the default privileges on the public schema of this database are suitable.

The comments in the above section for PostgreSQL apply.

The comments in the above section for PostgreSQL apply.

When using SAP HANA Database as the underlying database, certain schema evolutions are not supported. It is, for example, impossible to reduce the length of a column; this is a limitation of HANA, as mentioned in the SQL reference guide: "For row table, only increasing the size of VARCHAR and NVARCHAR type column is allowed."

The SAP Hana JDBC driver uses the local timezone of the JVM to handle timestamp SQL columns. Hence, for the specific use cases described in the section SQL access to data in relational mode, the JVM powering the Hana JDBC driver - that is the JVM powering EBX® - should be started with the property user.timezone set to UTC. This configuration is not free of side effects: for example, the timestamps shown in the EBX® logs will be in UTC instead of the local timezone.

When used with Microsoft SQL Server, EBX® uses the default database collation to compare and sort strings stored in the database. This applies to strings used in the data model definition, as well as data stored in relational and history tables. The default database collation can be specified when the database is created. Otherwise, the collation of the database server is used. To avoid naming conflicts or unexpected behaviors, a case- and accent-sensitive collation must be used as the default database collation (the collation name is suffixed by "CS_AS" or the collation is binary).

The default setting to enforce transaction isolation on SQL Server follows a pessimistic model. Rows are locked to prevent any read/write concurrent accesses. This may cause liveliness issues for mapped tables (history or relational). To avoid such issues, it is recommended to activate snapshot isolation on your SQL Server database.

The user with which EBX® connects to the database requires the following privileges:

• CONNECT, SELECT and CREATE TABLE on the database hosting the EBX® repository,

• ALTER, CONTROL, UPDATE, INSERT, DELETE on its default schema.

EBX® has been qualified on Microsoft Azure SQL Database v12 (12.00.700), and is regularly tested to verify compatibility with the current version of the Azure database service.

When used with Microsoft Azure SQL, EBX® uses the default database collation to compare and sort strings stored in the database. This applies to strings used in the data model definition, as well as data stored in relational and history tables. The default database collation can be specified when the database is created. Otherwise, the database engine server collation is used. To avoid naming conflicts or unexpected behaviors, a case- and accent-sensitive collation must be used as the default database collation (the collation name is suffixed by "CS_AS" or the collation is binary).

The user with which EBX® connects to the database requires the following privileges:

• CONNECT, SELECT and CREATE TABLE on the database hosting the EBX® repository,

• ALTER, CONTROL, UPDATE, INSERT, DELETE on its default schema.

H2 is not supported for production environments.

The default H2 database settings do not allow consistent reads when records are modified. Relational tables are locked following a pessimistic model. To prevent concurrency issues, it is possible to activate the MVCC feature. Note, however, that the H2 documentation states this feature is not yet fully tested.