In the Windows operating
environment, it is possible to save a DataFlux Data Management Server
job to a directory, and then not be able to see that job in that directory.
To resolve this issue, save your jobs in a location that does not
use mapped drives. A Windows service is not able to access mapped
drives, even if the service is started under a user account that maps
those drives.
DataFlux Data Management Server cannot run a remote job
or service whose location is specified with a mapped drive letter,
such as Z:\path\remote_job.ddf. The
server runs as a service under a SYSTEM account and no mapped drives
are available to such an account. Use a UNC path to specify the location
of a remote job or service, such as \\ServerHostName.MyDomain.com\path\remote_job.ddf.
The following restrictions
apply to the name of a job that will be deployed to DataFlux Data
Management Server. You should follow these restrictions for all jobs.
A job name can contain any alpha-numeric characters, white spaces,
and any characters from the following list:
The maximum length of
job names is 8,192 bytes. DataFlux Data Management Server will not
upload, list, or run a job name with characters other than those cited
above.
In UNIX or Linux, to
run a shell command in a job, use the execute() function, as shown
in the following examples. To run the command directly:
execute("/bin/chmod", "777", "file.txt")To
run a command through a shell:
execute("/bin/sh", "-c", "chmod 777 file.txt")The
preceding examples return the host authorizations for a text file.