1. Request Source
Request Source – HR
Request are created from Sucess Factor – Joiners / Leavers / Movers
When to Consider?
- HR system is SF- not supported for Other HR system- Even SAP HR- PA30
- Employee Central is activated and Role Mapping- Job Code Mapping is Clean & Well Defined
Request Source – AC
- Request are created from Access Control – ARM
When to Consider?
- Operational Access Request is already in place.
- Requirement only to provisioning cloud applications- Like Ariba, SF, Concur, Field Glass, SAC and so on.
Request Source – IAG
- Request are created directly from IAG.
When to Consider?
- Simple Workflows in place- No Custom Stages possible- only 4 stages are supported.
- Approvers needs to be defined in IAS system with relevant user groups in place.
Request Source- Custom
- Request are created through IAG API Sources- From Custom Apps
When to Consider?
- Request Engine is custom field- Like Service Now/ Custom Web/ UI5 Applications
- IAG API licenses are available and workflows are defined and handled in custom applications / IAG based on requirements.
2. Integration Options
- Cloud to Cloud
- Cloud to On-Prim
- On-Prim to Cloud
Cloud to Cloud
- IAG Uses BTP & IPS
- IPS Proxy is to establish a communication between Cloud Applications
Steps-
- Set up BTP Connections
- Set up IPS Proxy Settings
- Setup OAuth in Destination
Cloud to On-Prim
IAG Uses BTP Cloud Connector destination options to connect with On-Prim Application
Steps-
- Set up BTP Connections
- Setup Cloud Connector in On-Prim landscape
On-Prim to Cloud
On-Prim Applications calls IAG via API Service
Steps-
- Set up BTP Connections
- Setup Cloud Connector and OData to establish.
Conclusion:
IAG is a great asset for any company, it becomes a true success only when we implement it right and that’s where we help using my vast experience in consulting.