If you want to run your existing Data Services or Routes on the new 6.4.x Container, you need to re-build, re-publish and re-deploy the Studio models to use the latest code changes.
We support the mixed installation and use of Talend ESB container 6.3.x/6.2.x/6.1.x/6.0.x/5.6.x with Data Services and Routes generated by Talend ESB Studio6.3.x/ 6.2.x/6.1.x/6.0.x/5.6.x and the Talend ESB Infrastructure Services in 6.4.x.
The Service Registry 6.4.1 migration from older versions requires an export of all
artifacts in the older version Service Registry (using the TAC Service Registry UI or
tregistry:export command). Then this full export can be used to
import the Service Registry content into a new Service Registry installation done for
Note that due to a change in the
container/etc/org.talend.esb.job.saml.policy file to use an SHA2
instead of SHA1 algorithm suite, if you run on previous versions of Talend Runtime older
than 6.4.1, you need an updated policy using the Basic128Sha256 AlgorithmSuite. This
only affects clients who need to communicate with a 6.4.1 provider and who use the
design time SAML Token authentication option (tESBConsumer > Authentication > SAML Token
). Clients and 6.4.1 provider that use the Service Registry are not affected by this
change as they get the policies from the Service Registry.