Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

In this article

You can find below the major changes and improvements of Analytics 2.3.x version.

This article only highlights the most important changes.

If you need further information, please consult the full changelog and/or reference documentation.

Prerequisites:

Analytics 2.3.x requires a Java virtual machine 1.8 or higher

 

What's new in 2.3.5?

Bug fixes

This version fixes several issues which can be found in the full changelog.

Do not hesitate to give it a look to have an idea of what have been fixed.

 

What's new in 2.3.4?

Refreshing Runtimes in background

When you refresh all the Runtimes from Runtimes root node in the Navigator, Analytics now offers to perform the operation in background.

This can be useful when there are a lot of Runtimes, which some may be unavailable, and therefore take some time to refresh everything.

You can now simply put this task in background so that you can continue working while the Runtimes refresh operation is finishing behind the scenes.

refresh

 

Bug fixes

This version also fixes issues which can be found in the full changelog.

Do not hesitate to give it a look to have an idea of what have been fixed.

 

What's new in 2.3.3?

Stambia DI Designer 2020 / DI Runtime 2020 compatibility

This version supports importing packages generated from Stambia DI Designer 2020 and connecting to and operating Stambia DI Runtime 2020.

 

Ability to connect to Runtimes through HTTPS

This version supports connecting to Runtime secured with HTTPS.

Make sure you have read the Communicating with Runtime article to know learn about how to configure the necessary certificates and when it is required.

 

Runtime RMI / RMIS hostname syntax

When defining your Runtimes in Analytics, you can now prefix the hostname with the RMI or RMIS protocol.

For instance, you can define a Runtime as "rmi://<hostname>" or "rmis://<hostname>".

As a reminder, when you define a hostname without protocol, it will automatically guess it is RMI or RMIS, and try with each one to know the correct one to use.

 

Being able to specify the protocol helps to know exactly which protocol will be used and is clearer to know which Runtime is connected with which protocol.

Refer to Communicating with Runtime article for further information.

 

RMIS Configuration

Analytics does not anymore include the internal certificate used for communicating with Runtimes through RMIS.

This certificate has been removed, as from Stambia DI Runtime 2020 you can customize it to use your own.

Therefore, when you want to connect to Runtimes through RMIS, you may now have to configure Analytics application server to specify the public certificate to be used.

 

Refer to this article to learn how to configure the clients such as Designer, Analytics, or command line scripts to communicate with a Runtime which endpoints are secured with TLS.

It also proposes as a separate download the internal public certificate which must be configured in Analytics if you want to connect from Analytics through RMIS on previous Runtimes which were using this internal certificate (Runtime S17.x.x).

 

Other improvements

This version contains other improvements which can be found in the full changelog.

Do not hesitate to give it a look to have an idea of what have been fixed.

 

What's new in 2.3.2?

Bug fixes

This version fixes several issues which can be found in the full changelog.

Do not hesitate to give it a look to have an idea of what have been fixed.

 

What's new in 2.3.1?

Ability to connect to Runtimes through HTTP

Runtime versions S17.6.6 and higher offering possiblity to connect through HTTP in addition to RMI, Analytics has been updated to support this new new protocol.

When HTTP client connections are enabled on a Runtime, simply specify hostname and port accordingly, as described in following article.

 

Bug fixes

This version fixes several issues which can be found in the full changelog.

Do not hesitate to give it a look to have an idea of what have been fixed.

 

What's new in 2.3.0?

Analytics updated to use latest eclipse platform

Recent browsers updates broke some of the graphical component such as labels overlapping others or scrollbars not effective anymore.

Eclipse platform on which Analytics is based has therefore been updated to address those graphical issues which are fixed on latest Eclipse platforms.

Updating this platform changed the minimum Java requirement for Analytics which is now Java 8.

Note also that this update will help benefiting of all other eclipse platform issues fixed.

 

Ability to connect to Runtimes which are secured through TLS.

S17.6.0 Runtime version and higher offers the possibility to secure the RMI connection through TLS, as explained in this article.

Analytics has been updated to support connecting to Runtimes on which this is enabled.

Everything is handled automatically by Analytics while connecting to Runtimes, no specific configuration is needed on Analytics part.

 

Regional settings used to format statistics

Statistics which are displayed in Statistics View are now automatically formatted using regional settings of the browser, making them clearer and more intuitive to read.

 

Bug fixes

This version fixes several issues which can be found in the full changelog.

Do not hesitate to give it a look to have an idea of what have been fixed.

Articles

Suggest a new Article!