Team for Capella 5.2.0 (2021-12-28)

Compatibility: Capella 5.2.0

 

What's new

The Team for Capella 5.2.0 maintenance release brings several major changes (compared to Team for Capella 5.1.0):

  • Compatibility with Capella 5.2.0
  • UX enhancements
    • In the Export project wizard, the behavior of the Override existing resources has been improved: whereas on previous versions the override was simply forbidden as soon as a Library project was detected on the server, now the export is forbidden if one of the resources to override is a Library resource and at least one of the remote projects is not overriden.
    • Location selection page displayed at representation creation (and move) has been improved to use less ambiguous labels and terms for end-users.
  • Locks management
    • The save action now sends the commit data and the unlock messages in the same network request.
      • This allows to optimize the network usage and also to minimize the number of notifications to send to all connected users and the implied distribution potential issues.
    • All impacted elements by a deletion are now locked as soon as possible before executing the delete command.
      • After a deletion (ie after having validate the impact analysis dialog), some impacted semantic elements by the deletion (such as the container of a deleted element) were locked only in a second time. Most of the time, that was not visible by the end user but a second lock message was later sent to the server.
      • That might lead to interrupt the delete during its execution if a lock instance exception was received.
  • Packaging, installation and deployment enhancements
    • The embedded documentation has been extracted in order to be available for administrators without having to launch the Team for Capella client. 
    • Scheduler
      • Jenkins has been removed from Team for Capella bundles. Jenkins becomes a required installed software to deploy the Scheduler.
      • The bundle now contains documentation and scripts to help the installation and configuration of Jenkins.
        • The provided scripts and configuration tips allow to retrieve the same set of Jobs, Views of the Scheduler as in Team for Capella 5.1.0.
        • The installation and configuration process and script have been described and tested with Jenkins LTS 2.303.3.
        • The System Administration Guide have been complete with Jenkins installation page.
      • The targeted Jenkins version has been updated from LTS version 2.277.3 to LTS version 2.303.3.
        • This brings several important security fixes and also notable changes as documented in the LTS release notes.
  • Server
    • OpenID Connect authentication support has been added to Team for Capella.
      • The configuration to use OpenID Connect targeting MS Azure AD can be retrieved in the Activate OpenID Connect authentication documentation section.
  • Tools
    • Command
      • New API has been added to send timeout specification to the OSGI console client.
        • The parameter -consoleTimeout can now be used for the importer and maintenance applications and jobs to define the timeout for the commands sent to the server.
        • If a command is stuck too long compared to the timeout, a SocketTimeoutException will be thrown.
    • Importer
      • A lock is acquired on aird resources before performing the CDO XML dump.
        • This action prevents other connected users to commit their changes during the XML dump.
        • This modification concerns only the Snapshot import importer strategy.
      • The import steps order has changed to avoid issues with imported images.
        • There is now a first step with import of projects and a second with archiving of projects.
        • The number of projects in "Import to local final status" can be different of the number in "Archiving final status".
        • Indeed, some dependency projects can also be archived.
      • The parameter -includeCommitHistoryChanges now works with Snapshot and Offline import strategies.
      • Images from Libraries are now correctly imported by the Importer application.
      • It is now possible to import a project whose Project element status has been set.

More details can be found in the documentation.

 

Important note

Windows 10 users: Windows 10 Defender significantly slows down Eclipse, reason being Windows 10 Defender scanning the JAR files. The problem has been reported to Microsoft here. Until then, a workaround to this problem is to add Eclipse root directory to Windows 10 Defender's exclusion list, detailed steps are shared here.

Note: This issue is not specific to Eclipse.

 

Fixed Issues

This version also introduces several fixes:

  • Capella fragments are now shown after an import from repository.
  • Lock state prefetch is now more robust against ObjectNotFoundException, NullPointerException or RemoteException.
  • Avoid random infinite loop in SSL Connector.
  • Remote session manager subscription: reaction to remote session notifications instead of multiple calls to the server.
  • Better handle exceptions in import/export wizards.

 

Rebuild on 2022-02-22

The Team for Capella 5.2.0 bundles have been modified to include a patch plugin in the server.

In some conditions, the attempt to lock aird resources before performing the CDO XML dump fails due to a missing permission to access data when the revision cache has been garbage collected. Several component can be impacted: the cdo export command, the Importer application, the automatic backup jobs (Projects - Imports and derivative jobs), ..

The patch plugins brings the missing permission to the command provider, it also allows to retrieve the 5.1.0 behavior (no lock aird attempt) with the use of -Dcom.thalesgroup.mde.collab.internal.server.export.xml.disableAirdsLocking=true in TeamForCapella/server/server.ini.

The Scheduler resources have also been improved in the Linux bundle in order to avoid several manual installation steps around Xvnc.


For servers deployed with Team for Capella 5.2.0 downloaded before February 22nd, 2022, the patch is available through your usual support channel.