Accessing external shares
UNC paths are only allowed in phase 1 (Input Agent "File") and phase 6 (Response "File"). Hidden shares are not allowed, furthermore the use of UNC paths is not supported for file events and in postexecuter classes. Please do not use UNC paths in any other place. See also section File names, file patterns, paths, system constants and variables. Please also note that virus scanners on the machine providing shares can cause problems regarding access to these remote files. This is not a problem of our software itself, but can then show up as an error there.
If it is necessary to read or write a file in an external directory via an SMB share (Windows share, Samba, etc.), this is possible under certain conditions with the following UNC syntax.
|
//server/share/path/file.ext |
Please note that unlike in Windows, the path separators are always written as right-slanted slashes. The target system should be a highly available system, otherwise, you have to expect performance problems. In this case, we strongly recommend that you only access local directories in profiles. Maybe a local directory can be released for external access.
If a share requires authorisation, the Integration Server must either be run with the identity of an authorised user (the service must also run with the authorised user if the Integration Server runs as a service), or the SMB login that is available for time-driven Input Agents with data source "File" and Responses of type "File" must be explicitly used.
Important note: If you are accessing a file via SMB in an Input Agent or Response, be sure to specify the complete UNC path to a file there. The server specification in an "SMB" partner channel is only for the login.
If the Integration Server runs as a Windows service
It depends on the startup type of the Integration Server which access rights it receives on the external system. Especially under Windows, it is often run as a service. If you do not define a specific user with whose rights the service is running, it is the local system. This local system user has no rights on other computers in the network. However, authorising the Integration Server at the external share requires a domain user, or better, a domain administrator.
But otherwise, there is no need for the Integration Server computer to be included in a Windows domain at all. You can access shares with the explicit SMB login without being a member of a Windows domain.
If required, please configure the properties of the Windows service for the Integration Server so that it runs with the identity of a domain user. It is now up to the domain administrator to give the domain user, under whose identity the Integration Server is running, the necessary rights. But access to various shares with different user identity is not possible this way.
Connected network drives not possible
At the service level, there are no connected network drives. This is not because of the user identity, but because the launch as a service is not taking place in a user environment. However, access to network drives from a test system, which was started in a user session with ./bin/hub.bat, is quite possible, because then the Integration Server indeed works in the environment of the login session of this user. If you then transfer the profiles to a live system that is running as a service, all network drives are invalid. It is better to use the UNC notation instead.
|
//server/share_name/file_path/file.ext |
SMB login
The SMB protocol is used by Windows shares as well as by SAMBA on Linux. It is used to access resources (especially files) of a remote computer over the network. The sharing side decides whether a login is necessary and optionally what rights a particular user receives. Note: The SMB protocol is not suitable for high-frequency/high-availability connections. For such connections, use (S)FTP, AS2 or the file system (without SMB).
An explicit SMB login will be provided in phase 1 (time-driven Input Agent of type "File") and phase 6 (Response of type "File").
If an external share is accessed and the input field User is not empty, then the login takes place via the explicit SMB login. The fields of the SMB login must only be filled when accessing an external share. It is an invalid operation when SMB credentials are applied to a local path. Therefore, mixing local paths and external shares in the field Folder of a time-driven Input Agent of type File will result in an error.
Note: Basic settings for Samba shares can be configured in file ./etc/admin/datawizard/smb.properties (timeout, etc.).
Note: If the SMB login is used for reading files from a share in a time-driven Input Agent of type File, it is not possible to listen to file events at the same time. In that case, only cyclic polling is possible. The repetition period should not be less than about 10 seconds.
Note: If the SMB login is used to write files to a share in a Response of type "File", a postexecuter cannot be used at the same time.