Stambia Data Integration versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January 15th, 2024.


It is recommended to move to a Semarchy xDI supported version.


Read the Global Support Policy for more details about the LTS and MS release types. 
This page also lists, per release, the first release, end-of-maintenance, and end-of-support dates.


There are dedicated upgrade procedures for different major versions. 


The game changer : Components introduced in S20

In its history, Stambia has improved constantly and added some key concepts mainly in S20.

So, if you are coming from a version prior to S20, we must talk about the Components and specially Templates and Modules that have an impact on the Migration. 


Starting from S20, all the technical resources required to work with your environment such as "Technologies", "Templates", "Modules", "Sample Projects" and "Documentation" are included in Components. This implies that if you are coming from a version prior to S20, you will have to install the Components you need.

Templates


One of the major points to have in mind is that you don't have to import anymore any Templates in your workspace. 


Most Templates have been updated, so previous Templates from S17, S18, S19 versions might not work properly.


Unless you have modified some Templates that you would like to keep, you must remove all the Templates of your workspace. For this, simply delete them from your Project (they are usually imported in the "global" Project).


Modules


A Module is a set of all what is necessary to communicate with a technology.


Instead of having to download some files and copy them in different folders, xDI allows you to handle all through Modules.


Also, keep in mind that :


No intermediate version is mandatory

Whatever the Stambia version you are coming from, there is no mandatory intermediate version you need to go through. 
Of course, the older the version is, the higher the upgrade impact will be.


Compatibility

For all releases, upgrades are incremental and backward-compatible. Customers using any (MS or LTS) release may upgrade to any subsequent (MS or LTS) release of the same product.
We strongly recommend to have all the components versions aligned.


Review the Documentation

Before starting the upgrade, you should review the following information:
  • The Release Notes provides the latest information about the Semarchy xDI Release, including new features and bug fixes.
  • The installation instructions for installing and configuring Semarchy xDI. You should review the System Requirements for this new release.


Plan some tests

Testing is not optional.



This article summarizes the procedure for a major upgrade from Stambia to Semarchy xDI 2023.1 LTS.
- Read the Release Notes.
- Read the System Requirements.
- Read the Upgrade Notes.


Step 1 - Upgrade the Licence Server


Upgrading the Semarchy xDI License Server is a prerequisite to the migration of Semarchy xDI Designer if registration is performed against an on-premises license server.



Caution


Configure SSL/TLS

The License Server communicates with the clients using the HTTP protocol. You must configure whether SSL/TLS is enabled for the communications.

Enable SSL/TLS

If you enable SSL/TLS and configure it with a self-signed certificate, you must provide this certificate to Semarchy xDI Designer. Otherwise, the Semarchy xDI Designer will refuse to connect the license server because the certificate is self-signed.

Designer versions prior to 20.4.0 did not allow using a custom certificate. If you are connecting to the License Server with these versions, contact the support team who will assist you to configure the License Server with a legacy certificate.

Disable SSL/TLS

If you disable SSL/TLS in the license server, make sure that it is accessible only via an SSL/TLS secured layer, such as a proxy, load-balancer, or a similar application. This is mandatory as Semarchy xDI Designer only accepts connecting with SSL/TLS.



Prerequisite


Get a Compatible License File

Contact the Semarchy support or your account representative to obtain a new license file to deploy in your License Server.



Upgrade Procedure


Follow the Upgrade Documentation.


Step 2 - Upgrade the Runtime


Caution


Noticable changes

When upgrading to 2023.1 LTS, pay attention to the Noticable changes.


Scheduler Database

If you are using the Semarchy xDI Runtime Scheduler, you will have to manually update the Scheduler database during the upgrade procedure.


The database structure has changed following an upgrade of the third-party library used for the Scheduler, which requires an update of the database structure.


Upgrading from version S17

About Modules

The major change of version S20 is the introduction of Modules which is now the main mechanism to handle additional libraries.

