Checklists - Compliant user provisioning (Access Enforcer)

Pre-Installation Checklist

-> Access Enforcer installation contains two parts:

1) Access Enforcer Java Front End Package;

2) Access Controls RTA (Real Time Agent).

-> It is imperative to make sure that all the pre-requisites are satisfied before beginning the installation process.

-> Download the Java front end package as well as the Real-Time Agents (RTA) from the SAP Service Marketplace for the appropriate SAP backend R/3 or mySAP ERP systems. For further details, please refer to the Product Availability Matrix (PAM) located on SAP Service Marketplace. Please note that the Access Controls RTA needs to be only installed if it has not been already installed with another Access Controls module (e.g. Compliance Calibrator).

-> Install the non-HR RTA on the backend SAP R/3 or mySAP ERP systems if the RTA is already not installed.

-> Install the HR RTA if there is an HR component in the system (Check in SPAM transaction in the ABAP stack for the HR component) if the RTA is already not installed.

-> Deploy all the files as per the installation guide and refer SAP Notes 723909 and 723562.

Post-Installation Checklist

-> Validate that the standard Virsa roles have been loaded and assigned in the UME (NetWeaver only)

-> Login to AE as the Admin user and you should see all three tabs: Access Enforcer, Informer, and Configuration.

-> Verify that the initial data upload has been successfully performed in AE by following the steps below:

1. Make sure that you are able to see all the pre-defined request types as per the screenshot below.

2. Identify the landscape and the number of systems where provisioning will occur.

Each system should meet the minimum hardware and software requirements.

(Please refer to the Installation guide of AE for minimum hardware & software requirements.)

3. Identify the system to be used for user authentication.

4. Validate that Virsa Real Time Agent BAPIs have been transported to the backend systems.

5. If using CC4.0, CC should be installed on each system (RTA). If using CC5.x, CC should be installed on same WAS system (NetWeaver system).

6. Confirm with BASIS that the Virsa AE RTA transports were successfully imported with no errors (Code 8 represents an error, Code 4 represents a warning; 8=Bad 4=Not a problem).

7. Validate that the Virsa Function Modules of the RTA exist in the backend systems.

8. Run transaction SE37.

9. Search function module /virsa/*

10. Confirm AE BAPIs exist in the system.

11. Confirm the Initial Data Load in AE.

12. Click the Configuration tab.

13. Validate that standard Virsa request types exist.

14. Create a connector to an R/3 system and test the connection.

15. Validate that the RTAs are operational:

16. Import one role from the R/3 system to confirm that the RTA is operating successfully.

17. Validate that AE has been configured for CC by providing the appropriate web services URI (Universal Resource Indicator) for Risk Analysis.

18. You can find the web services URIs in the Web Services Navigator link: http://name>:/index.html. Select the appropriate web service, then select the Document option. Finally, copy the URI under the WSDL heading.