{{indexmenu_n>1}} ====== 1. Prerequisites ====== ===== Hardware ===== The hardware requirements directly depends on the number of SAP systems that you want to monitor.​ ^ SAP systems ^ CPU ^ Application Memory ^ Disk ^ | <10 | 2 Cores | 4 GB | 30 GB | | <50 | 4 Cores | 8 GB | 30 GB | | <100 | 4 Cores | 10 GB | 60 GB | | >100 | 4 Cores | 12 GB | 60 GB | ​ ​ ===== Software ===== **Supported OS:** * **Windows** server 2012 / 2016 * **Linux** CentOS/SUSE/RedHat (7 or above) **systemctl** must be available for a smooth installation **Mandatory software:** * Java JRE v1.8 **64 bits** * SAP JCO drivers for SAP NetWeaver systems * SAP HANA drivers for HANA systems ===== Network ===== Network routes must be open between Pro.Monitor server and the monitored SAP systems. Below table indicates the standard ports to open. ^ SAP system type ^ Ports to open (defaults) ^ |SAP NetWeaver |36XX (Message server) \\ 33XX (App. Server) \\ 5XX13 \\ 5XX14 \\ 5XX00 | |SAP HANA |3XX13 \\ 3XX15 | |SAP BusinessObjects |64XX XX: System number | ===== Users and authorizations ===== **NetWeaver - ABAP:** * Pro.Monitor uses a **Communications data** user associated with the [[https://agentil.box.com/s/6w05lw2cfwju3z1wn30rnvdgbzehdkn1|provided authorization profile]]\\ * In most cases, user can be created in client 000. But sometimes access to target client must be necessary as well. **NetWeaver - SAPControl:** * Pro.Monitor uses SAPControl web services to collect information on the system. * The access to these services can be either without authentication, or controlled by using an OS user similar than [SID]adm, see [[https://launchpad.support.sap.com/#/notes/ 927637|Note 927637]] * Look for the section describing the use of **service/protectedwebmethods**, make sure to allow the access of all **Getter/Reader** services **HANA:** * SQL user associated with MONITORING role​ **BusinessObjects:** ​ * User access to CMS repository and CMC portal