Job Configuration
Job configuration is a flexible process, which allows you to find more than one way to achieve the same result. To get an idea of various tasks you can perform, see Tutorials and Job Examples.
The broad procedures below explain how to configure a job in FlowForce Server. Some of the procedures are optional (e.g., caching job results).
1.The first step is to create a new job.
2.If you need to pass some values to the job at runtime, create job input parameters.
3.Then add steps of the job. Every job must have at least one step. Every step executes a step function (e.g., a step can call the /system/filesystem/mkdir function to create a directory at the specified location).
4.If the last step of the job returns a result, and if you intend to use the result in other jobs, select the return type in the Execution Result section.
5.If you want to reduce the server load and the response time of your job, specify your caching preferences. Note that to be able to cache the result, you must select the return type of the job in the Execution Result section.
6.Next, add a trigger (or triggers) that will fire the job. If the job runs as a Web service, adding a trigger is not necessary.
7.After that, select an existing credential record or specify a local credential with which the job will be executed.
8.You can also define the job's queue settings to control the usage of server resources more efficiently.
9.The last step is to save the job configuration by clicking Save. FlowForce Server will validate the configured parameters and display warnings if something is wrong.
The job configuration process is closely associated with performing various calculations, computing expressions, and calling functions. For details, see the following sections:
For information about basic concepts and terms associated with job execution, see Terminology.
Windows network paths
When you create jobs, you will need to refer to file paths on the machine where FlowForce Server runs or to file paths on the network. When you refer to a Windows network path (e.g., a mapped network drive), use the Universal Naming Convention (UNC) syntax. This is necessary because drive letters are not global to the system, and each logon session is assigned its own drive letters.
The UNC has the following syntax: \\server\sharedfolder\filepath, where server refers to the server name in the network (defined by the DNS); sharedfolder refers to a label defined by the administrator (e.g., admin$ is generally the root directory of the operating system installation); filepath refers to the subdirectories below the share.