Professional Documents
Culture Documents
1.1 Update OS services and hosts entries in CEN and all monitored ABAP systems Step-by-Step 1. On solution manager add entries of the satellite systems IP and Hostname on the /etc/hosts eg. vi /etc/hosts
3. On solution Manager update services the satellite systems message servers port. eg.vi /etc/services
4. On satellite systems update services the Solution managers message server port. eg.vi /etc/services
SapmsCSO Vi services
3600/tcp
Insert I SHIFT I Shift G to go to end Paste the info Escape (disable the edit mode) :wq! To save or :q! to quit. More to know whether the entry is added or not.
1.2 Activated background dispatching in monitored ABAP systems in client 000.-done Step-by-Step 1. Call transaction RZ21. The Monitoring: Properties and Methods screen appears. 2. Choose Technical Infrastructure > Local Method Execution > Activate Background Dispatching
1.3
Required a user with specific, greatly restricted authorizations for communication between monitored systems and CEN. Created the user monitored ABAP systems Step-by-Step 1. Call transaction RZ21 in the relevant system (Business client ). 2. Choose Technical Infrastructure > Configure Central System > Create CSMREG User.
Passowrd: C1B3RR0CKS
1.4 Required super user in Monitored system for RFC connections (solution manager to relevant system 000 client) ---BIP Step-by-Step 1. Login to 000 client and call transaction SU01. 2. Create solman user in 000 client as a super user.
Data collection (transferring monitoring data to CEN) Analysis (calling analysis methods in the monitored system from CEN)
Step by-Step Create RFC Destination for ABAP and JAVA solution manager 1. login to solution manager system and call transaction sm59 Create new RFC connections, we required four RFC connections SPDSWWA_RZ20_ANALYZE SPDSWWA_RZ20_COLLECT SPDSWWJ_RZ20_ANALYZE SPDSWWJ_RZ20_COLLECT On the Techinical Settings tab page, enter the Target system information Enter the following: Target Host System No
Choose the Logon/Security tab page, and, depending on the RFC destination to be created, enter the data for the appropriate user in the Logon group box:
Choose the Logon/Security tab page, and, depending on the RFC destination to be created, enter the data for the appropriate user in the Logon group box:
1.6
Navigate to the path E:\usr\sap\SOL\DVEBMGS10\log\sapccm4x and created sapccmsr.ini file and in that specify LONGSID SOLBAGA.(LONGSID BIPBAGA) IN Linux:to create a file below command. Vi file name(sapccmsr.ini) Shift i
Path: E:\usr\sap\SPD\SYS\exe\uc\NTAMD64>sapccm4x -R pf=E:\usr\sap\SPD\SYS\profile\SPD_DVEBMGS02_swwh-scap-pp1 INFO: CCMS agent sapccm4x working directory is C:\usr\sap\SPD\DVEBMGS02\log\sapccm4x INFO: CCMS agent sapccm4x config file is C:\usr\sap\SPD\DVEBMGS02\log\sapccm4x\csmconf **** Welcome to SAP CCMS agent program sapccm4x **** Please enter the name (system ID) of the CENTRAL (!) monitoring system. SAP system ID : cso additional CENTRAL system y/[n] ? : n INFO: found ini file C:\usr\sap\SPD\DVEBMGS02\log\sapccm4x\sapccmsr.ini. INFO: CCMS version 20040229, 64 bit, multithreaded, Unicode compiled at Nov 18 2008 systemid 562 (PC with Windows NT) relno 7000 patch text patch collection 2008/4, OSS note 1129577/1136330 patchno 185 INFO Runtime:
running on SWWH-SCAP-PP1 Windows NT 5.2 3790 Service Pack 2 4x AMD64 Le vel 6 (Mod 23 Step 10) running with profile E:\usr\sap\SPD\SYS\profile\SPD_DVEBMGS02_swwh-scappp1 INFO profile parameters: alert/MONI_SEGM_SIZE = 60000000 alert/TRACE =1 SAPSYSTEM = 02 SAPSYSTEMNAME = SPD SAPLOCALHOST = swwh-scap-pp1 DIR_CCMS = C:\usr\sap\CCMS DIR_LOGGING = C:\usr\sap\SPD\DVEBMGS02\log DIR_PERF = C:\usr\sap\PRFCLOG INFO: pid 5436
INFO: Attached to Shared Memory Key 13 (size 60211232), no pool used INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application s erver swwh-scap-pp1_SPD_02, created with version CCMS version 20040229, 64 bit m ultithreaded, compiled at Nov 18 2008, kernel 7000_20050900_185, platform 562 (PC with Windows NT)] segment status ENABLED segment started at Wed Aug 05 02:33:33 2009 segment version 20040229 **************************************************** ********************** CSO ********************** **************************************************** Please enter the logon info for an admin user of the central monitoring system [CSO]. The user should have system administrator privileges client [000] : 100 user : sapagent language [EN] : EN hostname of CSO message server : cbrcsoascs00 use Load Balancing n/[y] ? :n hostname of application server [cbrcsoascs00] :
system number (00 - 98) : 02 (solman system no) [optional] route string : trace level [0] : please enter password for [CSO:100:sapagent]: ********** Try to connect ... INFO: [CSO:100:SAPAGENT] connected to CSO, host cbrcsoascs00, System Nr. 02, tra ceflag [ ] INFO: CSO release is 700 , (kernel release 700 ) This program will act as registered RFC server lateron. Please enter the info for a gateway of monitoring system CSO gateway info: host: [cbrcsoascs00] service: [sapgw02] Gateway info ok n/[y] ? :y
**** CCMS agent sapccm4x: RFC client functionality **** This CCMS agent program sapccm4x is able to actively report alert data into the monitoring system [CSO]. To enable this feature, you have to setup the user CSMREG in [CSO]. (refer to SAP Online-help, search for 'CSMREG'). Alternatively use any user in [CSO] that has at least authorization ). to call per RFC function groups SALC, SALF, SALH, SALS, SAL_CACHE_RECEIVE, SCSMBK_DATA_OUT, SCSMBK_RECONCILE, SCSM_CEN_TOOL_MAIN, SYST, RFC1 After entering the RFC logon info for the user, the password will be stored here on this machine in a Secure Storage. client [000] : 100 user [CSMREG] : language [EN] : hostname of CSO message server [cbrcsoascs00] : use Load Balancing [n]/y ? : hostname of application server [cbrcsoascs00] : system number (00 - 98) [02] : [optional] route string : trace level [0] :
please enter password for [CSO:100:CSMREG]: ********** Try to connect ... INFO: [CSO:100:CSMREG] connected to CSO, host cbrcsoascs00, System Nr. 02, trace flag [ ] INFO: CSO release is 700 , (kernel release 700 ), CCMS version 20040229 INFO: RFC logon info for [CSO:100:CSMREG] can be updated at any time with -R opt ion: sapccm4x -R <params> INFO: Updated saprfc.ini in agent work directory C:\usr\sap\SPD\DVEBMGS02\log\sa pccm4x INFO: LongSid SPDSWWA set in sapccmsr.ini INFO: Connected to CSO, CCMS version in ABAP: 20040229 [optional] monitored system SPDSWWA belongs to system group INFO: handling destination SAPCCM4X.SWWH-SCAP-PP1.02 INFO: successfully registered at CSO INFO: trying to register service SAPCCM4X.02 at Windows Service Control Manager starttype of service: manual/[auto] : auto DomainName\UserName or [<LocalSystem account>] : SWW(Computer name)\SAPServiceSPD(baecsdev01\SAPServiceSOL) password (SAP login Password) : **********INFO sapccm4x is no longer running INFO or file was deleted. INFO: trying to start Windows service SAPCCM4X.02 ... Windows service SAPCCM4X.02 has been started. INFO: The following service is registered and started: SAPCCM4X.02 (command ["E:\usr\sap\SPD\SYS\exe\uc\NTAMD64\sapccm4x.exe" -Serv ice pf=E:\usr\sap\SPD\SYS\profile\SPD_DVEBMGS02_swwh-scap-pp1] user [SWW\SAPSe rviceSPD]) INFO: Updated config file C:\usr\sap\SPD\DVEBMGS02\log\sapccm4x\csmconf. EXITING with code 0 :
1.7 Installing sapccmsr on a Java Instance (Double-Stack System) Procedure 1. Log on to the host of J2EE Engine of the system as <SID>adm. Copy the CSMCONF path specified (E:\usr\sap\QWD\DVEBMGS00\log\sapccm4x) start file to the following directory Microsoft Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. No.>\sapccmsrMicrosoft Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. No.>\sapccmsr Step by-Step 1. login to visual administrator 2. Go to Dispatcher Services Monitoring
2.
Dispatcher --services
Start transaction RZ21 in the central monitoring system (solution manager system), and choose the menu path Technical Infrastructure Availability Monitoring Configure CCMSPING Monitoring