PUSH and PULL Automation Events in Titan MFT Server Next Gen
Question
Pre-requisites:
Titan MFT Server Next Gen must be installed on your server system
WebDrive 1.1.16 or later (File Transfer Client) must be installed on your server system
Steps
Install WebDrive 1.1.16 or later on the same system as Titan MFT Server if not already installed.
Open WebDrive and click the “+” icon at the top of the UI to setup a connection a remote server of interest.
Select the appropriate connection type for the remote server to which you would be Pushing/Pulling data.
The drive letter to use will default to w:\ -- if this is changed, please note the drive letter selected for later use, OR
- It would be recommended to edit the Settings for
this site connection in WebDrive and select the option under Advanced to map as
UNC path only (no drive letter). Then, drive letter conflicts/use will be of no
concern
From WebDrive’s main UI, you can test the connection by attempting to map the drive. If this succeeds and connects, then the site is ready to go. If it fails, read through any errors and verify the connection information for the remote server.
Once ready, from the main WebDrive UI, right-click the site you’ve created and select “Export”.
- NOTE: When Exporting a single site from WebDrive, ensure to use the right-click menu for the Export and NOT the top menu Export option, which is for use when Exporting multiple sites for use when Migrating WebDrive to another system.
Choose a name and location to save the .wdexport file. You will be Importing this into Titan.
Open the Titan MFT Server Administrator and navigate to the “Events” tab.
Click the “+” icon toward the upper right to Add a new Event.
Ensure “Events” is selected and then click “Add Event”.
Events can be run either on a Schedule or based on a specific trigger. Choose based on your specific need.
If wanting a Scheduled Event, select “Scheduled Events” and then “Scheduled Standard Event”
Next, click the Scheduled Standard Event dropdown, select “Conditions”, “Add Condition”
If wanting a Trigger-based Event, search through the various options available based on your specific need.
Next, click the dropdown for your Trigger-based Event, select “Conditions”, “Add Condition”
Add Conditions as desired/required to narrow the scope for your Event
Click on “Actions”, “Add Action”. Select either:
Push to remote Internet site (to send data from your environment to a remote server) OR
Pull from remote Internet site (to bring data from a remote server onto your local environment)
Review the Event Handler, add more Actions to the workflow if desired, or click “Next” at the bottom right.
Provide a friendly name and description for your Event – this will display in the list of Events within the server.
The Event now exists and is Enabled by default unless specifically unchecked during setup.
Example Configuration: Pushing a file to a remote server
This example leverages a trigger-based Event and pushes a file that meets the trigger criteria to a remote server. The sitename of the WebDrive site is SFTP and is assigned the w:\ (default) drive letter.
Further, the options selected will result in the WebDrive site connection being disconnected after the transfer to the remote server is completed, and Titan will wait for the script to complete before continuing to any subsequent Action in the Event workflow. You can see these two options enabled in the screenshot below with the example syntax.
Example Configuration: Pulling a folder (and contents) from a remote server
This example leverages a Scheduled Event and pulls a folder and its contents from a remote server. The sitename of the WebDrive site is SFTP and is assigned the w:\ (default) drive letter. The folder being Pulled exists in the root location after initial connection to the remote server.
Further, the options selected will result in Subdirectories to this folder also being Pulled and the source content (on the remote server) being deleted after the data is pulled to Titan. You can see these two options enabled in the screenshot below with the example syntax.