Configure Needed Memory
In this microlearning module, we will build on what we covered in the other microlearning about determining the necessary memory for your solution with eMagiz. Now, we’ll shift our focus to configuring the memory for each runtime, ensuring it aligns with the machine-level constraints available to you. This guide will help you understand how to make these adjustments within the Deploy Architecture, whether you’re working in the cloud or on-premises.
Should you have any questions, please contact academy@emagiz.com.
1. Prerequisites
- Intermediate knowledge of the eMagiz platform
- At least one runtime that you want to run or that is running
2. Key concepts
This microlearning centers around configuring the memory on runtime level.
- With configuration we mean: Based on the calculations assign the correct heap and non-heap memory per runtime in Deploy Architecture.
- Configuration of memory takes place in Deploy Architecture.
- Use the calculation made by eMagiz and checked by you to fill in the numbers if you deviate from the recommended settings.
3. Configure Needed Memory - Runtime level
In the following microlearning, we learned how you together with eMagiz can determine the memory that is needed to run your solution. In this microlearning, we will focus on how can configure the memory that each runtime needs within the boundaries of what is available on machine level.
In case your solution falls within the assumptions of eMagiz you only have to change the configuration when you exceed a threshold (think back to the table we shared in the last microlearning) and let eMagiz do all the heavy lifting.
In cases where all or part of the assumptions are violated, you should determine the correct number and based on that change the settings to mimic your calculations.
3.1 Deploy Architecture
Editing the memory settings can be done within the Deploy Architecture overview.
When you enter "Start Editing" mode on this view you will be able to edit the exact memory settings per runtime.
With a right click of your mouse, you can access the context menu and select the option called "Details."
Selecting this option will lead you to the following pop-up
As you can see, the details page tells you the current memory settings among other information elements. For each runtime you can change the memory settings if needed to a desired setting.
3.2 Apply to environment - Cloud
When you are satisfied with the changes you have made there is one more step left for you to do to actualize them in the cloud. This step is called "Apply to environment". Pressing this button will send a command to the eMagiz Cloud to change the configuration of your eMagiz Cloud setup based on the changes made in Deploy Architecture.
When you open the context menu on the eMagiz cloud slot itself (right mouse click in Deploy Architecture away from the integration landscape overview) you can access the details page
On this page, you can track the progress of your update. When it says Update complete the command has been send and processed successfully.
3.3 Actualize changes - On-premises
To effectuate the changes made to your deployed architecture, you should create a new release and deploy this via the deployment plan. In case you need more information on the creation of releases or deploying release you can check that information here and here.
4. Key takeaways
- Memory configuration is managed within the Deploy>Architecture page.
- Use the memory calculations provided by eMagiz and adjust them as needed based on your specific requirements.
- Ensure that any changes are applied to both the eMagiz cloud environment and your on-premises setup to reflect your updated configurations.
5. Suggested Additional Readings
If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: