ExportProfiles

Description

The ExportProfiles class exports profiles in .pak and .xml format to a defined directory. Per line, the class expects a profile ID or a profile name. It always interprets each line as an ID first. The input comes from the input file. This is either a file directly or, for example, a database query in the input agent (see example profile). A profile that uses this class therefore does not need an active mapping.

You cannot re-import exported .xml files as profiles. You can re-import .pak files. The .xml files are only for documentation or a profile comparison (diff).

NOTE You can use this class to create automated profile exports as a backup, for example.

Parameters

As the only parameter, enter the path of the target directory. Enter it in the Additional parameters field.

Example

-1301252d:150cc436e03:2d4a.63f3351b93729ea1:-1301252d:150cc4360e1:-7ff8
XML_ORDERS

With this input and the parameter ./temp/export/profiles/, the class creates the respective .pak and .xml files for both profiles. They are located in the ./temp/export/profiles/ directory.

Example profile: Profile-Custom_response_ExportProfiles.pak

In the example profile, a database query determines all existing profile IDs. The class thus exports all profiles.

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