Volume Mapping (On-premise)
When you need to read and write files from an on-premise disk, you need to know the path in which the data is stored and make sure that the docker container in your runtime(s) running has access to this path. There are several ways of dealing with this challenge. First, this microlearning will discuss the various alternatives and best approaches in these scenarios.
Should you have any questions, please contact academy@emagiz.com.
1. Prerequisites
- Basic knowledge of the eMagiz platform
2. Key concepts
This microlearning centers around learning how to set up your volume mapping correctly so you can exchange file-based data on-premise.
By volume mapping, we mean: Creating a configuration through which the docker container can read and write data on a specific path on an on-premise machine.
There are several options for volume mapping for your on-premise machine.
- Volume
- Bind mount
- Temporary file system
- Named pipe
3. Volume Mapping (On-premise)
When you need to read and write files from an on-premise disk, you need to know the path in which the data is stored and make sure that the docker container in your runtime(s) running has access to this path. There are several ways of dealing with this challenge. First, this microlearning will discuss the various alternatives and best approaches in these scenarios.
There are several options for volume mapping for your on-premise machine.
- Volume
- Bind mount
- Temporary file system
- Named pipe
Below we will explain the differences between the various options available for your volume mapping. But before we do, we first explain how to set up this configuration within eMagiz. Then, you must navigate to Deploy -> Architecture on the model level. In this overview, you can access the Volume mapping per runtime deployed on-premise. To do so, you can right-click on the runtime to access the context menu.
When you click this option, you will see the following pop-up. In this pop-up, you can define the machine-level and runtime-level volumes. More on that later. This is the starting point for configuring your volume mapping. We will walk through each available option and explain how they work and should be configured.
3.1 Volume
3.2 Bind mount
3.3 Temporary file system
3.4 Named pipe
4. Assignment
Configure an entry in which you build the archiving and the clean up of the archiving.
This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
5. Key takeaways
- Archiving is used for audit purposes
- Archiving is used for retry scenarios
- Ensure that data is cleaned after a retention period to keep in control of the data
- Don't forget the max messages per poll
6. Suggested Additional Readings
If you are interested in this topic and want more information on it please read the help text provided by eMagiz and check out the following store content:
7. Silent demonstration video
This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.