This document will go through the functionality found within JetTrac FTP. Automate movement of files between computers. One specific example is when JetTrac Field Service is running in the cloud and QuickBooks is on-premise, when a Work Order is approved then the data from that Work Order can be sent to the customer computer for import directly into QuickBooks – completely automatic and unattended.
If you need assistance in installing and configuring JetTrac FTP™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at firstname.lastname@example.org. Please note that the JetTrac FTP™ license fee does not cover configuration services and technical support so there may be an additional charge. Please ensure you read these instructions carefully before calling for technical support.
To run the program, you will need to have the following files located in the same folder:
Server-side sending of file by FTP
1. ftp server
3. destination directory (to cd [dir] to)
4. option to delete local file after transfer Y=delete, N=leave it
When setting up a job step using JTFTP in JobConfig the only two lines of the config you need to worry about are the first two, the Config file and the File to FTP. These fields should be filled with the fully qualified paths to the intended files. Eg: C:\JetTrac\…\input.pdf
In JobConfig, file paths entered should not be in quotes.
As with all modules, there is a dropdown to select whether or not the job should stop completely if this step fails. If you select Yes, any error will terminate the job process and write to the log file what happened, if no, then the job will try to continue anyways. However if any steps further down the line rely on the output of a job set to not stop on error, they may not work properly.
For more specifics go to the JetTrac BYODJobConfig page.
java ” -jar -DJETTRACLF=””C:\JetTrac\JobController\License\JetTrac.lic”” “”-DFTPMETHOD=3″ “”C:\JetTrac\Programs\JTFTP\JTFTP.jar”” “C:\JTFTPInput.pdf” “C:\JTFTP.ini” “C:\JTFTP.log”
Looking at the job row in the JMD config file starts off with the declaration of the license location. The DFTPMethod is explained in detail under additional notes below. Anything beginning with an @ symbol is referring to a variable value of inputs ( @InFile ) and output ( @MDFName ). Each part of the line is divided by spaces (the amount doesn’t matter), and contains the fully qualified file path ( unless its a variable ) to the file you are referencing surrounded by quotes. The last part is an optional comment on the step.
Looking at the job row in the JMD config file starts off with the declaration of the license location. The DFTPMethod is explained in detail under additional notes below. Next is the file path to the .jar file for JTFTP followed by the input PDF file, the config .ini file and ends with the file path to the JTFTP log file.
JTFTP supports three different FTP connection methodologies:
Method 1 is Windows/Java default – it supports PUT and GET only, but does not support creating folders. It supports user name and password for access control, and it works through most network setups – it is tested and supported by Windows and Java.
Method 2 is an older method that bypasses the Windows/Java built-in method. It generally works ok as long as both computers are on the same intranet – but it won’t work through firewalls to cross from intranet to internet. I think method 2 can support creating folders, but this feature has not been put into our application at this time.
Method 3: this is the default method if you don’t specify any method, Method 3 is and FTP mode called PASSIVE mode. Right now PASSIVE is the only method that supports creating folders. This has the best chance of being able to work if there are multiple firewalls between the two computers that are exchanging files. But it is not always supported on computers as some people feel it presents some increased security concerns.