Changes for page SMB - Dynamically Manipulate Settings

Summary

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

Details

Page properties

Content

...	...	@@ -11,15 +11,35 @@
11	11
12	12	== 2. Key concepts ==
13	13
14		-This microlearning centers around error handling concerning GDPR
15		-With GDPR, we mean The law on General Data Protection Regulation.
	14	+This microlearning centers around dynamically manipulating settings on the SMB Session Factory.
16	16
17		-* The GDPR is a European privacy regulation. It ensures the careful processing of personal data by businesses and organizations.
18		-* eMagiz has various security measures in place to keep your data safe
19		-* You also have a responsibility as a user how you use the data of the customer
	16	+* When you dynamically need to create a directory or have multiple hosts that hosts file shares this option is the correct approach.
20	20
21		-== 3. Error Handling regarding GDPR ==
	18	+== 3. Dynamically manipulate SMB Session Settings ==
22	22
	20	+In a previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.File based connectivity.intermediate-file-based-connectivity-smb-connectivity.WebHome||target="blank"]] we learned that we need an SMB Session Factory to setup the initial connection to the SMB drive. In this component there are five main settings that are of relevance.
	21	+
	22	+* Host
	23	+* Port
	24	+* Username
	25	+* Password
	26	+* Share and directory
	27	+
	28	+In theory each of these settings can be overwritten everytime a message is consumed and processed by the flow. In practice we see two main use cases that are relevant to mention in this microlearning as we see them currently being applied in our community.
	29	+
	30	+=== 3.1 Dynamic Host ===
	31	+
	32	+In case you have a multitude of SMB directories (i.e. shares) that span across a multitude of different host servers you are in need for a solution that can dynamically manipulate pre-existing information on the SMB session factory. In other words, you need to be able to override the default host configuration in the component with one that is determined based on information in the headers or message.
	33	+
	34	+To do so we need to add an additional component to the flow that will override the host setting. This component is called the "Standard service activator".
	35	+
	36	+[[image:Main.Images.Microlearning.WebHome@advanced-file-connectivity-dynamically-manipulate-smb-settings--standard-service-activator.png]]
	37	+
	38	+In here we need to define an expression that will set the host based on a supplied value. Important in this expression is that we correctly reference the complete name of the SMB Session Factory support object in the flow and that once the host is set the actual message is passed along. An example of such an expression is {{code}}@'smb.gtwydynm.exit.support.smb-session'.setHost(headers.server) ?: #root{{/code}}. This expression will set the host based on the value in the header called "server" and once done will pass the full message to the output channel.
	39	+
	40	+[[image:Main.Images.Microlearning.WebHome@advanced-file-connectivity-dynamically-manipulate-smb-settings--standard-service-activator-filled-in.png]]
	41	+
	42	+=== 3.2 Dynamic Share and Directory ===
23	23	In eMagiz, all errors are raised when a process fails, and you want to have some form of logging end up in the Manage phase of eMagiz. The Manage phase of eMagiz is primarily accessible to support employees, employees working on the project, and in some cases, even more, people have at least view rights. You can imagine that when many people have access to potentially sensitive data, you should consider countermeasures. This way, you can reduce the chances of sensitive data ending up in the wrong hands. Some of the potential countermeasures are available within the platform. Some of them are procedural in nature. In this microlearning, we will learn what you can do to keep your data safe within eMagiz.
24	24
25	25	In eMagiz, we value the security of your data. A detailed overview of how your data is secured within the platform and when data is exchanged can be found in our [[Security Guide>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-security-guide||target="blank"]]. One of the additional measures you could take on our data models is to indicate whether the information stored in those attributes is confidential. More information on how that works exactly can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Defining message structures.intermediate-defining-your-message-structures-data-model-attribute-confidentiality||target="blank"]].