JAMS file transfer integration
Automated File Transfers with FTP, SFTP, FTPS, and SCP
JAMS Scheduler moves files over FTP, FTPS, SFTP, SCP, or a network copy as ordinary jobs. Transfers retry on their own, accept wildcards, start when a file arrives, and alert you when one fails or stalls.
Five transfer types
FTP, FTPS, SFTP, SCP, and Copy over UNC paths
Retries and wildcards
Built into every transfer job
File triggers
Start a transfer when a file shows up
What JAMS Scheduler Transfers
Pick the transfer type, choose whether to get or send files, and fill in the blanks. Each transfer is a normal job, so dependencies, schedules, and alerts work the same way.
How JAMS Scheduler Connects to File Servers
Save each server once as a file transfer connection in the JAMS Connection Store and reuse it across jobs, or enter the server and user right on the job.
Logins come from JAMS credentials, so the job references a credential instead of holding a password.
Requirements
Protocols
FTP, FTPS, SFTP, SCP, or Copy
Server details
A Connection Store item or the server name on the job
Authentication
A JAMS credential for the remote server
File Transfers in a Cross-Platform Workflow
A transfer can wait for a SQL Server export, send the file, and then start the job that loads it on the other side. Inside a sequence job, it’s one step among many.
When a transfer fails or stalls, you get the same alert as any other job.
File Transfer FAQ
Which file transfer protocols does JAMS Scheduler support?
FTP, FTPS, SFTP, and SCP, plus Copy for moving files between folders or across the network with UNC paths.
Can a job start when a file arrives?
Yes. File transfers support file event triggers, so a transfer, or the job after it, can start when a file shows up.
Do I need a separate MFT product?
Not for scheduled FTP, FTPS, SFTP, SCP, or network copy jobs. If you already run GoAnywhere MFT, JAMS Scheduler can run and monitor those projects too.
