This release introduces critical updates, including a brand-new user interface as well as the possibility to run ADx and Conversion nodes as part of a cluster, utilizing ActiveMQ for communication between nodes.
On this page
- Updated User Interface
- Clustered Setup
- New Features and Improvements
- Bug Fixes ADx
- Bug Fixes Conversion
- New Runtime Properties
- Changed Runtime Properties
- Removed Runtime Properties
- Known Issues
You can install this release from the provided package. Follow Installation Instructions for more details.
New user interface is now available, providing ADx-specific landing page and branding. Documentation has been updated as required to match the newly implemented logic.
Clustered setup for ADx and Conversion is now available. Example installation settings file has been updated with comments accordingly and installation documentation has been updated.
For architecture details, check architecture documentation.
The following features are provided in this release:
|https://jira.braintribe.com/browse/AD-319||ADx Landing Page||Critical|
|https://jira.braintribe.com/browse/AD-401||ADx Admin: Migration Tool for 1.1 Configuration migration||Critical|
|https://jira.braintribe.com/browse/AD-455||Add resulting content IDs to ContentRepresentationJob||Major|
|https://jira.braintribe.com/browse/AD-405||ADx architecture: use single database for Conversion system & business data?||Major|
|https://jira.braintribe.com/browse/AD-440||Refactoring deep health check for graphical reports||Minor|
|https://jira.braintribe.com/browse/AD-323||ADx Explorer: Show Repository Information||Major|
|https://jira.braintribe.com/browse/AD-474||Deep health check: Save report as resource||Minor|
The following issues were resolved.
|https://jira.braintribe.com/browse/AD-442||Resource not found while downloading from Content Access||MAJOR|
|https://jira.braintribe.com/browse/AD-492||New allows creating every entity||Blocker|
|https://jira.braintribe.com/browse/AD-502||Download of Logfiles doesn't work||Critical|
|https://jira.braintribe.com/browse/AD-476||Scroll-issue in Properties-panel||Critical|
|https://jira.braintribe.com/browse/AD-503||Cannot delete new version of file after older is deleted||Major|
|https://jira.braintribe.com/browse/AD-306||Demo repository Documentum 6.7 is not working||Major|
|https://jira.braintribe.com/browse/AD-431||Users list is stuffed with duplicates and cartridge names||Major|
|https://jira.braintribe.com/browse/AD-461||Repository with name 'CMIS Documentum 7.3 R2' cannot be created||Major|
|https://jira.braintribe.com/browse/AD-283||Transformation is working with max 40MB txt files||Major|
|https://jira.braintribe.com/browse/AD-425||After editing repository error pops out||Major|
|https://jira.braintribe.com/browse/AD-490||Error when creating folder without a name||Major|
|https://jira.braintribe.com/browse/AD-392||Adding new role with description fails||Major|
|https://jira.braintribe.com/browse/AD-485||Error when upload a file without specifying the file||Major|
|https://jira.braintribe.com/browse/AD-509||Handling large repository names and names with special characters||Major|
|https://jira.braintribe.com/browse/AD-478||Testreport opens on localhost||Major|
|https://jira.braintribe.com/browse/AD-442||Resource not found while downloading from Content Access||Major|
|https://jira.braintribe.com/browse/AD-426||Password is stored as plane text in postgresql DB, even with @Confidential annotation Major|
|https://jira.braintribe.com/browse/AD-409||UI cannot display a large number of tabs properly||Minor|
|https://jira.braintribe.com/browse/AD-462||Cleanup errors on conversion when conversion access is not deployed||Minor|
The following issues were resolved.
|https://jira.braintribe.com/browse/AD-513||Converting PPT fails||Critical|
|https://jira.braintribe.com/browse/AD-442||MAJOR||Resource not found while downloading from Content Access|
The following runtime properties were added in this release:
|TRIBEFIRE_RUNTIME_OFFER_STAYSIGNED||When this is set to true, the login dialog will offer an option to stay signed-in after a browser restart. If set to false, the user session will always be closed when the browser is closed. This is achieved by using a session cookie that stores the user's session ID until the browser is closed.|
|TRIBEFIRE_IS_CLUSTERED||Indicates whether or not this node is part of a cluster.|
The following propertied had their functionality or default values changed.
|TRIBEFIRE_USER_SESSIONS_MAX_IDLE_TIME||Default changed from 24h to 30m|
The following properties were removed in this release:
A list of problems we're aware of and working on.
|https://jira.braintribe.com/browse/AD-447||CRITICAL||Potential Race Condition when checkout & updating Content consecutively|
|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-324||CRITICAL||ADx Content: DCTM/CMIS Repositories throws error on some queries|
|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-330||MAJOR||ADx Content: Missing ADx context information for conversion jobs|
|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 running conversion health checks from either administrator area or the landing page, you may get a connection refused error in case the health check page cannot be embedded.
Checking from the administrator area:
Checking from the landing page:
Error message (highlighted icon is only present if you navigate from the admin area):
If it happens, use the health check from the admin area and click the indicated icon to open the page in a separate tab, where it should work normally.
Due to cache database being shared between repositories, it's not possible for now to run multiple migration jobs from a single legacy repository at the same time. You need to wait for the previous migration to finish before running a new one.
|https://jira.braintribe.com/browse/AD-337||MAJOR||Make TF Conversion workbench consistent to ADx|
|https://jira.braintribe.com/browse/AD-501||MAJOR||tf-conversion user has the admin role assigned|
|https://jira.braintribe.com/browse/AD-338||MAJOR||Finalize Permissions on accessing TF Converion|
|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.