Welcome Guest! Log in

In this article

You can find below the major changes and improvements of the Stambia DI Runtime S17.4 version.

This article only highlights the most important changes.

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

 

The configuration files of the Runtime have been reviewed and reorganized in this version to be clearer and more intuitive. See below for more information.

 

What's new in 17.4.10?

Bug fixes

This version comes with bug fixes that can be found on the full changelog.

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

 

What's new in 17.4.9?

Bug fixes

This version comes with bug fixes that can be found on the full changelog.

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

 

What's new in 17.4.8?

Stambia Published Web Services Asynchronous invocation

Stambia Published Web Services now support to be called in an asynchronous mode when invoked through HTTP REST.

When doing this, the session will be started on the Runtime and the Web Services call will hand back to the user without waiting it to finish.

This offers the possibility to start time consuming sessions without being locked on the client side.

To perform this, simply call your Stambia Web Service with an additional X-asynchronous=true HTTP header to the request.

Refer to this article for further information.

 

Ability to use the PATCH method in REST Web Services Invocations

This is now possible to use the PATCH method when invoking REST Web Services.

 

Minor enhancements

This version comes also with other minor enhancements that can be found on the full changelog.

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

 

Bug fixes

This version comes with bug fixes that can be found on the full changelog.

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

 

What's new in 17.4.7?

Bug fixes

This version fixes a bug on database saved Metadata Variables with large string values.

When storing large values, there was issues when retrieving them: they were truncated on some databases.

This issue should not happen anymore.

The full changelog of this version can be found here.

 

What's new in 17.4.6?

Get files with FTP can be binded

The Get Files with FTP Process Action now supports being the source of a bind.

This means that you can now bind the result of the action to another one and retrieve through all the information about the retrieved files.

The bind variables available are the same as the ones which are stored in the table created when drag and dropping a database schema on the action.

The complete list can be found in the action's reference documentation.

ftpgetbind

 

What's new in 17.4.5?

Runtime security: ability to specify an anonymous user

When Runtime security is enabled, there is now the possibility to define an anonymous user, with its specific permissions.

This offers the ability to authorize anonymous connections (without user / password) with restricted permissions on secured Runtimes.

This allows for instance to allow anonymous connections only for consultation:

<user anonymous="true" roles="Connect View"/>

 

Refer to this article for further information.

 

XML Reading performance improvements

We've made some improvements on the action used to read XML files, proving better performances.

This will mostly impact the XML templates using the export functionality, such as the 'Load XML to Vertica' one, but it also features improvements for common XML Reading.

You may therefore notice performances improvements on your treatments reading XML files.

 

New parameter supported for the Execute delivery Action

A new parameter is supported on the Execute Delivery Process Action: 'Deliv Remote Delivery Mode':

executeDeliveryRemoteDeliveryMode

 

When 'Deliv Engine Host' and 'Deliv Engine Port' parameters are set, by default the execute delivery action is looking for the delivery in the Runtime executing the action.

This option offers the possibility to specify that the delivery should be searched in the remote Runtime instead (the one defined with the parameters).

In this case, the delivery file must be present in the remote Runtime.

 

New parameter in Execute Delivery Command

The execute delivery command was missing the possibility to specify the session name to use for the execution.

This isn't the case anymore!

The 'sessionName' parameter is now available to define it as you want.

execute delivery mydelivery sessionName mySessionName

 

Bug fixes

As usual, this version also comes with bug fixes that can be found on the full changelog.

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

 

What's new in 17.4.4?

Minor enhancements

Some minor enhancements are shipped in this new version.

They are all listed in the full changelog that can be accessed from this link.

 

Bug fixes

As usual, this version also comes with bug fixes that can be found on the full changelog.

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

 

What's new in 17.4.3?

HTTPS Security for Published Web Services

The endpoints exposed for Stambia Published Web Services can now be secured with HTTPS.

This new security can be enabled in the Runtime's property files, as explained in the dedicated article.

Do not hesitate to consult it for more detailed information about the configurations steps.

 

File Driver and hierarchical folders

The Designer S18.3.3 introduces a new feature in the File Metadata that allows to design the folders hierarchy as it is physically.

Therefore, the Runtime has been updated to support this change to be able to lo handle this kind of Metadata.

Using the S17.4.3 Runtime is mandatory to benefit of the Designer's enhancement.

 

Bug fixes

As usual, this version also comes with bug fixes that can be found on the full changelog.

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

 

What's new in 17.4.2?

REST Web Service Invocation

Raw, unstructured data, such as binary files or plain text, can now be sent seamlessly when invoking a REST Web Service.

This new feature can be used easily, as explained in the following article.

Do not hesitate to consult it to learn how to use this new functionality in your developments.

 

What's new in 17.4.1?

Sorting data when loading XML / JSON

This version introduces a new functionality on XML and JSON files.

When loading them, it is now possible to sort data as wanted with the use of sort keys.

Refer to the following articles for more information:

 

