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	+189 - Private Eye

Content

...	...	@@ -2,56 +2,73 @@
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 major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
	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.
6	6
7		-== **Start/Stop Flows** ~*~* ==
	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).
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}}
	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}}
10	10
11		-To enhance the options you have 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 runtime level you can open the context menu and select the option called "Start/Stop Flows".
	12	+== **3rd generation runtime bolstering** ==
12	12
13		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
	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.
14	14
15		-After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
	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. 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.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
	19	+//__Changing SSL settings for 3rd generation runtime models works__//
	20	+As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
18	18
19		-{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
	22	+//__Improved migration for JMS flows__//
	23	+This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
20	20
21		-== **Manage overview Event Streaming** ~*~* ==
	25	+{{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}}
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 streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
	27	+//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
	28	+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.
24	24
25		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
	30	+//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
	31	+We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
26	26
	33	+//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
	34	+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.
	35	+
	36	+//__Added "Reset" functionality__//
	37	+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.
	38	+
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 topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
	43	+//__Improved naming convention on Store related pages__//
	44	+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 a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
	46	+//__Update security protocols for our internal architecture__//
	47	+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}}
	49	+//__Improved read-only description for "if exists" constructions in Transformations__//
	50	+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.
	53	+== **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 with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
	55	+//__Decent validation feedback when not filling in the property value__//
	56	+We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
47	47
	58	+//__Incorrect resource locations__//
	59	+We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
	60	+
	61	+//__Apply to environment in User Management performance improvement__//
	62	+We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
	63	+
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"]]
	68	+* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
	69	+* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
	70	+* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
	71	+* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
55	55
56	56	== **Key takeaways** ==
57	57