What's New in TIBCO EBX® 6.2

Latest version available for download on eDelivery

TIBCO EBX^® product documentation

Back to the What's New in EBX^® landing page

This page describes the new features and improvements brought by EBX^® 6.2.0.  

Main topics

• Metadata
• Next Gen UI
• Data Visualization
• Scripting
• Search
• Permissions & User management
• Workflow
• Data Integration and Development APIs
• Matching & Merging
• Digital Asset Management
• Staging
• Important information for current users before upgrading

Metadata

Important note: Available only for EBX 6.2.0 Container Edition at this stage

Ability to manage your metadata

A data catalog
Search and manage access to data available within the company

A data governance solution
Document and assist in regulatory compliance

A metadata repository
Discover, collect and manage all your metadata

Functionalities

Catalog

Document your applications and easily access to their relationship

The Catalog section groups all logical descriptions including applications, datasets and data elements.
You can describe your applications, document your datasets and data elements.

Then, you can easily have a view of the relationship  between them.

Governance

Describe how data is managed by different business domains

Each domain can have its own data related terminology and roles.

This section also defines user groups, their related roles, and data rights. Comprehensive metadata management programs aim to register any program, initiative or project around data.

Metadata repository

Document the technical description of your data

The materialization of the dataset described in the catalog is documented in the Metadata section. 
This section includes assets, which are physical resources that contain or provide data. Assets are the materialization of the logical descriptions in the Catalog.
Asset technical structures and properties are stored according to their types.
You can use the harvesting functionality to retrieve metadata from a data source that exists in your system. 
You can also introspect EBX.

Please note that the use of TIBCO Data Virtualization as an agent is mandatory to harvest metadata with this first release.

Next Gen UI

Introduction of Next Gen UI: the Homepage

A configurable landing page for the users

Previously, it was not possible for users to define themselves shortcuts to data inside EBX.

Now, users can place and configure widgets to directly access where they need to navigate on a day to day basis.
Widgets are placed via a simple drag & drop.
The homepage is accessible in the perspective menu.

A library of widget is available to display information or redirect directly the user

Different types of widgets are available: 

• Quick access: Link to 1 or multiple tables
• Last creations: The list of the last created records
• Last modifications: The list of the last updated records
• Workflow Inbox: Tasks assigned to the user
• Top rated: Records with the highest ratings
• Number of records: Count a table record

Data Visualization

New display of record history

Focus on the User Experience to display the information in a non technical way

Previously, it was sometimes difficult to quickly understand the record history.

Now, the display is simplified, and a faster access is provided through the side bar.

Org Chart : Search

Search on node data is now available on the org chart

Previously, it was sometimes difficult to find a particular node when a lot of nodes are displayed at the same time on the Org Chart.

Now with the new search feature, you can easily find the node you want by using the search on the top right of the graph. 
Each time a new letter is entered, the filter is applied to show only matching nodes. 
When a node is selected on the result page it is then highlighted on the graph and the focus is directly put on the selected node.

Org Chart : UI options

Additional UI options are coming to the Org Chart

Previously, the node style of the Org Chart (colors, border, etc) was predefined and it was not possible to personalize it.

Now we added several options on the configuration allowing you to define several parameters : Border color, Background color, Text color, Sub text color, Border width, Border style.
In addition, it is also now possible to assign a default image or an icon to the nodes. In case the node has no image attached to the record, a default image will be displayed instead. 
Previously the default image was not configurable.
Lastly, the image options allows you to define how the image should be displayed on the node (stretch or keep aspect ratio).

Display data model graph

Enhancements on display data model service

Previously, the labels of data model elements were displayed always on lowercase with some removed characters. Also, when displaying optional fields, the associated links were not synchronized (Foreign Key, associations, etc).

Now, the labels of each data model elements are exactly the same as the one entered by the user.
To improve diagram readability, some links can be hidden: When unchecking the "Display Options" for elements like Associations, Computed  Attributes, Inherited Fields, Linked Fields and/or Hidden fields, we now automatically remove the corresponding "link" (if any) from the diagram.
When checking back any of the “Display options” we now display back the corresponding links on the data model graph.

