Changes for page 190 - Fast Forward

Summary

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

Details

Page properties

Content

...	...	@@ -10,7 +10,7 @@
10	10
11	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		-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.
	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	15	[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
16	16
...	...	@@ -35,6 +35,8 @@
35	35
36	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	37
	38	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
	39	+
38	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	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.
...	...	@@ -44,30 +44,36 @@
44	44	* Search option
45	45	** Original queue name
46	46	** 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.
47	47
	54	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
	55	+
48	48	== **3rd generation runtime bolstering** ==
49	49
50	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.
51	51
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.
	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.
54	54
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.
	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.
57	57
58		-//__Improved migration for JMS flows__//
59		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
	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.
60	60
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}}
	69	+//__Updated H2 database setting__//
	70	+As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down.
62	62
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.
	72	+{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
65	65
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.
	74	+//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
	75	+As a replacement of the current HTTP settings context menu we have added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service) you now also can define whether the control bus needs to work for this runtime.
68	68
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.
	77	+//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
	78	+With this release, we have added a context menu item that allows user to deploy the agent that is needed to run your 3rd generation architecture on-premise. For more information on how to install this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture Store.On-premises deployment new runtime architecture||target="blank"]]
71	71
72	72	//__Added "Reset" functionality__//
73	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.