To import an application via automatic provisioning, copy the import file into the
var/data/carbon-provisioning/autoimport/incoming directory of your standalone node or of your primary node.
The application is imported by overwriting the current application version.
When you import an application on a node that contains no application yet, an initial application version is created at the valid time field specified in the
.appx file. To modify the date at which the initial version is created, add a
.properties file in the same location as the import file.
When an application is imported using automatic provisioning, the hidden spaces specified in the file:
- In the case of full import, are deleted together with all their content.
- In the case of partial import, are ignored.
If the imported application is not the node application, no merge is performed, the import is rejected
The node regularly scans this directory and automatically imports all files with an
- If the file can be imported as an application, the application is imported and the file is moved to the
done subdirectory (the file name is prefixed with the import date).
- If an error occurs during the application import, the file is moved to the
error subdirectory (the file name is prefixed with the import date).
A temporary file (named after the file but with the
.tmp extension) is created at the beginning of an import process and deleted just after the import has completed.
For more information, see Automatic process.