Development environment in SailPoint Development

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.

Practice challenge

+0 XPStreak ×0

Question 1 of 1

How should configuration move to production?

Frequently asked questions

What does the term Development Environment refer to in SailPoint?

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

Where do rules or workflows touch Development Environment?

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.

What is worth remembering about Development Environment in practice?

Versioning configuration is what makes changes reviewable and reversible across environments.

Want this with a live instructor and a lab tenant?

SailPoint Developer training →