Symptom
System Monitoring doesn't work in SAP Solution Manager
Other terms
Solution Manager, System Monitoring, CSMREG user, S_CSMREG, CCMS.
Reason and Prerequisites
System Monitoring is available within SAP Solution Manager Release 2.1. It's required, that CCMS is activated on all satellite systems of the SAP Solution Manager, you want to monitor. This is the default setting for R/3 systems with release 4.X and higher.
Solution
1. To use System Monitoring in Solution Manager you need to have CSMREG user with appropiate authorizations in all monitored systems.
This user is used to get monitoring data from CCMS via a remote access.
The user is not created automatically.
1.1 Check existence of profile
- Check the existence of authorization profile S_CSMREG in the system. Verify that profile S_CSMREG contains the authorization objects listed below and adjust if necessary.
If S_CSMREG does not exist create a profil and assign the objects listed below.
- The authorization object S_CCM_RECV does not exist in R/3 Releases 4.6B and lower. In this case, it's not required to assign it to the
authorization object.
- Assign the second authorization object (S_RFC) to the authorization object
1.2 Create the CSMREG User.
Afterwards create CSMREG user, assign the profile you have created as described above to this user and select type COMMUNICATION for the user in the systems with release 4.6X-6.X or type CPIC in the systems with lower releases.
1.3 Required user profile with the following authorizations:
Authorization object Field Value
S_CCM_RECV (for rel. >=4.6X) ACTVT P0-P2
TABLE *
S_RFC (for all releases) RFC_TYPE FUGR
RFC_NAME SALC
SALF
SALH
SALS
SAL_CACHE_RECEIVE
/SDF/*
SYST
SCSM*
/SOMO/BP_MONI
/SOMO/MA_ANA
/SOMO/MA_DSA
URFC (for rel. >=6.20)
RFC1
THFB
DSWP_BPM
SADB
SALT
SLCA (for rel. >=4.6C)
ACTVT 16
S_RZL_ADM ACTVT 01
1.4 As of release 3.1 of SAP Solution Manager the user profile "S_CUS_CMP" must be added to the CSMREG user account !!!
2. Systems with release 3.X don't have CCMS infrastructure and therefore you have to install special CCMS agent on these systems to monitor them. The procedure how to install such agents is described in SAP Note 308061.
3. Important: Usage of CSMREG user in RFC-Connections
Use CSMREG user only in one from two RFC-Connections, which are used in the Solution Monitoring in SAP Solution Manager. The second RFC-Connection, which is used for running analysis methods should use normal dialog user.For details read the help texts in the "Setup System Monitoring" session in SAP Solution Manager.
4. If you have received a message that RFC call can't be executed while you are using System Monitoring in SAP Solution Manager, apply last Solution Tools Plug-In (ST-PI) on all monitored system (see SAP Note 116095). The missing functions modules are included in ST-PI.
System Monitoring doesn't work in SAP Solution Manager
Other terms
Solution Manager, System Monitoring, CSMREG user, S_CSMREG, CCMS.
Reason and Prerequisites
System Monitoring is available within SAP Solution Manager Release 2.1. It's required, that CCMS is activated on all satellite systems of the SAP Solution Manager, you want to monitor. This is the default setting for R/3 systems with release 4.X and higher.
Solution
1. To use System Monitoring in Solution Manager you need to have CSMREG user with appropiate authorizations in all monitored systems.
This user is used to get monitoring data from CCMS via a remote access.
The user is not created automatically.
1.1 Check existence of profile
- Check the existence of authorization profile S_CSMREG in the system. Verify that profile S_CSMREG contains the authorization objects listed below and adjust if necessary.
If S_CSMREG does not exist create a profil and assign the objects listed below.
- The authorization object S_CCM_RECV does not exist in R/3 Releases 4.6B and lower. In this case, it's not required to assign it to the
authorization object.
- Assign the second authorization object (S_RFC) to the authorization object
1.2 Create the CSMREG User.
Afterwards create CSMREG user, assign the profile you have created as described above to this user and select type COMMUNICATION for the user in the systems with release 4.6X-6.X or type CPIC in the systems with lower releases.
1.3 Required user profile with the following authorizations:
Authorization object Field Value
S_CCM_RECV (for rel. >=4.6X) ACTVT P0-P2
TABLE *
S_RFC (for all releases) RFC_TYPE FUGR
RFC_NAME SALC
SALF
SALH
SALS
SAL_CACHE_RECEIVE
/SDF/*
SYST
SCSM*
/SOMO/BP_MONI
/SOMO/MA_ANA
/SOMO/MA_DSA
URFC (for rel. >=6.20)
RFC1
THFB
DSWP_BPM
SADB
SALT
SLCA (for rel. >=4.6C)
ACTVT 16
S_RZL_ADM ACTVT 01
1.4 As of release 3.1 of SAP Solution Manager the user profile "S_CUS_CMP" must be added to the CSMREG user account !!!
2. Systems with release 3.X don't have CCMS infrastructure and therefore you have to install special CCMS agent on these systems to monitor them. The procedure how to install such agents is described in SAP Note 308061.
3. Important: Usage of CSMREG user in RFC-Connections
Use CSMREG user only in one from two RFC-Connections, which are used in the Solution Monitoring in SAP Solution Manager. The second RFC-Connection, which is used for running analysis methods should use normal dialog user.For details read the help texts in the "Setup System Monitoring" session in SAP Solution Manager.
4. If you have received a message that RFC call can't be executed while you are using System Monitoring in SAP Solution Manager, apply last Solution Tools Plug-In (ST-PI) on all monitored system (see SAP Note 116095). The missing functions modules are included in ST-PI.
Affected Releases
|
No comments:
Post a Comment