No. SailPoint XML objects must be imported through IdentityIQ ' s supported object-import mechanisms, not inserted into IdentityIQ by using a SQL database-management utility.

IdentityIQ XML represents application-level SailPoint objects such as Rules, Workflows, Applications, TaskDefinitions, EmailTemplates, Bundles, Policies, and configuration objects. Importing these objects through IdentityIQ ensures that the XML is parsed according to the SailPoint object model and that object identifiers, references, persistence behavior, and associated processing are handled by the IdentityIQ application layer.

SailPoint officially supports importing files through Global Settings > Import From File and also supports XML import through the IdentityIQ console using the console import functionality. The existing bank already contains the latter approach as a valid proposition.

Direct SQL insertion bypasses the application/object persistence layer and risks creating malformed records, missing relationships, inconsistent identifiers, or cache inconsistencies. WEB-INF/database and database-management tools are used for database schemas/scripts, not for treating SailPoint object XML as ordinary database rows.

References/topics: IdentityIQ Engineer — XML import, Import From File, IIQ console, SailPointObject persistence, configuration migration.

=======