IT CanvassTalk to an advisor
Development · LessonReviewed by Neelima, SailPoint Architect · Updated · Published · IdentityIQ 8.4 · all levels

SailPoint Development environment

Setting up a SailPoint IdentityIQ development environment: local instances, IDE, source control and object export/import.

Quick answer

Setting up a SailPoint IdentityIQ development environment: local instances, IDE, source control and object export/import.

Key takeaways
  • Build on a non-production instance
  • XML/Java editor plus iiq console and debug pages
  • Export objects to Git for versioning
  • Promote via import, never hand-edit prod

A dev instance

Development starts with a non-production IdentityIQ instance where you can safely build applications, rules and workflows without affecting live identities.

IDE and tooling

Rules and workflows are XML and BeanShell, so a good XML/Java editor plus the IdentityIQ console (iiq console) and debug pages form the core toolset.

Source control

Export objects to XML and keep them in Git. Versioning configuration is what makes changes reviewable and reversible across environments.

Promotion

Move configuration between dev, test and prod with the deployment/import process, not by hand-editing production.

Want this with a live instructor and a lab tenant?
SailPoint Developer training →
Already working on SailPoint and stuck on a live ticket?Get an expert SailPoint developer on screen-share to finish your daily tasks with you. Deliver on time, protect your reputation and your job. Monthly support only, no task-wise plans.Task assigned · no idea where to startStill stuck · your job on the lineExpert joins your screenDelivered on timeExplore On Job Support