Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 102.1
edited by Erik Bakker
on 2023/04/13 09:23
Change comment: There is no comment for this version
To version 60.1
edited by Erik Bakker
on 2023/01/18 09:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +190 - Fast Forward
Content
... ... @@ -2,95 +2,109 @@
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 few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
5 +**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
6 6  
7 -== **Release properties** ==**
7 +== **Queue Browser** ==
8 8  
9 -With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]].
9 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
10 10  
11 -As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s).
11 +To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
12 12  
13 -{{video attachment="release-blog-easter-party--release-properties.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
13 +To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies of your actual message that pass through the queue from the moment you pressed the Wiretap button.
14 14  
15 -{{info}}The following considerations need to be taken into account when using this functionality:
16 -* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture
17 -* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted
18 -* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment).
19 -*{{/info}}
15 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
20 20  
21 -== **API improvements** ==
17 +After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
22 22  
23 -//__Improved auto-generated error handling__//
24 -When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
19 +* Delete the message from the queue (Explore option)
20 + ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21 +* Clear message from the wiretap queue (Wiretap option)
22 + ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23 +* Refresh messages list (both options)
24 + ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25 +* Save as test message
26 + ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27 +* Download
28 + ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
25 25  
26 -//__Switch default message format__//
27 -We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
30 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
28 28  
29 -//__Re-using elements in gateway message__//
30 -This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
32 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
31 31  
32 -//__Improved naming of API operations when adding integrations to Create__//
33 -Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
34 +== **Message Redelivery ** ==
34 34  
35 -== **3rd generation improvements** ==
36 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
36 36  
37 -//__Update of the static alerting engine__//
38 -In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
38 +Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
39 39  
40 -//__Add "Data pipeline" functionality__//
41 -This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
40 +Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
42 42  
43 -//__Fix related to the debugger__//
44 -This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
42 +On top of that we have added some additional functionality.
45 45  
46 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
44 +* Search option
45 + ** Original queue name
46 + ** Original message ID (which can be found as a header called jms_messageid in the error message view)
47 47  
48 -//__Improved migration process__//
49 -This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
48 +== **3rd generation runtime bolstering** ==
50 50  
51 -//__Deployment plan change__//
52 -In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
50 +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.
53 53  
54 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
52 +//__SOAP and REST web services migration, including splitting them__//
53 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
55 55  
56 -== **Feedback items ** ==
55 +//__Changing SSL settings for 3rd generation runtime models works__//
56 +As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
57 57  
58 -//__License Tracker improvements__//
59 -With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
58 +//__Improved migration for JMS flows__//
59 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
60 60  
61 -//__Ability to view the message definition for a topic__//
62 -Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
61 +{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
63 63  
64 -//__Restricted access for uploading custom certificates to endpoints__//
65 -To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
63 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
64 +As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
66 66  
67 -== **Bug fixes ** ==
66 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
67 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
68 68  
69 -//__Improved deletion behavior for enumerations__//
70 -To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
69 +//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
70 +With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
71 71  
72 -//__Prevent "async" api operations__//
73 -With this release, we have removed the ability to select the "async" option when the default message format is API Management.
72 +//__Added "Reset" functionality__//
73 +With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
74 74  
75 -//__Importing a response definition broke the request definition__//
76 -Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
75 +== **Feedback items ** ==
77 77  
78 -//__Removing a flow does not update the API "all-entry" anymore__//
79 -When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
77 +We have also solved other feedback items besides the flow designer's critical updates.
80 80  
81 -//__Stop deployment plan when a property is missing__//
82 -Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
79 +//__Improved naming convention on Store related pages__//
80 +We have improved various display names using the merge functionality within our store offering.
83 83  
84 -//__Cap stack trace of error messages and log entries__//
85 -To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
82 +//__Update security protocols for our internal architecture__//
83 +Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
86 86  
85 +//__Improved read-only description for "if exists" constructions in Transformations__//
86 +To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
87 +
88 +
89 +== **Bug fixes ** ==
90 +
91 +//__Decent validation feedback when not filling in the property value__//
92 +We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
93 +
94 +//__Incorrect resource locations__//
95 +We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
96 +
97 +//__Apply to environment in User Management performance improvement__//
98 +We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
99 +
87 87  == **Fancy Forum Answers** ==
88 88  
89 89  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:
90 90  
91 -* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
92 -* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
93 -* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
104 +* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
105 +* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
106 +* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
107 +* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
94 94  
95 95  == **Key takeaways** ==
96 96