Skip to Content

Changes for page SMB Connectivity

Last modified by Danniar Firdausy on 2024/09/18 20:40
From version 31.1
edited by Erik Bakker
on 2024/06/21 11:52
Change comment: There is no comment for this version
To version 26.1
edited by Bouke Reitsma
on 2024/05/13 16:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.BoukeReitsma
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}(((
3 -In some situations, direct communication with a local file directory is not possible, or in other case, an external party requires the files to be placed elsewhere. Typically, these files need to be retrieved from or uploaded to a server location using the FTP or SFTP protocols. However, there is a third communication protocol that can be used for file transfer. In this microlearning we will take a look at Server Message Block (SMB) connectivity within eMagiz.
3 +In some cases, there is no communication possible with a local file directory. Or there is a requirement from the external party to place the files somewhere else. Mainly the somewhere else is either an FTP or an SFTP. However, there is a third communication protocol that can be used for file transfer. In this microlearning we will take a look at Server Message Block (SMB) connectivity within eMagiz.
4 4  
5 5  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
... ... @@ -31,10 +31,8 @@
31 31  
32 32  So, where the file pickup component searches on the local host for the correct directory, the idea of the SMB setup is that the directory with whom to communicate exists on a remote host. The local host and the remote host can talk to each other via the SMB protocol. That is, in a nutshell, the difference between setting up an SMB connection and communicating with local directories.
33 33  
34 -{{warning}}Note that the auto create directory setting on all SMB components only works for a "one-level" directory (i.e. /directory) and not for a "multi-level" directory (i.e. /directory/sub). To ensure this "multi-level" directory is created by eMagiz you need to take a look at this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]{{/warning}}
34 +eMagiz provides only one support objects to connect to an SMB:
35 35  
36 -eMagiz provides only one support object to connect to an SMB:
37 -
38 38  * SMB session factory
39 39  
40 40  [[image:Main.Images.Microlearning.WebHome@intermediate-file-based-connectivity-smb-connectivity-smb-support-object.png]]
... ... @@ -46,7 +46,7 @@
46 46  * SMB inbound Channel adapter
47 47  * SMB outbound Channel adapter
48 48  
49 -On top of that, you need the following support object.
47 +On top of that, you need the following support objects.
50 50  
51 51  * SMB session factory
52 52  
... ... @@ -84,7 +84,7 @@
84 84  
85 85  === 3.2 SMB Gateway ===
86 86  
87 -The SMB Gateway is an additional component that can be used to interact with your SMB share. It allows the use of a set of pre-configured commands to perform actions such as deleting files. Compared to the outbound channel adapter replies are send back to eMagiz. These reply messages depend on the selected command. Every command option is explained in detail within the helptext. An example configuration to send files is shown below.
85 +The SMB Gateway is an additional component that can be used to interact with your SMB share. It enables the use of a set of pre-configured commands to for example delete files. The reply messages depend on the selected command. Every command option is explained within the helptext. An example configuration to send files is shown below.
88 88  
89 89  [[image:Main.Images.Microlearning.WebHome@intermediate-file-based-connectivity-smb-connectivity-smb-outbound-gateway-filled-in.png]]
90 90