Development environment
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 to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
How should configuration move to production?
- A. Hand-edit prod
- B. Through import/deployment from source control
- C. Only via the UI
- D. It cannot move
Show answer
B. Through import/deployment from source control
Promote versioned configuration via import; never hand-edit production.