Import Task
Please see the Full Tasks Documentation for details of how to call the WebSphereConfigPropertiesImportTask task from your orchestration file.
We hope you find this article useful when you're using this plugin for application release automation.
This task loads properties from a previously exported WebSphere Config properties file. This file is a template specified by the exportFile.
Properties file loading and templates
Absolute Path
You may specify an absolute path to the properties file template to import on the target server using only the exportFile resource. Generally, this mechanism should not be used as it is not portable across environments.
Path relative to archiveRoot and data dictionary
You may specify a path relative to the archiveRoot for the exportFile resource by using the $ARCHIVE_ROOT built-in variable. In this scenario you should use the exportFile as a template, and use the environment specific data dictionary to specify environment specific values.
If your target environments will need to use two or more templates (where for example production environments are significantly different from development/test), this can be achieved by using an exportFile resource that is itself a data dictionary item. this data dictionary item can then reference a different template file relative path for each target environment.