Changes for page 190 - Fast Forward

Summary

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

Details

Page properties

Content

...	...	@@ -4,13 +4,13 @@
4	4
5	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		-== **Queue Browser** ~*~* ==
	7	+== **Queue Browser** ==
8	8
9	9	{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
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 (on a special queue) 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 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
...	...	@@ -31,7 +31,7 @@
31	31
32	32	[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
33	33
34		-== **Message Redelivery ** ~*~* ==
	34	+== **Message Redelivery ** ==
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
...	...	@@ -57,62 +57,62 @@
57	57
58	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	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.
	60	+//__SOAP and REST web services migration, including splitting them__//
	61	+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.
62	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.
	63	+//__Changing SSL settings for 3rd generation runtime models works__//
	64	+As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
65	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.
	66	+//__Improved migration for JMS flows__//
	67	+This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
68	68
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.
	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}}
71	71
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}}
	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	73
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.
	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	76
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.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
	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	79
80		-//__Performance improvement creating a release__//
81		-With this release, we have improved the performance of creating a release.
	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	82
83	83	== **Feedback items ** ==
84	84
85	85	We have also solved other feedback items besides the flow designer's critical updates.
86	86
87		-//__Sensitive information stored in properties is masked __//
88		-We have made how we display sensitive information across the portal in the same manner for various parts of the portal.
	87	+//__Improved naming convention on Store related pages__//
	88	+We have improved various display names using the merge functionality within our store offering.
89	89
90		-//__Importing "Private" store content to which you do not have access__//
91		-We have improved the user feedback a user will get when trying to import a "Private" store item that is not available to the user.
	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.
92	92
	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.
93	93
	96	+
94	94	== **Bug fixes ** ==
95	95
96		-//__Fix possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
97		-We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
	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.
98	98
99		-//__Synchronization of Event Streaming topic states__//
100		-We have fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
	102	+//__Incorrect resource locations__//
	103	+We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
101	101
102		-//__Copy and paste default support objects__//
103		-With this release you can now copy and paste components without having to worry that additional support objects that already exist in your target flow are copied over and over into the same flow.
	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.
104	104
105		-//__Fix editability of properties when importing store items__//
106		-With this release you can once again change property names upon importing a store item.
107		-
108	108	== **Fancy Forum Answers** ==
109	109
110	110	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:
111	111
112		-* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
113		-* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
114		-* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
115		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||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"]]
116	116
117	117	== **Key takeaways** ==
118	118