Importing entity configuration during startup
This feature can be used when you don’t want to perform account configuration manually using the interface or with
utransfer. Instead, you point the system to a file or folder containing your configuration and the import is performed when the server starts up.
Configure com.unblu.entityImport.source to point to the location of a single JSON file, ZIP file or folder produced by a
utransfer export. Upon server startup, the main account is then configured as defined in the imported JSON files.
|Pointing to a folder doesn’t work in an OpenShift environment. Some JSON files are detected twice.|
You can configure behavior in case of import errors using the property: com.unblu.entityImport.preventStartOnImportError
true: (default) Any import failure appears in the server startup logs as an
ENTITY_CONFIGURATION_IMPORT_ERRORand prevents the Collaboration Server from starting. This ensures that the server only starts if the account is configured as defined in the imported JSON files.
false: An error is logged but the server starts. In this case, there is no guarantee that the account is configured as defined in the imported JSON files.