PDF Export using vector graphics

The quality of graph PDF exports has been improved

Previously, the quality of PDF export was not very good especially when having multiple nodes on the graph. It was the same problems on data models when having a lot of tables and fields.

Now, we completely refactored the PDF export in order to use vector graphics. This allows user to zoom in with no limitations and keep the high resolution quality on each element of the graph.
This evolution applies to all PDF exports of the module  

• Data graphs with configuration
• Data graphs without configuration
• Data models

Please note that the render of images on nodes depends on the quality of the original image attached to the record.
 

DMDV Public API

New method and parameter available on public API

Previously, when using the standard DMDV UI Widget to display a graph using configuration, the nodes were automatically expanded by default and this parameter couldn’t be changed.

Now we have added a new parameter on the UI Widget called “forceRecursiveExpand”.
When set to Yes, the graph will be automatically expanded.
When set to No, the graph will not be automatically expanded.

For developers, when using the JAVA API “GraphModelSpec” to generate an HTTP Manager Component to display a DMDV graph, a new Java method is now available to set this parameter.

Scripting

An embedded IDE for EBX Scripts

A new tool to manage your EBX scripts

Previously, EBX scripts were defined in a simple editor window. 

Now, an out-of-the-box integrated development environment can be used to create, update, and deploy EBX scripts.
This IDE eases scripts management with:

• A single tool to handle all types of EBX scripts
• Code completion
• Automatic code formatting
• Contextual help
• Scripts updates history
• and more

Standard deployment and easy access

Support of scripted Workflow tasks

Workflow tasks can be configured using EBX scripts

Previously, Workflow tasks can only be defined using the Java API.

Now, Workflow Script tasks can be created using the EBX Script IDE.
It means that you can define tasks that should be automatically performed by EBX without any line of Java coding.

Input and output parameters are also supported.

Support of scripted Table triggers

Table triggers can be configured using EBX scripts

Previously, table triggers can only be defined using the Java API.

Now, table triggers can be managed using the EBX Script IDE:

• A reference to a new script must first be entered in the DMA
• Then it is possible to directly access its definition within the Script IDE

As EBX scripts they automatically benefit from EBX6 performance optimizations.

Search

Stop words case insensitive

Previously, stop words were case sensitive

It means that using “Street” and “STREET” were having different outputs. Now, Stop words are case insensitive, to simplify your configuration.

Permissions & User Management

LDAP support

Out-of-the-box support for LDAP (Lightweight Directory Access Protocol)

Previously, using EBX Java API, it was possible to access LDAP directories to retrieve users and groups of users informations in order to provide them permissions within EBX.

Now, such integration can be achieved without a development effort, only through a configuration step. 
This support has been designed as a custom directory implementation and can be configured in the main configuration file.

The use of custom LDAP directory access remains possible.

Current limitations

• One LDAP server can be configured at a time: Simultaneous connections to multiple LDAP servers are not supported within the same instance
• No support for role inclusion or the addition of specific roles on the EBX® side: the structure and nested relationships of groups within LDAP are not considered in the calculation of permissions. This limitation highlights a straightforward, group-based access control approach without the complexities of LDAP's hierarchical group dynamics
• Only simple and anonymous authentication methods are allowed: more complex or secure authentication protocols used within LDAP is not supported
• Roles and usernames display is not locale dependent and is limited to one format introduced by display expressions in the configuration file
   

Permissions on DMDV

Permissions on data graphs

Previously, when creating a new data graph configuration, it was not possible to define permissions for this configuration.

Now, permissions are available on Edit graph display services allowing any owner of the configuration to define who can do what with each configurations.
Permissions available for each profile : 

• Use the configuration (if set to no, the configuration is not available in the list of configuration to select when launching the Edit graph display service)
• Update the configuration
• Delete the configuration
• Export services (Use of the different export services (PDF, SVG, PNG))

Insight indicators able to follow access rules

Ability to apply the permission rules for the indicator execution

