Checklists - Risk analysis and remediation (Compliance Calibrator)

Pre-Installation Checklist

-> Compliance Calibrator installation contains two parts:

1) Compliance Calibrator Java Front End Package;

2) Access Controls RTA (Real Time Agent).

-> It is imperative to make sure that all the pre-requisites mentioned i

are satisfied before beginning the installation process.

-> Download the Java front end package as well as the Real-Time Agents 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.

-> Install the HR RTA if there is an HR component in the system (Check the SPAM transaction in the ABAP stack for the HR component.) .The screenshot below shows the imported VIRSA HR and VIRSA NHR RTA s via transaction SPAM.

-> Please refer the installation guide and SAP Notes 723909, 70228, 179116, 458731, which are related to the installation of Compliance Calibrator

Post-Installation Checklist

-> Confirm the deployment of CC 5.2 files, which include the NetWeaver database, J2EE Library and UME Actions and Permissions on SAP WAS 6.40 or above

-> Confirm the installation of CC 5.2 RTA on the target system. This includes the installation of both HR and non-HR RTAs for the SAP-HR system and only the non-HR RTA for SAP systems without the HR component.

-> Confirm the configuration of SLD and JCo destinations to connect to a particular backend system and perform risk analysis for that system. Please refer section 3.5 of this guide which discusses the procedure of configuring SLD and JCo Destinations.

-> Confirm the configuration of the Internet Graphics Server (IGS). (Please refer to the Installation guide for the configuration of IGS for UNIX and Windows systems for both the Java stack and ABAP stack.)

-> Create a role in the UME for all CC actions (all actions of the pattern com.virsa.cc.*).

-> Confirm the status of NetWeaver J2EE Server as Running from

http://:500/index.html

-> Confirm the status of the Data Supplier Bridge as Running from http://:500/sld/index.html

(NetWeaver SLD home)> Technical Landscape> Administration>Data Supplier Bridge.

-> Test the status of the IGS as Running from

http://:480/

-> Test the SLD Connection from

http://:500/sld/index.html

(NetWeaver Home)> Web Dynpro > Content Administrator.

-> Test each of the JCo Connections from

http://:500/index.html

(NetWeaver Home)> Web Dynpro > Content Administrator > Maintain JCo Destinations.

-> Test the status of the Background job daemon as Running from

http://:500/virsa/CCBgStatus.jsp

If the Status of Background Job Daemon is not running restart the J2EE engine and bgear and confirm the status of the Daemon as Running.

-> Test the status of the Analysis Daemon as Running from

http://:500/virsa/CCADStatus.jsp

-> Validate a connector in Compliance Calibrator by logging on to the system. Go to Configuration Tab> Connectors> Search.

-> Validate the Master User Source by logging on to the system. Go to Configuration Tab> User Master Data.

-> Verify the IGS URL in the Visual Administrator tool for NetWeaver.