Application Configuration Packages (ACP:s) are possible to export from one environment and install in another environment. A package is exported from the Application Configuration Package window using the option Export. Read more about the export options in Export an Application Configuration Package.
An ACP can be imported manually or using IFS installer. Manual import of an ACP is described in Install Application Configuration Packages.
To use IFS Installer to install an ACP, the exported ACP must be put in a file structure in a delivery folder. If exporting as a zip, the files needs to be extracted from the zip archive before added to the delivery.
IFS Installer will install all ACP:s that are included in the delivery in the server/appconfig folder. A delivery can look like the example below:
The server folder is the same folder where for example profiles and lobby also are located. The appconfig folder can contain zero, one or many package files and the Items folder contains the actual configuration items for the packages and/or configuration items that are not connected to a package.
The example above shows two packages "BookPkg" and "MediaExtPkg". Normally the package is complete, that is all configuration items are included. However if there are changes only to some configuration items, it is possible to make a delivery only containing the changed items. If the packages are dependent of each other this will be resolved in the installation process. That is "BookPkg" may contain configurations items that are dependent on configuration items in "MediaExtPkg" and the other way around. Both packages must be imported at the same time to resolve this.
Running IFS Installer installing a delivery will automatically detect if there are any ACPs or single configuration items to install. Refer to IFS Installer for the installation options. The result of the ACP installation is logged to file located in the IFS Installer log output directory, <instance>/logs/import_application_configurations_<date>.log The installation is done if the validation step is successful without errors.
If the configurations are stored in the version control system and using IFS Auto Builder to install ACP:s the files needs to be located in a component just as other source code. ACP:s are typically not bound to any standard component and can therefore be put in a separate component like for example "config". When the files are extracted in the build process all ACP:s are put to the same build directory regardless of component.
The version control system file location would then be config/server/appconfig/ , where "config" is an example and server/appconfig/ is the required location.