Your prepare data step could create new files with the respective info and store them to the XLT project folder to the
config subdirectory. When the master controller is executed in the next step, these files will be uploaded together with the rest of the test suite to each agent machine. Your test cases can then read the files and access the info they need.
You might as well modify existing files, such as
config/project.properties, for example by simply appending some properties.
Which way is prefered depends on the info you want to transport. If it is a list of IDs to use during the test, then separate data files would be the right choice. XLT comes with some helper classes to read data files, such as DataProvider and ExclusiveDataProvider.
If your info can be expressed using properties then I would go for appending these properties to an existing properties file. In your test cases you could use
XltProperties.getInstance().getProperty(...) to access them.
Instead of appending properties to an existing file, you could also create a new properties file, for example
info.properties in the
config subdirectory, but in this case you need to include this file in
project.properties or the test-run-specific properties file such as
test.properties. For more info on including properties files, see the user manual.