- Products & services Products & services
- Resources ResourcesCustomer resources
- Customer resources
- Customer support Find more information about engaging support and get help
- Services guide Find more information about working with Services teams
- Free resources Leverage our free tools and trainings
- Modernize to Identity Security Cloud Transition to the cloud for advanced capabilities and a future-ready security posture
Learning- Learning
- Identity University Get technical training to ensure a successful implementation
- SailPoint professional certifications & credentials Advance your career or validate your identity security knowledge
- SailPoint recertification program Get recertified by demonstrating ongoing learning
- Training onboarding guide Make of the most of training with our step-by-step guide
- Training FAQs Find answers to common training questions
- Community Community
- Compass
- :
- Discuss
- :
- Community Wiki
- :
- IdentityIQ Wiki
- :
- Testing many application connectors at once
- Article History
- Subscribe to RSS Feed
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Content to Moderator
Testing many application connectors at once
Testing many application connectors at once
Introduction
There may be a time where you want to test all of the connections of your applications. Doing this one-by-one in the IIQ user interface may be cumbersome if you have a lot of applications. You could do something programmatic, leveraging the IIQ API, however this requires development knowledge.
The easiest way, without any development, is to leverage the connectorDebug command in the IIQ console. Easily done in 3 simple steps, and no development is necessary!
Get application list
First you'd want to list all applications in the system, and save that to a file:
$ iiq console
> list Application > appTest.iiq
When you open appTest.iiq you'll see something like the following (your data may vary):
Name
----
Active_Directory
Composite_ERP_Global_App_Users
Composite_ERP_Global_DB
Composite_ERP_Global_Platform
ERP_Global
HR_Contractors
HR_Employees
NBA Active Directory
Oracle_DB_oasis
Procurement_System
Transform application list to console commands
Second, we'll want to modify this file to be a set of connectorDebug commands which test each connector. For reference:
> connectorDebug
usage: connectorDebug application method [methodArgs]
valid methods are test, iterate and get
examples:
connectorDebug appName test
connectorDebug appName iterate [account|group] (defaults to account)
connectorDebug appName get account|group nativeIdentity
connectorDebug appName auth username password
Our modified appTest.iiq file will look something like this, with each command on its own line:
connectorDebug "Active_Directory" test
connectorDebug "Composite_ERP_Global_App_Users" test
connectorDebug "Composite_ERP_Global_DB" test
connectorDebug "Composite_ERP_Global_Platform" test
connectorDebug "ERP_Global" test
connectorDebug "HR_Contractors" test
connectorDebug "HR_Employees" test
connectorDebug "NBA Active Directory" test
connectorDebug "Oracle_DB_oasis" test
connectorDebug "Procurement_System" test
Run console commands
Third, save the file, and source this file from the IIQ console:
> source appTest.iiq
Test Succeeded.
Test Succeeded.
Test Succeeded.
Test Succeeded.
Test Succeeded.
Test Succeeded.
Test Succeeded.
Test Succeeded.
Test Succeeded.
Test Succeeded.
Each command runs in order that it was written in the sourced appTest.iiq file.
