Skip to Content

Changes for page V3.0.0

Last modified by Carlijn Kokkeler on 2024/07/17 14:41
From version 17.1
edited by Carlijn Kokkeler
on 2024/04/08 11:44
Change comment: There is no comment for this version
To version 18.1
edited by Carlijn Kokkeler
on 2024/04/08 11:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,19 +18,14 @@
18 18  * JDBC Data source support: The BoneCP data source support object has been removed and replaced by the Hikari data source support object. eMagiz will generate a Hikari data source in every flow containing a BoneCP data source, after which you should verify the settings, replace the data source references and remove the BoneCP support object before deploying.
19 19  * Several components have small changes in their configurations which require a new flow version to be included in your release. eMagiz will create new flow versions for these changes, which you need to manually include in your release. These affects any flow that has any of the following components:
20 20  ** Data pipelines:
21 -*** ‘simple job launcher’ → eMagiz will push a new flow version which replaces this with ‘task executor job launcher’
21 +*** ‘simple job launcher’ → eMagiz will push a new flow version which replaces this with ‘task executor job launcher’
22 +*** ‘job explorer’ → eMagiz will push a new flow version which adds a ‘data source’.
23 +** Http message sender: HttpComponentsMessageSender → eMagiz will replace this with HttpComponents5MessageSender
24 +** SOAP webservices: Web service outbound gateway → eMagiz will push a new version to keep the resulting code compatible. No functional changes
25 +** Credentials
26 +** SFTP session factory → eMagiz will push a new flow version to keep the resulting code compatible.
27 +** Secured channels support object, used by API gateways with OAuth2 security, is removed → eMagiz will push a new flow version where this is migrated to the ‘HTTP security’ support object instead.
22 22  
23 -‘job explorer’ → eMagiz will push a new flow version which adds a ‘data source’.
24 -
25 -Http message sender: HttpComponentsMessageSender → eMagiz will replace this with HttpComponents5MessageSender
26 -
27 -SOAP webservices: Web service outbound gateway → eMagiz will push a new version to keep the resulting code compatible. No functional changes
28 -
29 -Credentials
30 -
31 -SFTP session factory → eMagiz will push a new flow version to keep the resulting code compatible.
32 -
33 -Secured channels support object, used by API gateways with OAuth2 security, is removed → eMagiz will push a new flow version where this is migrated to the ‘HTTP security’ support object instead.
34 34  =====Minor changes=====
35 35  
36 36  )))((({{toc/}}))){{/container}}