Checklists - Enterprise role management (Role Expert)

Pre-Implementation Checklist

-> Role Expert installation contains two parts:

1) Role Expert Java Front End Package;

2) Role Expert 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

-> Login to RE as the Admin user. You should see two tabs: Role Expert and Configuration.

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

1. Make sure you can see actions as per the screenshot below.

2. Make sure you can see data in Miscellaneous section as per the screenshot below.

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

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

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

systems.

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

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

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

9. Run transaction SE37.

10. Search function module /VIRSA/*

11. Confirm RE BAPIs exist in the system.

12. Confirm Initial Data Load in RE.

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

14. Validate that RE has been configured for CC by providing the appropriate URI in the Miscellaneous option of the Configuration tab for Risk Analysis.

15. Validate that RE has been configured for AE by providing the appropriate URI in

the Miscellaneous option of the Configuration tab for starting workflows.

16. 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.