Configuration properties files let an administrator extract the configuration of selected objects with AdminTask.extractConfigProperties, edit or reuse the resulting file, and apply it elsewhere with applyConfigProperties. A properties file extracted in the default form includes data that is tied to the source cell, such as node names, server names, and unique identifiers, so applying it to a different cell can fail or misconfigure objects. To produce a file that can be reused across cells, the extraction must be run with the portable option, which removes or generalises the cell-specific values. The name of that option is PortablePropertiesFile, so option D is correct.
Options A, B, and C are plausible-sounding names but are not valid option names for this task. The wording "cross cell" in options A and B reflects the intended use but does not correspond to anything the command accepts, and "PortableFile" in option C omits the properties designation that identifies the file type.
When moving the EJB timer configuration or scheduler settings to other cells, an administrator should extract with the portable option, check the generated file for references that still point to resources that do not exist in the target, and then apply it with the matching apply task. A configuration review after applying confirms that scheduler definitions took effect.
[Reference: Configuration properties files; extractConfigProperties and applyConfigProperties; Portable properties files; Scheduler configuration.]
Submit