Description

This class exports profiles in formats .pak and .xml in a specified folder. As input from the profile, the class expects a profile ID or a profile name per line (will always be interpreted as ID first). The class uses the input file of the profile as input, which might, for example be the result of a database query in the input agent (see example profile). So if you use this class, the profile does not have to have a mapping.

Exported XML files cannot be re-imported as profiles (.pak files can) and are only used for documentation or profile comparison (diff).

Note: With the help of this class, it is possible to implement automated profile exports as backup.

Parameters

The only parameter (in field "Additional parameters") is the path to the folder in which the profiles should be exported.

Example

If the above input and the parameter ./temp/export/profiles/ are used, the respective .pak and .xml files of the two profile are saved in folder ./temp/export/profiles/.

Example profile: Profile-Custom_response_ExportProfiles.pak

In this example, all existing profile IDs are determined via a database query and thus all profiles are exported.

Note: The SQL in phase 1 is suitable for a MySQL database. If you are using a different database, you may need to slightly adjust the syntax accordingly. For example, for an Oracle database, you must remove the semicolon (;) at the end.