About Events
You can define events that, when triggered, cause ActiveTransfer Server to perform a specified action or set of actions. There are two types of managed file transfer events:
Post-processing events cause
ActiveTransfer Server to perform a specified action or set of actions when a user uploads, downloads, or deletes a file.
Scheduled events cause
ActiveTransfer Server to perform an action at a specified date and time.
Creating an event consists of the following high-level steps:
1. Add a post-processing or scheduled event.
2. Define the conditions that trigger the event.
3. Define one or more actions to execute when the event is triggered.
4. Define an error action to execute if the specified event action fails.
5. Activate the event.
Using SMB Protocol for File Sharing
In ActiveTransfer, you can configure events to exchange files with an SMB server. The SMB protocol allows ActiveTransfer to read, create, and update files on a network file share or a remote server that supports SMB, with the option to specify the user name and password for access. ActiveTransfer supports SMB 1.0, SMB 2.0, and SMB 3.0 versions. By default, Microsoft Windows systems support the native SMB protocol. However, UNIX systems must have interoperability utilities like Samba. SMB also allows for cross-platform file access. For example, ActiveTransfer running on Microsoft Windows system can access files on a Linux system.
Now, you can specify the version of the SMB server that you want to connect to. Additionally, you can select the SMB 2.0 to use the services of the SMB version 2.0 or later.
Typically, file operations are faster when you connect to a network file share using SMB protocol (SMB://host/Folder/) than when directly using a network file path (for example, FILE:////host/SharedFolder/). This is especially true when the operations are carried out on a large number of files.