Plugin XML Artifacts

Any IdentityIQ objects that are required as part of a plugin need to be represented in XML artifacts. This could be something as small as a single new SPRight object or a complex workflow or rule. The mechanism that is used for importing these artifacts during installation is the same as any IdentityIQ object import, so the normal import actions are also available, merge, include, execute, logConfig.

Development of these XML artifacts can be done directly in the build folder, or in the IdentityIQ user interface and either exported using the console or copy and pasted from debug into the build.

When developing in the user interface and then migrating to your build folder using cut and paste, you must remove the id attribute assigned by Hibernate and any other hibernate ID value references. For this reason, it is preferable to export the artifacts using the IdentityIQ console command ./iiq export -clean.

Everything in the import folder is imported The objects can be separated into individual files, or combined into a single file. When a plugin is uninstalled, the XML artifacts that were imported remain in the IdentityIQ database, but the .zip archive from which the plugin files was loaded, is removed from the spt_file_bucket and spt_persisted_file tables.