We highly suggest to read "Getting started with Modules" article to understand the concepts and what this will change.

The default location for Modules is now <semarchy-xdi-runtime>/modules folder. 
On version S17, all the libraries where copied under <Stambia Runtime>/lib folder.

From now, you should use Modules instead of manually copying libraries inside this Runtime folder which must not be used anymore.

About "default" Module

For the upgrade, you can put all your existing libraries inside the Module called "default" which is a fallback Module used when no Module is specified in Metadata.

If you put all the libraries you were copy/pasting in lib folder in previous versions inside this "default" Module, your existing Mappings should work without having to define a Module in all your Metadata.

As indicated, this "default" Module is a fallback module which is used when no Module is specified, so it will be used for all your Metadata if you do not specify a Module in.

Note that using "default" Module will not work for the following Components which requires to create and use a Module explicitly: Salesforce, MongoDB, Hadoop, Google Cloud Platform, Google BigQuery, Kafka, Elasticsearch, SAP or Excel.


JDBC Pooling Connections

In the Semarchy xDI Runtime configuration, JDBC Connection management and pooling have been reviewed to improve stability and performance. 

The following pooling parameters have been removed :
  • enableConnectionPoolForJdbcDatabases
  • enableConnectionPoolForLogDatabases


The pooling is now :
  • enabled by default 
  • the configuration is managed in the metadata configuration.


RMI Protocol Discontinued

Semarchy xDI Designer and Semarchy xDI Runtime no longer use the RMI protocol for their communications. HTTP entirely replaces this protocol.

Semarchy xDI Production Analytics still supports this protocol to communicate with previous Runtime versions. This support will be removed in a future version.



Upgrade Procedure 


Follow the Upgrade Documentation.


Step 3 - Upgrade the Designer


Upgrading the Semarchy xDI License Server is a prerequisite to the migration of Semarchy xDI Designer if registration is performed against an on-premises license server.


Caution


Noticable changes

When upgrading to 2023.1 LTS, pay attention to the Noticable changes.


RMI Protocol Discontinued

Semarchy xDI Designer and Semarchy xDI Runtime no longer use the RMI protocol for their communications. HTTP entirely replaces this protocol.

Semarchy xDI Production Analytics still supports this protocol to communicate with previous Runtime versions. This support will be removed in a future version.



Prerequisite


Get a Compatible License Key

Semarchy xDI Designer 2023.1.x requires a 2023.1.x compatible license key.

Contact the Semarchy support or your account representative to get a compatible license key.



Upgrade Procedure 


Follow the Upgrade Documentation.


Tips

Create a reference Designer that :
  • contains the Components corresponding to the technologies you are working with - Installation is detailed here. Test your connection to each of your technology to make sure you have installed all what you need.
  • contains the Modules you need - you can see how to manage modules here
  • keeps only the personalized templates you wish to use (because they do not exist in 2023.1 for example) in your global project. Be aware that if a personalized Template as the same name than an official one, it will be the personalized one that will be used in your mappings. This is the reason you should keep as less templates as possible to benefit of all the new features added in the new versions.


Step 4 - Upgrade the Production Analytics


Caution


Noticable changes

When upgrading to 2023.1 LTS, pay attention to the Noticable changes.


Upgrading from version 2.x.x

Migrating from 2.x.x requires a particular attention as 3.x.x introduces major improvements and changes.

A complete migration wizard included in the application has been developed to help users to migrate.


RMI Protocol Discontinued

Semarchy xDI Designer and Semarchy xDI Runtime no longer use the RMI protocol for their communications. HTTP entirely replaces this protocol.

Semarchy xDI Production Analytics still supports this protocol to communicate with previous Runtime versions. This support will be removed in a future version.



Upgrade Procedure 


Follow the Upgrade Documentation.


Tips

We recommend to delete (or rename) the Semarchy tomcat work folder - it will avoid conflicts with the temporary objects. A new one will be created when tomcat will be restarted.