The latest Sprint 2020.26 bring us a new version 2.1 of Design Room ONE available for HCL RTist users. In this new version authentication functionality has been significantly improved and lost its EXPERIMENTAL tag.

One of the improvements includes refactoring the way the Design Room ONE server integrates with Keycloak for authentication. As a result, the configuration procedure is now easier: all the settings that need to be updated are now located in Design Room ONE’s main configuration file – server-config.json.

Due to these improvements, there is now no need for Design Room ONE to store a Keycloak administrator key making this integration even safer, since Design Room ONE server would only be able to access pieces of Keycloak information it needs to manage access to its designs.

You can refer to Authentication Setup for detailed instruction on migrating Keycloak realms configured with previous versions of Design Room ONE without loosing any information about users and their roles.

Another update related to server configuration is the introduction of a single property dr_db_url controlling database connection — provides more flexibility and allows using password protected databases, which are standard in cloud environments like Azure or AWS.

This is since version 2.1 Design Room ONE supports integration with Collaborative Lifecycle Management (CLM) tools version 6.0.6.1.

If you are using CLM tools to track your requirements with CLM 6.0.6.1 (read System Requirements for the full list of supported versions and other requirements) you would be able to create “Derived From” links in your modeling tool e.g. HCL RTist from a model element to a requirement.

These links will be visible in Design Room ONE after the model has been exported to the server. After that matching “Derives Architecture Element” links will be visible in your requirements management application and you would be able to create “References” links from say a requirement or a testcase to a model element published in Design Room ONE.

Keycloak integration

It is also possible to configure Keycloak integration to use the same Jazz Authorization Server (JAS) that is used by your CLM suite. This will allow users to authenticate with JAS when exporting the models and in web browsers it would be enough to authenticate once to access both CLM and Design Room ONE resources.

DesignRoom One

The procedure of configuring Keycloak identity provider is described in detail in Authentication Setup document.

The full list of improvements includes many more, for example the version of jQuery library used to render Design Room ONE web pages has been upgraded to 3.5.1 to improve security. Also, slot values for attributes in class InstanceSpecifications are now shown in the Properties view.

Properties

And the deployment script deploy-dr.js, which usage is described in Installation Instructions document, has been improved to report deployment name in all messages related to the server, this will help in cases when you want to run several Design Room ONE server instances on the same machine.

This video also provides these important updates.

Comment wrap
Further Reading
article-img
Secure DevOps | May 5, 2021
HCL RTist Development Team Announces RTist 11.1 for Download
The RTist development team has been busy finalizing RTist 11.1, and today we are happy to announce its general availability for download. The full version number is 11.1 2021.16, and at the same time we also release 11.0 2021.16, which is planned to be the last delivery on the 11.0 release track. All new features in the 11.0 release are also present in the 11.1 release. The only exception is the OneTest Embedded integration which we will make available in the next release of RTist 11.1 (expected to arrive mid-June). Let's have a look at the new features. Code Preview It's now possible to get a preview of what generated code will look like for an individual model element. This feature can be used for understanding how changes made in the model will affect the generated code. It can also be used as a means to compare two versions of a model at code level. Simply generate a code preview for each of the model element versions and compare them. You can also use this feature on transformation configurations to get a preview of all code and/or make files that it will generate. This can be of great help for troubleshooting build problems and to compare versions of an RTist application at code level.     OneTest Embedded Integration The integration with HCL OneTest Embedded allows you to compute and visualize the run-time coverage of state machines in your application. For example, it can be used for finding states and transitions of a state machine that are not covered by current tests. In this release a number of usability improvements were made, in particular in the Model Coverage viewer. For example, you can now choose to show coverage graphically in only some of the state chart diagrams.     Again, remember that...
article-img
Secure DevOps | March 4, 2021
Storing Code in Model Files Using CDATA
RTist models are stored in XML files (.emx and .efx). If you have ever opened such a file in a text editor you have probably noticed that code snippets stored in the model can be quite difficult to read due to the encoding of certain characters that is mandated by XML. Here is an example:     Some code snippets are stored as attributes in XML and they can look even worse, since newlines also will be encoded so that the whole code snippet appears on a single line:     Starting with RTist 11.0 2020.33 it's now possible to set a preference so that code snippets will be saved in CDATA sections in the XML file. Thereby the code does not need to be escaped which greatly improves its readability. The preference is called Use CDATA when saving model files and is located on the Modeling preference page. In addition to code snippets, it also affects how documentation texts are stored.     After setting this preference, the code snippets in the examples above will look like this:       Note that older versions of RTist can still read model files that use CDATA. In that sense this feature is backwards compatible. Note, however, that if you edit and save the model in such an old tool version the code snippets will once again be stored without usage of CDATA.  If you decide to start using CDATA in your model files it can be a bit tedious to manually re-save all files in the workspace to use the new format. To simplify you can run a model fixup which will automatically convert all your model files to use CDATA.     Watch this video for more information.
Close