Quick Reference Guide - Access Control SAP v5.2 - GRC Applications Integration Documentation
Quick Reference Guide - Access Control SAP v5.2 - GRC Applications Integration Documentation
Prerequisite:
Page 1 of 33
3. Remote Function Call (RFC) User This user is used to communicate between the front end Java application(s) and backend target system(s). o Create the RFC user with User Type as Communications Data in the target system(s) and assign administrative authorizations for all application(s). o Assign appropriate RFC authorization.
4. The following Role Attributes Master Data must be defined and named the same across the GRC applications (Required) o Functional Area (Functional Area ID field in RE must exactly match the Functional Area Name field in AE) o Business process (Business Process ID field in RE must exactly match the Business Process Name field in AE) o Sub Process (Sub Process ID field in RE must exactly match the Sub Process Name field in AE) GRC Applications Integration Documentation Page 2 of 33 August 14, 2007
AE Integration Configuration
Integrating CC with AE provides the ability to workflow approvals of mitigation control changes. When a user creates and/or updates a mitigation control in CC, the request is sent to AE for the appropriate mitigation control owners approval based on workflow configuration.
Page 3 of 33
Delete, Create, and Update Risk RE Request Type: RE Role Approval (RE_ROLE_APPROVAL) CC Priorities: MC_HIGH Mitigation Control MO_HIGH Mitigation Object
Page 4 of 33
Page 5 of 33
Page 6 of 33
Delete Risk
Create Risk
Page 7 of 33
Page 8 of 33
Page 9 of 33
a. Repeat Step 4 above to get Mitigation URI http:// <server>:<port>/VirsaCCMitigation5_0Service/Config1?wsdl&style=document Example : http://iwdfvm2363:51000/VirsaCCMitigation5_0Service/Config1?wsdl&style=document
b. Repeat Step 4 above to get Risk Search URI http:// <server>:<port>/VirsaCCRisk5_0Service/Config1?wsdl&style=document Example : http://iwdfvm2363:51000/VirsaCCRisk5_0Service/Config1?wsdl&style=document
Page 10 of 33
c. Repeat Step 4 above to get Org Rule Search URI http:// <server>:<port>/VirsaCCOrgRules5_3Service/Config1?wsdl&style=document Example : http://iwdfvm2363:51000/VirsaCCOrgRules5_3Service/Config1?wsdl&style=document
Page 11 of 33
Page 12 of 33
For Role Expert workflow a. RE INITIATOR Initiator for Role Expert approval workflow integration with AE. Requests for role create/update approval from RE is sent to AE via web service to trigger this initiator.
For Compliance Calibrator workflow b. For CC Users/Roles/Profiles mitigation changes CC_MITIGATION_CHANGE. Requests for mitigated users, roles, or profiles update approval from CC is sent to AE via web service to trigger this initiator.
Page 13 of 33
c.
For CC Mitigating Control changes CC_MITIGATION_INITIATOR. Requests for mitigating control create/update approval from CC is sent to AE via web service to trigger this initiator.
Page 14 of 33
d. For CC Risk changes CC_RISK CHANGE. Requests for risk create/update approval from CC is sent to AE via web service to trigger this initiator.
Page 15 of 33
For Role Expert Workflow The Custom Approver Deteminator determines approver for role approval initiated from RE. Create RE CAD with: o CAD Type = Web Service o Workflow Type = RE o URI This URI can be retrieve from repeating Step 6 above. Choose
Page 16 of 33
Select appropriate attributes for approver determination. In this example, Request Type is the only attribute selected to determine approvers. You can also select additional attributes such as Business Process to differentiate approvers for different processes, etc. Assign approvers for each Request Type
2. For CC Mitigating Control changes approver o Create CAD with CAD Type = Attribute o Workflow Type = Mitigation Control
Page 17 of 33
Select appropriate attributes for approver determination. In this example, Request Type is the only attribute selected to determine approvers. You can also select additional attributes such as Business Process to differentiate approvers for different processes, etc. Assign approvers for each Request Type
Page 18 of 33
Select appropriate attributes for approver determination. In this example, Request Type is the only attribute selected to determine approvers. You can also select additional attributes such as Business Process to differentiate approvers for different processes, etc. Assign approvers for each Request Type
Page 19 of 33
Page 20 of 33
Page 21 of 33
Page 22 of 33
Page 23 of 33
Page 24 of 33
Page 25 of 33
Page 26 of 33
14. Miscellaneous Configuration Workflow Types Configure Exit URI for all integration workflow types. All workflow Exit URIs are the same. For CC MITCTRL, MITOBJ, RISK Enter this Exit URI http://<server>:<port>/VirsaCCWFExitService5_2Service/Config1?wsdl&style=document Example: http://iwdfvm2363:51000/VirsaCCWFExitService5_2Service/Config1?wsdl&style=document For RE Enter this Exit URI http://<server>:<port>/AEWFExitServiceWS_5_2/Config1?wsdl&style=document
Example : http://iwdfvm2363:51000/AEWFExitServiceWS_5_2/Config1?wsdl&style=document
Page 27 of 33
Scroll to right hand side of screen and enter the correct User Name and Password (maintained in UME) for the Exit URI. Ensure all workflow types are Active.
CC Integration Configuration
1. Configure Workflow Options
The workflow options are set to yes to enable workflow integration with AE to provide approval workflow for risk, mitigating control, and mitigation maintenance. Workflow Service URL: http://<server>:<port>/AEWFRequestSubmissionService_5_2/Config1?wsdl&style=document Example: http://iwdfvm2363:51000/AEWFRequestSubmissionService_5_2/Config1?wsdl&style=document
Page 28 of 33
Page 29 of 33
Example Assigning the approver(s) for FINANCE group name. Assigning Cyrus Perkins as the approver for Procure to Pay business process and Vendor Maintenance sub process.
Enter FINANCE for Group Name. Click on + sign to add attributes Business Process and Sub Process.
Page 30 of 33
Click on Assign Approvers Click on + sign to add value Procure to Pay for Business Process and Vendor Maintenance for Sub Process. Click on +sign to add (via search icon) Cyrus Perkins as Approver and Alternate Approver
Page 31 of 33
Web service for CC Function integration http://<server>:<port>/VirsaCCFunction5_0Service/Config1?wsdl&style=document Example: http://iwdfvm2363:51000/VirsaCCFunction5_0Service/Config1?wsdl&style=document Web service for AE role approval workflow integration http://<server>:<port>/AEWFRequestSubmissionService_5_2/Config1?wsdl&style=document Example: http://iwdfvm2363:51000/AEWFRequestSubmissionService_5_2/Config1?wsdl&style=document Page 32 of 33
You have completed workflow integration configuration for Access Control 5.2.
Page 33 of 33