Welcome Guest! Log in


 

In this article

You can find below the major changes and improvements of Stambia DI Designer 2020 (S20.4.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

Migration from S17, S18, S19

Stambia DI 2020 (S20) major version changes some important part of the software which require your attention.

Migrating from Stambia DI Designer S17, S18 or S19 require to follow the migration guide, which can be found in the following article.

If you are simply updating from another Stambia DI 2020 (S20) version, simply follow the minor version upgrade guide, as usual.

 

What's new on Stambia DI Designer S20.4.3

Bug fix

This version includes an updated Runtime which contains a fixed issue.

The release notes of the Runtime can be found here.

Note that the Designer itself has not changed, it only contains an updated Runtime.

 

What's new on Stambia DI Designer S20.4.2

  • We have disabled the download of this version because a regression was found inside.
  • Please use next S20.4.3 (or higher) version fixing it.

 

Usability improvements

Some improvements and fixed issues. Have a look at the Changelog for further information.

 

What's new on Stambia DI Designer S20.4.1

  • We have disabled the download of this version because a regression was found inside.
  • Please use next S20.4.3 (or higher) version fixing it.

 

Stambia DI Components Updated (20.4.1)

You can find in this section the list of Components which have been updated in Designer 20.4.1

Note that this lists only the Components shipped within a default Designer.

Components name Update Description Components release notes
HTTP REST Component Fixed issues Release notes
Microsoft Excel Component Fixed issues Release notes

 

Usability improvements

SQL Explorer - New Stambia Query Editor

A new Stambia Query Editor has been implemented from this version to replace the SQL explorer.

This new Query Editor allows us to preform the SQL queries.

This is what the Stambia Query Editor looks like:

custom query editor

Note:

Note that this is the first designer version which include its own Stambia Query Editor. The most used features have been implemented in this version and they work well, and we still work on it for more improvements.

 

Minor improvements and fixed issues

This version also contains some other minor improvements and fixed issues, which can be found in the complete changelog.

 

What's new on Stambia DI Designer 2021 (S20.4.0)

  • We have disabled the download of this version because a regression was found inside.
  • Please use next S20.4.3 (or higher) version fixing it.

 

Stambia DI Components Updated (20.4.0)

You can find in this section the list of Components which have been updated in designer 20.4.0.

Note that this lists only the Components shipped within a default Designer.

Components name Update Description Components release notes
Base Component Some improvements and fixed issues Release notes
HTTP REST Component Some improvements and fixed issues Release notes
Microsoft Excel Component Fixed issues Release notes
Oracle Component Fixed issues Release notes

 

Usability Improvements

EMF Compare Tool

EMF Compare Tool has been added to allows to compare more easily such XML models.

EMF Compare can be used to make the usage of versioning easier with Stambia: to resolve easier merge conflict when using this versioning.

Further information about EMF compare tool can be found at this article.

 

Transparent staging area

Since Stambia DI 20.1.0, there is a capability : Ability to define transparent staging area on a target datastore.

Now, we add the list of preferred staging areas, in the properties of the target metadata.

In the Window / Preferences menu, the preferred staging areas are defined. (Stambia/Mapping/Staging Area).

staging01

Then, on the target metadata, the preferred staging areas are displayed, in the properties:

staging03

 

Computed fields in the mapper

On the mappings, the computed fields are now displayed in the mapper :

mapper

 

Modules Third Party Definition

Module Wizard guides you to manage, create, and use Modules.

When possible, we provided all the necessary libraries for a given Module to communicate with a given technology.

When this is the case, the libraries are shipped within the Modules itself or through the selection of a third party pack.

When we cannot redistribute the libraries, for licensing purposes for example, the third party pack combobox is now greyed out when there is no third party pack available.

Third 01

 

Import internal resources in the workspace

In the "Internal Resources" view, it is possible to import an element, a template for example, in the wokspace, with right click.

import01import02

Until now, it was not possible to import an element that was already imported. The menu was no longer displayed even though you wanted a different location.

Whith this version we can import an already imported element. The menu is always displayed. If you select the same location, an overwrite confirmation message is displayed.

import03

 

Export Models and Dependencies

Exporting a project now generates a configuration file, included in the zip: export.configuration.

The file contains the same elements as the Help / About Stambia Designer / Installation Details Menu, Configuration tab.

export02

 

export03

The file contains a lot of information: Date/Time of export, the Designer version, the Java version and architecture (32/64 bits), the operating system (linux / windows) and its version and architecture (32/64 bits), installed Components and their versions, versions of potential git / svn plugins ...

 

Metadata Improvements

XML Metadata

XML Reverse

To practical usage and especially to guide user with the different reverse methods (from XSD or from XML data file), XML wizard has been improved in order to propose reversing in XSD mode or XML mode. Reversing from an Xsd file mode is defined as default selected mode.

xml wizard

Reverse from an Xsd file mode

When keeping this default selected mode and continue by clicking to the "Next" button, user will be redirected to a screen where we select the XSD data file and the recursivity depth, initialized at 1 by default but user can change it.

from xsd

After selecting the Xsd data file, the screen to select the root element based on this selected Xsd file is proposed.

root element

Finally, user will be redirected to the usual screen where is proposed the nodes to reverse according to the selected root, and he can finish the reverse.

selective reverse

Reverse from an Xml data file mode

When the mode Reverse from an xml is selected instead of the Xsd mode, then the user will be redirected to screen where we select the Xml data file.

xml file mode

Selective reverse will be proposed to choose the nodes to reverse according to the selected .

After that, user will be redirected to the usual screen where is proposed the nodes to reverse according to the selected Xml file and user can finish the reverse .

 

XSD generation

"Generate XSD" option has been separated in a dedicated wizard. This new wizard named “XSD Generation Tool” is available on the root node of an XML Metadata.

generate xsd wizard

When starting the wizard, the fields to choose the Xml Data file from which we want to generate the XSD File are proposed, and then user can start the generation by clicking to the "Generate XSD" button.

xsd generation

 

Reverse REST Wizards

Selective reverse window

On selective reverse window, when asking to finish the reverse without selecting a node, a confirm message will be opened to inform the user that no node has been selected.

selective reverse window

The finish button closes the popup and the reverse window and the cancel button closes the popup but do not close the reverse wizard, to allow user to select node to reverse.

 

Reverse REST Wizard - Media Type field

A new input information named "Media Type" has been added on HTTP REST reverse wizard. The Media Type field allows to define which type of data it is, for instance JSON, XML, FORM, … and which is used to know which parser to use. When starting the wizard, The Media Type field is automatically filled with the defined value in Media Type Metadata attributes, if the attributes have a value defined.

The Content-Type Header has been also updated to allow to define the http content type header to be sent with the request.

An check option has been added to link "Media Type" and "Content-type Header": if checked, when a Media Type is selected then the Content-Type Header is automatically filled according to the selected Media type. For instance if JSON Media Type is selected, application/json should be selected automatically in Content-Type Header.

httprest wizard

Reverse REST Wizard - FORM values

Reverse REST wizard has been improved to ease the definition of FORM values.

FORM values used to be manually defined in the input body, which could not be very user friendly.

They will now be defined directly in the parameters table, and the wizard will automatically generate them with the proper syntax in the input body.

form values

 

Reverse REST Wizard - Authentication

The HTTP REST wizard has been updated to support NTLM authentication type and to support proxy security.

When NTLM security and Proxy security are defined then it will be successively proposed in Authentication type and in Security Proxy Reference on Reverse REST wizard launched launched an operation:

Authentication wizard

 

WSDL Wizard - NTLM node

A new node has been added on WSDL metadata to define NTLM properties.

wsdl ntlm wizard

Asking to create a new NTLM security allows to define the Name, UserName, Password and Domain of the security.

wsdl ntlm property

 

Reference content wizard

The reference content wizard which allow to create a Metadata based on a reference Metadata, such as Twitter Component, proposes the nodes to copy and new buttons "Select all" and "Deselect all" have been added in this wizard to allow user to mass select/deselect nodes.

content selection

 

Versionning systems

Egit plugin installation

Egit plugin is already installed by default on Stambia DI designer 20.4.0 or higher, and the version installed by default is the recommended version to use.

You can find the EGit installation at this location.

 

Subclipse Installation URL

Subclipse Installation URL has been moved from https://dl.bintray.com/subclipse/archive/release/1.8.x/ to https://subclipse.github.io/updates/subclipse/1.8.x/.

Product URL has been updated following this Subclipse Installation URL update:

subclipse

 

Stambia Licenses

In Licenses Service, we have the possibility to customize the certificate used by the license service,the designer has been updated to be able to define define certificate.

Designer certificates

Stambia.ini file has been updated to support four new properties to define an additional keystore containing the certificate for the license service.

To define the custom keystore that the designer will use additionally, we should configure stambia.ini file by adding the following lines:

-Dlicense.service.keystore.path= the path where is located the keystore.file
-Dlicense.service.keystore.type= the keystore type
-Dlicense.service.keystore.password= the security password
-Dlicense.service.keystore.key.alias= the keystore alias

After stambia.ini configuration set, we can use the matching server or key license in designer.

JVM certificates truststore

When exchanging with the license service, the certificates checks take into account the certificates of the JVM truststore.

For the exchanges the designer takes into account a combination of the following certificates:

  • the internal certificate
  • the JVM truststore
  • the custom keystore defined in stambia.ini (if defined)

With this, the designer takes into account automatically the truststore of the JVM, which allows to accept most of the signed certificates automatically.

For the configuration, following standard JVM options are used to specify the JVM truststore configuration, and should defined in stambia.ini file:

-Djavax.net.ssl.trustStore= the path where is located the keystore.file
-Djavax.net.ssl.trustStoreType= the keystore type
-Djavax.net.ssl.trustStoreProvider= provider
-Djavax.net.ssl.trustStorePassword=the keystore password

After stambia.ini configuration set, we can use the matching server or key license in designer.

 

Minor improvements and fixed issues

This version also contains some other minor improvements and fixed issues, which can be found in the complete changelog.

 

Bug fixes

This version fixes a list of issues which can be found on the full changelog.

Do not hesitate to take a look at it to have an idea of what have changed.

 

 

You have no rights to post comments

Articles

Suggest a new Article!