Objects' XML representations can be extracted from IdentityIQ through the IIQ console using the export and checkout commands. The export command writes all objects of one or more types to a single XML file. The checkout command writes a single named object to an XML file.
Frequently, customers want to get all objects of a given type out of the system at once but need them all in separate files (e.g. to store them separately in a source code repository). Though there is no built in console command that does bulk exports into separate files, the attached Perl script can take the output from an export command and parse it into separate files per object.
How to use this script:
Download the script to the filesystem where IdentityIQ is installed.
Use the export command to export all objects of a given type from the console. Note: This script only parses export files that were created with the -clean option (ID values stripped).
Run this script, providing the export filename and the target directory name. (When no target directory is specified, split files will be written to a subdirectory of the current directory called splitOut.)
I encountered an issue when using the tool which could be tracked down to "unpretty" XML - the tool relies on the XML being formatted in a specific way.
Aftter using the pretty print functionality (with linebreaks!) of the Notepad++ XML Tools Plugin, everything went smoothly.
I found an issue where the exported <sailpoint> tags are getting cut off. A good example is the OOTB ObjectConfig object for Link. Even though this isn't a commonly managed object, it breaks the <sailpoint> tags and will break the WAR building process.
The issues when the names contain things like single quotation marks or certain other characters, can be fixed by making the following modifications to the code:
Search for the part where the script assigns a value to: $objectNameHy.
A few lines above that, are 2 regular expressions that define what should be used for the name. Edit the regular expressions to include the characters that are causing the errors.
And below the assignment are substitutions that replace things like "&" with "and". Add the appropriate substitutions here to create a normal filename.
By the way: if you want separate xml files, you could also use the SSD XML Exporter. Here's a link to the 3.1 version:
Just now tried the Object Exporter Version 3.0 and it did worked successfully . But Im not still understanding when using the attached script, in the cmd, it is still showing the $ symbol as unknown command. Tried to remove the dollar and executed the remaining command and still showing the result as unknown command.
