Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 86.1
edited by eMagiz
on 2023/02/28 11:57
Change comment: There is no comment for this version
To version 48.1
edited by Erik Bakker
on 2022/11/21 13:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,71 +2,77 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last couple of weeks, we worked hard on API improvements and 3rd generation improvements for you all to see. Amongst the API improvements we now introduce the option to define REST/XML structures in your API gateway for your API callers to call. This brings more options to the user community in setting up the API Gateway structure in accordance with the needs and desires of the client. On top of that we have released several 3rd generation improvements. Amongst these we will add WS-Security functionality to the runtime and improvements on viewing release properties. Furthermore we have released new cloud templates to improve security in our current runtime and improve the auto-healing for 3rd generation runtime cloud slots. Last but not least we release the first adaptation of "State generation" that can be implemented with the help of us in your model. In the upcoming monts we will gather feedback from actual client cases and improve on this functionality.
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6 6  
7 -== **REST XML for API Gateway** ==
7 +== **3rd generation runtime bolstering** ==
8 8  
9 -{{warning}}Note that a decision needs to be made to select XML or JSON as default format for all your operations hosted in your API Gateway.{{/warning}}
9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
10 10  
11 -To enhance your options when developing an API gateway that can be called by others we now introduce the option to select XML as the default message format on your API Gateway pattern. You can do this under Design -> Settings -> API Management. In here you can select and edit the settings.
11 +//__Migration of JMS backup configuration improved__//
12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
14 14  
15 -Every operation made after this decision will default to XML (or JSON which is still the default). Should you want to support JSON on some operations and XML on others you can select a default and manually correct the mediaType for the requests and responses to which it matters.
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
20 +//__Code mapping functionality available on 3rd generation runtime__//
21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
18 18  
19 -==**Cloud Template update** ==
20 -
21 -===Cloud Template R23 - Single Lane ===
23 +//__Improved the performance when activating a release__//
24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
22 22  
23 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 2nd generation runtime. This cloud template will update some specific security settings on these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
26 +//__Failing runtimes won't be restarted indefinitely anymore__//
27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
24 24  
25 -===Cloud Template R6 - Single Lane ===
29 +== **Exportable Release Audit** ~* ==
26 26  
27 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
31 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
28 28  
29 -===Cloud Template R6 - Double Lane===
33 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
30 30  
31 -This release introduces a new cloud template for all our customers running in a double-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
35 +{{warning}}Note that the following restrictions apply when exporting an audit document:
36 + * Changes made on definition and transformation level are **not** restored
37 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022
38 + * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
39 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
32 32  
33 -== **WS-Security on the 3rd generation runtime** ~*~* ==
34 -
35 -To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols.
36 -
37 -== **State Generation ~*~* ==
38 -
39 -With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
40 -
41 -{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
42 -
43 43  == **Feedback items ** ==
44 44  
45 -//__Removed OData as option for an API Gateway operation__//
46 -With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
43 +We have also solved other feedback items besides the flow designer's critical updates.
47 47  
48 -//__Changes in API Gateway operation paths is automatically updated in Create__//
49 -When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
45 +//__Data Sink Refactor__//
46 +We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end, we will contact you separately.
50 50  
51 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
48 +//__Improved naming convention on Store related pages__//
49 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
52 52  
53 -== **Bug fixes ** ==
51 +//__Press "Enter" to search on multiple pages__//
52 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
54 54  
55 -//__Prevent endless loop in Deploy -> User Management__//
56 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
54 +* Deploy → Deployment Plan
55 +* Deploy → Properties → History
56 +* Deploy → User Management → Roles
57 +* Manage → Error Messages → Error Messages
58 +* Manage → Error Messages → Flows with Error Messages
59 +* Manage → Error Messages → Exceptions of Error Messages
60 +* Manage → Log Entries
61 +* Manage → Alerts
62 +* Manage → Triggers
63 +* Manage → Tags – Cant find (only Gen2)
64 +* Manage → Notifications
65 +* Manage → Notification Settings
66 +* Manage → Data Usage → History
67 +* Manage → Code mappings → All tabs
57 57  
58 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
59 -
60 -//__Update error handling during migration to the 3rd generation runtime__//
61 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
62 -
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
66 66  
67 -* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
68 -* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
69 -* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
73 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
74 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
75 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
70 70  
71 71  == **Key takeaways** ==
72 72