Ciop-appcheck » History » Version 3
Herve Caumont, 2013-09-20 23:39
| 1 | 3 | Herve Caumont | h1. ciop-appcheck CLI reference |
|---|---|---|---|
| 2 | |||
| 3 | Perform a completeness check of an application template. |
||
| 4 | The application template is defined as a disk space with a structure of directories and files following a set of template rules. |
||
| 5 | Applications must conform to this template in order to integrate correctly as a processing workflow in Cluster mode. Moreover, an application workflow must be defined as a directed acyclic graph (DAG). |
||
| 6 | |||
| 7 | h2. Name |
||
| 8 | |||
| 9 | ciop-appcheck - checks the validity of the application descriptor file (application.xml) |
||
| 10 | |||
| 11 | h2. Synopsys |
||
| 12 | |||
| 13 | <pre> |
||
| 14 | ciop-appcheck [options] |
||
| 15 | </pre> |
||
| 16 | |||
| 17 | h2. Description |
||
| 18 | |||
| 19 | ciop-appcheck checks the validity of the application descriptor file (application.xml) against the XSD schema. |
||
| 20 | |||
| 21 | The following options are available |
||
| 22 | |||
| 23 | > -f file |
||
| 24 | application descriptor file |
||
| 25 | allows providing a application description file instead of ${_CIOP_APPLICATION_PATH}/application.xml |
||
| 26 | |||
| 27 | h2. Exit status |
||
| 28 | |||
| 29 | The ciop-appcheck returns are: |
||
| 30 | |||
| 31 | 0 the application descriptor file check is successful |
||
| 32 | 1 the application descriptor file is not found |
||
| 33 | |||
| 34 | *See man page for range and list operators.* |
||
| 35 | |||
| 36 | h2. Examples |
||
| 37 | |||
| 38 | Example 1. Check the validity of the application descriptor file in its default location (${_CIOP_APPLICATION_PATH}/application.xml) |
||
| 39 | <pre> |
||
| 40 | ciop-appcheck |
||
| 41 | </pre> |
||
| 42 | |||
| 43 | Example 2. Check the validity of an application descriptor file |
||
| 44 | <pre> |
||
| 45 | ciop-appcheck -f /tmp/test.xml |
||
| 46 | </pre> |
||
| 47 | |||
| 48 | h2. See also |
||
| 49 | |||
| 50 | ciop-package |