Version 6.2.2
Related information
New features
The add-on was updated to ensure compatibility with TIBCO EBX® 6.2.2 and the Add-ons Bundle 6.2.2.
Changes in Functionality
This release contains no functionality changes.
Changes to third-party libraries
This release contains no changes to third-party libraries.
Closed Issues
This release contains no closed issues.
Known Issues
This release contains the following known issues:
-
To improve consistency, the default commit threshold for EBX was changed from 100 to 0. This threshold determines the number of records processed prior to committing a transaction. However, when the threshold is not set, or set to 0, it can potentially cause performance and memory optimization issues for the add-on. If you notice issues when using the add-on's services, you can adjust the
ebx.manager.import.commit.thresholdproperty in yourebx.propertiesfile. For additional information, see Tuning the EBX® repository. -
Fonts are no longer shipped with the JDK 11. Font rendering in Java 11 JVMs now uses pre-installed operating system fonts. This can cause issues in Linux environments when exporting Excel files. As a workaround, you can install the
fontconfigpackage. -
Association object and selection node are not supported.
-
Data lineage.
-
Graphical view of the data mapping configurations.
-
Split of string transformation function is not supported for a multi-valued string field.
-
Data transfer between complex terminal nodes is possible only if they use the same Java Bean.
-
You can not export data from multiple complex nodes in EBX® that when there is at least one complex node with multiple occurrences.
-
You can not import data from multiple complex nodes in an XML file when there is at least one complex node with multiple occurrences.
-
Split of data works for terminal nodes only.SQL export:
-
You can only export data from EBX® to the selected columns in the same tables of a view which is joined by multiple tables.
-
The add-on doesn't support exporting SQL with the Replace all content mode to a view which is joined by multiple tables.
-
Checking mandatory fields of a view in SQL database is not supported.
-
The export still executes normally and shows an error message from database when no privilege granted.
-
Exporting data from multi-valued fields and multi-valued groups is not supported.
-
You can not export data from EBX® to a view in PostgreSQL database.
-
Exporting data from EBX® to an auto-increment column in SQL Server is not supported because the IDENTITY\_INSERT property is always set to
OFF.SQL import: Checking privileges for a view in PostgreSQL is not supported.Dynamic data modeling: Foreign key statements in the DDL file are not managed.
Dynamic Data Modeling service limitations
The Generate from file service has the following limitations:
-
Only Data Definition Language (DDL), XML, and Excel (XLS and XLSX) file formats are supported.
-
Template files do not support declaration of tables inside of groups.
-
When choosing an XML file to generate, the root node cannot be selected as a table.
-
All configurations cannot be cleaned in the DDM.
-
Fields generated in the Field table do not have an order property.
-
No import options are available when importing using DDM.
-
Comment lines in DDL files are not supported.
-
Declaration of foreign keys, associations, or auto-incremented Id's in Excel import are not supported.
-
Certain keywords in the DDL are not supported, such as "asc" and "desc".
-
A constraint's name must not have space characters and is case sensitive.
-
DROP queries in the DDL file are not supported.The Generate XSD service has the following limitations:
-
This service does not support generation of constraints, rules, or triggers.
-
Only simple data types are supported (not Resource or user-defined attribute types).
-
Defining fields and groups outside of tables is not supported.