Using a Variable to override a File Name
A project outline is shown below which connects to a SFTP server and puts a file onto that server. See Figures 1 & 2.
Notice how the Source File is hard coded with the file name of C:/temp/gademo.txt. This is not flexible if your file names change regularly.
Instead of using a hard-coded value, you can use a variable in the SFTP PUT task to supply the file name. To do this, right-click on the Project Level in the Outline and select “Add a Variable.” Give the variable a name, “MyFile” and leave the initial value blank (See Figures 3 & 4).
Your project outline now has the variable MyFile added.
You now need to add this variable to the PUT task Source File field. Variable names are wrapped with ${} when they are used as an input attribute in a task (See Figure 6).
With this change, you can now run the project and pass the name of the file you want to transfer.
Passing parameters can be done several ways:
- Interactively
- From another Project
- From a Monitor Job
- From a Scheduled Job
- From a GoAnywhere Services Trigger
- From an External application using the GACmd API
This allows you to pass a value to the variable defined earlier within the project (see Figure 8).
By filling in the File Path and Name, then clicking on the “Execute Interactively” button, you can then view the job log to see where ${MyFile} is created and set to the value “C:\Temp\GADemo2.txt.” You can also see that the file has been uploaded successfully (see Figure 9).
Figure 9
The Source for this project is located below.
Code: Select all
<project name="Using Variables - Part 2" mainModule="Main" version="2.0" logLevel="verbose">
<variable name="MyFile" value="" />
<module name="Main">
<sftp label="Connect to Server" resourceId="Test SFTP" version="1.0">
<put label="Put file on Target Server"
sourceFile="${MyFile}"
destinationDir="/Demos/inbound" />
</sftp>
</module>
<description>Basic Project with Parameter</description>
</project>