Running Jobs from USoft Binder
This is the most common way in which your end users will run jobs that are not run automatically from the USoft application. The first time you distribute a job definition file, you will need to provide a mechanism that enables the end users to include it into a USoft Binder project, together with instructions on how to run a specific job.
The best way to do this is to create an empty USoft Binder file, and to add a Batch Runner item to it for each separate job that the end user is to run.
Next, you should the set the properties of the Batch Runner item, using the Properties option.
It is best to use the Edit Job Name and Parameters dialog to define any parameters that the end user can change at run time, and give them dummy values. This will make it easier to explain what the user must do the first time they run that job (see below).
If there is more than one parameter, enter each one on a new line, by ending the current line with a comma, and then pressing CTRL+ENTER to start a new parameter line.
Once you have repeated these actions for each individual job that the end user can run, you can save the current USoft Binder project, and distribute it to the end users, together with the job definition file. The job definition file must be placed in their <installation directory>\APP directory.
In order for the users to use the USoft Binder items you should give them the following instructions:
The USoft Binder will automatically fill in the username and password parameters in the items after they have been pasted.
If a job requires an end user to change parameters for different runs, you must make sure that you tell them how to do this, by giving them the following instructions:
Finally, here are some important items to tell your end users:
You may wish to have the jobs run on the server, from within USoft Binder.
In this case, you should add a Free Object to the USoft Binder, that contains everything necessary to make the remote connection and run the job. The syntax for running the job is the same as that for running jobs from the command line.