Changes for page 210 - Deployment Delights

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-192 - Small Step
	1	+190 - Fast Forward

Content

...	...	@@ -2,56 +2,117 @@
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 building several essential things that will be released later this Q. On top of that, we finished additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the other features, we have a new event streaming graph and general updates to our platform.
	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		-== **Start/Stop Flows** ~*~* ==
	7	+== **Queue Browser** ==
8	8
9		-{{warning}}Note that depending on the alert, this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
	9	+{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
10	10
11		-To enhance your options when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option.
	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		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
	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 (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button.
14	14
15		-After selecting the option, eMagiz will open a pop-up where you can stop and start the starting point of each flow deployed on that runtime. This effect is that the flow will process no new messages, but the flow will still process all remaining messages after stopping the flow. To prevent a flow, you select a flow and press the Stop button. To start it again, press Start.
	15	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
16	16
17		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
	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.
18	18
19		-{{info}}Only in "Start Editing" mode can you start and stop specific flows{{/info}}
	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.
20	20
21		-== **Manage overview Event Streaming** ~*~* ==
	30	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
22	22
23		-To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data.
	32	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
24	24
25		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
	34	+== **Message Redelivery ** ==
26	26
	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}}
	37	+
	38	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
	39	+
	40	+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).
	41	+
	42	+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.
	43	+
	44	+On top of that we have added some additional functionality.
	45	+
	46	+* Search option
	47	+ ** Original queue name
	48	+ ** Original message ID (which can be found as a header called jms_messageid in the error message view)
	49	+* Save as test message
	50	+ ** By pressing this button you can save the message and use it in our flow testing functionality in Create.
	51	+* Download
	52	+ ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
	53	+
	54	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
	55	+
	56	+== **3rd generation runtime bolstering** ==
	57	+
	58	+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.
	59	+
	60	+//__Define memory settings for on-premise runtimes from Deploy Architecture__//
	61	+With this release, you are now able to define the memory settings (and therefore the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes you need to create a new release and deploy it to actualize the changes on-premise.
	62	+
	63	+//__Empty runtime feedback when deploying a release (or setting the release as active)__//
	64	+To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in Deploy Architecture we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
	65	+
	66	+//__Auto-fill namespaces for SOAP hosted webservices__//
	67	+Based on your configuration in Design eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
	68	+
	69	+{{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}}
	70	+
	71	+//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
	72	+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.
	73	+
	74	+//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
	75	+We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	76	+
	77	+//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
	78	+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.
	79	+
	80	+//__Added "Reset" functionality__//
	81	+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.
	82	+
27	27	== **Feedback items ** ==
28	28
29	29	We have also solved other feedback items besides the flow designer's critical updates.
30	30
31		-//__Topic configuration calculation__//
32		-With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics.
	87	+//__Improved naming convention on Store related pages__//
	88	+We have improved various display names using the merge functionality within our store offering.
33	33
34		-//__Make preparation step in deployment plan visible__//
35		-For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan.
	90	+//__Update security protocols for our internal architecture__//
	91	+Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
36	36
37		-{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
	93	+//__Improved read-only description for "if exists" constructions in Transformations__//
	94	+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.
38	38
39		-//__3rd generation runtime debugger feedback__//
40		-We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
41	41
42		-//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43		-As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
	97	+== **Bug fixes ** ==
44	44
45		-//__User Management synchronization now happens in one step__//
46		-With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized.
	99	+//__Decent validation feedback when not filling in the property value__//
	100	+We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
47	47
	102	+//__Incorrect resource locations__//
	103	+We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
	104	+
	105	+//__Apply to environment in User Management performance improvement__//
	106	+We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
	107	+
48	48	== **Fancy Forum Answers** ==
49	49
50	50	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:
51	51
52		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53		-* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54		-* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
	112	+* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
	113	+* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
	114	+* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
	115	+* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
55	55
56	56	== **Key takeaways** ==
57	57