on ‎2019 May 29 8:13 PM
When using centralized EAM in GRC how do you setup the GRC environment to use EAM for itself?
Also, what are the options for users to have access to EAM if GRC is down for a centralized environment.
Request clarification before answering.
Hi Myra,
When using centralized EAM in GRC how do you setup the GRC environment to use EAM for itself?
You need to create connector for your GRC system and then maintain all associated connector setup in the same way as how you do for other plug-in systems (e.g. ECC, S4HANA etc).
All remaining steps like creating FF IDs in GRC, setting up owners n controllers for your GRC FF IDs, assignments of GRC FF IDs to users etc. need to be done and then your users can access GRC FF IDs through transaction GRAC_EAM.
Also, what are the options for users to have access to EAM if GRC is down for a centralized environment.
This is a very common question i hear from the clients. Generally production system will have High Availability to handle both planned and unplanned down times however if the whole system goes down I feel that is a bigger problem to be solved immediately whereas EAM is just another application level functionality out of lot of other functionalities provided by GRC.
To answer your query, Generally when EAM module is being setup I will always prefer De-centralized mode because it supports both Centralized and De-Centralized design. In the event, GRC system is down, your support team can login to Firefighter IDs in the plug-in system instead of accessing through GRC.
Regards,
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 17 | |
| 7 | |
| 7 | |
| 6 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.