Skip to Content
Last modified by eMagiz on 2022/06/22 13:55
From version 2.1
edited by eMagiz
on 2022/06/22 13:49
Change comment: There is no comment for this version
To version 1.1
edited by eMagiz
on 2022/06/22 13:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,101 +1,36 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
3 3  
4 -**Hi there, eMagiz developers!** As you probably have heard, a vulnerability has been discovered in the Apache Log 4j module. This vulnerability exposes applications worldwide. We analyzed our complete stack in response to this vulnerability, including our cloud and on-premise runtimes. Although there is **no** risk of this vulnerability on your current eMagiz runtime, we choose to upgrade the library in our runtimes. Our advice is to upgrade your runtime soonest. This blog will highlight the best migration approach given specific scenarios.
4 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked on various main platform features. Sadly they are not yet ready enough to release to you guys. We did, however, improve the platform in different more minor ways. Among these improvements, we have improved the speed of handling error messages and creating models by hand. Furthermore, we have several more minor improvements and bug fixes for you. So let us dive into all that we have to offer this time around!
5 5  
6 -== **Migration Path** ==
6 +== **Infrastructure Update** ==
7 7  
8 8  As you might already have seen via the notifications sent from our status page (https://status.emagiz.com), we will update our infrastructure with our upcoming release. This will lay the foundation for more infrastructural changes in our future. For specific information, please check out the notifications via our status page.
9 -As a customer, you have the option to run your eMagiz solution within the eMagiz Cloud or your network (i.e., on-premise). Furthermore, you have the opportunity to run part of your solution in the eMagiz Cloud and part of your solution on-premise. For all these scenarios upgrading your complete environment needs a different approach. In the remainder of this blog, we will discuss the migration path for each of these scenario.
10 10  
11 -Before we dive into the various scenarios, we would like to define some general remarks:
10 +[[image:Main.Images.Release Blog.WebHome@178-release-blog-1.jpg]]
12 12  
13 -* Make sure that your active release mimics what is currently running on an environment, as the upgrade will result in a clean slate based on the active release.
14 -* For business-critical processes, we advise stopping these processes before executing the upgrade
15 -* You will experience a short amount of downtime while executing this upgrade
16 -* Each scenario has some additional specific restrictions and considerations.
12 +== **Bug Fixes** ==
17 17  
18 - ===1.1 Cloud Only===
19 -If your complete solution runs in the cloud, you need to upgrade to the latest cloud template suitable for your model. This will be the R13 template for double lane setups, and for single lane setups, this will be the R19 template.
20 -
21 -Note that your Test and Acceptance environments are automatically scheduled to be upgraded after we release the templates. However, if the planned date is after this weekend, we urge you to manually change the planned date to any time during this weekend. See the section on changing the planned date of the upgrade for more information.
22 -
23 -====1.1.1 Considerations for this scenario====
24 -All data stored on EFS, such as the JMS Artemis folder, is kept. As a result, all this data is accessible again after the upgrade has been completed.
25 -However, this does mean that any data stored on a custom folder on runtime will be deleted. So please take action accordingly by stopping these processes before upgrading the cloud template.
26 -For single lane setups we advise to stop the core machine before migrating to the newest cloud template to ensure that the JMS will be started in the correct manner under the new cloud template. If this action is not performed beforehand a reset of the JMS runtime is required afterwards.
27 -
28 -====1.1.2 Upgrade your cloud template====
29 -To upgrade your cloud template please execute the following steps:
30 -
31 -* Log in at my.emagiz.com
32 -* Navigate to the eMagiz model for which you want to upgrade your cloud template.
33 -* Navigate to the Deploy phase and open the Architecture tab
34 -* eMagiz will show a pop-up that you can upgrade your cloud template. Please read the text carefully and select the appropriate action
35 -* In case of a single lane you can press Apply to environment
36 -* In case of a double lane you should first upgrade zone B and when that was successful upgrade zone A
37 -* If you do not want to execute the update immediately but plan it, you can do that in a slightly different way. For more information on how to plan the upgrade, please see: https://emagiz.github.io/docs/microlearning/novice-emagiz-cloud-management-cloud-templates-explained#322-planned-manual-cloud-template-upgrade
38 -
39 -====1.1.3 Change the planned date of an automatically scheduled upgrade====
40 -To change the date and time on which the upgrade will take place, please check out the microlearning on the subject and, in particular, the section on planned upgrade: https://emagiz.github.io/docs/microlearning/novice-emagiz-cloud-management-cloud-templates-explained#322-planned-manual-cloud-template-upgrade
41 -
42 -===1.2 Hybrid (Cloud and on-premise)===
43 -In case you have a hybrid setup, you have your core machine(s) (which contains, among others, the JMS) running in the eMagiz Cloud, and you have at least one connector runtime running on-premise. This means that a two-step approach is needed to upgrade your complete model.
44 -
45 -====1.2.1 Considerations for this scenario====
46 -* All data stored on EFS, such as the JMS Artemis folder, is kept. As a result, all this data is accessible again after the upgrade has been completed.
47 -* However, this does mean that any data stored on a custom folder on runtime will be deleted. So please act accordingly by stopping these processes before upgrading the cloud template.
48 -* For single lane setups we advise to stop the core machine AND the connector machine before migrating to the newest cloud template to ensure that the JMS will be started in the correct manner under the new cloud template. If this action is not performed beforehand a reset of the JMS runtime is required afterwards.
49 -* For the on-premises & Cloud runtimes you will do a clean install which also means that the H2 database, if used in your entry, is created again. To prevent data loss please stop the Entry Flows after the data is successfully processed and before new data is sent.
50 -* For the on-premises runtimes make sure that in case you adjusted the memory previously you do the same for the new runtime.
51 -* For the on-premises runtimes make sure that you know under which account the service is currently running and make sure the new runtime will also start under that account.
52 -
53 - ====1.2.2 Cloud update====
14 +//__Update eMagiz Slot Status does not lead to logging errors__//
15 +With this release, we have made several improvements in retrieving the eMagiz Slot Status when a user executes an action on the eMagiz Cloud. These improvements will resolve logging errors within the platform.
54 54  
55 -The first step of the model is to upgrade the cloud section of your solution. The steps described in the Cloud Only section 1.1 should be followed and executed. For this part, the same restrictions apply as specified in that section.
17 +== **Feedback items ** ==
56 56  
57 -====1.2.3 On-premise Update====
58 -The second part of the model is to upgrade your connector runtimes currently running on-premise. To update these runtimes, you need to execute the following steps:
19 +Apart from the key updates around functionality, we have also solved other feedback items.
59 59  
60 -* Log in at my.emagiz.com
61 -* Navigate to the eMagiz model for which you need to update the runtime(s)
62 -* Navigate to the Deploy phase and open the Containers tab
63 -* Select the environment for which you want to download the runtime(s)
64 -* Select each runtime (one by one) and download each of them (one by one) by pressing the Download button
65 -* After you have downloaded each one of them please check out one of the following microlearning (based on your operating system) on how to update.
66 -Windows: https://emagiz.github.io/docs/microlearning/expert-platform-deploy-install-local-connector-windows
67 -Linux: https://emagiz.github.io/docs/microlearning/expert-platform-deploy-install-local-connector-linux
21 +//__Notify model owner when mails are sent to deactivated users__//
22 +We will notify model owners via mail that their alerting sends emails to deactivated users within the platform with this release. Furthermore, once we encounter a notification setting in which a deactivated user is part of the recipients, we will remove the user from the notifications (if possible).
68 68  
69 - ===1.3 On-premise Only===
70 -
71 -====1.3.1 Considerations for this scenario====
72 -For the on-premise runtimes you will do a clean install which also means that the H2 database, if used in your entry, is created again. To prevent data loss please stop the entries after the data is successfully processed and before new data is send.
73 -For the on-premise JMS runtime you need to ensure that all data is processed before stopping the JMS and installing and starting the new JMS. Please make sure that you stop all entry flows so that the environment can process all remaining messages before updating the JMS server. More information below in section 13.2
74 -For the on-premise runtimes make sure that in case you adjusted the memory previously you do the same for the new runtime.
75 -For the on-premise runtimes make sure that you know under which account the service is currently running and make sure the new runtime will also start under that account.
76 -1.3.2 On-premise JMS Update
77 -There is special attention needed to upgrade the JMS on-premise. On JMS level there is an Artemis folder that holds among others certain messages that still need to be processed. To ensure that there is no data loss please make sure that all data is processed before switching over to the new runtime for your JMS. To update the JMS runtime(s), you need to execute the following steps:
24 +//__Updated infographic Capture__//
25 +As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture.
78 78  
79 -* Log in at my.emagiz.com
80 -* Navigate to the eMagiz model for which you need to update the JMS runtime(s)
81 -* Navigate to the Deploy phase and open the Containers tab
82 -* Select the environment for which you want to download the JMS runtime(s)
83 -* Select each runtime (one by one) and download each of them (one by one) by pressing the Download button
84 -* After you have downloaded each one of them please check out one of the following microlearning (based on your operating system) on how to update. Before you stop the current JMS please make sure that no data is currently being processed within your model.
85 -Windows: https://emagiz.github.io/docs/microlearning/expert-platform-deploy-install-local-connector-windows
86 -Linux: https://emagiz.github.io/docs/microlearning/expert-platform-deploy-install-local-connector-linux
27 +== **Fancy Forum Answers** ==
87 87  
88 - ====1.3.3 On-premise Update====
89 -The second part of the model is to upgrade your connector runtimes currently running on-premise. To update these runtimes, you need to execute the following steps:
29 +As always, a gentle reminder to all 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:
90 90  
91 -* Log in at my.emagiz.com
92 -* Navigate to the eMagiz model for which you need to update the runtime(s)
93 -* Navigate to the Deploy phase and open the Containers tab
94 -* Select the environment for which you want to download the runtime(s)
95 -* Select each runtime (one by one) and download each of them (one by one) by pressing the Download button
96 -* After you have downloaded each one of them please check out one of the following microlearning (based on your operating system) on how to update.
97 -Windows: https://emagiz.github.io/docs/microlearning/expert-platform-deploy-install-local-connector-windows
98 -Linux: https://emagiz.github.io/docs/microlearning/expert-platform-deploy-install-local-connector-linux
31 +* [[Access to local files>>https://my.emagiz.com/p/question/172825635700363485||target="blank"]]
32 +* [[Oauth database not updated>>https://my.emagiz.com/p/question/172825635700363386||target="blank"]]
33 +* [[Input/Output error>>https://my.emagiz.com/p/question/172825635700363385||target="blank"]]
99 99  
100 100  == **Key takeaways** ==
101 101