A new permission strategy has been added which is “Follow access rules”. 

This strategy changes the way of computing the indicators results by taking into account access rules, so that the displayed results of indicators relate only to the data that a user can access. 
For example: If a user having permission to see only records related to customers located in the United States (4000 records), the result of the "Record count" will display 4000 instead of 10,000 as the total of the table.

As the other proposed permission strategy, it can only be configured by an administrator at a Role, a Profile or a User level.
 

Workflow

New APIs

Retrieving process instances having a specific data context variable value from the publication name

Previously, it was not possible to retrieve a Workflow instance based on its publication name and some specific data context variables.

Now, an API method has been updated to allow this new behavior:

// Signature of the API
WorkflowEngine.getProcessInstanceKeysForDataContextVariable(PublishedProcessKey publishedProcessKey, String varName, String varValue)

Data Integration and Development APIs

Related Objects in REST calls

Ability to directly get the associated objects as part of a single REST call

Previously, when a Business Object was configured and requested via a REST call, only links to related objects (through associations) were provided.

Now, it is possible to directly get the related information.
Declaration of the maximum size of service answer is done in the ebx.properties file.

Force import/transfer option

Ability to disable all constraints during import/transfer services execution

Previously, if some errors occurred during the import, or some data couldn’t be imported, the process was not able to complete.

Now, it is possible to only import valid records (without errors caused by constraints on DMA).

Handle CSV Export services with no Cell delimiter provided

Export data with CSV format without Cell delimiter is now available

Previously, it was impossible to export CSV with no Cell delimiter.

Before when exporting CSV with Cell delimiter not provided, the default cell delimiter was automatically applied.
Now, user can let Cell delimiter option empty and export successfully. 

Matching & Merging

Vertical display for merge and manage group view

Ability to switch the display of the records from horizontal to vertical in the Merge view screen as well as in the Manage Group

Previously, only horizontal display was available.

Now:

• More flexibility to easily review the records with a big number of attributes

• All the services work in the same way as for the horizontal display

Better UX for the Evaluate matching service

More details are provided for the pre-processing step of the data comparison and for the decision tree explanation screens

In the past the users were confused by the redundant information and because of the color code.

Now:

• In the pre-processing explanation screen the redundant fields have been omitted and the values compared for each field are shown

• The decision tree explanation details display for every comparison node has been reviewed to make it easier to understand

Alternative calculation formula for the Full text algorithm

An additional calculation formula is available to better fit with the existing search strategies

Previously, the formula used by MAME addon was different from the search engine similar finder mechanism that could lead to missing match results. 

In order to be able to use the new formula to calculate the Full-text algorithm formula, the user can declare the information in the ebx.properties file (ebx.addon.mame.algorithm.fulltext.version={version}, where version has value Legacy or Compatibility).
The old formula will still be applied by default in case no attribute is declared in ebx.properties (equivalent to setting the property to Legacy)

New algorithms filtering based on the search strategy

The filtering mechanism has been updated to ensure a better compatibility between the search strategy selected by the user and the algorithms available for this search strategy

This enhancement is necessary because new search strategies and new algorithms have been added to the product. 

• The compatible algorithms will be displayed on the top of the list
• In case the algorithm is not compatible, it will be grayed out and displayed on the bottom of the list (even if it will remain clickable)
• The errors will be included into the validation report
• This mechanism will work for both standard matching and the business objects

JAVA API to manage the auto-created golden composite PK

It is now possible to configure the auto-created golden composite PK generation in a way that it includes a part of the composite PK of the Merged records

Previously the composite PKs were not available for the auto-created goldens.

A new Java API allows the customers to register a custom PK Generator for their business.

In this Java API, we provide the information context of the current Group containing the merged records, which can be used to create new PK for golden record.

Mandatory fields for a better performance

The “mandatory field” concept is introduced to reduce the number of the Decision tree comparisons

Previously, this kind of fields was not taken into account by the pre-processing.

