Who is Eligible?
Active Faculty or Staff
Overview
End User Requirements
- The source server sending the file to GoAnywhere.
- IP Address
- Protocol by which to send to GoAnywhere (currently must be SFTP only)
- File name.
- For Banner, it must be JobName_OneUpNumber.extension. For other services, like Argos, it must have a distinct title with a timestamp of yyyyMMdd_HH:mm:ss.SSS to ensure uniqueness.
- The destination server GoAnywhere will forward the file to.
- IP Address
- Port
- Protocol
- File naming standards for the receiving service
Banner to GoAnywhere Process Flow
As an example, consider the Curriculog job which runs on the Banner Job server.
Banner Jobs generates a file called szrcurr_123.csv, where szrcurr is the job name on the Banner Jobs server and 123 is the unique job identification number known as the ONE_UP_NUMBER.
Banner Jobs uploads the szrcurr_123.csv to the webdocs directory of the GaRemoteUser_A, using curl. For an example of how this is done, look at the $BANNER_HOME/oakdev/general/misc/gzpgatr.shl script.
A successful upload triggers the RunTriggeredJob project. (This is located at Workflows->Projects->GaJobTrigger)
The trigger runs and passes the name of the uploaded file to the Curriculog project (located at Workflows->Projects->Curriculog->Projects).
The Curriculog project moves the uploaded file to a local workspace and uploads the file to the Curriculog third-party vendor server.
To see how this is used in practice, view the $BANNER_HOME/oakdev/student/misc/szrcurr.shl file, which calls the triggerGoAnywhereJobIfFileExists function to send the file.
All source servers should have their own Web User and Triggered Job controller project on GoAnywhere.
Additional Support
- OU Technology Center
- 44 Oakland Center
- Rochester, MI 48309-4479
- (248) 370-4357
- Office Hours: M-F 8:00am - 5:00pm