Changes for page 198 - Great Migration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+190 - Fast Forward

Content

...	...	@@ -2,71 +2,93 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
	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		-== **Private Store** ==
8		-On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
	7	+== **Queue Browser** ==
9	9
10		-{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
	9	+{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
11	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	+
	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	+
	15	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	16	+
	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	+
	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.
	29	+
	30	+[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	31	+
12	12	== **3rd generation runtime bolstering** ==
13	13
14	14	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.
15	15
16		-//__SOAP and REST web services migration including splitting them__//
17		-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 and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal.
	36	+//__SOAP and REST web services migration, including splitting them__//
	37	+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.
18	18
19	19	//__Changing SSL settings for 3rd generation runtime models works__//
20		-As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime.
	40	+As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
21	21
22	22	//__Improved migration for JMS flows__//
23	23	This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
24	24
25		-{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}}
	45	+{{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}}
26	26
27	27	//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28		-As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow.
	48	+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.
29	29
30	30	//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31	31	We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
32	32
	53	+//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
	54	+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.
	55	+
	56	+//__Added "Reset" functionality__//
	57	+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.
	58	+
33	33	== **Feedback items ** ==
34	34
35	35	We have also solved other feedback items besides the flow designer's critical updates.
36	36
37	37	//__Improved naming convention on Store related pages__//
38		-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.
	64	+We have improved various display names using the merge functionality within our store offering.
39	39
40		-//__Press "Enter" to search on multiple pages__//
41		-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.
	66	+//__Update security protocols for our internal architecture__//
	67	+Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
42	42
43		-* Deploy → Deployment Plan
44		-* Deploy → Properties → History
45		-* Deploy → User Management → Roles
46		-* Manage → Error Messages → Error Messages
47		-* Manage → Error Messages → Flows with Error Messages
48		-* Manage → Error Messages → Exceptions of Error Messages
49		-* Manage → Log Entries
50		-* Manage → Alerts
51		-* Manage → Triggers
52		-* Manage → Tags – Cant find (only Gen2)
53		-* Manage → Notifications
54		-* Manage → Notification Settings
55		-* Manage → Data Usage → History
56		-* Manage → Code mappings → All tabs
	69	+//__Improved read-only description for "if exists" constructions in Transformations__//
	70	+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.
57	57
	72	+
58	58	== **Bug fixes ** ==
59	59
60		-//__Loading problems of Deployment plan execution overview__//
61		-We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
	75	+//__Decent validation feedback when not filling in the property value__//
	76	+We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
62	62
	78	+//__Incorrect resource locations__//
	79	+We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
	80	+
	81	+//__Apply to environment in User Management performance improvement__//
	82	+We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
	83	+
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		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
68		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
69		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	88	+* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
	89	+* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
	90	+* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
	91	+* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
70	70
71	71	== **Key takeaways** ==
72	72