| Note |
|---|
This jobtype was added in Qube v6.4-2. This jobtype requires Python to AppFinder jobs require that Python be installed on the each executing worker. |
What are they, and what do they do?
These jobs differ from the standard SimpleCmd cmdline- and cmdrange-based jobs in that they will "find" a particular version of a 3rd-party application on the worker when the job runs. This has several benefits:
- the The submitting user is not required to know that application's installation path on the remote worker.
- since Since the application does not include a hard-coded path to the 3rd-party application, the job is able to run across machines of differing operating systems at the same time.
| Warning |
|---|
The appFinder jobs do not perform a "best match" for version number; . For example, if AfterEffects CS5.5 is specified, but not installed, it will not use look for CS6 if CS5.5 is not installed. A . Instead, a warning message will appear in the job logs, and the job instance will be restarted on another worker. |
...
- AfterEffects (all versions)
- Cinema4D (R14 and later)
- Maya BatchRender
How do they work?
...
When the job is submitted, the command line contains a "application template" that looks like __XYZ__ The XYZ portion between the double-underscores specifies which application to run. CurrentlyCurrently, the following application templates are supported, being as specified in the API library file $QBDIR/api/python/qb/backend/appDefaultPaths.py
...
The job's package dictionary will contain an appVersion python tuple value tuple which specifies what version of that application to search for. So if the command-line contains an __AE__ application template, and the package's appVersion is the tuple (6,), then AfterEffects CS6 will be used on the worker. To specify CS5.5, the appVersion would be set to (5,5).
...
If a suitable application installlation installation is found on the worker, the application template in the command-line is replaced with the path to the application's executable. Something like the following should appear in the jobs' STDERR logs:
...
- Replace the application template __XYZ__ with the full path to the executable on the worker (not recommended)
- Define your own application template in the worker's worker_path_map, and use that application template in the "executable" field in the job submission UI. NOTE NOTE: this approach also requires that you set the 'convert_path' job flag in the submission UI's "Advanced Job Control" section.
...
For example, to implement approach 2 for a non-default installation of AfterEffects CS6, you could decide to use an application template of __AE6__. Then, define this value in the worker's worker_path_map value (which can be managed via the central worker configuration file qbwork.conf).
...