This release provides a number of critical updates, including the possibility to create a default repository upon installation and to create a default conversion user (non-admin).
On this page
You can install this release from the provided package. Follow Installation Instructions for more details.
These updates are available in this release.
|https://jira.braintribe.com/browse/AD-391||CRITICAL||ADx Admin: Provided option to automatically configure/setup a default repository during the installation process via the new |
|https://jira.braintribe.com/browse/AD-305||CRITICAL||ADx Admin: Legacy Deep Health Check Integration for Repositories|
|https://jira.braintribe.com/browse/AD-346||CRITICAL||ADx Admin: REST API - Configure/Expose missing endpoints for User Management and Health Checks|
|https://jira.braintribe.com/browse/AD-318||CRITICAL||Finalize Architecture Diagram|
|https://jira.braintribe.com/browse/AD-320||CRITICAL||ADx Admin: Add TablePrefix (Support) for Standard Repository|
|https://jira.braintribe.com/browse/AD-366||MAJOR||FIX: Failing Conversion Health Check.|
|https://jira.braintribe.com/browse/AD-364||MAJOR||FIX: Failing Storage Health Check.|
|https://jira.braintribe.com/browse/AD-315||MAJOR||ADx API: Missing features required for Legacy ADx Endpoints.|
|https://jira.braintribe.com/browse/AD-345||MAJOR||ADx Admin: User Management (Search support & bi-directional linking)|
|https://jira.braintribe.com/browse/AD-344||MAJOR||ADx Admin: Ensure ADx specific roles/groups on startup|
|https://jira.braintribe.com/browse/AD-358||MAJOR||ADx Content: Extended Check-In Options|
|https://jira.braintribe.com/browse/AD-388||MAJOR||ADx Conversion: Added runtime properties related to the configuration of the default conversion user.|
|https://jira.braintribe.com/browse/AD-353||MINOR||ADx Admin: Pending Icon & Labels configuration|
|https://jira.braintribe.com/browse/CORETS-447||MINOR||ADx Content: Updated the Aspose library that is used for converting Office documents.|
|https://jira.braintribe.com/browse/CORETS-448||MINOR||ADx Conversion: Fixed the statistics in the Health page of the Conversion Cartridge.|
|https://jira.braintribe.com/browse/AD-395||MINOR||ADx Core: Fixed a bug where Conversion health check wouldn't work with self-signed certificates.|
This release introduced the following changes in runtime properties (also explained in example-installation-settings.yaml available in the package):
The following properties were added in this release:
|CONV_STANDARD_USER_NAME||Conversion standard user used to send conversion requests.|
|CONV_STANDARD_USER_PASSWORD||Password for the above user|
|ADX_INIT_DEFAULT_REPOSITORY||when set to |
ADX_ENABLE_DEFAULT_TEMPLATE was removed in this release. This feature was deprecated and consequently the property has now been removed.
A list of problems we're aware of and working on.
|https://jira.braintribe.com/browse/AD-321||CRITICAL||Add missing indices|
|https://jira.braintribe.com/browse/AD-354||CRITICAL||ADx Admin: Problem when synchronizing Type Definitions form DCTM/CMIS|
|https://jira.braintribe.com/browse/AD-350||CRITICAL||ADx Admin: Repository Activation state sometimes not correct in case of errors|
|https://jira.braintribe.com/browse/AD-306||CRITICAL||ADx Admin: Demo repository Documentum 6.7 is not working|
|https://jira.braintribe.com/browse/AD-324||CRITICAL||ADx Content: DCTM/CMIS Repositories throws error on some queries|
|https://jira.braintribe.com/browse/AD-297||CRITICAL||ADx Content: Repository Audit functionality disabled because of performance issues|
|https://jira.braintribe.com/browse/AD-348||MAJOR||ADx Admin: Repository Modification-Status not updated on Update|
|https://jira.braintribe.com/browse/AD-347||MAJOR||ADx Admin: Repository Deletion not properly working|
|https://jira.braintribe.com/browse/AD-331||MAJOR||ADx Content: After updating content with new file, old one is still presented in ADx explorer and is opened in web-reader|
|https://jira.braintribe.com/browse/AD-330||MAJOR||ADx Content: Missing ADx context information for conversion jobs|
|https://jira.braintribe.com/browse/AD-297||MAJOR||ADx Content: Enabled FullText could cause performance issues|
|https://jira.braintribe.com/browse/AD-342||MINOR||Hibernate warnings in the log files|
|https://jira.braintribe.com/browse/AD-341||MINOR||Java warnings during for Java 9 and later|
|https://jira.braintribe.com/browse/AD-311||MINOR||Oracle - DbLockManager prints Oracle constraint message|
When using Health/Conversion from the admin access, you may get the following error in case the health check page cannot be embedded:
In that case, simply click the indicated icon to open the page in a separate tab, where it should work normally.
|https://jira.braintribe.com/browse/AD-337||MAJOR||Make TF Conversion workbench consistent to ADx|
|https://jira.braintribe.com/browse/AD-338||MAJOR||Finalize Permissions on accessing Conversion|
|https://jira.braintribe.com/browse/AD-394||MAJOR||Remote conversion user needs extended access rights.|
|https://jira.braintribe.com/browse/CORETS-427||MINOR||Finalize TF Conversion health check|
|https://jira.braintribe.com/browse/TFSTUD-187||MINOR||Add diagnostic package for failed resources|
|https://jira.braintribe.com/browse/EXTDOCS-71||MINOR||Fix wrong encoding on opening resource in Browser|
When using Java 9 or later, the following warning may appear in application logs and also during installation procedure:
WARNING: An illegal reflective access operation has occurred WARNING : Illegal reflective access by com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1 (file:/path/to/instant-type-weaving-1.0.28.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte,int,int) WARNING: Please consider reporting this to the maintainers of com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release
The log files may contain Hibernate-related warnings. They can be identified based on the fully qualified class which starts with
org.hibernate, as in:
WARNING org.hibernate.tuple.entity.EntityMetamodel 'HHH000084: Entity [com.braintribe.model.user.User] is abstract-class/interface explicitly mapped as non-abstract; be sure to supply entity-names' [TribefireServices-2.0:tribefire-services#initialize,ApplicationLoader:/tribefire-services#initialize]
These warnings do not affect the functionality of the application and can be ignored. We are working on a fix.