The mandatory fields are the fields of the “All fields match” comparison node that are a mandatory condition for 2 records to be a Match or Suspect. Mandatory fields are compared with Exact or Full text algorithms.
The Pre-processing can now get the Mandatory fields set to cut all the couples of records that don’t match based on mandatory fields and then reduce the number of Decision tree comparisons.

Better field weight management

Reduce the need of weighting your attributes in your decision tree where multiple fields are used in the data comparison

Previously, fields containing multiple values or long values had a greater impact on the similarity computation.

The computation method has been reviewed, to improve the relevance of the results.

By default, the new behavior will now be applied. And this can be reversed thanks to a dedicated property.
 

Digital Asset Management

Configuration migration service

Some DAMA services have changed between EBX5 and EBX6. It’s now possible to smoothly map the old and new configurations thanks to the “Migrate digital asset manager data” service

Previously, the user had to manually adjust all the configurations after the archive import.

“Migrate digital asset manager data” service is available in the actions menu of the DAMA administration dataset.

Previously this service was only working for the migration between EBX 6 versions.

Better duplicate assets management

“Reject duplicates” permission is now applied not only to the duplicated assets uploaded to the Drive, but also to the assets versions that are duplicates of the existing assets

Previously, the assets versions were not covered by this setting.

From now on, in case the “Reject duplicates” is set to “Yes”, an error message will appear if the user uploads a duplicated asset in the versioning UI.
If this setting is set to “No”, a warning message will be displayed, but the asset can still be uploaded.

Control the External Drive space

It is now possible to control the maximum usable space for the external storage, so that the user can upload or import larger files

In the past this setting was only available for the internal storage.

Now:

• The user can input the value of the max usable space into the corresponding field of the all the built-in external connectors (Amazon S3, Azure Blob, Share point, etc)

• The default value is 1,024 MB

• Total file size in a Drive cannot exceed the specified max usable number

Staging

Search and Select All

Staging widget is improved with Search and Select all features

Previously, it was sometimes difficult to find the elements to add on the staging and impossible to select all elements of a dataset for example.

Now with the new search bar, you can easily find the item you want to add in the staging by using the search on the staging widget. The search is performed on all elements of the staging widget.
A second search bar is displayed on the “Selected components” pane to quickly find an item on the content of the domain.
The select All feature allows you to add in one time the full content of a dataspace for example which is very helpful.

UI Improvements

The UI of the selected components has been improved for a better visualization of the selected staging elements

Previously, it was sometimes difficult to visualize the selected components and understand which element belongs to which main EBX feature (Dataspace, dataset, etc).

Now, the selected components are grouped by categories reflecting the structure of the staging elements so that users can easily find and understand the content of their staging archive.
Plus, with the second search bar displayed on top of the “Selected components” pane, it is much more convenient to find a selected item on the content of the domain.

Staging for matching in-module data models

Matching configurations linked to the in-module data model can now be migrated via staging

Previously, staging of matching artefacts was supported only for embedded data models.

In the staging screen, the matching configurations will be removed from the “Model publications” section for both embedded and the in-module data models.
All the matching configurations can be now found under the “Dataset” section.

Important information for current users before upgrading

• TIBCO EBX version upgrade strategy and recommendations

• Jakarta migration and upgrade to Java 17

EBX 6.2.0 includes a migration from Javax to Jakarta and from Java 11 to Java 17

This migration was mandatory in order to receive security fixes on third-parties frameworks/libraries used by EBX

What are the impacts for you?

• A package name refactorization from javax.* to jakarta.* might be needed in modules or in libraries
  • As EBX now supports Jakarta EE
• An upgrade to several third party libraries will be required, such as Servlet 5.0 or greater, JSP 3.0 or greater, JMS 3.0 or greater, and Mail 2.0 or greater
  • As EBX now supports Jakarta EE 9 and above
• A project recompilation with JDK 17 may be required
  • As EBX now requires Java 17
• An upgrade of your application server may be needed
  • As EBX now requires Java 17 and Jakarta EE 9
• WebLogic 14c is no longer compatible
  • As EBX is now Jakarta EE 9 and above compliant