What's new in 17.4.0?

Reorganization of the Runtime's Configuration files

All the files located under the <stambiaRuntime>/properties/ folder has been reviewed and reorganised.

  • All the configuration is now centralized in one file: engineParameters.xml
  • Comments, descriptions, and examples have been added to illustrates the available and possible options
  • Several samples have been added in the <stambiaRuntime>/properties/samples/ folder to make easier the understanding of the configuration through examples

 

Notes

  • Configuration files from previous versions will continue to work.
  • The parameters can still be externalized in dedicated files if needed.

 

Java additional Options

In addition, Java additional options, usually set with the -Doption01=value01 argument on the Java command launching the Runtime, can now be specified directly in the Runtime's configuration file.

Refer to this article for more information.

 

Security

User restriction and roles

The connection to the Runtime can now be secured with a user / password.

This new functionality offers the possibility to define a list of users, with specific roles, that can connect and make operations on the Runtime.

Refer to this article for more information.

Prerequisites:

Stambia DI Designer S18.3.0 or higher is required to connect to a Runtime secured with a user / password.

 

Hostname / IP restriction

The connection to the Runtime can now be restricted to a list of allowed hostnames / IP addresses

Refer to this article for more information.

 

Load balancing / Failover

Runtime clustering

A new system has been introduced to allow the configuration of a native load balanced pool of Runtimes with failover management.

When configured, the sessions executed on the cluster will be automatically load balanced to one of the Runtimes with the chosen method.

Failover Runtimes can also be defined to take over the executions when the main Runtimes are unavailable.

Refer to this article for more information.

 

Auto-Restart of sessions

The sessions can now be configured to be restarted automatically when errors are detected.

The delay and the number of restarts can be specified directly in the Processes.

Refer to this article for more information.

 

Web Services improvements

Stambia Web Services improvements

Input / Output / Fault temporary files deletion

Three new configuration parameters have been added to manage the Input, Output, and Fault temporary files generated during the invocation of a Stambia Web Service.

They offer the possibility to choose if they should be kept or not, or only when an error occurred during the invocation.

Refer to this article for more information.

 

URL Path Parameters

Parameters defined directly in the Input URL's path can be used as Input parameters.

E.g http://stambia:42200/rest/StambiaDeliveryService/2/myDelivery/id/3

In this example, 'id' and '3' can be retrieved in the Web Service's Process.

Refer to this article for more information.

 

Input and Output HTTP Headers

Input and Output HTTP Headers can be defined in Stambia Web Services.

Refer to this article for more information.

 

HTTP Response Code

A new META-INF allows to customize the HTTP Response code returned by the Web Service.

Refer to this article for more information.

 

Web Services Invocation improvements

Response HTTP Headers

The HTTP headers returned after a Web Service invocation can now be retrieved and stored in a database.

They can be defined under the Output node of the WSDL Metadata, and then mapped as usual in the Mappings.

Refer to this article for more information.

 

HTTP Response Code and Message

As the HTTP Headers, the HTTP Status code and HTTP Response Message returned by a Web Service can now be retrieved and stored in a database.

They can be defined in the Output of the WSDL Metadata and then mapped as usual in the Mappings.

Refer to this article for more information.

 

Customizing the HTTP Verb at invocation

The HTTP Verb used when invoking a Web Service, such as POST, GET, PUT or DELETE can now be specified directly in your Mappings.

This allows to dynamically choose the HTTP Verb used at execution.

Refer to this article for more information.

 

JSON and XML improvements

Property Fields

A new type of field has been introduced in the Stambia's JSON and XML technologies, called "Property Field".

This new type of field offers the possibility to retrieve dynamically the information about the JSON and XML files at execution, such as the file name, size, or path.

It moreover allows to load dynamically JSON or XML nodes' name at write.

Refer to the following articles for more information:

 

Name Selection Pattern

It is now possible to read JSON and XML files which contain nodes with varying name.

This specific case happens when the nodes do not have a generic name like 'customer' for instance but data information instead.

E.g. The name of the node below is the name of the person:

{
    "json_person": {
        "GIBBS": {
            "id": 1,
"firstname": "Jason", "lastname": "GIBBS", "company": "" } } }

 

Refer to the following articles for more information:

 

Reading multiple files

This version introduces a new feature that allows to read multiple JSON or XML files at the same time.

It consists of using masks in the file's path, such as:

D:/folder/customer*.json|exclude::D:/folder/customer2.json

This offers the possibility to load a bunch of files with the same structure.

Refer to the following articles for more information:

 

File Driver improvements

Ending lines to skip

A new parameter has been added on the File Metadata to specify a number of ending lines to skip when reading the file.

This is particularly useful on files containing footers for instance.

endingLinesToSkip

 

Filtering a range of records

The filters available on the File Metadata have two new parameters that offer the possibility to specify the range of record to process.

This allows to filter the lines when loading files.

Refer to this article for more information.

 

You have no rights to post comments

Articles

Suggest a new Article!